gwizairshows

Okay, after many more game crashes, and experimenting with numerous MiG29A scenarios involving "vanilla" Nav, Nav with just NS430, Nav with just the DTC, and Nav with DTC and NS430 I can report the following: First off, as I mentioned above, if a start a different module mission such as with the Mig15, and then drop the 29A into it (no DTC/NS430), it flies perfectly. It seems that the DTC game crashes my system routinely. Not so much the NS430, but even then sometimes. If I generate a "vanilla" 29A Nav mission, things seem to work, then if I add the NS430, and then the DTC it works just fine...most of the time, but still crashes occasionally. However, if I start a mission with DTC enabled and pre-loaded , I can cold start and taxi out just fine, but every stinking time at the beginning of then T/O roll I'm sent to the Pimax Crystal Planet for time out...read game crashes to desk top. Is anyone else experiencing this issue? It really is frustrating, as I really love the MiG29A module. dcs0910-0.log 282.31 kB · 1 download dcs.log 27.02 kB · 1 download

Okay, after many more game crashes, and experimenting with numerous MiG29A scenarios involving "vanilla" Nav, Nav with just NS430, Nav with just the DTC, and Nav with DTC and NS430 I can report the following: First off, as I mentioned above, if a start a different module mission such as with the Mig15, and then drop the 29A into it (no DTC/NS430), it flies perfectly. It seems that the DTC game crashes my system routinely. Not so much the NS430, but even then sometimes. If I generate a "vanilla" 29A Nav mission, things seem to work, then if I add the NS430, and then the DTC it works just fine...most of the time, but still crashes occasionally. However, if I start a mission with DTC enabled and pre-loaded , I can cold start and taxi out just fine, but every stinking time at the beginning of then T/O roll I'm sent to the Pimax Crystal Planet for time out...read game crashes to desk top. Is anyone else experiencing this issue? It really is frustrating, as I really love the MiG29A module. dcs0910-0.log dcs.log

Thanks MAXsenna! Would never have guessed that Samsung thing for sure, but successfully got the computer purged from Web OS, LG, Samsung etc.. Also Un-parked all cores. Back to my original problem. I thought I had isolated the problem to the DTC. For when I put the 29A as a "drop in replacement" to other mod aircraft missions that did not have DTC enabled, everything worked perfectly. Well, I was wrong. I noticed that my DCS in game settings for FPS was 300! Whereas the Pimax play refresh was 90hz. I dropped the FPS to match (90/90), and now everything (after 3 tests) works perfectly. Guess that was the culprit all along, or so it seems thus far...

Wow! Samsung and windows...Really!? I have not connected my Samsung at all to my computer. I bought the TV a few months ago and all my electronics are on WiFi and not hardwired. As far as testing, I will set up a new mission with the F1, drop the 29A into it after flying, and do the reverse. When everything worked I dropped the 29A into the F1 mission engines running at the runway. I will report back the details. As far as the Samsung craziness, I will research out how to kill that "wonderful windows benefit"! Any suggestions as to do this would be greatly appreciated.

Interestingly, started a mission from scratch with the Mirage F1, then edited the mission by dropping in the Mig29A...everything worked perfectly. Mig flew excellently. Then closed that mission and went to a saved MiG29A mission and activated it, as usual everything worked perfectly as I got through the cold start, taxied out, then...(and at almost the exact same spot each time of a previous crash)... taxing out the sim crashes to steam. The logs are below for ref. Really weird if you ask me! dcs.log debrief.log

So to start the sim, I just use Pimax Play (which I re-installed) with the following settings: Device Settings -> Refresh Rate 90Hz, Brightness 100, Eyetracking, Under Games: Common Settings -> Image Quality High, GPU Upscaling- NIS/Quality, and Smart Smoothing Under DCS World Steam Edition -> Image Quality High, GPU Upscaling- NIS/Quality, and Smart Smoothing Also, I downloaded ParkControl and turned off Parking. Yes I have been deleting FXO and Metashader2 prior to each game start. As far as mods I have the WWII and Chinese Assets, UH-60L, A4E, and Bronco. They work great so I am reluctant to mess with them unless really necessary! Again, really appreciate the help and info.

Done. DxDiag Results.txt

