mdtenor22001

I've always found this developer to be responsive on his discord,but obviously YMMV. In my opinion,this was a really quick fix! (Admittedly,I tagged him on Discord when I posted about it and let him know others on the ED forums had notes the problem too.) Keep trying of you're having an issue. I'm sure he'll respond.

I'm seeing the same thing. Just finished the basic navigation mission and it failed. However, it is NOT a big deal and BD, I am really LOVING the style of training here. More modules need this level of instruction. Really well done all around!

A buddy and I decided to multicrew the C-130 today. We noticed that the cursor control wasn't working properly for either of us. It was slewing inaccurately and mapped buttons would not work. When the co-pilot left the aircraft, the controls went back to working properly. I think there is some sort of multi-crew de-sync going on. We also noticed several other anomalies that were likely caused by de-sync, but we didn't note them all. The cursor issue was a major issue since we were going to have one build a flightplan while the other was flying.

I just noticed that too. I thought maybe I broke it by setting up my Moza AY210 in DCS (previously only used in MSFS), so I didn't try it with other modules. Is it maybe just the C-130 module? Did you post on the Simhaptic Discord?

I've had this campaign for a while and just started learning the Mig-21. Has the campaign been updated? I just flew the first mission and it seemed like there were bugs (only one intercept appeared even though the mission briefing seemed to make it seem like there would be more). Also, only got 50 percent draw even though the controller told me I was done and to RTB.

Can't wait to check it out. Thank you so much!

Draken, I'm clearly late to the game here and have just started using your branch of Scratchpad for the Apache. Thank you for continuing to maintain this! I may be doing something wrong, but I read your Readme and searched this forum and still can't figure it out. Specifically, I'm trying to follow the method of creating target points (or Control measures) instead of the default WP type. From the readme, it appears that inserting a "T" where the # is in the string ("@|T| coords") should create a point as a Target Point with the default abbreviation of TG. However, when I do that, it just creates a standard waypoint. Same for when I use a "H". I must be doing something wrong (especially since I don't find a mention of that problem in this thread). Any ideas? Thanks in advance.

Ah, didn't realize that the route tool was newer than the F-4. Glad to hear it's on the list, and I appreciate that you replied!

So no known workaround to getting Multiplayer waypoints on a human WSO's kneeboard? Is there a way to export the values from the router planner into scratchpad or even a list to be written down? I searched the HB discord and didn't find anything there either. Seems like a pretty big oversight! Thanks for the response.

Good news! No more CTD! Bad news: George can't "see" FCR targets despite me seeing that he's got the tads right on them. They show up as unknown and he refuses to lock and engage them. He also won't engage with guns after selecting multiple targets in an area search. Very much appreciate all the work being done on the module. Fingers crossed that the rest of the kinks get worked out with George!

I am sure I'm doing something wrong, but I cannot find instructions on this anywhere: How do you get waypoints from the route planning tool into the WSO's kneeboard in multiplayer? When my pilot puts in coordinates, they show up in his kneeboard, but not mine (WSO). I get no waypoints. Likewise, when I use the route planning tool, I get nothing (and neither does my pilot, obviously, because he's already spawned). First off, is it possible to get waypoints into the WSO's kneeboard from the route planner? If so, how? We are following the same steps we've used for other modules, but can't seem to get it to work in the F4. Thanks in advance!

Totally agree. I just discovered this bug for myself (relatively new to F-14) and it makes it impossible for me to fly both front and back seat when I need to. I hope HB addresses this in the upcoming big patch.

It happened in online server missions too (although my recent tests have all been various single player missions). But I'll try that too, even though I suck at making missions.

Can confirm. Did another slow repair just now. Different mission this time (Caucuses live fire range). Same result, CTD right after I selected a target from the FCR scan list. dcs.log-20250729-215940.zip dcs.log LastMissionTrack.trk

Thanks for the follow-up. That track (and the CTD) was made after I updated and after a slow repair. I also made sure no mods were loaded at the time. I had experienced a crash before the one I reported, so I ran the slow repair just in case. I couldn't get it to crash with any other combinations of George commands, only that specific sequence--but it has been consistent for me, both before and after the last hotfix. The last few times when troubleshooting, I've only done it on that single player Afganistan Weapons Range mission, but I will also test it on other missions.