chase

Okay, so for whatever reason, now the seat is working again. I did nothing. The only thing i can think of is the other day windows updated to Build v24H2. So maybe it took another day or two for windows to update whatever it needed to, resulting with your program working again. Thanks for looking into it though. Was much appreciated. Dave.

Ok I think I found the log. Thanks for the quick response. I reinstalled the software again and made sure my virus software was suspended for this test. So nothing should be blocking it. and the seat is turned on with showing a red light. Thanks. Dave ForceFeelLog.txt log.log

Okay i updated my windows 11 to version Build v24H2/ 26100.3194. Now the Next Lvl gaming pad isn't recognized. I've tried uninstalling and everything. not sure what to do. Even tried the beta build, same thing. Anyone else come across this? Also i don't know where the log file is located. I looked in the installation folder but nothing says log file. There is a nlog and other simular files. Can someone give me the exact spelling of the log files which are needed to help trouble shoot my seat pad. Thanks for any assistance. Dave

Thanks, I think both were turned on. I'll verify the next time I give it a try.

Yes I understand. I kind of figured you'd have to redo a ton of triggers, etc. No worries, just wanted to make sure I wasn't missing a step or something. for the most part these missions are playable, i just use labels a little more till the SA page is fixed. Thanks for the reply. Dave.

It seams on all missions ( I've flown several ) non of the wingmen show up on SA page. Everything is turned on, Datalink, link, bcn etc... none of the hornets show up on sa page. I checked the ME and it appears they are all entered into the donor system, so not sure what's causing This. I'm able to create a new miz on my own add in wingman and other units, assign them donor info and they appear. So maybe there is an issue when porting older missions Into the updated multi threaded version of dcs. Idk. I'm sure others are seeing the same issue. How ever it was strange that when flying miz 10 in dominant fury sluggo about half way into the mission appeared on the sa. But that's the only time he was there. You can't even get a DME from TCN for any other units. It's like their system's are all turned off. Thanks. Chase

I just flew this mission today and still continue to run into the same problem you described. I don't know how to fix their mission because a lot of the mission parameters are hidden. I just found this video that Wags put out. It may help. I'll have to see if I can make these changes in the ME on this mission. I doubt it, but who knows. Hopefully the Dev's will fix this soon as this is not the only mission where I find this problem. Chase

BIOS Update has fixed my issues. That as well as your suggestions regarding graphic settings . Thanks for the help. Solved.

I have a very old build of this MOD. Haven't been on twitch in a long time and since upgrading to the latest multithread version of DCS I'm getting a ton of CTD. How can I remove this Mod, i have a feeling it's the reason for this issue, since I've removed all other mods and did a repair. Just not sure where and how many files to delete. Thanks Chase. Edit: Nvm. I figured it out.

I ran the dxdiag test which revealed no issues found on any device. I found the DCS log analyzer on your discord and ran my own test. The memory no longer appears to be the problem. it did advise to lower my textures though. So i did that. Both textures To medium and texture scenery to low. I also changed my water to medium. This has greatly lowered my vram to about 70-80% and RAM to about the same. My CPU stands around 70%. But as soon as i get near any asset's my CPU usage gets maxed out 99-100%. Even flying over the ocean my cpu is 70%. I get to the carrier group and again spikes to 100% and gets very laggy. I had better performance on the single thread version without crashes like this for years. I guess I'll have to build a new computer to keep up. My 8 core 8 thread cpu can't handke this sim with the new way it handles my cpu. What setting would reduce cpu load? The number of assets aren't that much. The carrier group should not be that cpu heavy. At least the game didnt crash this time. Just a slide show with much lower settings than i had been using.

@sleighzy Thank you for this information. Did you by chance check today's log? Did that also show an XMP issue? I've had the XMP on for all these years. That's the only way you can get the advertised speed out of your RAM otherwise windows will throttle it down. I'm not saying your wrong, but my guess is the log i sent in a few days ago might be showing timing issues because I know on that day I had a faulty stick of ram. Now today I know all sticks are good to go. Everything was running so smooth like butter right up till I was inbound on the 2nd target. I was monitoring the performance via task manager and saw my processor was maxed out for a few seconds right before the game just abruptly ended to desk top. I had looked over at the monitor because I heard my CPU fan speed up a lot and saw the spiking then bam, end of game lol. . I'm know my VRAM is maxed out. and regular ram was about 70% at most. But when the processor spiked, this is when it died. Like you pointed out it was without a crash log unfortunately. So again, I only add this information in case you can think of maybe another test I should run on top of the dxdiag test which I will do this evening. I'm going to run another mission tonight, one of my own without scrips and see if that makes any difference. Thanks for responding and looking at these files. I know your just a volunteer. I appreciate it. Dave.

So I've always played this game using the single thread version. Now I'm forced into this multi thread world. Once I updated, the game CTD and also created numerous BSOD events. The last one showing a memory issue. I ran a Memory diag test which resulted with a bad stick of RAM. So I replaced the bad stick and now the test passes every time. I re run Miz 9 of the orig campaign and at least this time was able to get half way through the mission. However, around the time I was closing on the 2nd APC with a GBU the game suddenly quit to desktop without any lag or warning what so ever. The game did not produce a Crash log or anything, so the only thing I could find was the DCS Log it self. This was the only file which was dated today. My VRAM was maxed out at 8 gigs. ( GTX 1080 yeah I know. But it has worked till now ) my DDR4 32 GIGs @ 3200 speed was around 60-70 % and my CPU was running around 40-50%. So you guys have done an outstanding job with optimizing your mission. Heck it's better than a small mission I made. My small mission was running my RAM around 70-80% Anyway, I'm going to attach the DCS log to this post in hopes maybe someone can tell me what all the warnings mean and if there is a way for me to correct it. It might just be a random crash. But it's getting annoying. I also posted the Log to ED's Support forum in case it's on them. But in case this is miz specific. I figured I'd cover all my bases. I prefer to fly your missions when I do fly DCS, so hopefully this is a short time issue. Oh it should also be noted, that right before the game quit, my processor was maxing out as if it was running in some scrips or something. usually the CPU would be around 40-50. But about 10 miles away from the target my CPU jumped up to the high 90's% utilization. I was monitoring using Task Manager. So maybe it was to much for my 8 core 8 thread CPU to handle with this new multi-thread architecture that ED has created? thanks, Dave. dcs.log

10-06-24 Okay new RAM came in. I fixed the problem. All 32 gigs of DDR4 @ 3200 speed is running like a top. Re ran the Diagnostics test without issue. This time, I got half way through the Ravon One initial campaign Miz 9 and while just approaching a target which I had designated, the Sim did a hard CTD. This time no crash report was generated. Just went from in game to desktop. No stutter, no warning just died. The only thing which was dated today in the Log Folder was the DCS Log which I'm attaching here.. No crash or other logs were generated. My RAM usage was around 50-60% and CPU about 40-50. VRAM is MAX'ed out at 8 gigs. Old GTX 1080. But a work horse for sure. Anyway, the log is throwing all kinds of errors up. I don't have any mods installed and I updated SimAppPro and all Hardware Firmware updates as well. So the crash must be from the game this time and not my computer. I'm thinking the way your new architecture handles moving processes around and utilizing vram and reg ram is causing a rift. But I'm just an amateur computer guy who can barely build one. So hopefully someone can dissect this log and maybe compare with the previous logs I had attached and help me diagnose the issue. As I don't know how to correct these warnings as the game is up to date and running without MODs. So... Thank for any assistance. Dave dcs.log

After updating to the lastest I've Been getting BSOD over and over again. Sometimes I can get off the boat in the Hornet. Then a SAM will fire on me and BSOD. Or other times BSOD upon loading into a game. I'm assuming now that it's multithreaded my RAM is used a lot more than before. As before this update i had no issues as I ran on the old prosessor usage mode. Now I'll admit the last BSOD revealed a memory issue. So I ran the windows memory diag test and it came back "Hardware Problem detected " so i took out all my RAM cleaned them reseated and still a problem with ram. So i ordered 2 new sticks. But the fact this never happened before is the reason I'm sending you all my logs incase you see something else that either I need to fix on top of the ram or maybe there is a code issue on your side. Either way at least I'll have better ram lol. Let me know what you think, or if you need something else From me. - MB: Asus ROG STRIX Z390-H GAMING - Processor: I7-9700 - Graphics card: EVGA GTX 1080 ICX - - 4 sticks = 32 GB DDR4 DRAM 3200MHz - Windows 10 Both OS and Video drivers are current and up to date. Thanks, Dave dcs.log-20241002-210509.zip

I have found that the best odds on making voip work the best is to first wait till each and everyone is first loaded and waiting in the spectator lobby before entering a plane and hitting fly. You need to wait first till all are fully loaded in and in lobby first, then all at the same time enter your aircrafts then all works. But if a few enter their ac while others are still loading into the briefing screen those guys won't be able to communicate with you. Dave.