Josh Posted December 21, 2023 Share Posted December 21, 2023 The development channel provides access to the very latest updates before a formal version release. This is good for getting the latest features and fixes, but may also be more unstable than the default channel. It's up to you how frequently you want to receive updates. In the standalone you can switch to the dev channel by opening the client app, pressing the uninstall button (if the engine is already installed) and then selecting the dev channel in the dropdown list, and pressing install. In Steam you can select the beta branch in the application properties. 1 Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
kasool Posted December 22, 2023 Share Posted December 22, 2023 Will there be an option to install multiple versions in the future? I seem to only be able to install one version at a time: Quote Link to comment Share on other sites More sharing options...
Josh Posted December 22, 2023 Author Share Posted December 22, 2023 I considered this during development, but it seemed like it could get very confusing, especially since an environment variable is used to point to the install path. 1 Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
kasool Posted December 22, 2023 Share Posted December 22, 2023 4 minutes ago, Josh said: I considered this during development, but it seemed like it could get very confusing, especially since an environment variable is used to point to the install path. That's fair. The only use case I was thinking of was trying new features without having to reinstall to flip between versions. Could be useful if you wanted to gather feedback before merging something into stable. Related to that: does loading a project with a different version engine than it was created in mutate any of the project "state"? Like, as you probably know, in some engines every project has an associated version with it, and trying to load a newer versioned project into a relatively older engine version is usually a recipe for disaster. I'm just imagining a scenario where you want to try upgrading the engine version, but the newer one might have some bugs/etc. so you decide to roll back. I think Unreal gets around this by asking if you want to duplicate the project before loading it into a different engine version, so you knowingly accept the risks/have some way to go back just in case. Or maybe Ultra is much more robust in this regard and it's not a concern, but just curious Quote Link to comment Share on other sites More sharing options...
Josh Posted December 22, 2023 Author Share Posted December 22, 2023 The engine does resave the ultra.json file often, where all the project settings are stored, but at this time it seems very stable. It's just a JSON file, so if new data is added in a newer engine version it will still be backwards compatible with older builds, unless there was some really huge change I can't imagine right now. 1 Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.