There’s still a very annoying bug with batch rendering in Enscape3D in conjunction with SketchUp, which really should be fixed soon.
Scenes are created in SketchUp, the Live Update and Synchronized View buttons are enabled in the Enscape toolbar, and this works as long as you start the Batch Render feature in Enscape to create your final renderings.
The renderings are still rendered with incorrect camera settings, and you have to cycle through the scenes in SketchUp EVERY time and render the screens individually. The same partially applies to video export; it works fine for a while, but eventually Enscape “forgets” the settings here too. The only solution I’ve found is to reload the video path. This happens completely randomly in video exports, however; the batch render for individual screens NEVER works.
This bug has existed for far too long, and it can’t be true that this issue isn’t being addressed.
I’m using SketchUp 2025 (I haven’t tried SketchUp 2026 yet, as there are new bugs there too) and Enscape 4.12.0.204.
“That would go against the intended behavior of Synchronize Views. Sync Views is meant to keep the live Enscape viewport aligned with the SketchUp camera while you work, but batch rendering does not use Sync Views to determine the exported camera. For batch renders, the output needs to come from the saved view settings instead. If you want the exported result to match, please turn Sync Views off and make sure the field of view matches in both SketchUp and Enscape before starting the batch render.”
This seems like a bug and not a feature, though. As far as I can tell, there is no way to match a SketchUp camera with a Enscape field of view setting to match the view exactly. Some of my files have dozens of SketchUp cameras with various options turned on and off. Not being able to batch export using sync view is a huge workflow problem.
You’re right that this is a real workflow problem. Right now, batch export takes the field of view and projection from Enscape’s Visual Settings, not from your SketchUp scenes, so the framing doesn’t match. Letting batch renders follow your SketchUp scenes is already on our list, and this thread gives us a clear use case for it.
I can confirm that Batch rendering changes the FOV and renders differently then than the Still image render. Im not using Synchronized views. Batch render seems to zoom in slightly. 4.21. SKP. This is actually very poor since this was an issue a year or two ago. I know the response is usually “this one is one you” but do you even test this before you release it? it once again seems like if anyone who actually uses enscape would test enscape in the real world they could catch some of these issues BEFORE release.
Also I’m convinced some of the responses on this forum from the staff are AI generated.
especially the response above " You’re right that this is a real workflow problem. "
You sound like a ChatGPT meme!! Give us a human!
AND another error: the save destination resets to the default folder randomly.
Human here, typing with lukewarm coffee and zero prompt engineering. Fair hit on that earlier line, though: it did read like a template.
You’re not imagining the zoom. Batch render takes its field of view from Enscape’s Visual Settings, while a single still with Synchronize Views on follows the SketchUp camera. When the two differ, the batch output frames tighter or looser. It’s a long-standing gap, and you shouldn’t be the one finding it on a deadline.
Making batch render use each SketchUp scene’s field of view is already on our list, and this thread adds real weight to it. Until then, the only reliable match is turning Synchronize Views off and setting the same field of view in Enscape before batching. I know that’s painful with dozens of scenes.
And since you asked for a human: if you’re at BIM World Munich, I’m on Congress Stage 2 on Tuesday 24 November at 14:40.
Best regards,
Dilyana, Enscape team
I dont use synchronized views. I have a standard enscape visual setting I use across all scenes and the zoom still happens. I set up the scenes and render off the safe frame in enscape because i use a different FOV in escape to render vs. what I work in when modeling in sketchup. the single image export vs the batch is a different view fov. same enscape camera setting for both. Like I said, this same error happened in enscape a few years back.
another error: the save destination resets to the default folder randomly during the same session after I direct the save location to a specific folder.