8o another stupid question about camera settings - And again, I can’t figure out what to do…
I’ve realized, that SketchUp views and Enscape views are not synchronizable really in the sense of a fixed reproductive workflow.
Now I notice another mistake, which however can be founded in my own misunderstanding or just my stupidity 8o :?: :
To set a particular desired camera view, I use Sketchup. Here I use the enabled Synchronize Views so Enscape shows me (more or less) this camera view as well (as already mentioned elsewhere, this is not really recognisable and controllable within Enscape)
After I have found my desired camera within SkUp, I want this view to remain frozen in Enscape - for that I switch off Synchronize Views then.
Strangely, as soon as I switch off Synchronize Views, the Enscape Camera does not stay where it was but jumps back to any random uncontrollable and unwanted point.
What can I do to avoid this again so unnecessary, strange and wrong behavior, but freeze my desired view instead?
Just an idea (*) but if you click the camera (Create View) button on the Enscape toolbar before you switch the sync off, select that scene within SU, then you can re-launch Enscape and it will fly to that position. OR you can select the starred camera icon next to the camera (Manage Views) and tic the box next to the newly created scene: this enables you to navigate to this position from within the Enscape window via the roll-out on the right hand side of the screen.
The position the camera jumps to in Enscape is not quite random: it’s the last remembered position, probably from the last time you clicked the button.
(*I use this technique when I have to clear a glitch from Enscape)
Could be great if the last used synchronized view would be kept. Also missed at Rhino. So, the user could work on a model and the final needed view could stay constant at the Enscape output.
Thanks Micha - so well formulated and exactly what I meant with the so unnecessary and anoying camera jumping!
In the case of a SkUp view adjustment, SkUp allways should be the “view-master” and any renderer allways the “slave”,
at least until I don’t start navigating in the renderer itself … (I cannot judge whether this principle could also fit for Revit?)
Thank you Gadget for your suggestions and ideas - I have never used the “Create View” function of Enscape before (to be honest not even noticed) - so I can’t yet understand your suggestion because of my lack of understanding this - so give me some time to close up. Does this function create a corespondending SkUp-scene as well? - which could then invert the “View Master-Slave” principle? Is there any good video tutorial somewhere about how to use this feature?