Andrimner

Hehe, ok, a bit embarrasing, but this might be solved. To find out whether the fans were running, I opened the cabinet, and sure enough, a piece of plastic foil was wrappen in both fans, which prevented them from running. Temperatures of 51 degrees when running DCS now (at least for the couple of minutes I tested), so I'm fairly sure this is solved. Thank you all for replying to this thread!

Ok, that makes sense, thank you. I can't say I'm noticing any noise at all, but I'll test again when I get off work tonight, and run GPU-Z as well. I'll check to see if it's running in silent mode (assume I do that in the Nvidia control panel?), any idea as to what could be causing it if that isn't it? The strange thing is that it started mid-game after a session of 1,5 - 2 hours on saturday (and that's after running at least 4 hours without issue on friday night), now it starts as soon as I start up the game.

Ok, I did this as the reinstalled finished. Then tried to launch DCS again with Furmark in the background. Same thing happened: Everything ran smoothly for about 1 minute, then severe lagging, and finally everything froze up. Furmark registered temps at above 90 degrees C and usage above 90 % when it froze (tried to screenshot, but had to hard reboot my computer due to the crash). So then I just ran Furmark and hit Benchmark P1440, and that gave me this: null Thanks for the reply. I'm not quite sure, I assume this is something I need to check by entering BIOS menu on startup? Couldn't find a clear description in the thread you linked to

Thanks for the reply. - I got the drivers from Nvidias site on thursday. Never touched anything since that - Not sure how to measure power demands in use, but the product says it need a 600 w supply, and I have a 700 w - Temps: Not sure how to measure them, but as the problem now shows up on startup, I'm fairly sure this isn't the issue. I've played hours without issue before, now it shows up immediately - Not sure how to run a stress test...

Hello all, Last night, I suddenly encountered an issue with DCS that rendered the game completely unplayable in VR. At the time, I assumed it was an isolated incident, so I just shut down and went to bed. But it turns out the issue still remained today. So, a little background info: I've been running this computer since 2018 (in norwegian, but the specs should be understandable enough): https://www.multicom.no/multicom-noox-i629c-gaming-pc/cat-p/c/p10639133 I've been playing DCS with an HTC Vive Pro for years without issues. Then, in the last month, I've made the following upgrades: - First I got an HTC Vive Pro 2 to replace the Vive Pro. This worked fine. - Then I added 16 GB of RAM - And finally, on last thursday, I replaced the 1080 GPU with a new RTX 4070 super So, I played DCS in SteamVR thursday night and friday night, without any problems (although SteamVR did crash on some occasions, which was solved with restarts). Saturday night worked as well, initially without any problems. But after several hours of gaming, the game suddenly started lagging to the extreme. I'm talking MUCH less than 1 FPS, the frame typically took several seconds to update, and eventually just froze up completely, and the image in my HMD just started "jumping around" randomly, as if I was moving my head erratically, although my head was perfectly still. Eventually, the game crashed, and SteamVR informed me of an "unexpected error". At the time, I thought nothing of it, and just went to bed, but when I tried to run a new session tonight, I was having massive issues just getting in to Steam VR Home. It either never launced, or launched with an EXTREME lag, and eventually just froze up. So I reinstalled SteamVR, managed to start DCS again as normal, and assumed everything was solved. But, 2 minutes into my next mission in DCS, the same thing happened again: Extreme lagging, and eventually everything froze up. So, I decided to try to uninstall EVERYTHING - Steam, SteamVR, every HTC Vive software, etc, and am currently in the process of reinstalling. While waiting for that, I'm googling the issue, and I'm finding several threads from about a year back from users with new RTX 40-series cards reporting similar issues, and the problem only being resolved when reinstalling their old GPU. Still waiting to see whether the reinstall will solve this, but I am not optimistic in light of the google findings. But I assume there's plenty of others RTX 4000 VR-users out there, any ideas what could be causing this and what the solution could be? Edit: Trying to test HTC Vive software while reinstalling results in the following error message: SteamVR could not be initialized for unknown reasons. (Error: Not initialized (109) (109)) I am, however, able to enter SteamVR Home as usual, which seems normal, Whether it will last or not remains to be seen when DCS is reinstalled again. Again: Not optimistic. SteamVR Version 2.4.3

Thank you

Ok, thanks, I'll try that. If this should happen again, is there a way to restart the engine in-flight?

It sputters, then completely seizes up. Propeller goes totally still I make sure to keep boost below 8 during normal flight. In combat I go higher, but the last time, I had turned down pitch until I reached about 2 200 rpm, with a low throttle. Didn't check the boost specifically, but as mentioned, throttle was in the lower half. Then I noticed four german planes which seemed like they were closing, so i maxxed out throttle, and increased pitch to about 2 800 rpm. WIthin seconds, the engine stalled.

Hello, I'm having the exact same issue, and while the fuel pump+pressurization resolved some of it, other aspects are still unresolved. In view of the advice on these forums, I tried switching on both the fuel pump and the pressurization switch as a part of my start-up routine. This led to the engine cutting off shortly after take off EVERY TIME (feeding from drop tank, not sure if that matters). So I went back to flying with these switches off, and only switching them on when the engine starts to struggle above 17 000 ft. That worked. However, I'm still experiencing unexplainable cut offs, although much later on. This is on the first sortie of the Beware-campaing: I'll typically switch switch on the pump and pressure as we approach 20 000 ft en route to the target, then the drop tank will empty out shortly thereafter, and I'll drop that. Then, the flight encounters german fighters upon returning from the target, and I usually get through the dogfight with the engine intact. HOWEVER, it will cut off on shortly after the dogfight, and I just can't understand why. The first time it happened I obviously overworked the engine, but this time around I kept a close eye on the temperature gauges which were both fine, kept my RPM well under 2 500, constantly checked that the fuel tank was still full. Yet still, as I was throttling up to escape some german fighters, the engine still cut off, with plenty of fuel left, and temperatures well below "danger" levels. I just can't understand why this happens. What could be causing my engine to cut off, when there's plenty of fuel left, and all temperatures are within range?