The_Bullet_Chef

Hi, After much troubleshooting, the COMPLETE fix for me was related to my XMP profile. I rolled back my RAM (32Gb DDR4) from 3600Mhz to 3300Mhz and since then have had no crashes with DCS or MSFS... Hope this helps...

Hey guys, Thanks for your feedback - after days of troubleshooting and pulling out my hair, I've found the cause and seem to have nailed it. I plan on writing up a detailed explanation about the resolution this evening in the hope of helping anyone else who may be suffering the same symptoms. Cheers..

Hey guys, Thanks for your feedback - after days of troubleshooting and pulling out my hair, I've found the cause and seem to have nailed it. I plan on writing up a detailed explanation about the resolution this evening in the hope of helping anyone else who may be suffering the same symptoms. Cheers..

Hi 'nobuttons' yes, I have had that set to 'OFF' from the start... Thanks anyway..

Hi guys, I’ve tried several Stress / Thermal tests all on a continuous loop with no issues. System is stable. It’s my same PC setup I’ve run for over two years with no stability issues. The only new changes have been the 3090 & Reverb G2. If the G2 is plugged in (using it or not) then I’ll get the BSOD at some random time. Memory constrained..? I assume you’re pulling my leg given the wink I’ve seen lots of Google / Reddit activity with the G2 paired with AMD products, but mine is Intel & Nvidia. It’s got me beat so far... Ahhh - I see what I did there... Whoops. Thanks for noticing

Hey guys, Thanks for the suggestions... OVERCLOCKING - Yes, I run the standard XMP profile with a very basic 4.8Ghz OC (Core Voltage @ 1.3v) that has been constantly stable under any conditions over the last 2 years. I will try 'optimised defaults' but given how stable my system has been, I don't hold much hope that that is the issue REVERB G2 - It is brand new, and been doing this since purchase. I've seen all the posts on Reddit & everywhere about the error 4-1, with Blue Flashes & then black screen. I've never had that, it's always a full system BSOD. If I forget to plug in the headset DP, then I see the error 4-1 which immediately rectifies when I plug in the DP. I have triple checked all connections. EXTERNAL USB 3 HUB - No, I have not tried this option yet. And will definitely purchase a powered external hub in the hope that it fixes it.... *** Thanks for all & any suggestions, they are appreciated ***

Hello DCS community... May I please request some assistance from anyone who has an idea about VR - 'Blue Screen of Death issues'...? Any ideas or help would be greatly appreciated. In short, I'm trying to troubleshoot the reason why using my Reverb G2 causes the dreaded 'Blue Screen of Death' 99% of the time I use it with DCS (and I think any other title). It can be 3 minutes after commencing a flight / mission, or 20 minutes - the timing is random. *** Further to that, I can be playing using the monitor (2D), and if the Reverb is simply plugged in (Display Port, USB 3 & Power Adapter) even without WMR & Steam VR running, then DCS will still BSOD at any random time after starting to play *** SYMPTOM: - Blue Screen of Death with varying error messages, causing a reboot of the PC - Timing can be at any stage of gameplay (2 minutes or 30 minutes) - I can play DCS all day long using the Monitor, but if the Reverb is plugged in & idle in the background (even without WMR or Steam VR running) I'll still get the BSOD after a random amount of time BASIC SYSTEM SPECS: - i7 8700k - water cooled - 32G 3600Mhz DDR4 RAM - ASUS Strix ROG 370-G Motherboard - Gigabyte RTX 3090 OC Edition GPU - Corsair RM-1000W PSU - Windows 10 - 20H2 TROUBLESHOOTING SO FAR: - Updates Updates Updates! Windows 10, BIOS, latest Nvidia drivers (clean install after using DDU in Safe Mode) - Re-Rack of GPU - Thorough check of all PSU wiring & plugs (GPU is using two seperate PSU Cables / Sockets) - 100% Stress / Thermal testing (using both AIDA64 and Superposition) GPU & CPU temps are quite good with no issues. - Plugging the Reverb USB into different USB 3 ports - Plugging the DP Cable into different GPU DP ports - Device Manager - USB Power Management Tab, preventing any / all of them from 'saving power / powering down' *** Am I missing something basic? May I please put it out there to anyone that is more 'Hardware Tech Savvy' or has seen this before? Any ideas or help would be greatly appreciated *** Cheers...

