Heliflyr

Thanks Elliot, glad to hear that.

I just uninstalled and reinstalled the F-14 Module and that didn't work. I also renamed the DCS file under Saved Games and that didn't work. Finally, I ran the repair utility and that didn't work. If it is a corrupt file is there anything else that can fix this?

I just checked the A and the nozzles are hitting 5 on the gauge. So the problem is with the B model and this rules out hardware and the curves are at default. Also, I noticed the B's RPM is not going over 100% in AB unlike the A model.

Hi all, I seem to remember that the F-14 nozzles use to go to 5 when in full AB. I notice a while back, that the nozzles now stop at 3.5 on the gauge. The only time the nozzle gauges read 5 is when the throttles are at idle or when the engine are off. I can also see in external view that the nozzles are not open fully with full throttle. Is this normal or is this a bug?

New development, just when I thought that random crashes were behind me, I started to bump up the settings and OC the PC and GPU until the crashes started up again. All this was a waste of time. I learned in the Forum that if you fly the F-14 in MP, on the 3rd time that you select an F-14 slot, DCS locks up. I tested it and yes DCS locked up on the 3rd time. I was flying the A-10 and AV8B most of the time with no problems. Then I switched to the F-14 and the random crashes began, but turns out it was not random. The F-14 is such a complicated Module that it requires a gaming rig with the best hardware to run it. But this is something else that will require some programing fixes. I'm just going to have to use the F-14 sparingly and hope that will keep DCS from "Not Responding" and locking my PC.

Hi Hornblower793, Since I don't know how to read the crash logs I could not tell you if the crashes are duplicates. The last 2 weeks I have been making changes to my graphic settings so often, its hard to say what settings are used. But I do see that the settings are recorded on the logs. As for what maps I am having crashes, that would be mostly be the Caucasus maps playing multiplayer on the 4YA servers. I also had many crashes on the A-10 Tactical Training Campaign. Also, I have had way more crashes that did not produce a Crash Log because the PC would be locked up or the game would crash to Desktop. Today, I reset my 2080 ti back to normal settings, and reran the DCS World Repair and removed a MOD for the AV8B that removed the screen mesh from the TV sensor. So far No crashes on 4YA servers. I am going to run the game today without any changes, and hopefully have no crashes. Then tomorrow I'm going to try to OC the i9-9900K. Here are some more logs. dcs.20210701-055128[1].log dcs.20210701-222559[1].log

Hi All, I like to add that I too have been having DCS crashes since the 2.7 update. I have tried everything mentioned in this thread and I am still getting random crashes. I have a collection of crash logs dating back to May 14. Before that the last time I had a crash was in Oct 2020. I updated drivers, reversed all OC back to normal settings, increased paging files, ran the game while monitoring temps, monitored ram usage. The only thing that I see that might be a problem is that RAM usage is almost maxed out. I have not had any trouble in the past running with 16GB, But I think that I will have to upgrade to 32GB of RAM to fix this. But since I never monitored my RAM usage in the past, I don't know If it is the problem. i9-9900K/ROG Strix Z390-E Gaming MB/ROG Strix 2080ti/Patriot Viper 16GB RAM/ADATA XPG 1TB M.2 dcs.20210702-193403[1].log

I learned that you have to unbox the DESG on the EHSI to get the TV sensor to work. Just Unbox the DESG and you will be able to bring up your TV sensor.

I know this thread is old, but I learned that if the DESG is boxed on the EHSI, I was not able to access the TV sensor. The MPCD would stay lock in the LST mode. Once I unboxed the DESG on the EHSI, I was able to bring up the TV sensor. I followed the AV8B training mission over and over many times and I was stuck when the TV sensor lesson came up because the lesson prior to that had me box the DESG on the EHSI, but it did not tell me to be sure to unbox it for the next lesson.

Ok. Solved the Chat window problem. Turns out there was a key binding to Hide/Show Chat Window control. Once that was removed, no more Chat Box disappearing and keyboard Nonfunctional.

Hi. Lately I have noticed strange bugs while playing Multiplayer on DCS World 2.5.6.49798 within the last 2 weeks The first one has to do with the chat. While typing in chat, the chat box disappears and the keyboard will become nonfunctional, but I can Ctrl+Alt+Delete to get out and restart DCS. This occurs often. Next, While in the AV8B-NA, the Weapons Stores page will go blank at random and indicate that I don't have any weapons loaded when I can see them on the pylons. This has happened 4 or 5 times. Finally, while in the A-10C, the HUD would go blank. This has happened twice. Note: none of this took place while being engaged, so It is not a system failure from taking damage. These bugs happened on the "Just Dogfight" server and the "4YA servers." I do run Reshade (Vibrance,Fake HDR and Luna Sharpen) which was installed 3 months ago. Anyone have a clue to what is happening here?

Another way to load the weapons is to cycle the CICU switch. After the Blue screen disappears, push the OBS- LOAD ALL. When the dot next to LOAD ALL reappears, the weapons will be loaded. It takes about a min. PhantomCat, PPL come here for help. If you are not replying with a solution to the problem, then keep your unhelpful comments to yourself. I too use autostart when I don't want to fuss with flipping switches.

A-10 flies with a right bank When I start any of the instant missions, the A-10 instantly goes into a right bank of 5 to 10 deg. It only occurs in the "Simulation" mode. When I change to "Game" mode in the game options, there is no longer a RH bank. I know about P-factor in prop airplanes, but it should not happen here. I'm using a Seitek Cyborg X. When I test the controlls, everything checks out good. There is no indication that the stick is leaning right. Drivers and software have been updated.