Jump to content

Wrong Heading


Recommended Posts

I just start to handle SweatBox. It looks great for the trainning purpose.

When a set a heading for the aircraft it is flying a +15º Magnetic Heading than the hdg I did set - i.e. I set 165º and it is flying 180º Mag Hdg

I´m testing it in Sao Paulo, Brazil area - S22.0 W47.3

I´m using a Sector File with a 19.1 Mag Declination. That was my first concern - the difference was due to the Mag Dec, but... the diference is 15º, not 19º

Thaks for any help

Jose Olyntho

Jose Olyntho

VATBRZ - ID 816398 - INS+

atc2o_peq.png

Since 2001 Trainning Pilots and Controllers at http://www.jo.eng.br/

Link to comment
Share on other sites

Dear Chistopher

Sorry about the delay.

I got twice a non deliver message (reason: Illegal Attachment) from your Host sending the files you asked

I just sent the files again.

 

So I renamed both files - SFile and Aircraft file - to simple TXT files.

Please change back their extensions when testing them, ok?

 

Thanks for your time and your atention

TCare

Jose Olyntho

Jose Olyntho

VATBRZ - ID 816398 - INS+

atc2o_peq.png

Since 2001 Trainning Pilots and Controllers at http://www.jo.eng.br/

Link to comment
Share on other sites

Dear Thomas

Below the Header I´m using at the SFile. Where we can see how the 19.3 Mag Var is defined

 

 

; --- Region: ACADEMIA E TMA-SP - V2.3 (SBYS_APP) Sector File

; --- Version: 12:05:01 04-Jan-05

; --- Built By: José Olyntho Machado Jr. ([email protected])

; --- Generated with GNDMAKER.EXE by Corey M. Wirun ([email protected])

; ---

; --- Do not manually edit the comment lines in this file!

 

#define white 16777215

#define navy 8388608

#define fuchsia 16711935

#define lime 65280

#define maroon 128

#define yellow 65535

#define gray 8421504

#define red 255

#define blue 16711680

#define silver 12632256

#define olive 32896

#define green 32768

#define aqua 16776960

#define teal 8421376

#define purple 8388736

 

 

[iNFO]

ACADEMIA E TMA-SP - V2.3

SBYS_APP

SBYS_APP

S021.59.04.000

W047.20.39.000

60

56

19.3

1.000000

 

[Airport]

......

 

Any help will be apreciated

TCare

Jose Olyntho

VATBRZ - ID 816398 - INS+

atc2o_peq.png

Since 2001 Trainning Pilots and Controllers at http://www.jo.eng.br/

Link to comment
Share on other sites

I have tried writing scenario's with the BOS sector file and everything works fine.

Writing scenario's for New Zealand sectors the aircraft fly a track sixty degree's less than the heading inserted in ACSIM.

I've tried altering the Mag Var values in the INFO section of the sector file but that doesn't seem to make any difference.

BOS has a Var of 16W while NZ is 21E a difference of 37 degrees so i dont think the answer lies here.

BOS is about the same distance north of the equator as NZ is south, thought there might be some corelation here but havent found it.

 

Oh well if we can't find the answer we will have to do all our NZ training in Boston. This training tool is just so good we have to find a solution to make it work downunder.

 

Rgds

John Gayford

Link to comment
Share on other sites

Hi Chris and Jose

You're right Jose we just have to be patient. We are all very appreciative of the time and effort people like Chris put into their software so that we can have so much fun.

A question while we are waiting. I made a light hearted remark in a previous post about the software working in the Boston area and that we could move our training to that area.

I have put together a scenario for the Boston area hoping to use it while we wait but i now suspect it would intefer with anyone else wanting to run a Boston exercise on the sweatbox server. Is this the case?

If so, would it be acceptable to use the Boston sector on the server outside your normal training hours ( say after 1am your time) taking advantage of our 8hr time difference.

Rgds

John Gayford

Link to comment
Share on other sites

John, did you try setting the magvar in the sector file to match the ones we use at Boston? (16W) Sounds like you did, but I want to make sure.

 

The only causes I could think of for the error are magnetic variation and the convergence of lines of longitude nearer to the poles. You say your sector file is in an area the same distance south of the equator as Boston is north, (42 degrees) so that shouln't be it.

 

Can you post the info section from your sector file?

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Hi Ross

 

[iNFO]

New Zealand Ubersector v1.1

NZWN_CTR

NZWN

S041.19.40.854

E174.48.30.285

60

46

-21.7

1

 

Thanks for your help. Changing the -21.7 to 16 has the effect of rotating the Geo Map by 37degrees clockwise.

Makes NZ look very strange .

The A/C tracks are then in error by some 22 degrees.

Sounds from Chris's post that he has identified a possible cause and that given time a solution will be found.

Thanks again for your interest.

Rgds

John Gayford

Link to comment
Share on other sites

OK, we have had this same problem since the Beta version. It definitely is not related to the MAG Variation since flying heading 160 doesn't work while heading 161 works just fine. We have been trying to solve this for over a year now. Finally, last night as I was trying to fall asleep, I figured it out:

 

We are trying to be "smart" and as part of our sector file, we use the NDB fixes to show the MVA. It so happens that the MVA around Mt Rainer is 16000 feet. Hence we put an "NDB" in the sector file called "160". Now when we try to fly an aircraft using AcSim on a heading of 160, it thinks we mean the navaid called "160" and flies toward the "NDB".

 

For anyone who has this problem, I would suggest looking through your sector file to see if you have a navaid with a three-digit name. (Use the Home command in ASRC or .center command in VRC).

 

To solve this problem which really isn't a problem in AcSim, I would recommend one of the following things, in order of preference:

1) Have AcSim ignore navaids consisting of three-digit identifiers

2) Change your sector file to use "navaids" that are in the format XX1 or XX9 rather than XX0.

3) Try to fly heading XX9 or XX1 instead of XX0

 

Hopefully this is the solution for most of the wrong heading problems that are not related to incorrect magnetic variation. Please let me know if this solves it for you!

 

--

Tomas Hansson

TA, ZSE

Tomas Hansson

Link to comment
Share on other sites

Tomas,

 

Very good catch but unfortunately, that's a different problem than the one the others seem to be having. I was looking at the code and my calculations for magnetic variation are incorrect which is why the headings are off for them. I need to read the variation from the sector file instead of trying to calculate it myself to solve the problem.

Christopher Serio,

Developer XTower/AVC/XSB/ACSim (Sweatbox)

667.png

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...