Lancer68

I'm fine with a bit of fun. But.... Heads up on this would have been nice so we could have turned it off before finding it in game. I like my experience to be more of a flight sim and not a flight arcade game. An easier way to turn it off is a must if this stuff is going to be in the game. An option in settings rather than downloading a file and putting it into saved games folder is not ideal. I get the humor and dont want it to go away. I just dont appreciate the way the implementation of it occurred.

F-15E Strike Eagle UFC - WIP: It's just a beginning right now. With the RAZBAM Strike Eagle in the works, I figured I would start to dive in on a desk mount UFC for it. Early days on it, but I thought I would pass along a glimpse of where things are at. The concept design is inspired by what Jself did with his Hornet build. My thanks to him for his posting on it. The screen display will use the typical LCD build you see in the TM Cougar MFDs. It's pretty straight forward really.

I too have noticed a difference. I never had to adjust brightness and contrast until the last update. I suspect the change occurred because of the rework of FLIR.

Software solution widely used is Helios. Info to get you started is right here in the forums.

Update: Learned that this is quite possibly the Over Current Protection OCP issue with combinations of some PSUs, RTX 30xx, and Ryzen CPUs. Very random/intermittent issue and very difficult to get a grip on. This is not a DCS issue as it has now occurred outside DCS. Looks like a new PSU is in my future. Thanks for everyone's help. You are all fantastic!

Ive run out of ideas as well. Thanks so much for your efforts. It would have been nice to reach a resolution to reward your efforts.

This loading went to the briefing screen. Further than the normal blue bar this time. As it was loading the temp high hit 64c and dropped to 63c on average. When the briefing screen came up it jumped to 73c and then the reboot happened. These temps I think aren't within the realm of causing the reboot. Good to put them off the table as to the cause. I appreciate your help by the way. Glad to have it.

Changes made. Rebooted and verified the change using the command line. Image is my verification. Reboot still happened. As most times it was going through the loading and was on the tail end it did the reboot. Didnt even get to the where the graphics card would be kicking in to display the world behind the briefing/fly overlay.

Did a windows memory test because why not. It passed without issue. Case/fans/vents/filters are clean. Fans are running fine. I cant say I suspect GPU or PSU issues as I am not seeing reboots with GPU stress tests. As stress tests dont have issues this keeps bringing me back to DCS as that is where the problem occurs and isn't 100% repeatable. Sometimes I get to flying and more often not. Sometimes it reboots during the progress bar before the briefing and sometimes it is after hitting the fly button. Had a good long 2 week stretch of no issues and I was about to close this thread out and boom... the latest update to open beta releases and the problem is back. Which brings me to when this all started which was the update that brought the Mariana update. Before that I never had a reboot issue with DCS. I was on the stable side and switched to beta as the multiplayer servers seemed better and it certainly is where all the cool kids hang out. When this issue started I did a repair and then even a complete removal and did a proper reinstall of DCS Open Beta. Followed all the advice and guide to the letter for doing so. None of this is making sense at this point as to what it could be. Just to add... Room Temp is 72F/22C.

and the exact same reboot issue on the next try has a failure with this log file so you can compare them. Both of those are from a reboot prior to the blue progress bar completing with no briefing/fly. As mentioned before there are times I get to the briefing and I get a reboot as soon as Fly is selected. dcs.log

Did as you suggested and still reboots. It's been a while since I posted one and Im not sure it really means anything at this point but the last log file generated on reboot. dcs.log

These seem to be a reoccurring theme.

The frustrating this with this is it only does this in DCS. And while the reboot happens a fair bit in DCS, it doesn't happen every time. I do get times where I get put on the ramp and can actually fly. More often, while after selecting the mission and it is loading the blue progress bar progresses along and before it hits the end... the computer reboots. On some occasions I'll get put on the ramp with the briefing box displayed. Hit the fly button and the second I do... Computer reboot.

In the event viewer this seems to have happened around the time things went sour.

Here is the CMD line info. Here is the DxDiag file. DxDiag.txt

