Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

Runway Centerlines


1275389
 Share

Recommended Posts

1275389
Posted
Posted

It appears that runway centerlines are being affected by magnetic variation... this is causing them to appear slanted.

 

Here is FLL's 10s and 28s for example: http://i.imgur.com/aazwoq2.jpg

The fixes displayed are those on the ILSs, clearly a significant distance from what is shown to be the runway centerline.

 

It's drawing them with a true heading of 264, 270 magnetic (using the latest update with the LA fix for the 28s).

In the file from MyFSim.com, 270 is the heading it has listed for FLL.

The runway heading it should be displaying is 276, it appears that in this case, it is actually subtracting rather than adding.

Link to comment
Share on other sites

Joshua Black
Posted
Posted

Posted slightly above yours.

 

viewtopic.php?f=148&t=70635

Joshua Black

22

Link to comment
Share on other sites

1275389
Posted
Posted

That post deals with the LA command, I am refferring to runway centerlines...which is somewhat of a different bug.

Link to comment
Share on other sites

Ross Carlson
Posted
Posted
That post deals with the LA command, I am refferring to runway centerlines...which is somewhat of a different bug.

 

This bug might have been caused by fixing the other ... I'll look into it.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Nope, these two issues are unrelated. The centerline rendering code uses the magnetic variation listed in the Airports.xml file, which has the correct value for FLL. (6.1083333333333334 degrees.)

 

It's working fine for me at KBOS.

 

Can you post your facility file for download?

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

1275389
Posted
Posted (edited)

Done

It seems like the variation is not as significant at some airports compared to others.

Edited by Guest
Link to comment
Share on other sites

Ross Carlson
Posted
Posted
It seems like the variation is not as significant at some airports compared to others.

 

Please elaborate ...

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

1275389
Posted
Posted

Tampa's centerlines look pretty close to what they should be, Fort Lauderdale's do not. (The variation appears to be less)

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Josh, what command did you enter to get the centerlines to display?

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

1275389
Posted
Posted

For FLL's 10L: .FC KFLL 10L

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Did you edit your airports.xml file? Because the one distributed with vERAM has the runways at FLL as 9s/27s.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

1275389
Posted
Posted

Updated to the latest files from MyFSim.com

Link to comment
Share on other sites

Dhruv Kalra
Posted
Posted

I don't think Casey's airports.xml file had reliable magvar data last I checked.

Dhruv Kalra

VATUSA ZMP ATM | Instructor | VATSIM Network Supervisor

878508.png878508.png

Link to comment
Share on other sites

1275389
Posted
Posted
I don't think Casey's airports.xml file had reliable magvar data last I checked.

 

Is there any updated Airports.xml file with reliable mag var data? We've tended to have many runway changes in the past year or two.

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Ugh ... it would be really helpful if you mention that you're using someone else's data when you post a bug report.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

1275389
Posted
Posted

Argggg -- I didn't think the mag vars would be so drastically different.

Link to comment
Share on other sites

Ryan Geckler
Posted
Posted

The runways at FLL changed from 9 to 10 ages ago... why was the data so old to begin with?

Ryan Geckler - GK | Former VATUSA3 - Division Training Manager

VATSIM Minneapolis ARTCC | FAA Miami ARTCC 

 

Link to comment
Share on other sites

1275389
Posted
Posted

My temporary fix -- setting all the mag vars to 0.

The runway centerlines are being calculated based on a magnetic heading rather than a true heading. I think this is more going to mess up other stuff than actual be a practical solution.

Link to comment
Share on other sites

Ross Carlson
Posted
Posted
My temporary fix -- setting all the mag vars to 0.

The runway centerlines are being calculated based on a magnetic heading rather than a true heading. I think this is more going to mess up other stuff than actual be a practical solution.

 

Yes, the centerlines are projected using magnetic heading, because the runway headings found in the Airports.xml file are magnetic, not true.

 

If setting the magvar to zero in your custom Airports.xml file fixes the issue, then I must [Mod - Happy Thoughts]ume that the runway headings in that file are true, not magnetic as they're supposed to be.

 

Why not just use the Airports.xml file that comes with vERAM and just change the runway numbers at the airports where there have been runway changes in your facility?

 

I'll make it a priority to get an updated Airports.xml file generated, same with Waypoints.xml.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

 Share