I have to concur with the previous poster, your numbers are way off. Most likely a genuine misunderstanding on your part or just complete fantasy.What would I gain from lying. And no its not a NASA supercomputer.
7700k @ 5ghz
1080ti @ 2025mhz gpu 5508mhz memory clock
2 x 500gb 960evo one for os one for gaming
32 ddr4 ram @ 3000mhz
In what way would you have me prove it? I have not made any tweaks to the graphicsconfiguration.xml
That makes more sense, but I would advise, strongly, get rid of any out-of-game settings and go with 1.5x HMD image quality and 1.0x supersampling. Will look fantastic and you should get 45fps+ in stations (you have ASW on anyway)Damn it as much as it pains me to say this I have made a mistake. I set another game in my profile list to 2.5 and then went into the game and input those settings and thought everything was peachy. After reading your post and then posting my reply I went to check myself the in game settings I gave were correct but the 2.5 in the tray tool was actually set to 1.5. I did however set it to 2.5 for elite dangerous set in game supersampling to .75 and hmd to .75 and I am getting 90 FPS in stations. I'm working out a way post a screenshot of some sort. I'm sorry for my mistake I did not mean to deceive anyone.[noob]
Thanks I'll give it a shot. But I can always tell when it drops to 45fps. It doesn't make me sick or anything its like a stutter or something. Thank you again sorry for the rigmarole. How much does a case of beer cost where you live?That makes more sense, but I would advise, strongly, get rid of any out-of-game settings and go with 1.5x HMD image quality and 1.0x supersampling. Will look fantastic and you should get 45fps+ in stations (you have ASW on anyway)
It's a kind of warping that happens when straight lines cross other stuff, but I find it still so important to maintain that crystal smoothness of ASW. When you come towards and then around a planet up close and you see it stuttering, nothing more immersion breaking, even the warping doesn't break the immersion as much.Thanks I'll give it a shot. But I can always tell when it drops to 45fps. It doesn't make me sick or anything its like a stutter or something. Thank you again sorry for the rigmarole. How much does a case of beer cost where you live?
As far as I am aware, the DK2 is not recognised as a separate monitor anymore and hasn't been for some time.I'll ask it here then.
I'm thinking about getting a used DK2. It's a price thing and I don't think my rig would comfortably run a CV1 anyway (GTX 970 Asus Strix, 4th gen i5 4460 3.4 GHz, Kingston Hyper Fury X 8GB DDR3)
Is it worth getting if Oculus prevent support of the DK2, or are there workarounds? As you can tell, I on't know what I'm talking about, but I can learn to tweak (built a HMD a couple of years back with a Nexus 7 and Trinus VR), so as long as it's possible to run, I'm happy to give it a go.
I think the OR is recognised by the PC as another monitor. But without Oculus support, would the screen fire up as it's hooked up via HDMI, or would it simply not switch on. Because (started a sentence with 'because', that should start a storm) if the screen works and motion can be detected with other tracking devices (which I have), then it should be good to go.
I've looked at a few AIO' HMD's, but I'm still keen on the DK2. I don't get motion sick, so lower frame rae isn't an issue.
TLDR; Ca\n the DK2 still operate without official support/drivers
Asus GTX 970 would be fine for CV1, not 100% sure about the cpu tho ... my 970 was fine with an i5 4690.I'll ask it here then.
I'm thinking about getting a used DK2. It's a price thing and I don't think my rig would comfortably run a CV1 anyway (GTX 970 Asus Strix, 4th gen i5 4460 3.4 GHz, Kingston Hyper Fury X 8GB DDR3)
Is it worth getting if Oculus prevent support of the DK2, or are there workarounds? As you can tell, I on't know what I'm talking about, but I can learn to tweak (built a HMD a couple of years back with a Nexus 7 and Trinus VR), so as long as it's possible to run, I'm happy to give it a go.
I think the OR is recognised by the PC as another monitor. But without Oculus support, would the screen fire up as it's hooked up via HDMI, or would it simply not switch on. Because (started a sentence with 'because', that should start a storm) if the screen works and motion can be detected with other tracking devices (which I have), then it should be good to go.
I've looked at a few AIO' HMD's, but I'm still keen on the DK2. I don't get motion sick, so lower frame rae isn't an issue.
TLDR; Ca\n the DK2 still operate without official support/drivers
With 16GB of ram, you might try turning off the pagefile entirely. I've run with no pagefile for years, without incident. Windows will use the pagefile for many non-intuitive things that I found to be unneeded and, in my opinion, just gets in the way. Give it a try!Needless to say, once I’ve changed the pagefile config, the performance have increased greatly.
Fly safe commanders…
I do not have a RIFT or a Vive but operate a PiMax 4K and I operate it in Elite at 60FPS at 1920 or 1600 (depending what I have going on in the background) but my rig is not as powerful as yours and the rendering and sound is without fault - with no venetian blind effect:Hey guys, pretty new to Elite and the Rift.
I've been playing with it at 45fps most of the time. I haven't really noticed any problems with this except maybe the menus in the cockpit sometimes flicker, is that ASW/45fps? It's not a problem if so.
Is there any detriment to using Elite at 45fps in VR? It feels smooth to me.
What settings really affect the FPS?
I have a 1070gtx
16gb Ram
4690k @ 4.3ghz
My settings. Some may seem odd as I was experimenting. I really struggle with the stations looking a pixelly mess until you're up close. Is there any setting to combat this? I'd rather them not be sharp at distance if it means no odd pixel flicker.
http://i67.tinypic.com/4kvipt.jpg
Cheers
If you're seeing exactly 45fps then that will be the result of ASW throttling the game because it's not able to hit 90. In this case the game generates 45fps and ASW then generates in-between frames to simulate 90fps. It does this very well on the whole and generally you should be fine. The only thing you might notice (indeed, it sounds like you have) are the edges of menu interfaces (particularly station menus) going a bit "wobbly" occasionally.Hey guys, pretty new to Elite and the Rift.
I've been playing with it at 45fps most of the time. I haven't really noticed any problems with this except maybe the menus in the cockpit sometimes flicker, is that ASW/45fps? It's not a problem if so.
Is there any detriment to using Elite at 45fps in VR? It feels smooth to me.
I believe the following settings are the particularly GPU heavy computations that will noticeably affect FPS.What settings really affect the FPS?
This is genius. Thank you so much for posting this. I just got my Rift yesterday and immediately ran into this problem. It was unplayable. I am running an i7-3820 with 16GB RAM and a GTX1080 SC2 card, and I found that I had to share the CPU cores equally between ED and Oculus as follows, so I could have the graphics maxed out and not get jitters even on a planet surface:Hey all- I stumbled across a nifty Oculus tweak, related to general smoothness. This is not going to improve your FPS or help out in RES (I don't think) - but for me it seems to have removed a minor but very visible annoyance: random minor hesitations/stutters. I'm curious to see if anyone else can give it a try to see if it improves the experience.
OK... Little backstory: As you may know, the Oculus runtime has been getting updates related to room tracking with multiple sensors. The current non-beta (1.13) seems to have introduced some rather bad bugs, apparently related to those of us using only 1 tracking sensor. See:
https://forums.frontier.co.uk/showthread.php/340565-Oculus-1-13-Update-anyone-having-tracking-problems?p=5339689
https://forums.oculus.com/vip/discussion/comment/512105
The Oculus tracking problems seemed to be related to high CPU usage.
So... I tried to use process affinity to pin the Oculus runtime to 2 cores, and the ED client to my other 6 cores.
And BINGO! Tracking issues gone!
But THEN I noticed that the entire VR experience seemed noticeably smoother - like magic!
Ok - so now it's your turn... Anyone want to give it a try to see what happens?
I pin
- OVRServer_x64.exe to cores 7-8
- EliteDangerous64.exe to cores 1-6.