Forum Discussion
Monoscopic renderer for Gear VR
I only just noticed this UE4 build by chance:
https://github.com/Oculus-VR/UnrealEngine/tree/4.12-gearmono
and the information about it:
https://developer.oculus.com/blog/hybrid-mono-rendering-in-ue4-and-unity/
It sounds really great for the right project!
Two follow up questions before I try it myself for my scenes to see what performance increase it gives:
1. Is there any chance of getting this for 4.13?
2. Is there any updated information on: "We are also working with Epic towards a potential future implementation on the main version of UE4." ? Which version is it pegged for?
GearVR performance improvements in UE4 is very much appreciated! Thanks in advance for the info
https://github.com/Oculus-VR/UnrealEngine/tree/4.12-gearmono
and the information about it:
https://developer.oculus.com/blog/hybrid-mono-rendering-in-ue4-and-unity/
It sounds really great for the right project!
Two follow up questions before I try it myself for my scenes to see what performance increase it gives:
1. Is there any chance of getting this for 4.13?
2. Is there any updated information on: "We are also working with Epic towards a potential future implementation on the main version of UE4." ? Which version is it pegged for?
GearVR performance improvements in UE4 is very much appreciated! Thanks in advance for the info
3 Replies
Replies have been turned off for this discussion
- Hello :)
1) For 4.13, the fastest way to get this would be to diff the 4.12-gearmono branch and the 4.12.3 tag (what it's branched from), and apply that diff to any engine version you want, there shouldn't be too much differences. If there is a strong interest for a 4.13 version, I can spend the time doing the merge myself. Let us know :)
2) We're currently shooting for an implementation in 4.15, so a few months out. I mean shooting for as in "don't be surprised if it doesn't end up there" ;) However, that doesn't mean you can't ship nor develop with the technique in mind now, we actually have some apps in the pipeline that will be using this tech, that merged the 4.12-gearmono/4.12.3 diff into their own engine.
This is still experimental, so let us know about your thoughts and comments! Thanks for taking a look!
rpalandri said:
Hello :)
1) For 4.13, the fastest way to get this would be to diff the 4.12-gearmono branch and the 4.12.3 tag (what it's branched from), and apply that diff to any engine version you want, there shouldn't be too much differences. If there is a strong interest for a 4.13 version, I can spend the time doing the merge myself. Let us know :)
2) We're currently shooting for an implementation in 4.15, so a few months out. I mean shooting for as in "don't be surprised if it doesn't end up there" ;) However, that doesn't mean you can't ship nor develop with the technique in mind now, we actually have some apps in the pipeline that will be using this tech, that merged the 4.12-gearmono/4.12.3 diff into their own engine.
This is still experimental, so let us know about your thoughts and comments! Thanks for taking a look!
Hi @rpalandri thanks for that info! I tried it out and worked fine for our already completed project (We Come In Peace...)
It would be great if you could do the merge for a 4.13 version though (my git knowledge is limited) as we are just starting our next project which is much more ambitious and would greatly benefit from this performance increase - and we need to use 4.13 for some other features.
Many thanks in advance if that is still possible! :)- I'll put that in my lists of tasks, will let you know if/when it gets done :)
