Inconsistent camera distance

[David Kubecka]

Hello,

after a few months away from Lego I started building my custom models again, including creating BIs for this. This included upgrading to latest lpub version (2.3.12). One of the changes I noticed there was how the camera distance increases as the model gets bigger. See early and late stages of a model in the attachments. The behaviour I want is that the camera distance (or absolute size of the bricks) stays the same by default but can be changed manually (from modified step onwards).

I have a suspicion that there's some new option managing this behaviour which can be switched off somewhere but I cannot see where exactly. I went through the most promising menus and also through corresponding ldraw file but found nothing useful or suspicious.

Thanks for any help

[David Kubecka]

Here you can find the early and late stages pictures as promised above.

[Trevor Sandy]

Hello David.

This behaviour is linked to the Native renderer and was addressed in v2.3.12 rev 52. See GitHub ticket #323 for details.

Cheers,

[David Kubecka]

I've read the linked ticket and if I understand it correctly the short term solution is just about being able to set the camera distance factor for Assembly and PLI/Callout separately. What I probably want to achieve is the state (in your own words) "so each image is consistent in its size relative to the Lego Draw Unit (LDU), page size, resolution and image scale". Essentially the behaviour of LDView renderer. So is there currently any way to achieve that with the native renderer?

My ideal scenario would be to set the camera distance (or rather scale as in LDView) at the beginning and in later steps when the model gets larger either:

• decrease the scale so that whole model fits onto the page, or
• zoom in to the particular area (as discussed in my other post Zoomstep)

Do you find this scenario valid? Or do you recommend different flow when building large models?

[Trevor Sandy]

...So is there currently any way to achieve that with the native renderer?

No, not automatically. This is the functionality to be implemented for the Native renderer which will include dynamic camera distance calculation. The aim is to have all the renderers use the same interface and parameter settings to manipulate the camera globe (angles, fov, and distance).

Do you find this scenario valid?

Of course. You are describing the current behaviour of the LDView and LDGLite renderers. It only make sense to have the Native renderer behave similarly.

Cheers,