|
|
Post by lecoyote on Feb 8, 2022 15:21:52 GMT
Hi there Hervé,
Thanks for the work you put into all this.
I'd like to know if it would be possible for you to "fix" the TACAN stations. Currently, they are defined as VOR stations with dmeOnly="TRUE", so no bearing reading available. I tried converting them to the real, native Tacan type available in the SDK, but the default gauges don't seem to be able to make anything out of it.
Right now my only solution would be to look up the TACAN stations I need one by one, decompile the BGL, extract the VOR section, make the changes and compile them back into a new file. It works, but it's going to take some time. I'm thinking you probably have a better way to do this semi-automatically; would that be correct?
Thanks a lot! Cheers --
Romain
|
|
|
|
Post by Herve Sors on Feb 8, 2022 17:09:55 GMT
Hi Romain In my updates, TACAN facilities are not defined as VOR stations with a dmeOnly="TRUE" but include 2 separate records (on the same Chanel of course) - A TACAN record that is coded as so (using the new P3Dv4-5 SDK syntax) that transmit azimut (bearing) on TACAN receivers - A VOR (DME only) record that transmits DME distance on standard civilian VOR receivers This last record shall not include an azimut (bearing) signal otherwise TACANs will act as VORTACs An example below (all TACANs only are coded this way) <Tacan lat="44.4769361" lon="-73.1567556" alt="93.88" range="74080" magvar="15.00" region="K6" ident="BJA" channel="71X" dmeOnly="FALSE" name="BURLINGTON"> </Tacan> <Vor nav="FALSE" dme="TRUE" lat="44.4769361" lon="-73.1567556" alt="93.88" type="LOW" frequency="112.40" range="74080" magvar="15.0" region="K6" ident="BJA" name="BURLINGTON"> <Dme lat="44.4769361" lon="-73.1567556" alt="93.88" range="74080"/> </Vor> So there's nothing to "fix" in my opinion, and TACANs behave as they should for civilian aircrafts (DME only information). The only problem is that, on default military TACAN gauges, TACAN azimuth is correctly transmitted (tested) but not DME. It seems to be a P3D bug. See here www.prepar3d.com/forum/viewtopic.php?f=6311&t=143736However, it appears it is not at all the subject of you post Feel free to tell me if I misunderstood some points Regards Hervé |
|
|
|
Post by lecoyote on Feb 8, 2022 19:29:11 GMT
Hi Hervé,
In the meantime I've created a small BGL where all the french TACANs are declared as VORs, which obviously work. But I'd love to get the real TACANs to work.
Does your BGLFacilityScanner look for TACANs? Because I couldn't find them, whereas I *did* find the DMEs.
However, I do confirm that, whether it's the default military gauge, Dino Cattaneo's Hawk, or RFN's TACAN gauge, none can find the TACAN
Where else should I look?
Merci beaucoup !
--
Romain
|
|
|
|
Post by Herve Sors on Feb 8, 2022 22:31:14 GMT
Hi Romain, >>Does your BGLFacilityScanner look for TACANs?<< I'm unsure. Will have a look to the code and let you know. EasyNavs does extract TACANs for P3Dv4-5 BGL files containing such records It is also easy to examine files for TACANs (and other navaids) with the latest BGLViewer from Patrick Germain www.fsdeveloper.com/forum/threads/bglviewer-for-fsx-bgl-files.432840/page-5www.fsdeveloper.com/forum/attachments/bglviewer2020_2_13-zip.79223/ >>I do confirm that, whether it's the default military gauge, Dino Cattaneo's Hawk, or RFN's TACAN gauge, none can find the TACAN<< On which BGL file(s)? I exchanged a lot on the subject with several users and there were no problem on their side (except this missing TACAN DME function). I cannot tell you how they tested it but it worked nicely. May I suggest you privately contact Michel ("mpni") on the Prepar3D forum- In case he doesn't answer, let me know by PM(I should have a contact email). He speaks French. Hervé |
|
|
|
Post by lecoyote on Feb 14, 2022 18:23:39 GMT
Hi Hervé,
I've used BglViewer on scenery file NVX05010.bgl from the current cycle (the file is datez 27/01/2022). I looked up the Landivisiau TACAN. It shows up as a DmeOnly TACAN + a "Is Nav: No" VOR (see attachments). Same results with the SAL TACAN from NVX06020.bgl.
To me this is absolutely in line with the behaviour I'm seeing in sim, ie. DME only but no bearing. I can't understand how it would work otherwise when it specifically says the VOR are declared as "not a VOR".
I will get in touch with Michel, but perhaps it would be more productive if we could arrange a discussion the 3 of us together? Thanks again for your time, Best regards --
Romain
Attachments:
|
|
|
|
Post by Herve Sors on Feb 15, 2022 9:11:19 GMT
Hi Romain,
In your pictures, you only show the VOR part (DME only indeed) but NOT the TACAN record (that is in another section).
As previously stated there are 2 records (a TACAN and a VOR).
For more clarity, let's discuss this point on voice if you wish. Please email me so as we can arrange a Skype meeting. We'll see later on if Michel wish to join
Cordialement
Hervé
|
|
|
|
Post by lecoyote on Feb 15, 2022 14:41:04 GMT
In your pictures, you only show the VOR part (DME only indeed) but NOT the TACAN record (that is in another section). The second section *is* from the TACAN section, as indicated by the "Ymode" attribute.
We can arrange Skype or Discord, as you wish! I'm emailing you right away. Thanks! --
Romain
PSEdit: please check your spam folder just in case, Hotmail being what it is, I sometimes get branded as such  |
|
