Rainmaker

(Cntrl + e) x 3

There is no auto-throttle. Does not exist at any stage of the -15.

All you do is click with the mouse.

Sounds like a minor bug, either due to sync or coding.

Yeah, would likely need a track or video then to see. The last version had some runaway drift, but it should hopefully be addressed already in todays patch.

Showing short sounds like the elevation delta. Current SP height needs to be as close as possible to actual target elevation. The radar uses SP height for target elevation.

Velcro all over. Tim has added it in the model on the respective places. The filters should also install when using the NVGs.

As above, the mismatch could be a few different things. There was also so unintended excessive drift that should be addressed in the most recent patch. Would need screenshots, video, something to see why it might be off. Could be a coordinate problem, or alt deltas. Cant speak to any of it for sure.

Update moves the entire route, des will effect the target point. Both can/will look tye same if you are just looking at the target point. From what you have said so far, its working as intended.

I’m not sure what you mean by polygon? If that is a ref to the offsets, they are in relation to the target point location. As for the radar/HUD mismatch, that could be due to two main things, drift and altitude deltas between the steer point/target point elevation anf actual elevation of the target location.

Nope. This is intended.

Not sure if I am understanding your issue correctly, but target points will shift with designations. Its is a feature of target points only.

Target points can be updated with designation, as will any offsets associated with it. Other points will not be. Designations, by themselves, should not be seen as any type of ‘point’ in the system.

Offsets are related to nav/target points, not designations. Points have to not be the active steer point in order to be edited.

They only existed on the MPCDs, and even still, the displays are not really NVG usable. What really needs to happen if for NVGs to be properly implemented, at least in VR, to not be full screen to allow the look-under technique as IRL.

The only units really utilizing -65s operationally were out of Mt Home. The had a specific task qual for them. It was just one of those niche case items that wasnt an across the fleet thing. So yes, they were operational at a time back around the turn of the century. As far as OEF/OIF, was a bit of a mix depending on the time period. A lot of precisions strikes in the beginning, moving on to what came to be known as XCAS later on. OIF had some DCA/escort in the early time periods. As far as weapons, just about everything to include slick MK-82s. PGMs being primary though. I dont have numbers in front of me, but in the early OIF days, about half of the GBU-12s expended in the AOR came off the E models.

Ctrl Enter will also show the trim position. If you dont have damage, etc, center of the cross should be 1G. I have a ‘wish list’ request of my own to open up the null range a little bit so its not quit so sensitive.

Pitch ratio has to do with mech gearing ratio for stick vs surface travel. Not really related to trimming for commanded G flight. There are ways to disable the PTC however if necessary. CAS is also not really in the loop on this. Trimming is done regardless and based on the mech side of the flight control system. Will operate in either fashion, CAS on or off.

CAS connects directly to the actuators. Mech is primarily control rods and linkage. The two are not really the same, hence why they are not reliant on each other to an extent, which is by design.

Hydro pipes? No, that’s not really how that all works. Hydo is just a power source, CAS and mech are not that way.

Majority is directly out of Eagle Talk papers. Just transcribed.

Needs route letter input along with number

Nothing ‘odd’ about it. A-10s were not using lantirn, and didnt have LLG either.

Sounds like you are not even talking about IFF....

The devs made the sounds like they are BASED on SME inputs actually. So it was done based on 'been there, done that' inputs and not 'we think' from the devs. Just to clarify those points.