I'm just going to add here that I've always been upset with the way that Archvision feels that they can have ownership/dominance over the only proxy file format within Revit....
I truly believe that all of this should be OPEN SOURCE, and that is the only way it can really thrive - so however Enscape can align itself with an open-ended community format where EVERYONE develops assets and adds them to a huge repository of assets - then we will.
Enscape should work towards their assets being renderable in everything, and transition all of this to a free community database. That is the only way you'll defeat Archvision.
I tend to notice my Revit consistently gets sluggish and can hang up for brief moments when I’m running Enscape, live updating or not.
Has anyone had any performance boost using two cards in their machine: one dedicated for Enscape and one dedicated for Revit? If so, what steps do you take to delegate the energy spent between the two cards?
No because these concepts only exist in Revit. For me it makes sense that these things are left to the host application which already has many tools (like view templates) to handle all these settings efficiently. It would also be a gigantic development effort.
The only 2 settings that I'd like to be governed by Enscape (in an ideal world) are the camera positions and sun position. You would still select a revit view from which Enscape should get the geometry, but camera positions and sun positions would be managed by Enscape. This is similar to how many other applications do this (as mentioned by renderwiz). It's interesting that you can re-use a revit view as an Enscape view, but it's kind of limiting that you NEED a revit view if you want to save a camera position or time of day in Enscape.
But like I said, I think given the current implementation that's unlikely to happen. And there might be other solutions to get to easily reproduceable renders. Like suggested in the other tread, an easier way to update cameras (so we can tweak camera position and time of day and save that back to the camera) would be a good step in the right direction without needing a major overhaul.
Pieter not sure I agree with you. They've already implemented a BIM mode. It seems like the only way to really solve the problem. Anything else is a workaround.
I see that we have BIM data now but it hasn't really proven useful to us yet. Can anyone state for the record how this feature is working for them? And how they are using it in meetings, etc?
I'm still waiting for the essential feature of measuring from one point to another point in the Enscape environment...are we still developing that feature?
yea we struggle with this as well...we end up just re-saving the view and deleting the original because there's no way to "push" the nuances in sun setting or camera re-positioning BACK to the view. Which is a confusing pain point for some projects.
And even if it did, what if that view has a VT that is locking that from changing? Would Enscape tell us that it cannot complete the transaction? Or would it be able to update the VT? Or remove the VT from the view?
And if it cannot, seems like a valid point to suggest that Enscape should catalog its views in its own browser UI? Independent from Revit's project browser?
Pieter Your point about a level playing field across the applications is well taken.
Like...are we suggesting that Enscape control the below elements within its own dialogue box (it will basically have its own VGO Panel)???
aka..all of the below controled DIRECTLY in Enscape UI (not pulled from a view's view properties)
Model Categories and Subcategories
Manual Override by Element
Linked File properties for all of the above
Currently we do this in photoshop using the material ID export. Would be nice to have as an option from the plugin's viz settings. See attached:
Yes, we do have plans to support both for the material editor. Right now normal maps are only supported for the new Revit 2019 materials.
However if you've got normal maps for your material right now, you might want to rename them with an _n at the end of the filename (e.g. myfile_n.png). Enscape will pick that up and interpret it as a normal map
Hope that helps
Clemens Musterle Woah I've never heard of the "_n" suffix. Does that mean that it won't be a normal map unless that suffix is present? Please clarify.
This will be interesting since AVAIL is essentially Archvision and their asset library is in competition with Enscape's but definitely +1
Thank you - I'll file a feature request for this accordingly. Anything else you'd like to enable/disable via a hotkey? Just so that I can also add it as further feedback.
If we can change the UI for the sync instead of ON/OFF, set it to "PUSH". Meaning its off by default but we hit one hotkey and then it pushes the data once. Basically syncing as needed instead of ON/OFF