I'll do that as soon as I can. Right now Im dead tired trying to figure this out. System works fine with other flight sim like X-plane and the graphics are turned way up. Also have tested the graphics card using a few GPU testing tools. No issues with that. Ill do as you suggest tomorrow after I get some rest. Thanks for the help. it is much appreciated.

Well, sad news. I still have the reboots happening and while normally they seem to occur with a single player mission, I have just had a system reboot with multiplayer. This issue only seems to come up after an update. It went away for a little while and it has comeback with the update. Thought that deleting the files fixed it as after doing so the single player mission worked with several successful consecutive missions launched and closed. With the last reboot my DCS main page has been reset back to the default background. It had set it to the Hornet. With that change a pop up box came up asking me about collection of anonymous data collection and selection to accept or deny. This is all too weird.

Seems I might have resolved the issue. <Fingers crossed> The only time the DCS caused a system reboot was on loading single player missions I made from the mission editor. I never had DCS cause a system reboot from instant action or using a multiplayer server. Deleted The files from the FXO and Metashaders2 folders in my DCS user directory and the problem seems to have gone away. Single player missions now have loaded 3 times without the system rebooting. Not sure why any of this happens but there it is. Hopefully this can be of help to other should it happen to them. It seems my case with it is unique as Ive not seen any other posting about a reboot being caused by the fxo and metashader2 files.

I thought this issue went away and was going to close it. Magically it seemed to resolve itself. The the update which I did today brought it back. What Im seeing. Computer reboots. Hasnt happened when I go onto a multiplayer server. Hasnt happened when I tried and Instant Action mission Has happened every time I try and do a single player mission that I've made in the mission editor. As the missions were made in previous versions, I'll try making a new single player mission in the current version and see if it still crashes. I recall reading something about deleting some files from the user saved games area but cant recall or find what it was. Ill post more as I discover... <additional info> Created a new single player mission to eliminate possible old version conflicts (a shot in the dark). System rebooted with a new mission created in current version. Attempted another Instant Action in a different theater map. Worked fine. Attempted a single player mission. Reboot occurred.

Silverdevil - While similar, not quite the same as I get a computer shutdown/reset and not a hang. I still did the suggested fix and deleted the folder and it did not fix the problem. I still get the resets. I wish it solved my issue and certainly appreciate your taking time to comment as I feel like I'm in this all alone at this point.

One last log upload for the evening as I'm running out of ideas trying to figure this out. This time the crash/reset occurred while the mission was loading with the blue status bar. dcs.log

Some more info on the issue. A short video I took of what typically happens. As soon as the "Fly" button is clicked on the computer resets. I had made sure to have a performance overlay on screen to show details. Most occurrences happen when I hit the fly button. On some occasions I dont even get to the screen where I can hit "fly". 20210707_004519_1_1.mp4

Update - Doing more testing and I had a shutdown with TrackIR not plugged or the software running. No longer suspect TrackIR conflict. Issue still remains and is not consistently replicated. Here is a new log with the recent occurrence of the issue. Verified WIndows 10 up to date and Nvidia Drivers are most recent version. System Info AMD Ryzen 6500X 6 Core Processor MSI B550M Pro-VDH WiFi Motherboard 32 GB RAM RTX 3060 Again, DCS never did this on my system prior to 2.7.3. dcs.log

Since the 2.7.3 update, I am having issues with running DCS with TrackIR. DCS runs fine without TrackIR for me. When I use TrackIR DCS will go to a black screen the computer shuts down/resets and starts back up to desktop. I have replicated this issue several times. Every time TrackIR is used i get the issue. TrackIR not used and there is no issue at all. TrackIR tests fine and works with the TrackIR software which I confirmed is the latest version (5.4.2) I even unistalled TrackIR and reinstalled version 5.4.2 to eliminate the possibility of a corrupt file. TrackIR has never given me any issues with DCS until the latest 2.7.3 release. I did a repair to DCS. Issue remained. I unstalled DCS OB and reinstalled and the issue remained. Attached is the log file. dcs.log