VW2023 has now been released - will the current version of Enscape install / work okay with it, please?

Vectorworks 2023
- PhilBixby
- Thread is Unresolved
-
-
-
I'm still waiting for, too...
Thank you Demian!
L.
-
I'm still waiting for, too...
Thank you Demian!
L.
Should be coming soon - I'll keep you posted.
-
Ah, I logged in and saw the Vectorworks folder in bold type and got all excited... ...but no, just a video query...
-
Ah, I logged in and saw the Vectorworks folder in bold type and got all excited... ...but no, just a video query...
Unfortunately, we encountered some issues With VW2023 SP0 and had to wait for the SP1 release which should be next week.
The latest Enscape Preview versions run in SP0 but you can encounter problems that can even lead to crashes.
Enscape with VW2023 SP1 should work as expected. -
Excellent - thanks for the update. Will await SP1 and then load it up.
-
What? Are you kidding me? I love Enscape, and I love Vectorworks. What could have changed in the program coding, so the two don't currently work together? I don't understand computer coding, but how could this even happen? I've been using Enscape for just less than two years - successfully! It's great and so easy to use with Vectorworks.
I'm so puzzled. Please, SP1 come quickly already.
-
Okay - well that last two hours didn't go well... ...so SP1 is now out. I installed it, so I have a standard install of VW2023 (in the default folder etc) which now has SP1 applied. The Enscape Tool Set has a row of red crosses, so I go to Tools>third Party and I get this:- "EnscapeWorkspaceIntegrationMenuItem not in Plug-ins folder". So I then uninstall Enscape and reinstall - same thing. I then uninstall VW2023 as well and reinstall everything step-by-step with reboots inbetween - same thing. So I *then* go to the VW2023 Plug-Ins folder to check, and lo and behold - no Enscape folder. I copy the one from the VW2022 Plug-Ins folder (which of course is a new folder thanks to the reinstall), but when I start up VW2023 I get an error message saying "EnscapeVectorworksPluginHost2022 not compatible with this version of Vectorwaorks".
So... what's going on here fellas and how do I get my now-a-few-weeks-old VW2023 working with Enscape?
-
Enscape's version may not be ready for now and may just test and adapt
to (mandatory) VW's SP1 update.
I do not think it will take too long.
Can't test or verify though.
A) I am on M1 Mac and B) I do not want to ask for another trial again ...
-
Okay - well that last two hours didn't go well... ...so SP1 is now out. I installed it, so I have a standard install of VW2023 (in the default folder etc) which now has SP1 applied. The Enscape Tool Set has a row of red crosses, so I go to Tools>third Party and I get this:- "EnscapeWorkspaceIntegrationMenuItem not in Plug-ins folder". So I then uninstall Enscape and reinstall - same thing. I then uninstall VW2023 as well and reinstall everything step-by-step with reboots inbetween - same thing. So I *then* go to the VW2023 Plug-Ins folder to check, and lo and behold - no Enscape folder. I copy the one from the VW2022 Plug-Ins folder (which of course is a new folder thanks to the reinstall), but when I start up VW2023 I get an error message saying "EnscapeVectorworksPluginHost2022 not compatible with this version of Vectorwaorks".
So... what's going on here fellas and how do I get my now-a-few-weeks-old VW2023 working with Enscape?
As Phil said,
Let's get this fixed already....please. -
I'm running the Australian Version of VW 2023 and I want to use Enscape but there is no SP1 available yet. Even if there was, it appears that according to this thread, it's not working anyway. Do we have a timeline for resolution?
-
PhilBixby - I have a thread on the Vectorworks forum trying to get attention on that end.
-
leecalisti Aaah - now that's more helpful - thanks. Sounds like (unlike what was suggested further up this thread) we're waiting for a new update to Enscape which responds to the VW SP1 changes. I wish we'd been told so I hadn't spent a teeth-grinding session uninstalling and reinstalling!
-
-
leecalisti Aaah - now that's more helpful - thanks. Sounds like (unlike what was suggested further up this thread) we're waiting for a new update to Enscape which responds to the VW SP1 changes. I wish we'd been told so I hadn't spent a teeth-grinding session uninstalling and reinstalling!
I'm sorry to hear that you wasted a lot of time on this. There was another bug that came up last minute just before the release and that's why we decide to delay it again to next week. I didn't have the time to respond here yet because of it.
As Dave mentioned in the VW thread there were issues with lights (and more) in SP0 that just weren't fixable on our side. They were fixed with SP1 except for one that slipped through which we found too late however, we can fix that on our side.
Usually, we find these kinds of issues way earlier before a release and you would never see them but this time was a bit cursed. We'd rather delay and fix these issues than cause everyone headaches because of these bugs.
As I mentioned before, if you really can't wait until next Wednesday you could install our preview version which does run on SP1.
It does not include that latest bugfix so I would still recommend going back to 3.4.2 as soon as it's out.
-
We've just released 3.4.2 that supports VW2023, preferably SP1.
You can use it with SP0, however we display a warning that there might be issues and recommend to update. -
Thanks Julian Hangstoerfer . I've installed ver 3.4.2 and I'm on VW2023 SP1 but I can't get the Asset Library to load from the Tool Sets. I also had to add the Enscape tools to my workspace. I can open the Asset Library from within the enscape renderer once launched but cannot open it from the Enscape tool set. Any idea why this is the case? All the other tools in the Enscape tool set are opening without issue.
-
Thanks Julian Hangstoerfer . I've installed ver 3.4.2 and I'm on VW2023 SP1 but I can't get the Asset Library to load from the Tool Sets. I also had to add the Enscape tools to my workspace. I can open the Asset Library from within the enscape renderer once launched but cannot open it from the Enscape tool set. Any idea why this is the case? All the other tools in the Enscape tool set are opening without issue.
I haven't seen something like that before. Nothing happens at all when you use the asset library tool? Or is it empty after it opened?
I'd be best to use the feedback tool to open up a ticket with our support so that they can also check the logs and all that. -
Julian Hangstoerfer - OK, so far so good - thank you.
PhilBixby - Have you tried it yet?