I created a mission using the wizard and an existing flight plan containing 40 waypoints and gates with associated rectangle areas and triggers. Twice while debugging I have gone through a gate and the next waypoint showed over 4000 miles away. I discovered that in spite of the correct location showing in the mission editor it placed the waypoint and associated gate and rectangle at 0 degrees latitude. I had to change the location and then change it back in order to get it to work. This wasn't that difficult when it was ust a few gates in on the debug process, but now I'm at gate 28 and it shows over 4000 miles, but this time I discovered it created the waypoint and gate at 0 degrees longitude. When I modify the locations it doesn't show up in my autosave through FSUIPC, but I think it shows when starting from the beginning, but that will take over 3 hours to debug. Are you guys aware of this and is there a quick workaround? One peculiar thing in using the send and grab feature the plane is sent to the correct coordinates, but the gate doesn't show. Even if using the send in the gate module.
-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
FSXME Lat/Long at 0 degrees
- Thread starter lvflyer
- Start date
- Messages
- 1,361
- Country
Hi Folks
lvflyer -
Please zip and attach your original flightplan file.
I'll follow up on that initial zero lat/lon placement later.
This is a PICNIC, (nor in FSXME),
it's you comparing two different file's content.
As explained to you elsewhere,
a saved mission flight,
does not use your original xml/spb.
It references a saved copy of your mission, (as an SPB),
which includes all trigger states.
Hence why from a previously saved flight,
(before you'd corrected the gate location),
you're still seeing the gate's old location.
Whenever you've changed your xml
you must always fly the mission from the begining.
N.B.
You shouldn't be "flying debugging", (especially a 3 hour flight),
without first
having checked every location's coordinates
using the node's GoTo button.
HTH
ATB
Paul
lvflyer -
Please zip and attach your original flightplan file.
I'll follow up on that initial zero lat/lon placement later.
This is a PICNIC, (nor in FSXME),
it's you comparing two different file's content.
As explained to you elsewhere,
a saved mission flight,
does not use your original xml/spb.
It references a saved copy of your mission, (as an SPB),
which includes all trigger states.
Hence why from a previously saved flight,
(before you'd corrected the gate location),
you're still seeing the gate's old location.
Whenever you've changed your xml
you must always fly the mission from the begining.
N.B.
You shouldn't be "flying debugging", (especially a 3 hour flight),
without first
having checked every location's coordinates
using the node's GoTo button.
HTH
ATB
Paul
Last edited:
Sorry for the time it took to respond. Apparently the email from this site can't get through the filters my provider uses. Anyway I flew the entire mission from the beginning and all the gates show correctly now.
Regarding using the send and grab, I did verify the gates but the send and grab took me to the entered and displayed coordinates, but the actual location of the created gate was as I stated.
My question is why does it select random gates to reset the lat long to 0? I did notice that if I entered a rounded number, for example N45*32' that it would interprit that as N45*31'60.0 where the 60.0 could be throwing the setting off. Why does Mission Editor try to change the Lat/Long and Altitudes? On the altitudes if I enter 3000' for example the mission compass reads 2999'.
Also BASys I see you have some extensive knowledge with this. Can we make direct contact so I can get some assistance on more advanced issues?
I've attached a zip of original .fsn and .pln used to create the mission
Regarding using the send and grab, I did verify the gates but the send and grab took me to the entered and displayed coordinates, but the actual location of the created gate was as I stated.
My question is why does it select random gates to reset the lat long to 0? I did notice that if I entered a rounded number, for example N45*32' that it would interprit that as N45*31'60.0 where the 60.0 could be throwing the setting off. Why does Mission Editor try to change the Lat/Long and Altitudes? On the altitudes if I enter 3000' for example the mission compass reads 2999'.
Also BASys I see you have some extensive knowledge with this. Can we make direct contact so I can get some assistance on more advanced issues?
I've attached a zip of original .fsn and .pln used to create the mission