Hello DCS community... May I please request some assistance from anyone who has an idea about VR - 'Blue Screen of Death issues'...? Any ideas or help would be greatly appreciated. In short, I'm trying to troubleshoot the reason why using my Reverb G2 causes the dreaded 'Blue Screen of Death' 99% of the time I use it with DCS (and I think any other title). It can be 3 minutes after commencing a flight / mission, or 20 minutes - the timing is random. *** Further to that, I can be playing using the monitor (2D), and if the Reverb is simply plugged in (Display Port, USB 3 & Power Adapter) even without WMR & Steam VR running, then DCS will still BSOD at any random time after starting to play *** SYMPTOM: - Blue Screen of Death with varying error messages, causing a reboot of the PC - Timing can be at any stage of gameplay (2 minutes or 30 minutes) - I can play DCS all day long using the Monitor, but if the Reverb is plugged in & idle in the background (even without WMR or Steam VR running) I'll still get the BSOD after a random amount of time BASIC SYSTEM SPECS: - i7 8700k - water cooled - 32MB 3600Mhz DDR4 RAM - ASUS Strix ROG 370-G Motherboard - Gigabyte RTX 3090 OC Edition GPU - Corsair RM-1000W PSU - Windows 10 - 20H2 TROUBLESHOOTING SO FAR: - Updates Updates Updates! Windows 10, BIOS, latest Nvidia drivers (clean install after using DDU in Safe Mode) - Re-Rack of GPU - Thorough check of all PSU wiring & plugs (GPU is using two seperate PSU Cables / Sockets) - 100% Stress / Thermal testing (using both AIDA64 and Superposition) GPU & CPU temps are quite good with no issues. - Plugging the Reverb USB into different USB 3 ports - Plugging the DP Cable into different GPU DP ports - Device Manager - USB Power Management Tab, preventing any / all of them from 'saving power / powering down' *** Am I missing something basic? May I please put it out there to anyone that is more 'Hardware Tech Savvy' or has seen this before? Any ideas or help would be greatly appreciated *** Cheers...

Hello all, This may be a very easy question... ** I have NotePad + + and am versed in modifying .LUA files ** Is there a way to 'properly' modify the F/A-18c DDI display 'sharpness & colour' so that it can pass the MP Integrity Check - if at all possible For the stroke thickness of the text in the DDI's the path is: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MFD_strokesDefs.lua For the colour of the text in the DDI's the path is: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\materials.lua (refer to lines 27, 28 and 29) I don't know enough about editing to make sure that my .LUA modifications will pass the IC.... Thanks in advance for any help or suggestions Cheers.

Yes - that sounds like it. You make a good point, being that the carrier was moving for me too. I'll try a quick mission with a Static Carrier and see if it happens there.

When spawning on a CAT (either F/A-18C or F-14B) in the new Supercarrier module, the Deck Crew around my Catapult looking after my aircraft are all simultaneously 'Jittering' laterally at what looks like 20Hz...?! Has anyone else experienced this. I'm running a pure installation with no mods. Thanks in advance.

Thanks all, I'll have a look at your ideas and report back my results. It's very much appreciated.

