Board index FlightGear Support

2017.1.2 amend fix.dat problem  Topic is solved

All general support: help on flying, installation, hardware, getting online etc. There are lots of users and developers to help you out.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- where did you download your aircraft/scenery from?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).

If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

2017.1.2 amend fix.dat problem  

Postby SVW » Tue Mar 28, 2017 5:09 pm

Hi folks,
2017.1.2 works great, BUT: I can't amend the fix.dat file. Unzipped fix.dat.gz with 7zip, amended the waypoints with Notepad++ (code UTF-8 without BOM), rezipped, replaced the old fix.dat.gz by the new one. FG loads and initializes navdata at startup, but the map won't show any fixes at all :shock:
Any ideas? Thanks for help in advance!
Greetings, svw

EDIT:
The coding must be ANSI, then it works fine. Sorry to bother you.
cheers
SVW
 
Posts: 54
Joined: Sat Jun 13, 2015 5:54 pm

Re: 2017.1.2 amend fix.dat problem

Postby rominet » Tue Mar 28, 2017 7:10 pm

Hi SVW,

What Windows calls ANSI... not sure if all fixes follow this, but at least the copyright sign at the top of the file is in ISO-8859-1 (aka latin1).

Taking the opportunity to tell you that in FG 2017.2.0, there is an easier and cleaner way(*) to add missing fixes (or even move misplaced existing fixes): see this message. And the same works for nav.dat.gz entries. It is the logical extension of the previously existing NavData/apt feature for airports.

The only thing is: please don't do this only privately: by submitting your corrections to the X-Plane scenery gateway (if not already there), you ensure that one day they will benefit everyone when FG updates these files (this is not directed at you personally, just a general remark!).

(*) Easier because you don't even have to compress the files (though it is possible), and can call them the way you want, as long as they end in .dat or .dat.gz. Just put them in a NavData/fix folder inside a scenery directory (thus, NavData should be a top-level directory inside one of your scenery paths).
Cleaner because you don't have to modify FG's files, you can easily disable your changes/reenable them, and when FG upgrades the files or when you reinstall it for whatever reason, your changes won't be lost.

Here are my files for LOWI and MHTG:

NavData/fix/LOWI-surroundings.dat:
Code: Select all
I
600 Version - Prepared by Florent Rougon

47.285633  010.570739 ELMEM
47.289506  010.645575 WI7X0
47.309697  011.052636 WI7X1
47.305883  011.085808 WI7X2
47.255247  011.239628 WI7X3
47.252219  011.270253 WI7X4
47.258944  011.332261 RW08
47.271247  011.446544 WI1X3
47.376669  011.825003 WI0X2
47.430925  011.940064 WI0X1

NavData/fix/MHTG-surroundings.dat:
Code: Select all
I
600 Version - Prepared by Florent Rougon

16.917833 -085.349833 TG001
14.338667 -087.191667 TG002
14.405167 -087.016333 TG003
14.321833 -087.531667 TG004
14.209667 -087.683000 TG005
14.182667 -087.209833 TG006
14.127667 -087.208833 TG007
14.086667 -087.208167 TG009
14.050833 -087.220667 TG010
14.041500 -087.248833 TGXY1
14.077000 -087.304667 TGXY2
14.098333 -087.323500 TGXY3
14.118167 -087.332667 TGXY4
14.173167 -087.323833 TGXY5
14.224500 -087.274833 TGXY7
14.057333 -087.200667 TG018
14.084667 -087.208833 TG020
14.108333 -087.207000 TG021
14.153500 -087.215500 TG022
14.178000 -087.216500 TG023
14.208333 -087.206667 TG024
14.056833 -087.218667 TG025
14.043500 -087.256000 TG026
14.073333 -087.308167 TG027
14.155000 -087.315000 TG028
14.255000 -087.201833 TG030

Note: some fix names containing X or Y are slightly different from the real ones, otherwise FG wouldn't show them (I believe this is due to an intentional filtering in order not to clutter the map too much; probably this should be improved some day to depend on the zoom level...).
rominet
 
Posts: 473
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: 2017.1.2 amend fix.dat problem

Postby SVW » Wed Mar 29, 2017 2:02 pm

Merci Florent! J'espère à bientot! :D
svw
SVW
 
Posts: 54
Joined: Sat Jun 13, 2015 5:54 pm

Re: 2017.1.2 amend fix.dat problem

Postby rominet » Thu Mar 30, 2017 8:26 am

Ja, ja, hoffentlich! :wink:

(yep, yep, hopefully!)
rominet
 
Posts: 473
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: 2017.1.2 amend fix.dat problem

Postby RenanMsV » Thu Jun 08, 2017 4:37 am

World Fixes by Airac 1705


Thats no English video, but I'm sure that you know what to do with the nav.dat.gz file.
www.flightgearbrasil.com.br
www.fgbrazukas.wixsite.com/fgbrazukas
RenanMsV
 
Posts: 112
Joined: Thu Oct 27, 2016 2:02 am
Callsign: BR-RVD

Re: 2017.1.2 amend fix.dat problem

Postby rominet » Fri Jun 09, 2017 4:50 pm

Glad to hear it works for you, but in FG 2017.2 and later, there is a cleaner way to do that, as mentioned in my message above. Basically, you can put *.dat or *.dat.gz files in NavData/fix and NavData/nav (as well as NavaData/apt) inside any scenery directory. You may want to create a scenery directory just to contain a NavData subdirectory for this kind of changes. FG will find the .dat and .dat.gz files at startup and merge them in RAM with the canonical ones in $FG_ROOT. This avoids modifiying contents under $FG_ROOT and allows enabling or disabling your changes by simply adding or removing the corresponding scenery path (either with --fg-scenery on the fgfs command-line, or with the corresponding interface in your launcher, if you use one).
rominet
 
Posts: 473
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: 2017.1.2 amend fix.dat problem

Postby RenanMsV » Sat Jun 10, 2017 12:54 am

Yeah I know, instead replace your apt dat just add it as a custom scenery. I'm just giving you a file with all fix in the world. Thanks
www.flightgearbrasil.com.br
www.fgbrazukas.wixsite.com/fgbrazukas
RenanMsV
 
Posts: 112
Joined: Thu Oct 27, 2016 2:02 am
Callsign: BR-RVD


Return to Support

Who is online

Users browsing this forum: No registered users and 1 guest