Horizons Beta VR

I haven't noticed any changes to the height of the view in the game, although it does seem to be slightly different, but more like my FOV is very slightly larger.

The game does seem to be running better overall, although I have still noticed judder when in SC at times, although this is not like the SC stutter we had till recently, but just like what we have seen now and then for some time.

I think the quality of the scaling/resolution has increased, as I noticed text is sharper and dropping the HMD slider by 2 or 3 notches got it back to how it has looked in previous versions.

I play with the rig in my sig, but have all options set to medium, SS at 1x, with Blur, Bloom, AA and AO being turned off, and Terrain details set to low to try and maximize framerate and reduce chances of judder, although it can still happen now and then in SC, but also on planets at stations when other Commanders are in the instance, although this has been smooth a couple times when only 2 Commanders were around the station. Planet exploring is smooth until I get up into Orbital Cruise, then it can judder now and then.

I find the graphic options for the terrain make little difference in the DK2, but this is most likely due to the resolution. Only option worthwhile imo is having Shadows at least turned on.
 
No, it's true that you cannot change the HUD Color while in game, but you can edit the color in the GraphicConguration XML
Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\GraphicsConfiguration.xml <-make sure you are in the correct Products folder, there are multiple if you are playing in a beta.

Just change the values in GUIColor

<GUIColour>
<Default>
<LocalisationName>Standard</LocalisationName>
<MatrixRed> 1, 0, 0 </MatrixRed>
<MatrixGreen> 0, 1, 0 </MatrixGreen>
<MatrixBlue> 0, 0, 1 </MatrixBlue>
</Default>

There is even a handy little website someone made that lets you experiment with colors so you find what works best for you.
http://arkku.com/elite/hud_editor/
Thanks for this!!. I knew it was somewhere but I couldnt remember where. After playing beta last night, I realized the HUD color is really terrible. Sun light on the dash makes it unreadable!!
 
So managed to get a little shot at it tonight

First impressions it looks like it has massive potential but man is it heavy on the graphics card, I'm getting stuttering in stations even with the shadows turned down to medium and that's with a Titan X
The srv deployment panel is extremely annoying just pops in and out all the time

The surface of the planets looked great and even got to fly the Cobra MKIV down to one which was superb

Have you overclocked your bits?
 
Well today Horizons is running well for me, I did delete the Gpuworkload.xml after installing latest NVidia drivers, which probably didn't matter as after a driver reinstall it recalcs shaders etc anyway.so now 1.5x SS, terrain quality set on high.. Maybe there was something to yesterday's patch but its definately running better than the first 2.0 release did for me. 980 GPU BTW.
 
No, it's true that you cannot change the HUD Color while in game, but you can edit the color in the GraphicConguration XML
Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\GraphicsConfiguration.xml <-make sure you are in the correct Products folder, there are multiple if you are playing in a beta.

Just change the values in GUIColor

<GUIColour>
<Default>
<LocalisationName>Standard</LocalisationName>
<MatrixRed> 1, 0, 0 </MatrixRed>
<MatrixGreen> 0, 1, 0 </MatrixGreen>
<MatrixBlue> 0, 0, 1 </MatrixBlue>
</Default>

There is even a handy little website someone made that lets you experiment with colors so you find what works best for you.
http://arkku.com/elite/hud_editor/

It's better to leave that file alone, and just edit this: %USER%\AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics\GraphicsConfigurationOverride.xml. This will work for any version, beta or otherwise.

Open the file in a text editor and copy/paste the following:

<?xml version="1.0" encoding="UTF-8"?>
<GraphicsConfig>
<GUIColour>
<Default>
<LocalisationName>Standard</LocalisationName>
<MatrixRed> 0.18, 0, -1 </MatrixRed>
<MatrixGreen> -1, 1, -1 </MatrixGreen>
<MatrixBlue> 0.15, 0.32, 1 </MatrixBlue>
</Default>
</GUIColour>
</GraphicsConfig>

Edit the values as necessary. To easily make changes and experiment with GUI colors, you can use EDDS:
http://edcodex.info/?m=tools&entry=170

Just make sure you edit the GraphicsConfigurationOverride first. If it is empty, EDDS will not be able to change colors, due to a bug.
 
SteamVR was recently updated to support Oculus 0.8. Has anyone tried to use the new SteamVR/Vive support with a DK2 to see if it performs any better than the direct 0.5 rift SDK support?

Theoretically, with OpenVR support FD wouldn't need to code separate rift sdk support.
 
SteamVR was recently updated to support Oculus 0.8. Has anyone tried to use the new SteamVR/Vive support with a DK2 to see if it performs any better than the direct 0.5 rift SDK support?

Theoretically, with OpenVR support FD wouldn't need to code separate rift sdk support.
I thought of that as well when I saw they added SteamVR support but I have no idea how you'd go about using it right now. Would adding the launcher as a non-steam game work?
UPDATE: IT WORKS! Install and run SteamVR, close the steam menu thing it opens. Launch Horizons with the launcher and it mirrors on your monitor and displays on the Rift. It's late so I have no idea how performance is like but if it's better I'll be very happy. This is with runtime 0.8 on Windows 10.
 
Last edited:
So, I just recently been playing the Horizons Beta, and also taking a hit in the VR framerate department. The biggest improvement/change you can make is lowering the shadow quality. It has the biggest affect on the frame rate. Because it changes the number of draw calls it has to do. My Horizons Beta setting was defaulted to Ultra.
 
