reported earlier Coordinate system is TU!

[RackMonkey]

F-10 map coordinates are off.
I tested using Al Qusayr in the F18 and using precision.
Arpt data for Al Qusayr is.. 
N34.34.02.73 E36.35.07.49 @1729ft

Putting the cursor over the arpt marker (runway center)the coordinates in the upper Left of the F10 map were..
BU 77213 27959
N34.34.02.73 E36.34.21.03

When I entered the MGRS into a waypoint the Lat/Lon converted to..
N34.34.15.68 E36.34.28.80
This did produce a TGP diamond on target and a GBU38 on target...this time.

When I entered the Lat/Lon into a waypoint, the MGRS converted to..
BU 77088 27722 
This produced a TGP diamond and a GBU38 50yds south of the rwy.

When I entered the arpt data waypoint into the INS the TGP was on a spot just south of the runway and at the east end of the runway. When I turned back in on the bombing run the TGP diamond was now way short of target and moving. I found that during the turn the elevation of the waypoint had changed from 1729ft to 48ft. I extended and corrected the elevation of the waypoint. After tuning back in again I check the elevation only to find it had changed to 14ft.

This really screws up any hope of using any preplanned bombing and need to be a top priority fix.

 

[Tholozor]

The airport information window doesn't give you the runway center, it gives you the touchdown point of the runway (N34°34'02.73" E36°35'07.49" being the touchdown point of runway 28 for Al Qusayr).

Also ensure you're using the same coordinate format in the jet as the map (Hornet's default is non-precise Degree Decimal-Minutes).

Waypoint elevation being cut down has been reported, only occurs when waypoint elevation is set in feet and designated; current workaround is to use meters.

 

[RackMonkey]

11 hours ago, Tholozor said:

The airport information window doesn't give you the runway center, it gives you the touchdown point of the runway (N34°34'02.73" E36°35'07.49" being the touchdown point of runway 28 for Al Qusayr).

Figured that. It is on centerline and 1000 ft from the threshold. Right where it should be. I mentioned it only to show the discrepancy between that point and where the TGP thinks it should be pointing.

Also ensure you're using the same coordinate format in the jet as the map (Hornet's default is non-precise Degree Decimal-Minutes).

I have my config file set for precise, which it doesn't do, so I have to change it once I'm in the f10 map. And I always change the data input to precise unless the weapons I'm carrying can't make use of precise waypoints.

Waypoint elevation being cut down has been reported, only occurs when waypoint elevation is set in feet and designated; current workaround is to use meters.

I was hoping it was already reported but I couldn't find any post that mentioned it. I probably just had the wrong search parameters. 

 

 

[Flappie]

On 7/13/2022 at 5:33 PM, RackMonkey said:

I was hoping it was already reported but I couldn't find any post that mentioned it. I probably just had the wrong search parameters. 

This will be fixed very soon.

[RackMonkey]

Contradiction-How can this be tagged as "correct as is" but Flappie says it will be fixed soon? There is noting "correct as is" about the system.

I use the 8 digit system and still cant find my target with the TPOD. There is no way in Hell that I can make a pre plan precision drop. 

[Flappie]

I was talking about this bug here:

On 7/13/2022 at 5:51 AM, Tholozor said:

Waypoint elevation being cut down has been reported, only occurs when waypoint elevation is set in feet and designated; current workaround is to use meters.

Please provide a track showing the issue described in OP.

[RackMonkey]

Heres the track file of a test run I did.
Target-Sakumi runway numbers
Both sets of numbers taken of the same point from the F10 map at full zoom
Waypoint 5- Entered as MGRS
Waypoint 6- Entered as L/L percision

Note the L/L coord in WPT 5. They were entered as MGRS. They don't match the L/L coord (WPT 6) taken from the F10 map.
Note the MGRS coord in WPT 6. They were entered as L/L. They don't match the MGRS coord (WPT5) taken from the F10 map.
Note that the MGRS WPT shows on target in the TGP where the L/L WPT show a little south and east.

Turning around I set WPY 0 (spawn point) as my target. The TGP show a little north and a little east of the point. 

INS test.trk