Jump to content
The simFlight Network Forums

Read A: variable by name?


RoystonS
 Share

Recommended Posts

Thanks. Ok, so to read those values I need to know both the offset and the datatype (e.g. 8-byte float, 2-byte int)?

Is there any way to look that information up based on, say, an 'A:' simvar name?

 

I'm basically trying to provide a simple way to control the lights on a Honeycomb Bravo. The standard Bravo software supports A: simvar names but not lvars so I was hoping to improve on that. I'm able to read lvars successfully through FSUIPC and the .NET wrapper but using offset+datatype instead of name for 'A:' variables is a bit less user-friendly.

Link to comment
Share on other sites

11 minutes ago, RoystonS said:

Is there any way to look that information up based on, say, an 'A:' simvar name?

Which FS are you using? If using FSUIPC7. see the offset status spreadsheet - this has the name of the simvar held in each offset, when applicable. I've also attached it. If using other versions of FSUIPC, you can still use this to see which simvar is used, but first check the offset status document for the version of FSUIPC you are using to see if available.

14 minutes ago, RoystonS said:

I'm basically trying to provide a simple way to control the lights on a Honeycomb Bravo. The standard Bravo software supports A: simvar names but not lvars so I was hoping to improve on that.

I thought the standard bravo software to control the bravo lights was via the AFC_Bridge from Aerosoft. There are also a couple of solutions posted in the User Contributions section, although I am not sure of the current status. See the following:

 

 

20 minutes ago, RoystonS said:

I'm able to read lvars successfully through FSUIPC and the .NET wrapper but using offset+datatype instead of name for 'A:' variables is a bit less user-friendly.

Accessing simvars via offsets was the main original purpose of FSUIPC and this method of reading/writing simvars has been around since FSUIPC was originally conceived. The lvar support came later.
The size of the offset is specified in the document and it should also be possible to determine the type, either from the description or by simply logging the values first.

John

 

Link to comment
Share on other sites

Yes, the AFC_Bridge from Aerosoft works but can _only_ access simvars, so it's not possible to get the master warning/caution lights to work as they're lvar only. It's also very slow, with 1s fixed updates, and its configuration is very clunky. (I've written all the details up here if anybody wants them: https://github.com/RoystonS/honeycomb/blob/main/bravo-lights.md)

I'm on MSFS with FSUIPC7. I'm trying to provide something fairly straightforward for non-developers to use without having to edit LUA code (hence preferring simvars to offset+type+size).  Ok, will check the offset status spreadsheet, and I might have a look at making direct SimConnect calls to read the A: variables.

Thanks!

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.