VR FPS (2.5.1.16543.355)

[sze5003]

So I’ll do a repair on my game and see if that helps anything, but I did take off and I’m still getting only 15-25 FPS. THis is quite frustrating as I’ve been jonesing for DCS for the last 5 months.

Have you tried what I suggested above? Having dcs rebuild the graphics sections by renaming your saved games folder to something else ?

 

That usually will resync everything.

[AMEDooley]

I’m not sure what that would do since it was a clean install. But I’ll try it.

[sze5003]

Ah I missed that part of your post. Something is seriously off if you are only getting those fps. Have you tested your gpu in other games to make sure it's performaning properly?

 

I can't think of what else it may be if a clean install was done, drivers all up to date, etc.

[giei]

Same FPS in 2.5.0 and 2.5.1 for me

[AMEDooley]

So I did what you suggested but it didn’t fix the problem. But the good news is I figure out what the problem was, it was my squadrons mission. I can do any other mission just fine, with 35-45 FPS with high setting so thanks for the help everyone, it was most appreciated

[muehlema]

Same FPS in 2.5.0 and 2.5.1 for me

 

 

Same for me. Same settings same frames

[Flighter]

Same for me. Same settings same frames

 

 

Guys, going from 2.5.0 to 2.5.1 with identical settings is not producing any noticeable difference in performance.

 

The whole issue is that 2.5.1 does not let you turn off Deferred Shading and the FPS penalty for that is gigantic (increasingly so with MSAA on x2 and x4).

 

Check what difference it makes using 2.5.0 and switching DS on and off (restart of the sim is required).

 

 

Cheers

[lemoen]

Switch MSAA off when using VR. Everything flickers either way.

[Flighter]

Switch MSAA off when using VR. Everything flickers either way.

 

lemoen, MSAA makes a hell of a difference on my system. Try on 2.5.0 with DS off, PD 1.5 and MSAAx4.

[sze5003]

Switch MSAA off when using VR. Everything flickers either way.

No flickering for me, I'm using a Pixel density of 1.5 on the Samsung Odyssey with mostly high settings. Without msaa in 2.5.1, the world just looks a bit more bland, there is no smooth shine as there is with 2x msaa. 4x makes it shimmer more but kills performance.

[Flighter]

2.5.1 update 1 no improvement... sad...

 

I have just installed and tested today's update (2.5.1.16987)

 

I am afraid that the miracle I was expecting did not happen... :cry:

Performance is identical with previous beta.

 

 

I am sad.

Edited May 11, 2018 by Flighter

[sze5003]

Yea I don't think there are any performance related updates here in this update.

[lemoen]

lemoen, MSAA makes a hell of a difference on my system. Try on 2.5.0 with DS off, PD 1.5 and MSAAx4.

 

I have a 1070 and a rift. MSAA 2x and off looks basically the same but the one is faster :D

[Hippo]

Well I bit the bullet and allowed the latest 2.5.1 update. IMHO, my experience in VR has been completely ruined.

 

When I test as I describe here, I used to get around 115 fps (in 2.5.0). Now with the same settings I get 50 fps.

 

If I turn off MSAA (from 4x), I get 100 fps, but it looks like sh1t.

 

I realise VR users are a minority, but I am now very annoyed. I have spent a lot of money upgrading my system, in the main for this game. The way ED just made the DS change on us without warning, causing a cut of > 50% of frame rate, is, I think, unacceptable.

Edited May 12, 2018 by Hippo

[Hippo]

Switch MSAA off when using VR. Everything flickers either way.

 

MSAA 2x and off looks basically the same

 

Well on my system, with my particular settings, MSAA off is an atrocious shimmering mess. 2x is a lot better, and 4x is considerably better than 2x. Unfortunately fps goes down the toilet.

 

When reading your comments, I wonder at how our subjective experiences can be so different.

[Flighter]

Well on my system, with my particular settings, MSAA off is an atrocious shimmering mess. 2x is a lot better, and 4x is considerably better than 2x. Unfortunately fps goes down the toilet.

 

When reading your comments, I wonder at how our subjective experiences can be so different.

 

Hi Hippo.

I cannot agree with you more.

I think people went for DF as it was the new kid on the block and did not compare/evaluate it properly.

Plus the priority in VR is the frame rate and the maximization of the perceived image quality (because of the low resolution of out HMDs).

These two things got a deadly hit from the new developments.

 

I tried last night to play on line in 2.5.1. I wanted to convince myself that there is some setting that is OK, even with less overall quality.

I am afraid that I was left in disappointment and frustration.

Cheers !

[Hippo]

Agree entirely.

 

To add to the frustration, I pre-ordered the F-18 assuming I had found settings which would work for me. This is no longer the case, and the sense of disappointment is enormous. I'm thinking of asking for a refund.

[sze5003]

Agree entirely.

 

To add to the frustration, I pre-ordered the F-18 assuming I had found settings which would work for me. This is no longer the case, and the sense of disappointment is enormous. I'm thinking of asking for a refund.

If you must use msaa keep it at 2x. I agree with you, performance in 2.5 was better. But I've always been on the beta branch for a while now.

 

What's odd is I seem to get about 45-55 fps with 2x msaa and higher settings than you with a pixel density of 1.5. Not sure what your specs are but it looks like you need at least a 1080ti to get playable performance with a decent look in VR. For me it's playable and seems smooth when I'm flying. I dont really know how to record fps because I'm using a Samsung Odyssey. With my occulus I could enable the tool tray and get the fps in my view.

[eaglecash867]

I tried the latest update to the Beta last night, and I'm with you Flighter. There is still no option to turn Deferred Shading off, and with AA on at all you only get slightly better performance than in the previous version of the Beta. Things seem smooth if you're looking straight ahead, but looking left or right in VR, everything is constantly jumping back and forth like one eye is lagging behind the other eye. Not to mention that Deferred Shading is just plain ugly, and the cockpit has gone back to looking like a cartoon. I can understand that they want to develop things in the sim to take advantage of newer technology and techniques, but I think it was a mistake to take the Deferred Shading option out of the settings menu.

 

My main gripe with the Beta, though, is the default position in the cockpit in VR. Now they have you sitting way too far back from the panel and HUD. So far back that its extremely difficult to keep the stick within reach so I can hit the VR re-center button I have mapped to the paddle switch once I'm finally far enough away and sitting high enough to set center at a more realistic distance and height.

 

Just to pre-empt any "Its a Beta!" comments, that is fully understood, and the reason for having a Beta being open to all users is so bugs can be reported and squashed more effectively. If we don't speak up about things we see and don't like, we're kind of defeating the intended purpose of an open Beta.

 

The really great thing about how they're approaching this now is that we can have both the Stable and the Beta installed without burning extra activations. We no longer have to worry about killing the whole thing with an update and having to wait for a fix. It lets the developers keep improving things, and lets us keep flying if they miss something. That was a brilliant idea! :pilotfly:

Edited May 12, 2018 by eaglecash867

[sze5003]

I tried the latest update to the Beta last night, and I'm with you Flighter. There is still no option to turn Deferred Shading off, and with AA on at all you only get slightly better performance than in the previous version of the Beta. Things seem smooth if you're looking straight ahead, but looking left or right in VR, everything is constantly jumping back and forth like one eye is lagging behind the other eye. Not to mention that Deferred Shading is just plain ugly, and the cockpit has gone back to looking like a cartoon. I can understand that they want to develop things in the sim to take advantage of newer technology and techniques, but I think it was a mistake to take the Deferred Shading option out of the settings menu.

 

My main gripe with the Beta, though, is the default position in the cockpit in VR. Now they have you sitting way too far back from the panel and HUD. So far back that its extremely difficult to keep the stick within reach so I can hit the VR re-center button I have mapped to the paddle switch once I'm finally far enough away and sitting high enough to set center at a more realistic distance and height.

 

Just to pre-empt any "Its a Beta!" comments, that is fully understood, and the reason for having a Beta being open to all users is so bugs can be reported and squashed more effectively. If we don't speak up about things we see and don't like, we're kind of defeating the intended purpose of an open Beta.

 

The really great thing about how they're approaching this now is that we can have both the Stable and the Beta installed without burning extra activations. We no longer have to worry about killing the whole thing with an update and having to wait for a fix. It lets the developers keep improving things, and lets us keep flying if they miss something. That was a brilliant idea! :pilotfly:

For the views all I did was copy my snapviews.lua from 2.5 stable and place it in the 2.5.1 directory.

 

To adjust your view in the cockpit use right shift+Ctrl and numpad keys 4, 6, for left right, * and / I think for forward and backwards. Save the view you want with right Ctrl+shift numpad 0.

[eaglecash867]

Thanks for the info sze5003! :D I was trying to find info on how to manually adjust the VR position, because I remember seeing that somewhere. Now I don't have to keep looking. Thank you, sir!

[pimp]

I have a huge performance boost in a way most of you may already be aware of. Normally, when I start on a new map, I create a startup mission file with a lot of static airplanes on the different airfields. I then use that file as a base to create my actual missions in SP. I did not realize those static objects effects the fps so much. So reducing the number of objects increased my fps tremendously. Even in NTTR map. Nellis was the worse where I was dipping into the high teens & low 20s, but now I'm not seeing anything under 45.

[D4n]

Wooooow just bought an RX 580 8 GB, these are my results (caucasus)...

in singleplayer I only get 17-23 fps when I start "M2000 missile combat", in multiplayer 14-17 fps on ramp (when M2000 warmed up) and 12 fps flying Mach 1 low over Krasnodar, using the settings you see in the 2 screenshots here

 

 

https://s9.postimg.cc/7ib50ot7j/Screen_180515_020339.png

 

 

https://s9.postimg.cc/gdbzbc019/Screen_180515_020851.png

 

 

Terrible. Needs optimization ASAP (or Vulkan API).

[MurderOne]

Turn your visibility to medium and msaa to x2 or off. I'm running a 1080ti and can't run msaa x4

[pimp]

^^ this