If only there were people inside Unity that actually used Unity for making games those sort of usability blunders wouldn't happen as often as they do.Īnd since 2021 has gone LTS and with 2022 nearing LTS status, if the feature comes back it will likely only happen in 2023, meaning two entire LTS cycles having to manually refresh assets to recompile our scripts. It's also super useful being able to make changes to things like shaders and textures during play mode and see the changes in the context of the game, so losing that ability just to keep Unity from blowing into a million NREs due to a mid-playmode domain reload clearing all statics and stopping all coroutine/async operations is not ideal at all. Why on Earth did Unity remove that feature? I often make several changes while in play mode so they get all batched for a single recompile the next time I stop and re-enter play mode. Absolutely maddening to hear that it was both deliberate and being defended I just thought it's been buggy, since I lose an editor session a couple times a day due to this, but I finally checked settings today. I haven't posted here since 2018, but I bothered to post this. Or, change a global option to stop importing any new assets without a manual refresh? Ugh Stop playing anyway, because there's a 0% chance anything will survive recompile and keep working.I get that it's a complex feature, but don't remove an actually-useful feature because it makes that complexity worse. I've been using Unity since the 1.x days, and past a very early prototype project with maybe a scene or two, something breaks during a hot recompile. Is this for some non-game use (configurable customizer or something)? I've asked around over the years, and I've never found a single project that is compatible with it, let alone uses it as a fixture of their workflow. I don't understand why it would be removed at all.įurthermore, I don't understand which projects are even capable of surviving a recompile while in play mode. I just noticed this and posted on Twitter, and saw this thread after a search there: Prevent Recompile During Play Mode (TRUE/FALSE)īut to be honest, I'd much rather have just kept the original "Script Changes While Playing" option determine this because it's worked that way as long as I can recall and it lead to much confusion when it quietly changed.Auto Refresh (same as current dropdown option).My personal workflow is to always restart play mode after recompile.įor what it's worth, if we have to direct this choice through the new Auto Refresh option then my ideal solution would be to have the existing auto-refresh option for assets, and then have an additional option for code changes. In fact, I never want to recompile code during play mode. There are times when I would want to reimport assets (such as art/audio) but NOT recompile code changes, and may need to reimport one but not the other. The new auto-refresh option is OK, but still not ideal. I came looking for others experiencing this issue and just wanted to add a +1 to the original post. Unfortunately I can't figure out how to add a poll here as I'm interested if we're the only ones who miss the feature. If I change a 2 gig Photoshop file, I may not want to reimport it immediately. If I change a script, I want to recompile. what we really want is to have option to have "only" scripts to be auto refreshed outside playmode, but not the all other assets." I later found this entry by which makes way more sense: It has been replaced with a new auto refresh feature in `Preferences -> Asserts Pipeline -> Enabled Outside Playmode`" When activating the "Enabled outside playmode", my scripts aren't compiled at all anymore. "This features has been depricated due to it not working as intented. Now maybe I didn't get it, but the recommended "solution" is not working the same as before, so I wonder if someone can explain to me how I can get the old behaviour again? It was one of the *best* features added in the past and decreased our iteration times big times! I assumed this to be a bug and searched for it and then found the issue in the bug tracker: Without this "Compile after playing" feature our iteration times will increase by a lot. I switched from Unit圓d 2019.4 to 2021.3.9f and found that the "Recompile after finished playing" feature has been removed from the editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |