I have no control over carrier-interaction. I have seen it do course changes while you're on it, that's pretty disconcerting. the plane has the tail_hook and located at the rear of the plane. afaik it's never been an issue before. it's possible that AM is being freaky about using the towing/winching position entry where prior just simply used the front wheel. I've never heard rolling into position for catapult takeoff after landing (even I'd probably use the special situation option to have it start the plane at the catapult position). I still would think that catapult should use front wheel position, whereas glider being towed, or glider towing aircraft would prefer to specify the tow/winch location. Otherwise, as usual, I have to deflect the issue to the carrier interaction is LR issues. to give that a test, try any of Jaques Barault or Barry Ledger's planes with the carrier. intentionally not v10 specific planes which might have any band-aids for that. I'd think those should work as expected not needing any 'new' entries to 'continue working normally', LOL.
i'll look and put the towed/winched position #'s at the front wheel in case.
the prop. well, it has a show hide relative to prop rotation speed. i'll look but there's a point when the prop blur appears and disappears naturally with x-plane, and i've had to guess at the rotational '
tacrad' to show the prop at low speed and hide it when the blur appears. I'll probably just compare it to the same entries on the Cirrus SR2X or Malibu family props. I thought it was pretty standard a # I used on them. but i'll look. Needless to say it's pretty frustrating to pick up pieces after AM may arbitrarily break things. Maybe compare and see if it's the same or different between 970 and 10.~. if there is different behavior and 10 is ill-behaving vs working fine in 970, feel free to file a bug report with LR.
Aquila, yep, that's most likely it for the prop, esp since it's free-turbine on the T6X,
probably windmilling and staying in the in between prop-rotation speed.
lessee;
T6X_prop
- Code: Select all
ANIM_begin
ANIM_hide 15.0 1000.0 sim/flightmodel/engine/POINT_tacrad[0]
ANIM_show 0.0 14.999 sim/flightmodel/engine/POINT_tacrad[0]
ANIM_end
PA-46-500TP_prop
- Code: Select all
ANIM_begin
ANIM_hide 35.0 1000.0 sim/flightmodel/engine/POINT_tacrad[0]
ANIM_show 0.0 34.999 sim/flightmodel/engine/POINT_tacrad[0]
ANIM_end
PA-46-350P_prop
- Code: Select all
ANIM_begin
ANIM_hide 50.0 1000.0 sim/flightmodel/engine/POINT_tacrad[0]
ANIM_show 0.0 49.999 sim/flightmodel/engine/POINT_tacrad[0]
ANIM_end
hmmm. I think the different #'s are because the engines turn different rpm, and I think the prop_disc_blur appears/disappears at an arbitrary rotational % ratio instead of specific rpm number.