Discussion in 'News & Notifications' started by Christopher Elliott, May 1, 2017.
Any word on the fullscreen issue? I just noticed vsync isnt kicking in.
Low = Glare Effects
Medium = Glare Effects and Depth of Field
High = All Effects at High Quality
Ultra = All Effects at Ultra Quality
Depth of field effects just impact fps count on replays?
I would like to know more. Is there more effects in high and ultra, like godrays or ssao or something. Is low effects just glare at low quality? It's a tad vague Imo no offense. One thing I have noticed, the fps isn't massive drops between them, literally had no recognisable drop between high and ultra or even med for that matter.
I would love to see the vsync fixed vo, it's hard to bench stuff with tearing to. Cheers
I get away with low setting which is all I'd like
I really don't need dof although looks really great on still shots
Would perhaps like about only half of the bloom that low gives
Ok so i tested now with DX11 content all around and i started with HIGH on most settings (stock settings after deleted JSON), and i deleted CBASH and shaders. Result with triple 1080p monitors and GTX980, AMD FX8350, 8GB RAM. AA Level 2 (devs please put the actual value like 2x, 4x, 8x etc. Its easier to understand for us), and Post Process MED. with 9 AI in practice was 30-55FPS with an average of 40FPS.
Tested to set it back to how i had it in DX9 which was HIGH on the top settings and then shadows MED, Soft Particles OFF, Reflections OFF. It was better but still stuttery, and i noticed vsync is not kicking in so fullscreen is not working. It could have been smoother but maybe triples/multiview is messing fullscreen up. Not sure. Tried ALT+ENTER to get it into proper fullscreen but it doesnt help so it needs to be looked into.
Conclusion: even with DX11 content the performance is worse than DX9 at this time for me personally. I know you can do it though S397! Also, balance that blue tint guys. Sim looks great otherwise.
It a known issue Mate alone with v-sync not working and all the other issues people are having. Give em a bit of time and im sure we will have a update soon enough.
@2ndLastJedi Thanks, the fullscreen thing doesn't seem to have been discussed much so wasn't sure if it was an acknowledged known issue.
As I say the stuttering is only intermittent for me so no big rush for a fix yesterday here!
If you get onto discord there is alot of chat about lots of stuff that may not make it to the forum.
I have an issue with VR mode. I cannot access to this mode, I am staying in the theatre mode and when I did this manipulation to fix the problem : disable VR game theatre for rF2 in steam. I have some message when I go to the launcher : "rF2 does not support VR"
And the game launch without connection with the VR.
Anyone have an idea ?
Ignore the warning about not supporting VR, do a steam integrity check on the files and see if that fixes anything.
Exit SteamVR before starting the launcher. Then start SteamVR before clicking on single or multi player. rF2 will automatically start SteamVR when you click on single or multi player but there is a bug where you may lose FFB so best to start SteamVR first (but after launcher)
Wasted info to those who dont use discord or want it.
Edit: I meant the info on Discord not the post. The info posted here would be more useful.
Sorry for any confusion!
The check is successful, and I ignore the warning but my VR is still not connect with rF2..
I try in your way but sill no connection between VR and rF2
Are you sure that SteamVr is definitely shut down, only I get the error message you showed if I run the launcher with SteamVR running?
SteamVR most be activated BEFORE even the Launcher. But make sure that you set up the 'room' even for just sitting. Starting SteamVR after the Launcher can cause FFB to malfunction. And yes you get the error, ignore it.
This is what I do:
Activate the rift
Press single player
Make sure in your video settings VR is ticked.
Interesting. If I let rF2 start SteamVR I get no ffb. If I start Steam VR manually after the launcher all is fine. If I start SteamVR before the launcher I get the error, I guess I could just ignore that then?
Well that's pretty obvious and useful . Thanks .
Separate names with a comma.