Display MoreHi Julian !
Thank you for your reply.
Ok for circular and generic shapes... doesn't matter, but rect area should behave like a rect area light... As you can see, it seems generated from a circle.
Thank you again
Ciao
L.
I can't tell you exactly why that is because I'm not part of the rendering team but rectangular lights only really show up rectangular if you move them extremely close to the surface that you are pointing them to.
Hey Toscano,
currently we only support line and rectangular lights in VW. Every other geometry (including circles) gets an emissive material instead and emissive geometry works fundamentally differently from light sources so you don't get the same light output.
I think it should be possible to add circular/disk light support, I will look into it. In SketchUp, all of the lights are our own objects so it's easy to detect what is what light, in Vectorworks however we need to do some non-trivial detection on what type of light it should be and that's probably the main reason it wasn't added yet.
OK Thank you for looking into it. We are gradually moving into Vectorworks 2021.
Hey Alan, I've implemented a fix that properly hides/shows assets when the layer visibility changes. It will be part of the next preview and also part of the next release.
unfortunately - same error after using "change" and also installing it for vectorworks...
best, fa
The problem occurs when at least one is missing, please select them all and try again.
New Preview version (for SU22) don`t boot. Fatal error
for me the same problem...
Did you install Enscape only for Sketchup? Could you try to install it for all CADs as a test?
You can try my workaround which I posted for SKP2021 - maybe this still works:
It won't work this time, unfortunately.
Hey Toscano.
Does one of the materials have a glow shader? Does it happen when it's only the shelf in a separate project? Could you upload a small project with just the shelf if it does?
Hey, mariam.mann seems like something is going very wrong here. Unfortunately, I can't see what's wrong in the logs from the normal release and preview versions.
Therefore I created a custom version with some extra logging for your case that should finally catch the errors so that we can see what's going wrong.
Please install this version https://installer.enscape.io/Enscape-3.2.0%2b62948.msi.
And then again try launching Sketchup and send all the resulting logs.
There should be an additional file %TMP%\Enscape\Logs\BootErrors\SketchupBootError.log that I need.
Hey Firas, could you try again with the latest preview. We have improved logging there to see what the issue really is.
Try starting it with the preview version and then attach the newest log files again (both boot error and sketchup) or send them directly to me.
I've looked at the project and the script that I had in mind doesn't work. It only works when the layer with the assets is not completely hidden.
I've looked a little into adding a workaround on our side and it won't be easy. As I mentioned above we simply do not get any updates when the visibility of the layer changes. I won't promise anything but I'll see what I can do.
Then for the moment, the only workaround is to reopen Enscape.
Hello Alan.
Unfortunately, the change events for layer visibility have only been added with VW2021.
The export API that we use was new to VW2020 and so it does not have all of the features.
A simple workaround is to restart Enscape. This will re-read everything from the project and have the correct visibility.
The big downside here is of course the export time for every restart.
How are your layers set up for visibility? It might be possible to write a small python script that forces an update on all of the assets but this doesn't work for all cases.
Could you provide a sample project with a few assets and layers set up as yours that imitates your real project?
VW2022 has to be launched once so that our installer can detect it.
After that using repair should also install it for 2022. You can also try a simple uninstall and reinstall.
Hey Vito, we have added the ability to scale assets in our 3.2 preview versions. The release will also be soon.
The edit mode placement refers to an issue we had with VW2021. When you go into an edit mode, for example creating a group and right-click -> edit the group and place assets inside, then VW2021 would crash sometimes. Those crashes have been fixed by Vectorworks so we simply re-enabled that ability.
...one further question though - how do I associate Enscape with the new version of VW, please? I've installed VW2022, installed the service pack which then just appears in VW2021...
For our installer to detect VW2022 it has to be started at least once. In your case simply start the Enscape Installer again, use the repair option and it should work.
Hi Julian,
The assets are set to class 'none' which is the same as the other elements of the design (Vectorworks 3d shapes like the slabs etc). When I changed the 'none' class to visible in VW it has now started showing in Enscape too, so thanks for that, this has worked to resolve the issue.
I'm glad I could help, the underlying issue should be fixed in the upcoming releases as well.
What class is the asset set to, what visibility does that class have and what is the active class?
We currently have a bug where the assets don't show up when the active class is the one from the asset and the class is set to grayed out or hide.
martinfdc could you give it a try with the latest preview version? I think that should include a fix for your case.
There seems to be an issue with the layer visibility. Could you try to "Show Others" to see if that makes them show up?
landrvr1 I have found the issue and it turns out it's pretty much random whether it occurs or not and might just depend on how your PC feels like today (just like you described).
I was able to reproduce the issue, but not naturally. I was able to force it to happen with some slight changes that made it more likely.
The more unique bitmaps you have the more likely it is but it's still a really low chance of ever happening.
The cause is that proxies are cached first and randomly a bitmap from the main model might end up with the same id of an already cached proxy-bitmap and so it's re-used even though they are completely different.
I might be able to get a fix into the preview next week, but no promises 
landrvr1 Another question: Is it only the Bitmap that is replaced in the material? Or are other values such as color, roughness, etc. affected as well?