More current crahses...:-( dcs.log dcs1.log dcs2.log

Appreciate the info. I mislead you, sorry...Let me clarify, the game/sim crashed to the steam menu 5 times, normally after a good cold start and just upon power up on the runway. I completely re-booted my system each 5 times to try and insure a clean system. In reference to the crash logs, I know they are in the saved games..., however the only ones I saw after the last crash was from a previous month. I'll try again tomorrow. BTW, thanks for your help!!

Update. Did the exact thing I did yesterday. Today, what worked yesterday did not today resulting in 5 system crashes in a row after 5 full and complete system reboots. However, using the exact same mission, but dropping random other modules (Mig-15, etc.) in place of the Mig29A...everything worked perfectly. Giving up for the time being on the 29 until a fix comes out...sigh...

Admittedly, I am not super computer software savvy. A while back I downloaded those three programs (and also Project Lasso). My understanding was Open Composite regulated the options for OpenXR versus Steam VR. Therefore, I assumed that in order to operate the subsequent programs of Open XR and Open XR tool kit properly, that Open composite had to be activated first in order to insure Steam VR would NOT be run. Please educate me otherwise, as there is a bit of confusion in my mind as to the best way to get the bloody sim to work consistently. BTW, I do find it a bit odd that Steam VR has always been a bugaboo. I do realize that VR was not native core, but after all this time I would hope that these issues would have been ironed out!

Well... I just may have solved the problem. I went back to Open Composite, activated it and disabled Steam VR in the Open Composite option. Activated Open XR and Tool kit programs. Started Pimax Play, and in the Games section disabled in the menus any reference to Steam VR (including aspects regarding the DCS Game Start option) and hit Apply. Then activated DCS from the Pimax Game option (with all the Steam VR stuff off). Held my breath, and to my amazement flew a complete 40 min solo Nav mission out of Maykop from cold start to shut down. Everything worked perfectly!! Therefore, I am assuming the problem is actually with Pimax, (not playing with) Steam VR and something to do with those two that relates to the Mig-29A module. Of course that was only one flight. Will try multiple flights soon and report if all is okay using the above process. Again this whole problem only seems to be a factor with 29A module, all others are fine. As I am fixated on the 29A for the time being, guess this will be the new DCS start norm using the Crystal for me.

here is the crash log file: dcs.20240625-155127.crash

This mod has great potential. Unfortunately it has some constant crash issues with Pimax Play resulting in game crashing to desk top. I have researched and tried numerous ways to comply with the online system crash advice, but nothing seems to work. Trying the old open XR and Pimax play start options initially start off fine, but then almost at the exact same spot taxiing from a cold start the sim crashes. It is very frustrating, especially considering the amount of time I have dedicated to learning this module. As far as my rig, I am operating a Cyber Power Intel(R) Core(TM) i9-14900K, 3200 Mhz, 24 Core(s), 32 Logical Processor(s), with Nvidia GeForce RTX 4090. So handling this module and DCS should be no problem. These crashes only happen with this MiG-29A module. It appears something is wrong with this module and Pimax Play. Anyone else having these issues?

This mod has great potential. Unfortunately it has some constant crash issues with Pimax Play resulting in game crashing to desk top. I have researched and tried numerous ways to comply with the online system crash advice, but nothing seems to work. Trying the old open XR and Pimax play start options initially start off fine, but then almost at the exact same spot taxiing from a cold start the sim crashes. It is very frustrating, especially considering the amount of time I have dedicated to learning this module. As far as my rig, I am operating a Cyber Power Intel(R) Core(TM) i9-14900K, 3200 Mhz, 24 Core(s), 32 Logical Processor(s), with Nvidia GeForce RTX 4090. So handling this module and DCS should be no problem. These crashes only happen with this MiG-29A module. Something is wrong with this module and Pimax Play. Anyone else having these issues?

Following check list procedure am unable to get HSI and ADI to work after the 15 sec mag&comp input. They work only if generating from ME in the air.

Kinda figured that but was not sure. Thanks!

Can't seem to figure how or where to set F4E bingo fuel levels. What am I missing? Any ideas?

Completely uninstalled and reinstalled the Steam MI-8 module. All my DLC content appears normal, however...still having the exact same problem as described initially above. What is strange is that all other 15 modules have never had this problem, only the MI-8! Any further help would be most appreciated.

Trying to post under bugs and problems, but did not see any opportunity to start new topic... Anyway...have Steam DCS 2.9, using DLSS. Just downloaded from steam store the MI-8, everything works just fine except all the stock skins/liveries are corrupted into a green mottled digital camo pattern. The interior cockpit instrument panel graphics are fine, but the pilots, rotor and exteriors are corrupted. Any ideas and or solutions? Thanks!