Hi all, Due to TrackIR 5 (and it's polling rate of 120Hz) I have to lock my FPS at 60 (because 120fps is unachievable in DCS) - and 60fps in an achievable derivative of 120. I achieve this by using 'Nvidia Inspector' locking DCS to 60FPS using the 'Flip Metering' method. ** NOTE - my normal average FPS without locking them are around 80FPS *** This eliminates that 'jittery condition' when panning around, and it's quite smooth. However, this only works when the FPS are dead on 60FPS. My question - I notice with the FPS counter (Ctrl - Pause) that the FPS never seems to stay perfectly on 60FPS, rather every couple of seconds etc, it will jump to 72 (for a split second) then back to 60, then 59 (split second), or 62 (split second) etc etc back to 60. My Rig seems capable of maintaining 60FPS but it appears there's something in the background (every couple of seconds) that seems to confuse (momentarily) the FPS lock. Does anyone have any better experience on how to completely lock 60FPS...? Thanks in advance for any assistance. My System: i7 8700K @ 5.0ghz Nvidia 1080ti 1TB SSD m.2 16GB @ 3200mhz 3440 x 1440 G-Sync TrackiR 5 Thrust Master Warthog HOTAS MFG Crosswinds

Thanks very much for the feedback. Nice to know it's not something misconfigured at my end. Cheers...

Hello all, Anybody else notice that when switching to F3 'Fly-By' view, there's about a 1 second delay before hearing the sound? *** I'm not talking about Supersonic Flight because it happens during normal subsonic flight *** The F-14 is the only module that's doing this.... My other aircraft don't have this sound delay... However when already in F2 'External View' then switching to F3 'Fly-By' view, there is no sound delay.... Weird.....

Ha..!! Your description literally made what I was just drinking come out my nose..!! :megalol: *types this while wiping Orange Juice off the keyboard*

Thanks for the clarification... I wasn't sure if the Laser Mavericks were able to be 'slaved' like that. Cheers...

Hello all, I may be jumping the gun here.. I noticed in Wags' tutorial video for TGP usage with Laser Guided Mavericks, that the Laser Maverick slaves over to the Target Position when the TDC is depressed. This happens before the 'trigger or laser' is fired...? I was just wondering how the Laser Maverick does this? Does the TDC depression momentarily fire the laser for the seeker head to 'see' and 'slave' over to the Target position..? Thanks in advance for any clarification... Cheers

Yes, I remember reading that somewhere... However it does not explain why the Carrier Runway Lights are sometimes ON, sometimes OFF in low light or low visibility conditions.... It appears very random since the 2.5.5 update

Hello all, Anyone else noticed that the Stennis Runway lights turning on (low light or fog) is a little random since the 2.5.5 update...? I'm not doing anything different since the update; (1) Still tuning the Stennis (2) Still stating inbound (3) Now getting the new ATC Comms stating BRC etc. Long story short, the same simple ME mission in low light and fog, has the carrier lights on sometimes, and off at other times...?

SOLVED Each scale range between each of the scale ‘dashes’ on the left side of the DDD is always a ‘600 knot range’ regardless of ASPECT switch position. The total ‘closure differential spread’ will always be 2400 knots. The 0 position actually moves up or down to the next dash depending on ASPECT switch position. For example, with the ASPECT switch in TAIL, the ‘0 knots’ closure point moves up one to the dash above the middle dash, meaning that the 3 gaps (or closure ranges) below this new ‘0 point’ are (0 to -600 knots) (-600 to -1200 knots) & (-1200 to -1800 knots) and the single gap (or closure rate) above this new ‘0 point’ is (0 to +600 knots) Hope this helps others out there. Hello Developers, May I please get some clear clarification relating to the 'ASPECT' Switch position and its relationship to the DDD Target? The quick scenario I set up was as follows; Head to Head with the 'enemy' aircraft, with the 'enemy' aircraft speed at 250 knots. Below I attached 3 quick successive pictures of the DDD in the scenario described above, with the ASPECT Switch in 3 different positions (1) BEAM (2) TAIL (3) NOSE. I am interested in the RAW DDD Data in the PD-Search Mode. The manual states the following; "The display shows closure rate vs the ground (as if own aircraft was stationary) as opposed to relative closure rate." "The operating range of the doppler filters can also be configured by the ASPECT switch on the same panel, NOSE sets 600 knots opening to 1 800 knots closing, BEAM sets 1200 knots closing to 1200 knots opening and TAIL sets 1 800 knots opening to 600 knots closing." My question is; (1) That this only seems to be true when the Switch is in the 'BEAM' position, as the Target is clearly shown to be closing at approx 250 knots (2) That when the Switch is placed in the 'TAIL' position, the Target is now indicated as 'closing' towards me at approx 400 knots (even though his actual speed is still 250 knots, and 250 knots would fit into the scale of the 600 knot closure rate per TAIL Switch position) (3) That when the Switch is placed in the 'NOSE' position, the Target is now indicated as 'opening' away from me at approx 160 knots (even though his actual speed is still 250 knots (towards me), and 250 knots would fit into the scale of the 1800 knot closure rate per NOSE Switch position) * I have made a BLUE mark on both the TAIL and NOSE pictures to indicate where I would have assumed the Target closing DOT would be * ** To preempt, I'm not confused with the 'closure scale' on the right side of the DDD, as this is used when an STT Lock is made and clearly shows 'total closure rate' with the target - and works as advertised... I'm looking forward to some clarification.. Thanks in advance

Hello, As far as I know this is a DCS thing and not related to the F-14. It's to do with the way the replay data is logged in the actual gameplay. If you want to record a carrier landing and watch an accurate replay, I just have the carrier sitting still in the water and avoid having the mission too complex or long. And avoid speeding up the replay any more than x2 Hope this helps...

Hello all, Can someone else please try this to confirm a possible BUG...? Multiplayer (actual player in PILOT and in RIO seats) - Free Fall Bombs (Mk82's - Mk83's etc) - 'Computer Target Mode' Issue appears as follows; (1) Simple Bombing mission - Simple ground target set up (2) Correct Munitions, Qtys, Intervals, Fuzes, Stores Positions, Ripple / SGL etc etc selected by RIO (3) RIO sets mode to 'Computer Target' (4) PILOT selects A/G Mode & Master Arm (5) Bomb Free Fall Line & Flashing Diamond Appears on HUD (6) PILOT is able to slew Diamond Up & Down (7) [bUG] When PILOT selects 'Target Designate Switch' the Diamond DOES NOT stabilise on the selected ground point, but instead continues flashing, moves down the free fall line a bit, and remains stuck on the Bomb Free Fall line *** Note, I play the exact same mission and scenario in Single Player Mode - switching between the Pilot and RIO and it all works as it should, no BUGS. It appears to be a multiplayer thing? ***

*** AUTOPILOT TEMPORARY FIX FOR THIS CURRENT VERSION *** Hello all, After much playing around with this issue, I've found what appears to be a temporary fix until this BUG gets sorted in the next update. When I started this thread I had a button bound for Autopilot 'ENGAGE' and a separate button bound for Autopilot 'DISENGAGE or OFF' and the behaviour I described was consistent every time (I'm using a Thrustmaster Warthog) Last night I bound the F-14 AutoPilot 'ENGAGE' Switch to an actual 2 way Toggle Switch on my Thrustmaster Warthog by selecting the option in bindings - 'Autopilot ENGAGE, else OFF' (forgive me if the binding terminology is not exact, I'm away from DCS at the moment but I'm sure you get my drift) and now when I disengage the AutoPilot, it is properly disconnected and the aircraft controls are back to normal & trim works etc etc Hope this helps...

Hello, I noticed this too - thought I was missing something... Hence I've just come on the forum to find out some more info... Keep us posted of what you find out.. Thanks