Last edited:
I thought of that as well when I saw they added SteamVR support but I have no idea how you'd go about using it right now. Would adding the launcher as a non-steam game work?
UPDATE: IT WORKS! Install and run SteamVR, close the steam menu thing it opens. Launch Horizons with the launcher and it mirrors on your monitor and displays on the Rift. It's late so I have no idea how performance is like but if it's better I'll be very happy. This is with runtime 0.8 on Windows 10.

can anyone else confirm this?
 
can anyone else confirm this?

IT WORKS! I'm on DK1 WIN10 Oculus runtime 0.8. Had to enable HMD in the game, but nothing happened until I restarted Elite. Then it worked.

Edit: Holy moly... the experience down on planet with Rift on is incredible! I had driven up and parked on a gentle sloped hillside before trying the Rift. Wow what a view!
 
Last edited:
Is anyone able to get their DK2 to run at 75hz with SteamVR? I've gotten everything else set up now (finally) but I just can't make it run at 75hz... Even if I switch my desktop to a resolution that can run at 75, the game switches automatically to 60 every time :mad: Anyone have any tips for this?

It does load the game and it does look great, so we almost have a workable solution here!


EDIT: Ok, I got the Rift running at 75hz by creating a custom resolution in the Nvidia Control Panel that exactly matches the 1280x768 mirror window that Elite defaults to displaying on the Primary monitor. Switched the desktop to that custom res before launching ED and it worked! Unfortunately, performance in-game is abysmal. Even on the lowest settings for every graphics option, the game was juddery and barely playable everywhere I tested... Well, back to Win7 and extended mode for now I guess. Still, it's good to see progress being made on the VR front by both FD and Steam here. Next year is going to be some good times! :)
 
Last edited:
Is anyone able to get their DK2 to run at 75hz with SteamVR? I've gotten everything else set up now (finally) but I just can't make it run at 75hz... Even if I switch my desktop to a resolution that can run at 75, the game switches automatically to 60 every time :mad: Anyone have any tips for this?

It does load the game and it does look great, so we almost have a workable solution here!


EDIT: Ok, I got the Rift running at 75hz by creating a custom resolution in the Nvidia Control Panel that exactly matches the 1280x768 mirror window that Elite defaults to displaying on the Primary monitor. Switched the desktop to that custom res before launching ED and it worked! Unfortunately, performance in-game is abysmal. Even on the lowest settings for every graphics option, the game was juddery and barely playable everywhere I tested... Well, back to Win7 and extended mode for now I guess. Still, it's good to see progress being made on the VR front by both FD and Steam here. Next year is going to be some good times! :)

I had discovered the steamVR functionality a few days ago when I went to run Elite without Oculus on .8 to test something and was surprised to see VR come to life.

I also noticed that the refresh rate and resolution was wrong. It was using my desktop monitor refresh. Apparently making a custom resolution for 75hz didn't help you at all so I won't bother doing that.
 
I finally got to have a go of Horizon's yesterday. I have a EVGA 970 SSC no overclock, and I also got the low frames, I was testing everything. I found with mine the ambient occlusion fix mine. then I flew away from the planet and then came back and the low frames mess was there again. I'm sure Mr Braben said that he had tested with a 980 and it had no problems. I even tried the old, turn your screen size up to the next one the then back to 1920 but no luck. As I said so far when turning ambient occlusion off it fixes it on my system until I go back to planet. Please can someone else test that also to see if its like the old SC bug.
 
Well today Horizons is running well for me, I did delete the Gpuworkload.xml after installing latest NVidia drivers, which probably didn't matter as after a driver reinstall it recalcs shaders etc anyway.so now 1.5x SS, terrain quality set on high.. Maybe there was something to yesterday's patch but its definately running better than the first 2.0 release did for me. 980 GPU BTW.

I'm also on a GTX980 and I really don't see how you can be using 1.5x SS unless of course you are moving the Oculus slider down? Performance in Horizons has been pretty hit and miss for me. The latest NVIDIA driver improved performance overall for me, I managed to restore SSAO from FXAA with out stations being jerky, but I get hit and miss performance when exiting orbital cruise and also while driving the SRV on the dark side of planets with the headlights on. Headlights off and everything is fine, as soon as mine (or anyone else) are on the SRV driving goes stuttery.
 
Last edited:
well i was intrigued by this but so far it doesnt sound like its worth me switching from runtime 0.5. If the performance was massively improved i would have given it a go but with 0.5 i dont have to mess about with custom resolutions and whatnot you know?
 
It runs fine with SteamVR as long as you don't land on planets (kind of ruins the purpose I know), close to planets I'm getting 60 FPS (extremely noticeable judder) but only 70% GPU usage so something is weird here. The game window was on my main monitor which is 144Hz so I doubt it's anything to do with VSync (goes above 60 in space). It seems to run without having Steam open at all, I forgot to change runtimes and it still ran even without steam running. It's a bit weird it works fine with SteamVR but not the native OVR SDK.
 
performance on 0.5 runtime SDK btw. If anyone is interested in just using that:

[video=youtube;l_wRz2uol6M]http://www.youtube.com/watch?v=l_wRz2uol6M[/video]

TL;DR - Some weird loss of tracking flickering on approach to planets but generally ok framerate.
 
Back
Top Bottom