On April 5, 2024 I was the first to discover and report the aforementioned bug in the newly released Enscape 4.0. Because of this bug we were forced to stay with Enscape 3.5.6 for 4 months and couldn’t upgrade**.** Precise camera placement is of utmost importance to us, because we batch render 50-200 scenes of furniture items per 1 SKP file, and the camera groups must stay consistent. This bug prevented us from typing desired values in the fields, making our work impossible to continue.
I was reassured that this would be fixed within 2 weeks, but 2 months passed until the issue was finally addressed and seemingly fixed in 4.0.1.48.
Having upgraded to the latest version 4.0.2.11, this bug is back again, as annoying as ever (see attached video).
Typing 3rd decimals like 1.25, trying to type a negative Pitch value starting with a minus, or any whole numbers for that matter sends Enscape to a craze frenzy!
Moreover - in 3.5.6 you could type in the field, and the second you’d press TAB to shift focus to the next field, the camera would update the viewport.
Now in 4.0.2.11 it seems there’s 2 focus fields active at the same time:
Pay attention to the dashed outline in the second screenshot. This sometimes blocks the input. When you press TAB you then have to press ENTER or vice versa, to force the viewport to update the camera position.
Also this second field means you have to click TAB twice to move to the next field. Especially if you want to go back to a previous field with SHIFT+TAB, it shows the dashed lines. Then you have to press SHIFT+TAB again to land in the correct field. See in action:
This is NOT normal! When I type a value and press SHIFT+TAB to focus on the previous field, it should focus on the field and let me type. I have to press SHIFT+TAB twice to be able to type in the previous field.
Going forward seems to be fine, although you still sometimes get those dashed lines. But this changed navigation and this persisting camera bug is a nightmare.
To say that I’m frustrated would be a drastic understatement. I don’t understand why we’re paying so much money every year, for our whole 3D team to be unable to use their programs because of bugs like these. It’s been almost half a year since March. We’re deprived of using the new features of Enscape because of hindrances like these.
Fix this please!
Now I don’t know what to do, I guess we have to downgrade to 3.5.6 againn