

mdtenor22001
Members-
Posts
57 -
Joined
-
Last visited
-
CTD after commanding George to engage FCR target
mdtenor22001 replied to mdtenor22001's topic in Bugs and Problems
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! -
mdtenor22001 started following F4 - Route planning tool and WSO - how to?
-
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.
-
CTD after commanding George to engage FCR target
mdtenor22001 replied to mdtenor22001's topic in Bugs and Problems
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. -
CTD after commanding George to engage FCR target
mdtenor22001 replied to mdtenor22001's topic in Bugs and Problems
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 -
CTD after commanding George to engage FCR target
mdtenor22001 replied to mdtenor22001's topic in Bugs and Problems
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. -
CTD after commanding George to engage FCR target
mdtenor22001 replied to mdtenor22001's topic in Bugs and Problems
Updated. Same exact behavior. George sees the FCR targets, I select one, tell George to change to missles, consent to fire, crash. Log and track attached. dcs.log-20250729-025926.zip dcs.log LastMissionTrack.trk -
Happened to me three times, once on 4YA server and twice in Afganistan weapons practice instant action mission. Command George to FCR area search; select target; select George weapon missile; consent to fire...instant CTD. Track attached. Edited to add: engagement with laser HF on point target worked fine, as did the traditional PHS point search and engagements. LastMissionTrack.trk
-
I also tested this in the P47 and P51 and trim was working for me.
-
Can you expand what you mean by resetting? I seem to occasionally have this and have not been able to figure it out. Doesn't happen all the time,but about 30% of the time for no apparent reason I can find.
-
I think the default fusing is the problem and that I was dropping the bombs too low. In the training mission, it instructs you to drop at 1000ft AGL (which, is probably way to low IRL). I don't think it had enough time to arm. When I tried again and dropped at a higher altitude, the bombs exploded. So, not an issue with the module (other than the training drop altitude should be set higher or the fuse set shorter).
-
Aaaand, the final IFR training was flawless and I passed the first time! I hope people buy this module. Lots of fun to do real procedures. On to the campaign next. Did you see my post about the MK-82s not exploding? I don't think I'm crazy, but I'm going to try again later. Not sure if the campaign has bomb dropping...
-
I'm not sure what I possibly did wrong last night over and over again, but when I tried it again just now, it worked. The only thing I can think is that I pressed the space bar before he got done talking last night, and this time I waited for a few beats before pressing space. Worked as intended. Thank you!
-
I hate to keep reporting bugs with the missions, but I just attempted the Air-to-Air training mission. After all the instructions completed, I got to the part where it asked to press space bar to leave Active Pause and spawn the bandits. I did that, the mission unpaused, but no bandits were spawned. Tried 3x, same results. I plan to try the final IFR training mission tomorrow, now that I feel pretty comfortable in the bird.
-
I can confirm that MK-82s are not consistently exploding when dropped. I dropped the C-101 into a bombing range mission and loaded it with MK-82s. Using the TITS script, I confirmed dropping a pair of bombs within 12m of a T-72 and can confirm visual bomb impact but no explosion. The mission had "unlimited ammo" enabled and the odd thing is: probably two pairs, out of 20 drops, exploded. But I was surprised that those two pairs exploded (and did nothing else different in settings). I could see both visually and hear that they exploded while all others were duds. Confirmed that in the same mission, several other modules could drop MK-82s and they exploded. I did see a post somewhere about the last DCS patch affecting blast values of MK-82s, but I'm not sure if that's true. Just wanted to report it, in case it's a new bug.