baylor703

I've noticed that the oil pressure on my 109 will slowly drop to 0 while in flight. It's like a consistent, steady "leak", and will happen slowly over the course of 20 minutes or so. It seems to have no effect on the engine or performance- the gauge just goes to 0. Is this a bug?

I get the exact same spikes- regardless of whether it is 2d, vr, various settings etc. I've tried literally every fix. The last thing I've seen was some random post where someone had an nvme drive with no dram, and switching to an ssd with dram fixed the issue for him. I'm about to try it myself.

I'll check it out I'll check and see. I've disabled all startup programs and my CPU usage usually sits about 1 or 2% when not running DCS. I've noticed that lowering textures helps with overall frames, but the frame spikes seem to happen regardless. Smooth for 3 seconds or so, then a major spike. Repeat indefinitely. Settings make no difference, and it will do it even when the game is paused. The spikes do not occur in the menu screen. I have an nvme drive and set preload to max.

Appreciate the response, edmuss. I have all LED RGB off. I run through openxr. There is plenty of headroom. Reprojection is off. I have absolutely no idea what could be causing this. It seems like I've scoured the forums and found virtually every possible fix and nothing has worked. Doesn't matter if the graphics settings are the lowest or highest possible- constant frame spikes and micro-stutter. Here's a vid with parameters shown. I've noticed it tends to get worse the longer the mission runs. It occurs whether I run in VR or 2D.

Recently got a new PC and everything runs great except DCS, including other sims. I've run through literally every tip I could find to fix these frame spikes. The game will run like butter, with plenty of headroom, but a major spike occurs every 4 to 6 seconds. It only lasts a split second, and visually it almost looks like the game is going "back" a frame or two and then jumping forward. An interesting observation is that it only starts once you're about 30 seconds into a mission. You can load directly over a city, high traffic, clouds, etc, and there are no spikes for half a minute. Then it starts. Also interesting is that it happens whether the game is paused, or un-paused. In the pics provided the game is paused. On a side note, with the new FPS menu, is the green line the GPU and white CPU? PC Specs *using reverb g2: -RAM: VENGEANCE® RGB RT 32GB -PSU: Super Flower Leadex III 850W 80+ Gold -MOTHERBOARD: ASRock B550M STEEL LEGEND AM4 -CPU: AMD Ryzen 5 5600 -GPU: MSI Ventus GeForce RTX 3080 12GB -NVME: Team Group MP33 M.2 2280 2TB Methods attempted: -disable hotplug, HAGS off/on, game mode and dvr mode off and on, pre-rendered frame adjustments in nvidea cp, low latency on/off, disable all unnecessary startup apps on windows start, Set physx in nvdia cp to GPU controlled and not cpu, Made exceptions for Exe and folder in windows security (not running avast/malwarebytes), locking and unlocking frames, 60hz mode vs 90hz, creating 32gb page files, disabling fTPM in bios (re-enabled after it didn't work), different outlets, different usb ports for hmd, deleting all shaders, running openxr vs steamvr, latest driver and bios for motherboard, disable track writing, allowing a 100gb shader cache in nvidea cp, vsync off, running in high performance mode... etc

Did you fix the ram air issue? grafspee's suggestion made a tremendous difference for me. I was constantly riding the envelope at alt- to the point of barely being able to turn. No longer. EDIT: You're in a spit, my mistake.

Fixed the ram air by modding the .lua as suggested in the thread. That needs to be fixed asap- can't believe it has been going on since April. It's exasperated by the fact that it's paired with a working animation, because unless you know specifically what to look for, you'd never know anything was wrong.

So, if I'm understanding correctly, engine wear is tied to manifold pressure rather than throttle position. Thanks. I'll have to look into the ram air issue. It is tied to a button on my stick, not an axis. It will either go full forward or back. It does feel like enemy fighters will get about a time and a half the turn rate I'm getting. In other words, they can use about a time and a half as much stick input, where I will get an accelerated stall at two thirds of what they are using.

I have good experience with ww2 birds across the two major titles, so this is a bit embarrassing, but I have been playing mp in a server where you may escort at very high alts of around 30k feet, and am having trouble. In the past I played mp only on the other one, and high alt fights simply didn't happen. DCS is a real adjustment. I know that engagements tend to happen in "slow motion" up high, that you have to be much gentler on the stick etc, but I can't even come close to competing at altitude flying a plane like a p51 or p47. If I get into a turn fight with a luftwaffe plane at those alts, they are basically on my six by the first circle, even if our energy states are the same. I feel like pulling any on the stick causes accelerated stalls, while others can get much better turn performance, albeit not as good if they were lower. I'm also, due to mainly playing the other sim, embarrassingly ignorant of how engine management works at high alts, and this may be related to why I am having issues. As you climb and manifold pressure drops, is engine wear modeled according to manifold pressure, or how hard you are running the throttle? For instance, let's say that I broke the wire and was running WEP on the throttle, but my manifold pressure could only reach 61 at that altitude... is that the equivalent of running military power (15 mins), or war emergency power (5 mins)? Or let's say I pushed the throttle all the way up to the wire, but my manifold could only reach 46. Would I be running max continuous?

This is the best mod I've ever seen for DCS in VR. Spotting ground targets, and identifying planes are now possible in my rift s (I just use opencomposite and hit "run via steamvr" when I hit play). Before, I couldn't id a target until I was well within firing range. Now, I can identify much further out.

Have you tried resetting your Nvidia control panel settings to default? I know you didn't make any changes, but could try it.

I think upgrading to the G2 will be worth it. In the meantime, I've found this: https://github.com/fholger/reshade/releases/tag/openvr_alpha2 If you place the contents in the bin folder, and run via SteamVR (required), the difference is dramatic. Particularly with colors. Identification isn't perfect, but it's much easier. The end key toggles the effect on/off, and the home key allows you to make changes on the fly. I find a 2.0 gamma works well with the rift, with the reshade. Definitely not a placebo effect. I can identify planes much further out. I haven't played with the sharpness too much yet- but 1.3 seems to be good for now.

Yes, even at the highest zoom it can be tough imo. Unless the angle is right, identifying shapes and outlines you could easily spot on a monitor are tough. A big part is the colors as well. For whatever reason, maybe a lack of contrast? I appreciate the input. I've heard about the sweet spot, but can live with it. I had an original rift and it had a poor sweetspot as well compared to the Rift S.

I'm considering upgrading from a Rift S to a G2. Has anyone else made this jump? The primary reason is for identifying targets. With the Rift S, it feels very difficult to CAP in multiplayer, not because spotting is bad (it's actually really good imo- I fly warbirds), but because identifying targets is so dang difficult. I often can't tell what a plane is until I am well within firing range. Even recognizing invasion stripes is tough in the Rift S. Can anyone who has made this upgrade comment? Does identifying become a bit easier with the G2?

I have no idea why, but I've found that if I flip only the oil rad full open and keep the other automatic, coolant rarely overheats. I know that sounds crazy but it works. I prefer it that way because there seems to be less drag.