Skip to main content
Question

Incorrect 3D model default rotation in Infield 2.0

  • February 17, 2025
  • 4 replies
  • 134 views

Forum|alt.badge.img

Hi, 

We experience that for one of our root assets the 3D model default position displays in infield 2.0, however when clicking open, the 3D model opens in a different position and rotates along the wrong axis. 

 

The same issue is occurring in CDF. 

 

I see on Slack a ticket was opened, what is the ETA on this? 

 

Regards,

Aleksander

Akerbp Data Delivery

 

 

4 replies

Hi ​@Aleksander Poverud

Thank you for your question.

We have a ticket in place to address this issue and will provide an ETA after today’s refinement meeting. However, the team currently has other ongoing priorities, but we aim to resolve this as soon as possible. We understand that this is not a critical bug blocking fundamental work, but please feel free to reach out to me directly if you need further clarification.

Kind Regards,

 

Filipe 


@Aleksander Poverud we have tried reproduce the error and concluded that this is not a bug. 

If you want the preview be the same as thumbnail, open the model → go to settings→ click on “set default camera position”. After reloading, the preview should be the same as thumbnail. 

Let me know if you have more questions :)

 

Kind Regards,

 

Filipe 

 


Forum|alt.badge.img

Hi Filipe, happy to hear from you!  

There is two issues here. 

When opening 3D models in CDF the default state is not initialized. “Set Default Camera Position” does not reset the position to that of the thumbnail, but captures a new thumbnail and axis state of the model, which is supposed to load into infield. 

However the main issue we have is not default position in CDF, but how the captured Default Camera Position is not reflected in Infield 2.0 as it should when the model is opened. The 3D model will appear in a different position and rotation than set default. 

This makes it very difficult for workers to inspect the assets. 

 

Regards,

Aleksander 


Hi Aleksander,

 

Nice hear from you as well.

After reading your clarification, I realized that this is an Infield error. It’s already reported and in their team board.

Regards,

Filipe 

 


Reply


Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings