Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Evander

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok, thanks for your effort. But how about offset 0874 he gives always the VOR?? Evan
  2. Hey, it's not the hard way it's another way. It's very simple infact: I know thw planes height I know thw runway height I know the glideslope degrees And when I also know the correct distance is it very simple Example: at 1000 feet with a glideslope of 5.50 degrees the distance = 1.709 Nm. at 1000 feet with a glideslope of 3.00 degrees the distance = 3.140 Nm. So when the plane is on the glideslope at 500 feet and the Glislope is 3.00 degrees distance is then 1.570 Nm. When on the glideslope at touchdown the distance is 0 Nm. In the graphical is the
  3. I check the distance from the plane for an ILS aproach with a glideslope in a graphical chart, when the distance is wrong then the plane is of the glideslope, i have made a work around but this is not 100% proof. So I imust have the lat/lon/alt from the localizer not the VOR , the alt is always good see this video:https://www.youtube.com/watch?time_continue=39&v=lDk3JpNb5mw&feature=emb_logo Ofcourse in this video is all working well. Evan
  4. I think not because the ILS identifier also not changed. Wich flag do you mean? When you mean offset 0C4D then Yes: on approach bit 7 and 6 set (192) near touchdown bit 7 (128) halfway runway bit 3 and 5 (40) and then bit 7 set (128) at the same time change to the VOR. Evan
  5. After further investigation I noticed that when you make a go around that after about 4 miles out it change also to the VOR without changing the radio frequency or something else. Evan
  6. the offset 0874 gives always the VOR and the offset 0C4D gives bit 7 set 1082023 Monitor IPC:0C4D (U8) = 0 1082039 SimRead: 0C4D="NAV BACK COURSE FLAGS:1" [also 0C4A] INT32: 131 (0x00000083) 1082039 Monitor IPC:0C4D (U8) = 128 1082039 SimRead: 0C4D="NAV HAS LOCALIZER:1" [also 0C4A] INT32: 1 (0x00000001) 1082039 Monitor IPC:085C (S32) = 5652883 1082039 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 1082039 Monitor IPC:0874 (S32) = 5652010
  7. Default scnenery Default Cessna 172 No NAVAID updates Airport EDDK Look at the end of the log, where it goes wrong. Reads the latitude and longitude ok and then: 1021713 Monitor IPC:085C (S32) = 5652010 the number now is: 5652010 must be 5652883 Evan Log file: ********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson ********* Windows 7 Ultimate 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) fsx.exe version = 10.0.61472.0 Reading options from "F:\FSX installed\Modules\FSUIPC4.ini" Running inside FSX on Windows 7
  8. Hello Pete, Thank you for helping me. I see nothing weird in the log Tested on EDDK RW 25 freq: 109.100 swap freq: 111.100 Output in FS windows gives: I started with no Ils and no VOR gives 0 (111.100) First swap was wrong gives number 5652010 the same as the VOR 2e gives 0 is ok 3e gives 5652883 is ok 4e gives 0 is ok 5e gives 5652010 and is wrong For FSX is this no problem the ILS is working fine Attached a screenshot Log File gives: ********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson ********* User Name="" Use
  9. FSUIPC 4949c FSX SP2 It's very strange when i swap the freq. I see short the good value and it change immediately in the wrong one. I have cheked many different default Airports, all the same. Evan
  10. Hello, I noticed that offset 085C has strange behavior The manual says: VOR1 Latitude in FS form. Convert to degrees by Ok-SimC N/A *90/10001750. If NAV1 is tuned to an ILS this gives the glideslope transmitter Latitude. But sometimes it reads the VOR1 latitude not the NAV1 latitude When there's an ILS Same problem with the longitude, offset 0864 I checked with the FSUIPC logging in a window, when a few times I swap the frequency, it gives the wrong result, it's very inpredictable. So in my program it reads about I guess 20% wrong. Have someone a solut
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.