Shared memory ADI question
-
Hello,
I’m trying to read the informations from the shared memory. All seems ok, but I can’t get to work the ILS bars in the ADI.Can someone explain me those two entries?
// ADI values
float AdiIlsHorPos; // Position of horizontal ILS bar
float AdiIlsVerPos; // Position of vertical ILS barThanks in advance!
-
post edited out by Red dog , too much wrong information
-
…. Also it could be the ILS isnt even in the right place for the particular field since the change of terrain files. Case in point Osan airbase, the runway should be 90/270 however it is 32, 14 tower callbacks on takeoff are screwed up and the Inbound for landing you can be over the runway and the tower will say your outside my airspace call me back at 30 miles.
…
This is factually incorrect IF one has done their setup properly, has NOT porked their install or has NOT fouled up the works with ill advised user modifications
You really need to stop spreading this unfounded rumour. Users who don’t know any better will read it and think it’s true.
-
Mebbe he is flying out of Pusan and hasnt noticed?
-
I was just asking what those value represent and in wich format they are (degrees, radians, …) I’m trying to code my own extractor, all function good, but I can’t get those ILS bars move as the ones in the Falcon 3d pit.
-
Check to see if the X/Y numbers are reversed (X is Y and Y is X).
This was certainly the case of the 3D Coordinates of the jet in the shared memory.
-
I will try this ASharpe, thak you.
-
I was just asking what those value represent and in wich format they are (degrees, radians, …) I’m trying to code my own extractor, all function good, but I can’t get those ILS bars move as the ones in the Falcon 3d pit.
I am far, far away from having any understanding how this works. However, the one relevant thing that was suggested in the ‘controversial’ post in this thread could be worth considering …. is it possible that the needles are ‘behind’ the float? Are they separate renderings and if so, are those rendering layers ordered somehow?
(And I apologize for my role in taking your thread off topic. :oops: )
-
However, the one relevant thing that was suggested in the ‘controversial’ post in this thread could be worth considering …. is it possible that the needles are ‘behind’ the float? Are they separate renderings and if so, are those rendering layers ordered somehow?
There are no renderings from the shared memory output, the shared memory output is simply out-putting two values assigned to the ADI. My guess would be these are the X/Y coords of either the center of the needle or the end of the needle, relative to one corner or the other of the item in question.
The rendering issue of Z-index order would depend on what he is doing with this data, but it sounds like he is having trouble with the data itself matching what is in the game.
-
Apologies for the erroneous post on here, cant even recall what is was about. Im assuming its the ILS needles that should appear on the floating situation ball on the heads down display. Ive been using BMS the last 8 weeks for approaches and have yet to see them. Thanks to Red Dog for removing the post. I suppose I must be doing something wrong like failing to turn on ILS, fasiling to select correct tacan for field, failing to select correct runway heading, failing to see the ILS crosshairs move away from the centre of the screen in landing mode.
But as mentioned previously I do not have a copy of the Falcon BMS code to work with or refer to, funny thing is Allied Force, Freefalcon both have the needles present as soon as you turn the rotary knob to TACAN / ILS, still I dare say its going to be sorted out in the next update. Keep up the good work guys.
-
I suppose I must be doing something wrong like failing to turn on ILS, fasiling to select correct tacan for field, failing to select correct runway heading, failing to see the ILS crosshairs move away from the centre of the screen in landing mode.
Just FYI, TACAN channel and HSI course has nothing to do with ILS needles.
-
… both have the needles present as soon as you turn the rotary knob to TACAN / ILS,
Once again, there is no bug in BMS on that area.
Please, give a factual example:
Which airfield? Which runway? What frequency? Did you set the ILS “ON”? … Did you read the BMS-Manual.PDF ?On previous versions of Falcon4, ILS wasn’t working like IRL (you should know this as a former military pilot)
EDIT:
Im assuming its the ILS needles that should appear on the floating situation ball on the heads down display.
If you are calling the ADI an “head down display” yes, your assuption is correct.
-
Instead of flaming the devs, how about describing exactly, step by step, what you are doing in-flight ?
-
Instead of flaming the devs, how about describing exactly, step by step, what you are doing in-flight ?
Because doing that would reveal the trolling for what it is…
-
But as mentioned previously I do not have a copy of the Falcon BMS code to work with or refer to, funny thing is Allied Force, Freefalcon both have the needles present as soon as you turn the rotary knob to TACAN / ILS, still I dare say its going to be sorted out in the next update. Keep up the good work guys.
AF had automatic ILS as soon as you were on the correct tacan channel. Highly unrealistioc and that was made more realistic in BMS.
you do not need to wait for an update, all works fine. you do need to educate yourself on how the ILS work in the F-16
I suggest you read the dash 1 and the chart tutorial