Just noticed that my name on this forum is xSPAC3MONKeYx, haha, I fat finger keyboards, man hands, the name is xSPAC3MONK3Yx, in life I am called alot of names, but my children call me DAD, thats the one im fond of.
I think I'm finished trying to play Elite in VR.
- Thread starter CMDR Muy Bien Gato
- Start date
Hi and thx CMDR.
My PC is already optimised and SLI works great, as long as I m not using it for VR.
Wow dude, that's a lot of good info right there. I hope you'll excuse me for a bit of a format tidy up though - was a touch hard to read!
You clearly have a fa rbetter grasp of networking and PC internals than I do - by my own admission, I know just enough to be dangerous, but not quite enough to navigate out of the the most dangerous bits.
I'm currently running an Asus Ranger VII with 4690K, Sandisk something or other SSD (480 up/down) and a GTX970 Strix.
Having said that, my new build, which is kinda just sitting there whilst I fault find (I think I have a RAM issue) is an Asus Gene VIII, 6600K, 16GB Corsair LPX 3200Hz RAM, Intel 256GB 600P SSD (couldn't quite afford to go for the Samsung Evo 950...) in a Corsair Air 240 case, using a Noctua NH-L12 cooler, so I'll be a tad limited with regards to OCing the 6600K, but I was after the form factor more than outright brutal OC'ing of the CPU. I can always go for a water cooler if I want to push it, I guess, though really, this case is designed as a good air cooling case.
Graphics, for now, will be handled by the GTX970, whilst I await the alleged GTX1080Ti... If I'm going to drop a heap of cash on a card, it may as well be a really good one.
As for networking, I'm using a Draytek Vigor130 (VDSL2 - I have a 100mb up/down fibre to the building connection), which is hooked up to a Mikrotik RB3011, and a Ubiquity AP-AC-Pro (can't afford Ruckus!!!) with a cloudkey, deals with wifi needs, though the gamer builds are always plugged via ethernet.
The Mikrotik is... Awesome, but it sure has been a learning curve, though it's damn impressive what it can do for the money, and it doesn't lack for processing power, that is for sure, my internal network flies. whenever I go to a house using an ISP provided modem/router, I cry a little inside...
Anyways, I'll go through your suggestions when I get home, we'll see how it affects things...
Z...
"Firstly, the 20% reserved bandwidth is for QoS traffic. This traffic includes stuff like streaming videos, Windows Update, VoIP, etc. — anything that makes use of the QoS Packet Scheduler. Windows has this reserved bandwidth to ensure a smooth experience with QoS traffic because this type of traffic typically needs a high amount of reliable bandwidth. If you go ahead and disable this reserved bandwidth, you may experience issues with QoS tasks.
Secondly, 20% of your bandwidth is reserved only when QoS tasks are running. When no QoS task is running, by default you have access to 100% of your bandwidth. So by going forward with removing the 20% reserve, essentially you wouldn’t be recovering all 20% of your bandwidth; you would be recovering the piece of the 20% that is wasted and unused"
^^ https://dottech.org/26628/how-to-force-windows-to-use-100-of-your-network-bandwidth-how-to-guide/
Windows 10 is a very different beast from all other OS systems previously , take care in tweaking it !!
Ps never clean the registry !!
Last edited:
Windows 10 also takes too much control and decides to disable things that shouldn't be. My partner and I have a business with requires our staff to have a Cisco VPN client running to allow access to our clients systems. The windows VPN, of course, does not support the protocols or some such, so, of course, the best course of action for windows is to not allow the VPN to be installed. Now, with the installation of another VPN, then installing the Cisco VPN, then a registry edit will make everything all nice and happy.
Of course then Windows decides to do a random update, and disable it again, meaning I have to go back to the registry and edit it again. Honestly, I'd love to just slap some of the people responsible for this stuff... On top of that, they actually make it incredibly difficult to turn off auto updates. It was nic ein previous versions to be able to perform an update WHEN YOU WERE GOOD AND READY.
It's always fun being on site, having to go to the next job, and discovering that windows has decided now is a good time to do an update - topped off with a laptop that needs to be plugged in because the battery no longer holds enough charge (not that it ever lasted more than an hour and a half of proper use anyway...).
Then, they give you the option to set a "metered connection", great, but only for wifi. Why? My gaming PC is connected to the SAME METERED CONNECTION that my wifi is on. How do you fix that? Registry edit, of course...
If anything, we need ot learn more and more about registry hacks to get around the constraints of Win 10. Using both OSX and Win10 quite heavily, I actually think Window sis now locked down wors ethan OSX, at least I can choose when to update OSX...
Z...
whoops, my bad. Pardon my ranting, Win 10 has been driving me mad, and I really want to slap someone at M$...
Z...
I did similar testing yesterday with My 1080 on the Rift. It is easier in the beta as you can change both the game SS and the HMD SS.
I never really understood why people dropped the ingame SS as to my eye it is blurry and worse. you might as well just drop the HMD SS a little.
However while experimenting yesterday I discovered that game .85ss magically improved the image. I was sitting in the station and turning it on and off while looking at the distant details I could see the vast improvement.
I found a sweet spot for my settings 1.75 HMD quality and .85 game super sample. I don' know if its because these values are not an even deviser. but on my rig its the best combo.
Yes I am using ASW in auto.. but most times I am at 90FPS.
I do have a Vive but I prefer the rift for ED. People yell and scream at Frontier but have you ever considered that the Vive drivers are simply not as good as the oculus ones? The framerates are higher for me with the rift and the same settings than within the vive and rift just looks sharper.
Don't get me wrong I love the vive and use it regularly but not for ED.
I never really understood why people dropped the ingame SS as to my eye it is blurry and worse. you might as well just drop the HMD SS a little.
However while experimenting yesterday I discovered that game .85ss magically improved the image. I was sitting in the station and turning it on and off while looking at the distant details I could see the vast improvement.
I found a sweet spot for my settings 1.75 HMD quality and .85 game super sample. I don' know if its because these values are not an even deviser. but on my rig its the best combo.
Yes I am using ASW in auto.. but most times I am at 90FPS.
I do have a Vive but I prefer the rift for ED. People yell and scream at Frontier but have you ever considered that the Vive drivers are simply not as good as the oculus ones? The framerates are higher for me with the rift and the same settings than within the vive and rift just looks sharper.
Don't get me wrong I love the vive and use it regularly but not for ED.
![[HJ]-RedRaven](https://forums-cdn.zaonce.net/data/avatars/m/67/67389.jpg?1553527112){kind=avatar}
Cool, glad you found a good combo that works for you.
However, setting the in-game SS to anything less than 1.0 will degrade image quality. 0.85 isn't too bad (not like 0.65, ugh), and it will net you a fair few extra fps. But the texture and fine detail will suffer quite a bit. However, you may not notice it too much depending on what you're doing in the game.
You've set a very high (1.75) HMD supersampling, then taking that big crisp image and down-sampling it to less than the normal display resolution (losing some of the image quality in this step), then ED re-scales it back up a bit for the Rift display resolution, and this is where the lost detail can become more apparent as you multiply the artifacts introduced by scaling.
Its a bit like buying a half-million dollar Bentley, then driving it in a demolition derby. It will work, it will be fast, but the end result may not be pretty!
My advice would be to drop the HMD Quality to 1.25 - 1.4 and keep the ingame SS at 1.0 to retain the image/texture quality. I run 1.25 HMD Quality/1.0 in-game SS and see 90fps in space, but not in stations with menus up. But then with the menus true 90fps isn't really important.
Keep playing and see how you go...you might find you like different settings for different situations in the game... and yeah with the HMD Quality setting accessible in the game, that makes things quite a lot easier!
Now if they'd only fix the memory leak!
The link you posted is not the way you dothis, folloing those instructions will just get you into trouble, I just started another 12 hour work shift, once I am home I will post detailed instructions, you dont use the registry, thats where issues are born, also when you follow directions from a ms partner keep in mind they have ms interest as well as there own in mind and not yours. I will also provide a link to s program that will show you exactly what that 20% is doing and its not what you posted not even what you think.
No. You ask the game for a bitmap that is 1.75 times native, but the game renders, in the first place, one that is 0.85 (or whatever) the size of that (of x1.75 - not of x1.0; Effectively 1.4875 native), and upsamples *that* to the requested 1.75, which is then passed to the HMD driver stack's compositor, for fitting to the native display and lens effect, possibly preceeded by a timewarp pass -- No initial downsampling, how ever that would even work.
There *is* resampling twice, with inherent softening of the image in both instances, but at no point are you degrading the resolution to below native (EDIT3: even with 1.75x0.65 you are at 1.1375 -- larger than 1.0), and the final downsampling is done at the stage that enjoys the conditions to make the most of any extra "source" resolution.
In this example, you'd get similar (a little bit more) resolutions throughout the process, using HMD Quality 1.5 and SS 1.0, ridding yourself of the one upsampling stage, for a crisper image. LOD and Mipmap bias should work the same in both cases (EDIT2: ...pulling in the same detail levels), but who knows how it differs from object/material to object/material, and between render layers...
Hopefully OpenVR will become a smoother experience, now that Valve have given in to popular demand, and have announced they will rework their reprojection to operate asynchonously (still only rotational, but with the forced 45Hz kickdown removed (EDIT: ...and without waiting for things to go wrong, before it "kicks in" a frame too late, but I am assuming that is probably what the "always on" option does already, albeit with less elegance))...
Last edited:
I've not played the beta (don't have a whole lot of time so just going to wait for 2.2 to land properly) but I've not had issues since I got my 1070. runs smooth as and haven't seen any of the shimmering like the OP since my upgrade. admittedly I'm also not running supersampling or anything else as what I see is awesome and I have no issues reading the text et al.
i7 6700k
Gigabyte 1070G1
16GB DDR4
Asus Z170
i7 6700k
Gigabyte 1070G1
16GB DDR4
Asus Z170
I ran SLI for generations and when VR went from Extended Mode to Direct Mode, SLI and crossfire were disabled. I think there must be some sort of confusion going on here. If what you are saying is true I can't believe Nvidia, Valve, Oculus, and Frontier would not mention that there is a manual way to add SLI while waiting for official support so we could brute force a solution. Also how are you getting FPS above 90 as that is the refresh rate of the screen and VR has V-sync on mandatory. You would have to hit 180FPS to see the frame rate go up. Just like when we drop frames below 90FPS it goes all the way down to 45FPS because of V-sync.
Its not an official fix, and im no better than them it is just a tweak off of another game setting that already has an sli profile not always perfect but works no less, before you trash me give it a try, is a prog from other gamers and constantly updated and tweaked and new profiles updated by other gamers. Find one that works for your system and adjust settings from there. Ive uploaded one of my game plays of ed on youtube showing fps ranging for about 120 to over 300 fps without my cards clocked, ill clock them tonight and capture higher fps and upload, even in stations my fps is 108-172 sometimes higher, i still have not figured out how to get everything to hook into the game without crashing the game but atleast you can see better performance, there are gamers/modders out there that are continually working to improve on games. My settings are all set to ultra, ill capture that also. Like I said, please dont be so quick to say that something doesnt work because you havent tried it or heard of it, the ptogram i am using has been around for awhile.
Last edited:
Anyone here wanna mail me their headset?
The main Question isn't if we can use SLI (using inspector profiles) but if we can use SLI while playing in VIVE or Oculus. I'm mid project (work), so I can't test myself quite yet, but the FPS doesn't add up to how VR works. VR is forced Vsynched to 45 or 90 fps, so hence the questions. If you are running it in DIRECT mode (really important that it is Direct and not Extended) and in VR headset. I'm not saying that what you are saying isn't truth, but I get confused by your reports as the most you can achieve with VIve or Oculus as 3d in ED is Native vsynched 90fps- there just ins't a possibility for higher FPS as far as I know.
Last edited:
SLI doesn't work with VR. Everyone should know that by now.
As for the OP, sounds like a weak GPU. Unfortunately, FDev's slow support for the Vive has resulted in a situation where only those with the latest GPUs can experience consistently good performance, and even then, setting have to be dialed back. In game I don't think it makes much difference to have some settings at Medium/Low instead of High, but it is a necessary component.
These are trade-offs the Rift doesn't have to make. It can get by with less horsepower. The visual "sweet spot" is also wider on the Rift making it more comfortable to look around without moving your head as often. For those with anything less than a 980Ti who's core intent is to play ED, the Rift is the only real option.
The trade-off here is that the Rift FoV is smaller (yea it is noticeable), godrays are extremely distracting and are everywhere due to the high contrast environment, the universe looks cloudy and a number of other visual effects look awful (smoke, the effects in a hyperspace jump, the light radiating off of stars), you get some visual warping when panning left to right (most apparent when menus are up), the tracking is not as crisp or precise as the Vive's (as expected) and the overall Rift image is not nearly as bright as the Vive's image. The Vive has none of these visual effects issues, the lens rings are far less distracting than the Rift's godrays are, the tracking is as good as you'd expect it to be, and the distortion/warping I see in my Rift (something I've seen many report on before) is not present at all in the Vive.
In my experience and on my rig (signature), the Rift offers the smoothest experience, with only the very ocassional hitch. It's also lighter weight and more convenient to take off/put on. The Vive has objectively more hitches along the way and takes a bit more time to "boot up". But outside of those hitches, I prefer everything about the Vive experience more. The brightness, color range, tracking precision, and other notes make for a better overall experience. Whenever FDev gets around to addressing the actual performance issues that seem to only effect Elite Dangerous in the Vive, it will be the best setup for ED. Until then, those who want a good experience with ED and have anything less than a 1070 (IMO, not even the 980Ti provides a consistently good experience in a Vive) should default to a Rift unless they plan on a GPU upgrade soon. Don't count on FDev to fix whatever issue is plaguing Vive + ED performance.
As for the OP, sounds like a weak GPU. Unfortunately, FDev's slow support for the Vive has resulted in a situation where only those with the latest GPUs can experience consistently good performance, and even then, setting have to be dialed back. In game I don't think it makes much difference to have some settings at Medium/Low instead of High, but it is a necessary component.
These are trade-offs the Rift doesn't have to make. It can get by with less horsepower. The visual "sweet spot" is also wider on the Rift making it more comfortable to look around without moving your head as often. For those with anything less than a 980Ti who's core intent is to play ED, the Rift is the only real option.
The trade-off here is that the Rift FoV is smaller (yea it is noticeable), godrays are extremely distracting and are everywhere due to the high contrast environment, the universe looks cloudy and a number of other visual effects look awful (smoke, the effects in a hyperspace jump, the light radiating off of stars), you get some visual warping when panning left to right (most apparent when menus are up), the tracking is not as crisp or precise as the Vive's (as expected) and the overall Rift image is not nearly as bright as the Vive's image. The Vive has none of these visual effects issues, the lens rings are far less distracting than the Rift's godrays are, the tracking is as good as you'd expect it to be, and the distortion/warping I see in my Rift (something I've seen many report on before) is not present at all in the Vive.
In my experience and on my rig (signature), the Rift offers the smoothest experience, with only the very ocassional hitch. It's also lighter weight and more convenient to take off/put on. The Vive has objectively more hitches along the way and takes a bit more time to "boot up". But outside of those hitches, I prefer everything about the Vive experience more. The brightness, color range, tracking precision, and other notes make for a better overall experience. Whenever FDev gets around to addressing the actual performance issues that seem to only effect Elite Dangerous in the Vive, it will be the best setup for ED. Until then, those who want a good experience with ED and have anything less than a 1070 (IMO, not even the 980Ti provides a consistently good experience in a Vive) should default to a Rift unless they plan on a GPU upgrade soon. Don't count on FDev to fix whatever issue is plaguing Vive + ED performance.
That's a good summary of the Rift issues and why I pick the Vive to play Elite despite them both sitting right next to each other on my desk.
I'd add that the Oculus software ie runtime/setup environment is absolutely terrible. Steamvr has lots of useful abilities to tune, fix and inspect many issues that are completely absent or broken in the Rift software. Oculus is filled with golden paths of dead ends.
.65*1.4 is working well enough for me but recently some kind of strange flickering has started that looks something like an overlay that has a raster line running out of sync with the rest of the display. It goes away if I load the map or sometimes just open another menu. Then it looks great for another 20 minutes...
bleh.
Look forward to the 1080ti, without Frontier actually rewriting the VR rendering pipeline it's going to take serious hardware to make it all right.
I stand corrected, thankyou good sir. Now I see the reason for the improved framerate. My bad, I got it the wrong way round.
I've actually played with reprojection forced off. I've had no problems with ghosting or nausea despite some other folks experience. (Keep in mind hover junkers and windlands both make me sick within minutes). when i turn reprojection on and crank up the settings going back and forth between high and low fps mode seems to create a lot of stutter... that said... with the new steam beta async reprojection update im going to experiment with that and see if i can find a better setting.
Last edited: