Warthog_Farmer

I completely disagree with the "ATW fixes everything" statement on page 1. I am tweaking away and generally sit between 40 and 90. If theres any action or low over towns I am in the 40s and for high level stuff it's usually higher. The difference, to me, is huge. Looking left and right quickly in the 40s results in a judder with slight double vision. The same can be said for low, fast flybys when you're holding short of the runway. The passing aircraft will look like it's drawn twice per frame as it passes - one slightly ahead of the other. It's not game breaking for me and I hope it becomes less of an issue as more optimisation comes along. But it may prove too much for some peoples stomachs if they are not already VR hardened. Like everyone else has said - I get MUCH more enjoyment using the VR in the sim than winning every fight. The presence, for the most part, is missing due to the frame issues... But that doesn't ruin the experience at all. It's still great being able to tell exactly how much clearance you have between your blades and his blades (in the Huey)

For your information the fix is not applicable to me. I never had "Let me choose one scaling level for all my displays" selected and I run "Change the size of all items" as the smallest setting available. 2560x1440 resolution on the monitor. I'll continue testing and when I get a second I'll try setting a common scaling setting less than 125% with that option selected...

I don't splodge on LATCH ON... I also don''t run any mods at the moment =[

I'll test your theory and report back. I think it happens a lot more frequently for me though!

I'll probably have a look. It can't be much more than using the commands from this and maybe a little jiggery-pokery to get the 3 position switches working for as many other aircraft as I can. Seems to be a little lazy that it isn't incorporated already on a lot of modules since the Warthog is a pretty common setup in these parts :p

Had a quick session of VA server there. Average FPS 45 with an occasional spike to high 80s - looks almost rhythmic (like a heart monitor) as if it's trying 90 out and doesn't like it so goes back to 45. 90% of the time it's at 45FPS pretty consistently.... CPU usage peaked at 55% with average mid 40%'s. RAM usage 11GB (16 avail) GPU temp fairly consistent 65-75 degrees with fan speed 40% as per EVGA Precision X curve. GPU Memory Clock 1253 solid GPU Memory Usage 100% constantly (6GB) So it's my understanding the GPU usage should be 100% as much as possible. Is there are thermal issue at 75 degrees that's causing the card to lock to 45FPS? I'd have thought the clock speed would have reduced if it was throttling. The temp target is set to 83 degrees in Precision X. Cheers :)

Hi guys... Quick question. I've noticed that the performance in my Rift has been getting slowly worse and worse - although I am becoming more used to flying about in lower FPS situations so the nausea isn't as bad.. Before I start playing with graphics settings and trying to tweak I thought I'd ask this quick question: I ShadowPlay most of my multiplayer with friends just incase we have funny moments. I ShadowPlay the "Desktop" and run a black image in fullscreen and then the Rift image is displayed in the middle. This is the best solution I've found to prevent the imaging being recorded in a weird, skewed, ratio... Anyway - GeForce Experience FPS counter is recorded in the top right of the DCS window. On playback I have noticed the FPS occasionally locks to 30 and will remain there for a few minutes. Other times I have noticed locking to 45 and, again, staying there for a while. I'm not too up to speed on how everything works but I am wondering if there is a V-Sync setting, or G-Sync setting or something that is interfering with DCS/Rift. It just seems unusual that the FPS isn't jumping around, as usual, instead it is solidly locked at 30 or 45 (The two figures I have noticed so far) I hope this makes sense.. I'm sometimes a bit crap at explaining things. Any help/advice is always appreciated :)

Thanks Squirrel.. I think we are on the same page but maybe I am bad at explaining... Say BST made us: Airbrake OFF Airbrake ON (ala FC3 aircraft) then it is impossible to code the speedbrake to work as per the A10C or this mod for the Tiger?

Man I wish I understood what all of this code means... I'll post this in hope of a little explanation/understanding to see if it's worth me learning to start messing with it... Is the 3 position only available because Belsimtek have left us with those "IN/OUT/OFF" and all we have to do is tell the sim: When Button X is pressed - run the command; when Button X is released - run this handy command that BST have implemented for us?

I get the yellow splodge and a yellow square, 8.1 with EVGA 980Ti. Run the CPU as fast as I can mind you so maybe it could be OC issue. Erratic in reproduction but I'd say, on average, it occurs randomly maybe once every 2-4 hours and need to restart game to restore original cursor. Mouse still works though when corrupt graphic..

Sacrificing the resolution for immersion is a no-brainer for me. And you get used to it after a while... Cannot go back to 2D/TrackIR...

#2 isn't a problem specific to this aircraft. All of them are bugged out. Been reported already in the VR sub which is highly recommended if you haven't already been.

This has always been noticeable for me. Pre and post VR. I could sit at Batumi and have over 100fps with my 4670k @ 4.5 and a GTX980Ti and then look north an immediately have a huge FPS drop... Down to 40-50. It's all to do with the rendered object count if my understanding is correct and is (and probably always will be) a problem with the game engine. I'm not entirely sure how, why or if that is accurate but it's what I have picked up from similar topics. With my Rift on I generally get about 40-50, occasionally when away from large towns I'll see 90: in heavily populated servers it can become a bit juddery and unplayable. Luckily I don't get sick from it but I'm sure it is very vomit inducing for some. As for your CPU - you say 4.6Ghz is 'not on the low side' but there is quite a bit more to a CPU than pure clock speed. I'm sure you would see improvements if you came up to a current gen system.

I can get Alt Hold to work... But it doesn't seem right. In level flight, about 180 speed units, and then flick it on via my HOTAS. The collective remains in the previous position (fairly high for fast, level flight) and the helicopter will pitch up wildly without gaining any height and without altering the collective. The helicopter will slow to about 140 and remain there in Alt Hold till the cows come home... Don't understand how, given the same conditions, the autopilot manages to fly it a lot slower and stay in level flight..

Me too!

I'd say the spacing indicates about 2020 for the new Warthog. Ties in with what was said by the TM rep for life cycle... Totally underwhelming in every way. Good job Thrustmaster :-| I was hoping to replace my Warthog throttle base as the right one (like many others) has become so loose I worry it will fall out one day (The left still has friction)

I'm not sure we're pessimistic.... It's more of a drive to make things better. I don't think many people aren't blown away by the possibilities of VR for our genre but the dream of better will always exist. Let's face it: the resolution is half of what we need and the performance isn't always tremendous, but that doesn't mean we're not happy to be where we are today. My opening post of this thread is for people to discuss how to get good performance out of the engine with what we have. It seems that no matter what your hardware it will often dip below the optimum frame rate for 100% smooth flight and we have to help work towards eradicating those dips if VR is to flourish in DCS. If you are able to fly totally smooth Huey flights then please, as the first post asks, share your system config and your graphics settings and let us know what your average and frame rate is in a built up town. Every little helps if we can figure out what's makes you different to those suffering the dips! As for pascal - I am hoping this will sort our problems but I am, in that regard, a little pessimistic ^_^ I have yet to see my GPU struggling with DCS on Afterburner

Will disabling threaded optimisations improve performance? I'm away from PC at the moment but any tweak is rather exciting. I had folk over flying an A10C last night who have never had a go of a flight sim to date. Then I took them on a recorded Huey track with lots of slow flying, fast and low flying and tail whipping into reverse flight - their VR virgin stomachs called it quits at that =]

Hey dudes and dudettes. We have our own forum now so we might as well use it. This is a continuation of a chat which got lost in the middle of the, now historic, Oculus mega thread. Rift/Vive/Other are free to join in the discussion. We are all one in this adventure. Is anyone here able to maintain ~50fps or greater consistently in the latest update? It doesn't matter what I fly, whether I fly alone or with AI, whether there is a war or not, whether I use mirrors or not or whether I turn everything to low or high... I really struggle to maintain decent FPS. Problem areas for me are built up areas. If I even look in the direction of them I will see huge frame rate loss and stuttering. I go from consistent 90fps sitting on the ground at Batumi to low 30s-40 when I look to the north. It happens even when the town is obscured by other objects such as trees. On the CV1 this causes very distracting stuttering as you move your head. I run a 4670k at 4.5GHz (no thermal throttling) and a EVGA 980Ti with DCS on its own 850Evo SSD. I assume this is a software optimisation issue as my hardware is fairly up to date (CPU is probably the weakest link) so I'm wondering if any clever people here have worked out a way to lessen the frame hit through a tweak or setting change. I don't remember this happening before the latest update - but I was running on the monitor so the frame drops may have been less noticeable. If you are having no issues with stuttering please post your rig and settings - and any things you have done which may have saved you from the stutter!

Don't be surprised if your comment is moderated. This thread is to discuss the Rift in DCS. It is not a support forum for the Rift recommended system requirements... Nor should people be discussing eBay prices with that policy in mind. I guess some slip through the net. I think you'd get away with it. Unless you need multi core performance though I'd switch to a 6700k (or equivalent at time of upgrade) to save a lot of money and have the current gen architecture. As you're probably aware... most gaming applications are still heavily influenced by a single thread so the 6 cores won't be doing you any favours for Rift (yet) which is perhaps why it's flagged.

This is a necessity. A gamechanging breakthrough technology which will most likely develop at a rapid rate. We should progress with it! The entire VR community should be able to discuss problems and optimisations in something other than a 700 page thread. VR isn't equivalent to a new joystick.. Only someone who hasn't been 'inside' could assume

This thread is too long to read... But I've just jumped over from the Rift thread. I am a CV1 user and the Rift head tracking never falters. It is always smooth and accurate. However - the image projected after the head tracking element will stutter when looking at or in the direction of towns. Take Batumi as the example - look north and it will reduce to 40fps and stutter. Look anywhere else and a solid 90 with smooth motion. If your head tracking is still smooth as butter and it's only the DCS generated world that's stuttering then don't think your kit is any further behind than the Rift with ATW. We're all in the same boat waiting on core engine optimisation for better, consistent frame rates =[

I get poor performance also when looking in the direction of towns. Batumi and look anywhere but north = 90fps locked... Look north and it drops to average 45 lows of 30. 4670k OC to 4.5 with 980Ti...

I'd take that gif with a pinch of salt personally. I take photos through the CV1 lens and it looks loads better on the phone screen after its finished with it. I can have the phone take both of those photos off the CV1 if I wanted to... I'd like to try a Vive as I still believe the rift is deliberately softened in the middle of the lens to reduce SDE (which is pretty critical for simmers).Luckily DCS is still playable with it but could have been even better! CV1 is pretty good though and I guess Vive is pretty good too. Just buy whatever one you want and help VR development! I can't wait to see where the tech goes!

Low! Various levels. 1024x768 if I recall correctly... Tried 1080... Tried inputting the rift native resolution. Nothing... I've just turned everything back up to high and get 90 pretty much locked when you're not looking in the direction of towns and cities (I think that's what is causing it) Will continue tweaking - but I've came home from work with a little bit of a headache and possibly even some eye strain hangover for last night so I'll take a break. Mig 21 cockpit feels really good in the Rift. it's also a perfect demonstrator for the fuzzy centre lens issue to see how many others report it vs those who don't. Have a look at the paper stuck in front of you (just under the HUD) both straight ahead and then with head titled forward (peering out the top of your FOV/eyeballs up). Can't wait till it's all patched and working 100%. Glad to have been proven wrong that the A10 HUD is pretty clear from the default position!