BLUEmako

I saw a thread for this in A10C bugs but this is happening in A10A for me. High frequency shaking of jet in flight. Can't seem to isolate to speed or aircraft settings. Started with latest patch. Checked and not related to my setup as does not occur with other modules I have.

Also have George controls in middle of screen. Is there a way to set location in the monitor lua like the jester menu for F14?

First to IronMike & HB thanks for the transparency with this thread, it's appreciated. Few questions though: 1. Did the changes to the phoenix performance include changes to the parameters for launch cues in TWS mode? I ask because since the changes I cannot get hits using the flashing TWS track cues as a guide to launch. The phoenixes run out of energy well before reaching the target and/or fail to guide in the terminal phase. 2. I've seen several phoenix just loft for outer space (missile is 45 deg nose up at over 100,000ft) when shooting from high and fast (30,000ft and 0.9M in the cat) with good TWS tracks on targets at about 60nm, is this expected behaviour? This behaviour results in the missile achieving range of about 30nm. I recorded video of these behaviours while testing against AI H6J bombers that I can post on YouTube if it helps. Unfortunately I'm not running Tacview at the moment. Best regards, BLUEmako

Just a note about my experience with the recent Nvidia drivers (471.68). On two PCs these drivers caused the modules I tested to CTD when loading a mission. Happened consistently with F14, F16, F18 on two pcs. Rolled back the drivers and CTD went away. Hope this helps if you experience the same.

I'm on stable... Hopefully fix is not far away then. ;)

This behaviour has been present in the F14 for me for a few months now. If I get killed in multiplayer then try to respawn in an F14 the game stops responding. I have to force close the game then rinse and repeat. This seems to be similar to the symptoms in this reddit post from April 2021 however my graphics drivers are up to date.

Also seeing this but I can move the switch while on the ground by mouse clicking it in the cockpit

I too am experiencing this. It is not logical to say they are too close to each other, if there's an option to ripple it should not destroy the aircraft... Tested and it seems to happen regardless of speed or altitude when using ripple set with distance 10m. Have not tested other ripple settings.

As noted in the other thread, disabling the Grinelli F-22 mod fixed the engine sounds. Thank you so much for a great mod. The Edge is awesome.

Confirmed that disabling the F-22 fixed the engine sound on the E540. Thanks for the tip.

Great mod thanks guys for your hard work. I have tried it out because I love aerobatics and it flies great. Only niggle is that the engine sounds appear a little bugged. From the cockpit the engine sound only idles, it doesn't change with throttle. From external view the prop sound is correct but the idle sound is present when viewing from behind the 3-9 line. Perhaps it's the exhaust sound not changing with throttle? Hope this post helps. Thanks, Bm

I glad this is not just me. Driving me crazy in the analogue aircraft,.

Okay, further update: reverting to release version did not change the behaviour. Perhaps it is related to an Nvidia driver update or Windows? Anyone else experiencing this behaviour?

Ever since the open beta introduced the new custom save slots for display properties my multimonitor display will not work. I have 2 screens (1x1440p QHD and 1x1080p FHD), the second is used to export the MFDs. The game will start to the menu but will not use the second monitor. It shows DCS on the main monitor only with the aspect ratio compressed. The mouse position sensing behaves like the monitors are working so I have to move my cursor beyond the compressed display to select options. I have tried every combination of rebooting, refreshing the display settings in windows and restarting DCS but it seems to be only randomly that it will correctly detect the second display. The setup was working fine in previous builds. I am now going back to the release client to see if it fixes the issue.

Yep, seems I was using old syntax, my bad. Thanks.

Hi, I'm trying to move my DCS installation back to the stable version by using the "DCS_updater.exe update @stable" command. When I do so I get a "404 not found" message from the updater. Has this functionality been removed? TYIA, BM

Well my release version is still not working. I don't have the hard drive space to have to run the open beta version as well as the release version with all of my modules installed. At the very least the F/A-18 datalink should not be causing ctd when you are using the release client. And is it intentional to allow connection to open beta servers when running the release client?

Okay, I installed the open beta version. I've done a quick couple of tests and I can connect to MP servers and use the F/A-18 datalink without an instacrash. My theory is that the issue is related to some change that has been made with the latest patch and implemented updates in the open beta that are not in the stable release. Joining openbeta servers when using the stable release seems to provoke the issue.

I did notice that the crashes might be related to having a JF-17 in the server mission? Consistent ctd with datalink active when JF-17 are around. Also, I seem to be able to connect to openbeta MP servers even though I am running the main client? Is that normal?

Completely fresh DCS install, everything from saved games deleted and vanilla settings. CPU and GPU are both stock settings.

Couple more log files after deleting fxo and metashaders directories and letting them rebuild. And more confusion. Crashes seem to be server specific. I was able to start datalink fine in one server but then when I went back into growling sidewinder the datalink crash happened again. Attached are two more log files, one for the ok mp server, the other for the crash in the growling sidewinder server. Note memory usage during these sessions got up to 17 GB with almost no paging pool, seemed to be all in the physical RAM. dcs-dl-ok.log.txt dcs-dl-not-ok.log.txt

Tried again after reinstalling all modules I have. Still getting same CTD in MP when using F/A-18 datalink. I have upped my swap file to 16384 MB but no change to behaviour. Attached new log file. dcs-dl-crash.log.txt

I ran a repair. Still the same. I removed all mods, ran cleanup and repair. Still the same. I uninstalled DCS completely. Reinstalled vanilla DCS with F/A-18 as the only module installed. Still instant CTD in multiplayer when activating datalink. Happens in at least two servers. The datalink works absolutely fine in single player. This is only occurring in multiplayer. Some log files attached. Will try to capture another to make sure it's there. BM dcs.log.txt dcs.log.old.txt

I recently purchased the F/A-18. When I try to turn the datalink on n multiplayer I get a freeze and CTD as soon as I hit the on button on the UFC. Is anyone else experiencing this? I couldn't find any other threads...

Okay, looks like the issue was on my end. I logged into DCS today and it ran the updater. Dunno why it didn't update a couple of nights ago or why it didn't warn me I was playing MP with an outdated client... Tested and it now looks like the TID repeater is fine. Thanks for the quick replies Ironmike. Sorry for the inconvenience. And thanks for the great Tomcat. I haven't had this much fun simming since Fleet Defender. Now I just need to learn how to fly it better. BLUEmako