Flappie
Thanks for responding.
I tried what you asked but still did nothing. My AMD video drivers have recently been installed fresh with a complete wipe of the older drivers. No hardware changes made in a long time.
Changing the setting preset to low allowed me to load the map without it crashing. I then changed each setting 1 by 1 to see which one was producing the crash.
I found that the only setting that created the crash was changing Water to anything above low. Medium and High produced the crash every time on Normandy and Marianas. However Caucasus, Persian Gulf, and NTTR loaded up just fine with a high water setting.
I'm only having the problem with these two maps crashing with water set to medium or high.
Hello
Every time I try to load the Normandy map or it hangs on the preload phase when the map loads and crashes shortly after. This happens every time on ST and MT versions.
I've attached the crash log zip. No mods and a fresh install of open beta client.
Thank you
dcs.log-20230509-014201.zip
Make sure enable VR headset is checked on the VR tab in settings. I found mine was unchecked for some reason but was still in VR. Vastly improved the slideshow that I experienced when I first started up after the update.
Very nice patch by ED and third-party Devs!!!!
Get long loading times on all missions. Followed by a black screen behind the briefing window for a few seconds.
Also sometimes when I exit out of the game after a few Tomcat missions the game will fail to close and hang. I need to open the task manager to end the task.
CPU: Ryzen 7 1700X 3.5 Mhz boosts up to 3.8 Mhz when ingame
16G RAM @ 3000mhz
Radeon RX Vega 64 w/ 8g of video ram
Installed on SSD
I wouldn't blame Early access just yet. I believe there is a special options in the special tab for the the F-14 for radio behaviors. For things like SRS and such to give them priority.
Also What do you mean it's not doing anything? Are you getting the communication menu to pop up at all?
Sorry to hear you're having issues.
Hello,
I noticed when applying some input on the throttles from idle there is about a 10% deadzone in the hornet. I thought it was a calibration issue or a curve setting I was unaware of but not the case here. I tested it with other aircraft and no deadzone after idle position at all, only the F/A-18.
A workaround I did was to set the Y Saturation to 90 on both left/right throttles and now get proper range.
I'm pretty sure this an issue with module and not on my end. Has anyone else noticed this when looking at the controls indicator or in-cockpit?
I'm using TM Warthog throttle along with the stick.
Same issue here
Doesn't matter if I do campaign, training, missions, or server. As long as start in a cold state the game will crash when I hit the first switch to power up the A-10c.
Log is attached
Best dcs.log-20180315-035143.zip