Is there a way to force Elite to use SteamVR instead of using the 1.3 runtime natively? Might be a fast and easy solution for DK2 users who are tired of incredibly ugly colours and smearing, now that Oculus somehow killed the runtime switcher to 0.8 :/
Forcing SteamVR over Oculus 1.3 runtime?
- Thread starter Dweezil_Moon
- Start date
I'd be interested to know how to do this as well.
Problem is, ED probably "searches" for the oculus driver before searching for the SteamVR middleware.
SteamVR also searches for the oculus runtime.
So how do you hide the runtime from ED, but then expose it for SteamVR to find. It might need a "forceSteamvr" command line argument or something.
This would need to be coded by the devs.
Come to think of it, using SteamVR probably just loads the oculus driver anyway (inside the SteamVR wrapper) so the graphical issues might remain.
Problem is, ED probably "searches" for the oculus driver before searching for the SteamVR middleware.
SteamVR also searches for the oculus runtime.
So how do you hide the runtime from ED, but then expose it for SteamVR to find. It might need a "forceSteamvr" command line argument or something.
This would need to be coded by the devs.
Come to think of it, using SteamVR probably just loads the oculus driver anyway (inside the SteamVR wrapper) so the graphical issues might remain.
Last edited:
I agree. I don't know if it would solve the issue for sure. I guess it al depends on whether the problem's source is the 1.3 runtime or the implementation in E : D. If Elite treats colour correction differently depending on the API then using SteamVR might really help with probably very little overhead on the side of Frontier.
or something like that.
or something like that.