Not sure if I understand your question but i'll give it a shot.
You can't extract local gauge variables from Flight Simulator using FSUIPC. You can find everything you CAN extract using FSUIPC in the "FSUIPC Offsets" pdf document that comes with it.
If you can't find what you need there try to...
I just started using FSUIPC. I am trying to create a table in C that acquires a series of variables from FSX (latitude, longitude, altitude, aicraft type, flight number).
I can get all the parameters fine but I don't know how to make it so that they are updated at a specific rate.
One last question (hopefully) where exactly should I place the EXE.xml, DLL.xml and SimConnect.xml files? The Simconnect overview tells me:
...But I have Vista...
Never mind... The Search Engine in Vista is terrible I found it manually in 2 seconds under: C:\ProgramData\Microsoft\FSX
Does anybody know of any straightforward Simconnect tutorials? I can't grasp much by trying to read the enormous document that came with the SDK. The URLs to Simconnect tutorials I found on similar forum posts were all broken:confused:
I was just wondering what would be the translation of " UseTransparency="Yes" " to FSX schema. I can't find anything in the Ace Tool that would allow me to define a mask image with that property. And without this property the image within the mask doesn't appear to be transparent in RGB 0,0,0...
I am trying to create a Way Point ALERT flag that goes off when the next way point is less than 4 miles away. But when I add a seemingly basic piece of code the entire gauge disappears:confused:... I really have no idea why.
Here is what is ruining my entire instrument:
Turns out when I used
(A:Indicated Altitude:2, feet) } 100 / flr
(14.34) flr =
And got the value displayed it did return 14, not 4. So it didn't read the 'ones value' but rather just rounded up to nearest integer smaller than the number.
Here's a little code I wrote to get just the 4...
Voce poderia postar sua pergunta em portugues? Acho q a pergunta seria mais clara. Pelo que eu entendi voce quer saber se eh possivel obter uma variavel XML do Flight Simulator e exporta-la para uma outra aplicacao?
So I want to create this specific HSI. I know some of you are pilots, I was hoping one of you would know the model number/make of this. If not can anyone please explain me what are:
- the "ALERT" flag on the left and the spinning thing:confused: on top of it
- The VN display on the top right...
It is possible. I know Mick Posch's Piasecki H-21C http://www.mickposch.com/flightsim/fs_freeware.htmhas a windscreen wiper switch located on the overhead panel. You might want to take a look at the H-21's gauge files that come with it and you should be able to find your answer. The...
As soon as I turned off the Auto Rudder the issue was solved. I tried 'position' and 'percent' for units. When I used 'position' the number returned was in between +1 and -1 and when I used 'percent' was in between .001 and -.001.
Either way my instrument works beautifully now...
Is anybody else having problems with their A:TURN COORDINATOR BALL variable?
None of my turn coordinator balls seem to work for ANY of my aircraft. It seems like I am getting a bad output from FSX, when I display the variable value (A: TURN COORDINATOR BALL, position) all I get is a constant...
that's great news thanks for sharing! Hopefully sometime in the near future Lockheed will open some simulation related positions for developers:D I've been dying to work for them and nothing is better than a shift from their part towards an area in which I already have some experience:D
ok I feel really retarded. I used a simple INCIDENCE ALPHA/ STALL ALPHA in the the Shift Script
(A:INCIDENCE ALPHA, degrees) (A:STALL ALPHA, degrees) /
and then calibrated the translation using nonlinearity (in which 0.65 is the middle neutral position)... really...
Okay so I figured the Fast Slow indicator should be pointing to zero if INCIDENCE ALPHA is equal to .65*STALL ALPHA. If it's greater then points to fast, if it's less it points to slow. Here's what I have so far:
<Element id="Define FastSlowInd">...
Has anybody figured out how to do a Fast/Slow Indicator? Would it be just the same thing as a trend indicator?
The only reason I am not sure is because I believe the angle of attack should be accounted for and yet I don't see it being used in any trend indicators samples I currently have.