Forum Discussion
Solved
How do I get my ue4.9 build to work with the latest runtime (1.6) ?
Heyo,
we made a build of our game 'VR Flush' in ue 4.9 a while ago.
Now, that I finally have the time to release it, it doesnt work with the latest oculus runtime anymore. The build still works with the 0800 runtime.
What do I need to do to make it playable for everyone (Without having to tell them to downgrade to the 0800 runtime first)?
I can rebuild it in 4.9, but I really don't want to migrate it to a newer ue4 version - That would be a ton of work....
What can I do?
We d really appreciate your help :))
It would be a shame not to release it..
iNvi
we made a build of our game 'VR Flush' in ue 4.9 a while ago.
Now, that I finally have the time to release it, it doesnt work with the latest oculus runtime anymore. The build still works with the 0800 runtime.
What do I need to do to make it playable for everyone (Without having to tell them to downgrade to the 0800 runtime first)?
I can rebuild it in 4.9, but I really don't want to migrate it to a newer ue4 version - That would be a ton of work....
What can I do?
We d really appreciate your help :))
It would be a shame not to release it..
iNvi
- The oldest version of UE4 that will work with the runtime without source changes is 4.10.4 from our Github. If you can't upgrade your project to 4.10.4, then you have 2 choices, as @dwood15 said:
1) Back-port SDK 1.4 support from 4.10.4 to 4.9 yourself. You can do this by diffing the above branch against stock 4.10.4 and then (very carefully) applying similar changes to a 4.9 version. Unfortunately, due to the large number of older UE4 versions, we can't provide much help with this process. But an advanced programmer should be able to do it.
2) Re-create your project with a newer UE4 version.
4 Replies
Replies have been turned off for this discussion
- Ah damn I just read THIS
"If you are planning on releasing a VR game that targets the Oculus Rift, you will need to make sure that you are using UE4 version 4.11.1
or later. Earlier version of UE4 will not be compiled against the
shipping versions of the Oculus Libraries. This means your project will
not be able to be submitted to the Oculus store.
"
Is there no way to get arround that? - Absolutely there is. Are you prepared to open the whole engine's source code and modify it? If not, I suggest you upgrade your project version by version or consider rewriting it.
- The oldest version of UE4 that will work with the runtime without source changes is 4.10.4 from our Github. If you can't upgrade your project to 4.10.4, then you have 2 choices, as @dwood15 said:
1) Back-port SDK 1.4 support from 4.10.4 to 4.9 yourself. You can do this by diffing the above branch against stock 4.10.4 and then (very carefully) applying similar changes to a 4.9 version. Unfortunately, due to the large number of older UE4 versions, we can't provide much help with this process. But an advanced programmer should be able to do it.
2) Re-create your project with a newer UE4 version. - Thanks for the responses;)
Going for option 1) of your suggestion would probably make me wanna kill myself;) I can do BPs, but beyond that I really don't wanna go if I dont have to.
I ended up migrating the project to ue 4.11.2 and it (amazingly) did not destroy the game at all. Sure there are a few bugs I still have to fix, but apart from an outdated FMOD plugin, it went way better than I d ever have expected:)
Again. Tahnks:)
