jvrmartinns you need grasshopper, were you able to open the gh file? it's literally just generating the camera coordinates (as text) along a path that you can then bring back into enscape using the xml file. Did anyone else get that to work?
i got a bit tired of searching so I just created a simple grasshopper script that generates the code for a camera path based on a line.
it's not super clean but it did the job. i'm sure there are other similar things out there
start a random camera path
save as .xml
open that in notepad, paste in the new camera locations and vectors from grasshopper in the hilighted bit.
(you have to edit the code a little bit once you paste it in, i couldn't figure out how to add line breaks in gh)
hope this helps someone
yes seems like it, thanks
I've tested Enscape (rhino) with Quest 2 and Rift S using the same 'moderately complex' model
I tested the Quest 2 with both Air Link over a 5G wifi and the Oculus brand link cable
Using VR capable laptop - Razer Blade with RTX 2070, not the fastest GPU possible but capable.
Rift S - Totally fine, adequate frame rate, occasional small glitches on 'high' render quality when you turn your head too fast, black areas at side of screen. Overall suitable for presentations etc.
Quest 2 - link cable - Low frame rate, some jitter and feedback when not moving your head. uncomfortable. Visually fine but weird lag between movement
Quest 2 - Air link - Same result as link cable as far as I can tell.
I was hoping I could get rid of the Rift altogether since we only use it for Enscape, but seems like not yet.
Would be good to know if there's a way to improve the Quest performance with the link cable! can't seem to find any way to improve in the support docs.
hi all, just wanted to close this thread out with the fix.
There were a few objects in the file that had custom render meshes set up. (they were curved geometry that would otherwise appear faceted in enscape.) Something had happened where these seemed to be taking a really long time for enscape to process. I don't know if the custom meshes were just extremely detailed or if they got otherwise broken over time - the file had been upgraded from rhino 6 to 7, converted from meters to mm, enscape 2 to 3 etc.
The fix was just to select all and un-tick custom render meshes in the rhino properties palette to clear the custom meshes. Seems to be performing well again.
Thanks Enscape team for your help.
ok Feedback sent, I can't remember if we opted in or out to feedback. let me know if you don't get it!
I have a model that is now getting quite 'old' ie. project began in 2019 and has been through multiple versions of Enscape. Now upgraded to the latest (3.0.1)
It's moderate complexity with some big pieces of geometry as disjoint meshes in rhino - 1gb file.
There are also some NURBS elements that were exported from Revit. Also a fair few assets that were placed from earlier version of Enscape 2, etc, so it's been building up over time.
I've got a decent laptop and spinning around the Enscape model is smooth with everything turned on / full settings, even in VR.
I'm noticing that 3 actions take significant time to complete:
- Turning layers on and off in Rhino and updating the Enscape view - 2 - 5 mins
- Changing named view from the Enscape view management toolbar - 2 - 5 mins
- Rendering a view (even if it's only HD) - 5 - 10+ mins. The 'export image' progress bar stays at 0% for like 10 mins and then takes 10 seconds to actually render.
I don't remember these things taking this long in Enscape 2 with the same model.
Things I tried:
- SelBadObjects in Rhino to clean out bad geometry - a few things popped up and I deleted them and purged the file. (seemed to make a bit of an improvement.)
- Turning off everything you can't see (no change?)
- Meshing some big objects (ie. city model) (no change in Enscape but speeds up rhino)
- Hiding all Enscape assets (slight improvement maybe related to less complexity though?)
- Making sure Enscape material textures are mapped to a local file location (we use a cloud server usually) (no change?)
- Some textures were large at around 5000 x 3000px jpg - tried turning those materials off (no change?)
Can anyone suggest anything else to try here? This led to a pretty long day yesterday and I'm trying to fix before the next round of updates.
When I start Enscape from Rhino, I get a blank white screen and no visuals whatsoever. Even on a fresh model or a model that previously worked well. Using version 2.8.0 / Rhino 6 SR8.
This happened straight away after I installed the update. I assumed there would be a fix so just left it for a couple of weeks but I see nothing and read nothing about it and getting worried.
Have restored default render settings.
Thanks, let me know! im on a deadline of course, will probably now try to roll back to 2.7 in the interim. Am I missing something obvious??