Mission 5 - Problem to hit last Hangar with precise coordinates

[Derfel75]

Hi all, I'm in the middle of this very enjoyable campagn, but I have some troubles to hit the very last Hangar in Mission 5. After receiving the precise coordinates, I created a custom waypoint and combined it with TOO feature to slave my last JSow to this target. After I missed a first time, I tried again a couple of times missing It again for few meters

During my last try, I noticed that after designeted as target my custom waypoint  (by using the wpdsg ddi button), the coordinates of the JSow and the custom waypoint, don't match. 

My question Is: Is normal that coordinates don't match? Or where I'm doing wrong? Should I use JSow PP mode rather than TOO to complete this task?

[Badger633]

Hi

They should match. Are you using the correct format for the precise coordinates you are given. I have a video of this mission showing how to select correct format and then entry. Check what you are doing with this.

It’s also explained in the brief.

Hope this helps.

 

Edited June 5, 2023 by Badger633

[Derfel75]

Thanks a lot! I'm sure now it's going to work, infact I didn't change the format of coordinates! 

 

[Badger633]

6 hours ago, Derfel75 said:

Thanks a lot! I'm sure now it's going to work, infact I didn't change the format of coordinates! 

 

That will do it

[Hillman]

Hi.

I tried to enter the coordinates into the final JSOW in PP mode. The bomb hit some trees outside the airfield. Not sure why PP should not work? I tripple checked coordinates and elevation. I was in range and all looked good until the last seconds...

And I wonder if you are mixing up Longitude and Latitude in the message that pops up? Longitudes are always east-west while latitudes are north-south as far as I know....

Also I was not able to remove the messagebox by pressing Space.

Edited November 3, 2023 by Hillman

[Badger633]

13 hours ago, Hillman said:

Hi.

I tried to enter the coordinates into the final JSOW in PP mode. The bomb hit some trees outside the airfield. Not sure why PP should not work? I tripple checked coordinates and elevation. I was in range and all looked good until the last seconds...

And I wonder if you are mixing up Longitude and Latitude in the message that pops up? Longitudes are always east-west while latitudes are north-south as far as I know....

Also I was not able to remove the messagebox by pressing Space.

 

Hi

I checked out the space bar for removal of coords issue. I guess you are on one of the simple versions as I found a small error in the script. I have corrected this and it will be out next update.  Thanks for picking it up. The normal versions with full refuelling are ok.

Regarding the coords, as you can imagine this campaign has been out for years and so am confident the coords are correct.  It is probably a matter of what format you are using. If I remember there is direction in the brief as to the format. I also produced a video on my u tube channel for the coord entry on this very mission. The link is below.

Hope this helps.

    

 

[Hillman]

3 hours ago, Badger633 said:

Regarding the coords, as you can imagine this campaign has been out for years and so am confident the coords are correct. 

I will try again to see what went wrong. To me it looks more natural to use PP mode instead of adding a new waypoint.... Surely that is why PP mode exists?

My point was simply there is no North indication for a longitude position. They only exists on latitudes. Equally there are no eastings on latitudes. They only exists on longitudes. You simply need to swith the text here. In your own video you enter the latitude first (N 44 etc) and then you enter the longitude (E 43 etc)

No big deal when you enter Waypoints in the Hornet because you never specify if it's longitude or latitude, but on PP JSAW you do. Anyways I of course swithced this around my self

 

As for the space, yes I was playing the one without refueling.

 

Looking forward to the rest of the campaign and has also RoPL installed and waiting

Edited November 3, 2023 by Hillman

[Badger633]

Thanks will look into the coord text issue. 
The idea of the additional set of coords on the hop is just to make life a little more difficult for the player having to enter the coords whilst flying and navigating. TOO would normally be used then, but you’re correct either can be used.

Hope you enjoy the Rise of the Persian Lion and the next chapter in Rise of the Persian Lion 2.

Just working on the latest, Operation Green Line, this based in Cyprus, Turkey, Syria, Israel and Jordan. The same characters running through. In fact you will see more characters are added as the Campaigns progress. 
 

Cheers

[rob10]

The JDAM PRE-PLANNED needs the co-ordinates as  DD MM SS.SS.  I haven't flown this mission in a long time, but are the co-ordinates given in DD MM.MMMM?  IIRC the Hornet NAV system defaults to DD MM.MMMM so if you're expecting the user to enter it as a waypoint and use TOO that's likely the format you used in the message and if the OP is plugging that into the JDAM then they'll have to wrong co-ordinates (even if they seemingly enter them correctly).

Edited November 4, 2023 by rob10

[Badger633]

Just checked coords out on this mission. The coords given are correct and in the precise format ie DD.MM.SS decimal SS. Which is correct for Precise coords. The use of these is noted in the in game brief plus the switchology required in the cockpit to enable them. So all good.

My mistake was putting the word latitude in front of the Northing and visa versa. This has now been corrected together with the voice over and will be updated. Thanks @Hillman for picking it up.

Hopefully in next update.

[Hillman]

Tried the mission again and the coordinates given worked perfectly for the PP JSOW. Direct hit on the 4. hangar. I guess on my first try I might have been a bit marginal on the range.
In my opinion it's much more efficien to drop the last JSOW using preplaned mode and punch in the coordinates directly since the PP already uses the DD.MM.SS.ss format given in the message.

So the only issue was the mixing of the words Latitude and Longitude in the message.

[Badger633]