Emmy

Looks like whatever is generating the road’s surface is trying to stay perpendicular to the slope instead of being parallel to a level horizon. I’ve noticed a couple of roads (Goat tracks?) running up through some of the canyons you can enter off the coast kinda doing the same thing.

Every wing has some degree of elasticity. If it didn’t, it would snap. Hog wings will obviously move a little but in comparison to a Viper or a Hornet, they may as well be called ridged.

Further musings while waiting for word from on high... Slightly different situation tonight but still Syria in SP - Hot Ramp Start at Ramat-David with six pre-placed steerpoints. - Jet navigated fine to all (and did not need to jog the SP Rocker) - Added a SP7 to go to Incirlik and while the TACAN showed my destination was over 200nm at about 355 degrees, the NAV System was taking me 014 degrees and only about half the distance. - So, I made a SP8 and put the same LAT/LON in that I had used for SP7 with no change to the bearing and distance I was flying. - HOWEVER, decrementing back down to SP7 suddenly gave me the CORRECT heading and distance to fly. I think in this case, it was the same issue related to having to jog the SP Rocker for a self-entered SP1. The Jet saw my SP7 in the same vein it would see SP1 had it been self-entered. Moving the SP Rocker made SP7 suddenly valid... It also means that SPs laid out in the ME are essentially irrelevant to the jet’s nav system. Players flying on servers where routes or targets are already laid out would never encounter the need to jog the SP Rocker.

I understand which coords the maps use but when the jet first woke up and you went to enter LAT/LON, the coords were natively in N/W and now they're in N/E.

When did LAT/LON entry in the Viper change from natively N/W to N/E ?

Ok, so having to "wake up" the system by jogging the SP Rocker aside, could these anomalies be related to working in EAST LON in Syria and not WEST LON? I just flew for about an hour on our NTTR Server and I waited until I'd reached my CP before I put in my TGT coordinates but when I changed the SP to my TGT, the entire system slaved right to where it should have for a CCRP GBU-12 drop and then when I went back to the SPs for my flightplan, everything behaved as it should. Oh, and @Machalot, everything seemed to line up ok on the NTTR... Haven't checked Syria yet.

Rats, I forgot to cross check all of them. My bad...

More Strangeness... Cold Start Incirlik .. Full Alignment Enter LAT/LON for Basser Al-Assad during warmup Once warmup was done, I racked the SP Rocker down to 127 and back to 1 (Jet navigated to BAA just fine so the "workaround" worked) En Route to BAA, I entered the LAT/LON for Incirlik RWY 23 so I could navigate back to base. Now play along with the pictures please: LAT/LON For The Numbers At Incirlik RWY 23 HSD Displaying My Two Steerpoints TACAN (21X) Heading Matches Heading and Distance shown on HSD But This Is What The NAV System Showed And Note: "Phantom Steerpoint 2" was not the same place that the original Phantom Steerpoint 1 took me the first time I encountered this oddity...

I should think in practice it would be far, far more translucent than Swift's example.

Honestly, except for those times when I select the wrong mode, the A/P has been pretty reliable. And you are for sure in ALTitude Hold and not ATITude Hold?

One further point: You don't even have to take off. If you put the HSI in NAV, you'll see that the Course Needle is not pointing toward Creech, it's pointing to 350 and the DME says 215nm

For the details on this track, reference "Cold Start From Nellis" posted above. I did the exact same steps and the jet did the exact same thing. It headed 350 degrees to a point 215nm away UNTIL I jogged the SP Rocker down to 127 and back to 1. Then the jet turns toward Creech. Phantom Steerpoint.trk

I’ll see if the jet still does it on a Stored Heading alignment. That might keep it short enough to get an acceptable track size. Really though, this one should be very simple to reproduce. - Put in LAT/LON for a destination while the jet is warming up. - Take off and engage Autopilot for SP1 (without touching the SP Rocker at all) - Jet will head towards a point that’s not in the direction of your intended destination nor the proper distance.

Gerard Butler

Hadn’t noticed but I’ll try to remember to look.

Yeah I’m thinking it’s not.

You only need to go up (down?) to 127 from 1 and back again. But I won’t hesitate to swing check my entire flightplan with my wingman, and I’ll swing check SP1 twice from two directions on the rocker.

I’m not a fan of not being able to leave the TGP where it is by going to area mode. In my mind it should work like INS Mode on the Hog and just stay pointed roughly where it’s pointed but apparently it doesn’t.

I’m aware it can be corrected by rockering up to 127 and back down to 1 I just want to know if this is a bug or a feature. ?

But you can hold the brakes yourself for that

Just give the enemy a “NOTHING” task when you place them on the map. You can also give them zero rounds in their guns and only captive missiles (where available)

Parking Brake

I think we found the same issue... https://forums.eagle.ru/showthread.php?p=4461908#post4461908

How far off the steerpoint are we talking here? A few hundred feet in any direction from the CZ point and a GBU-12 will still track the laser successfully. If you need to move your centroid by miles, then you need to use the TGP to get the LAT/LON and make a new steerpoint to CZ on.

Every point on the map should be in the CDU. And if you want to pass a particular point X miles from it in a specific direction, you can do an Offset and create a mission point that you can name and add to a flightplan. You can do a custom flight plan in the ME and name each point as you go, but if you use a duplicate name that already exists, I’d suggest you append it with a 1. eg, FLEX already exists, so if you create a point and want to call it FLEX, make it FLEX1