11-06-2023, 05:52 PM
Hello.
As you may know, Unity introduced a feature called "fast enter play mode" a while ago. When the user enable this feature, they do it by skipping the domain reload operation when going in and out of play mode in Unity editor. Thou, implementation of our games and 3rd parties we use need to be adjusted to be able to support this feature.
This feature "no domain reloading" will be mandatory in upcoming Unity versions when they complete upgrading Unity to modern .NET which doesn't support "domains" anymore.
As far as I know, many people were able to use this fast enter play mode in their projects but I was hesitant. Due to various reasons, it's time for me to switch to the new system.
When I tried my game in play mode with domain reloading disabled, it looks working fine (I haven't tested deeply yet) but I get an error from Curvy saying:
I investigated this and the error is caused by static applicationIsQuitting in DTSingleton class. It's value remains true after exiting play mode and the next time we go into playmode, the error happens.
Do you plan to fix Curvy by adding support for "fast enter play mode" feature?
Or did you already fix it in a version which I don't have yet?
(I don't know which version I'm on. I couldn't find that info in a quick glance)
Thank you.
As you may know, Unity introduced a feature called "fast enter play mode" a while ago. When the user enable this feature, they do it by skipping the domain reload operation when going in and out of play mode in Unity editor. Thou, implementation of our games and 3rd parties we use need to be adjusted to be able to support this feature.
This feature "no domain reloading" will be mandatory in upcoming Unity versions when they complete upgrading Unity to modern .NET which doesn't support "domains" anymore.
As far as I know, many people were able to use this fast enter play mode in their projects but I was hesitant. Due to various reasons, it's time for me to switch to the new system.
When I tried my game in play mode with domain reloading disabled, it looks working fine (I haven't tested deeply yet) but I get an error from Curvy saying:
Code:
[DevTools] DTSingleton instance was null. This happens if the instance is destroyed by the user, which is not a supported operation. If you did not destroy the singleton's instance, then please fill a bug report.
I investigated this and the error is caused by static applicationIsQuitting in DTSingleton class. It's value remains true after exiting play mode and the next time we go into playmode, the error happens.
Do you plan to fix Curvy by adding support for "fast enter play mode" feature?
Or did you already fix it in a version which I don't have yet?
(I don't know which version I'm on. I couldn't find that info in a quick glance)
Thank you.