Razor18

OK, will try again then...

It even does it when I WPDSG WP1 and uncage to that. Both MAV triangle and TGT diamond are both well within HUD FOV. That's why I went down too low and got shot by MANPADS...

Yeah, I experienced this the day before yesterday. So yesterday I triple checked it on purpose. COMM1 and comm 2 is both assigned to my TM HW Throttle 4-way thumb switch, but I tried both, looking at the pop up comms menu title (COMMs1 vs COMMs2). When trying on COMMS1 (Radio 1 Channel 1), no reply. If I tune COMMS2/Radio to "M" 133.000, Axeman immediately responds. Same for all subsequent JTAC communication. But I understand you couldn't reproduce it, so it is not a showstopper. But on the same note, sometimes JTAC doesn't seem to lase after I tell him LASER ON, and he responds "Laser on... Lasing". When Uncaged, the Maverick X wanders down to the spot it supposed to lock on, but more times than not, the X doesn't change to a square. I even tried "Terminate" and again "Laser on", but no square. 1688 set for both MAV, so I dunno... Thanks

It doesnt. TCN still only shows bearing, but no distance.

Hi Badger, Easy Comms OFF here, but Axeman only responds if I call him on COMM 2. Tried inside and outside of 20 NM, responds both cases only if called on COMM2. Also, if you try to extend to the North before turning in, to be on an easterly egress HDG at the end, Mission Fail counts me out. Could you please check maybe?

Sorry, you're right, not seconds but frame time.

Another suspect for me is the default TGT aging of 4 sec for AMRAAM (which is pretty much against common sense in my opinion). Anyway, before going into combat, select AMRAAM, on RDR page press DATA and cycle the top row right button to increase 4 to 8 to 16. Then exit by pressing DATA again.

You couldn't. If you were above, needle would be below, so it should say "Downd and on"...

During a CASE III, when Approach says "Say your needles", pilot's response is always "On and on", even if glideslope is way high, which would mean he should say rather "Fly up, on". Moreover, Approach then even says "Concur".

Just looked up DCS Supercarrier's own Operations Guide, Glossary, page 91: "Final Bearing (FB): The magnetic bearing assigned by CATCC for final approach (an extension of the landing area centerline); usually BRC minus the landing area angle of 10°." So if BRC (which is indeed the ship's magnetic course) is 360, you should Marshall on the reciprocal of BRC (in this example the 180 radial), and the Final Bearing will be 350 degrees (if the landing deck is angled in fact 10 degrees to the left of BRC). Seems this was copied from the CNATRA P-816 Naval Operations manual, page GLOSSARY A-3.

Yes, but final bearing is not equal to BRC, thats my point...

Didn’t find anywhere else in the Bugs section, sorry if missed it. Mother says (example) : BRC is 360…Marshall on the 180 radial…expect Final Bearing 360. But Final Bearing is not equal to BRC, it is rather BRC minus 9 degrees (landing deck angle). Am I mistaken somehow, or is it really an ATC bug? Thanks

No, it will not. As mentioned in my original post.

If memory serves me some, it works just like that on the A-10C. (Apologies if I'm wrong on this) But probably that's why this Hornet MAV procedure felt weird, for me at least...

Thank for your reply, BIGNEWY. I don't want to question what you guys doing, because I don't have better source of information than you do. I'm just wondering, if the procedure (after uncaging, MAV locks itself onto a predesignated point, then not being able to slew maverick off of that point without undesignating TGT, and completely "deleting" the point in the process, AND for the next shot you can start all over again by designating, whether the target is moving or not) is a bit "contraproductive" even for us simmers, why would it be benefitial for a real life pilot in battle, who has much more to lose than us chair pilots? I'm just speculating tough... But if anybody knows a more practical way to launch MAVs, I'm happy to hear it...

Ok, so I'm not the only one not seeing any change in this after the last patch? That's what confused me. To be honest I didn't remember Mav ever going back to Caged after undesignating. Max not being ground stabilized maybe? Bad memory, sorry...

Oh... so only the "return to Caged" behavior was eliminated after undesignating? Sorry, I might have misunderstood. Thanks for clarifying !

Well I tested it, but it doesn't seem ED fixed it. Tried to put down a point with HMD around some vehicles, extended and turned back nose on target. Focus Diamond on the MAV screen, Uncaged Maverick from Caged/Boresight, it locked on to the predesignated point on the ground, but I could not move the seeker head onto the vehicle. Not with depressing TDC btw Realistic TDC behavior was unchecked), but not even by holding the TDC down and slewing. Only after I undesignated the original TGT point could I slew the MAV onto the vehicle. Is it just me? Thanks

No, A-10C since very early. Apparently did it wrong until now.

Oh, I think I get it now. Making something SOI only tells the system "I want to manipulate this sensor around". With TMS FWD long I give a "target pointer" into the handof the SOI, but don't "draw" any point on the ground, rather wherever the pointer points to at any time, will be the point to attack. Thanks for enlighten me !

If you then move the SOI (TGP) around and for instance Area Track it onto a building with TMS UP Short, but you do NOT press TMS UP Long, will you be able to drop ordnance on that building?

Then what is the function of coolie hat right long for instance, if there is a (let's say TGP) sensor up on the right DDI?

I see what you mean. But then what is the function of TMS FWD Long?

Tank, until you press TMS FWD long again.

OK !