Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About andhog

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
  1. Unfortunately there's apparently something seriously wrong with the latest world update. Having a standalone WASM module in your community folder causes CTD when starting MSFS 😕
  2. @John DowsonYou have a pull request 🙂 https://github.com/jldowson/FSUIPC_WAPI/pulls
  3. Exactly, but that's only half true now. You can get LVar values by name but you can only set them by ID.
  4. My application is based around an .ini file with the names of the variables the user like to save/load, so I guess I'm using your API in the opposite direction from what you intended 🙂
  5. So, first I rebuilt the FSUIPC_WDLL with the latest WAPI lib (that's not necessary now that John have done it for you 🙂). Then I have the DLL functions declared like this (the ones I'm using in my app): [DllImport("FSUIPC_WAPID.dll", CallingConvention = CallingConvention.Cdecl)] private static extern void fsuipcw_init(IntPtr hWnd); [DllImport("FSUIPC_WAPID.dll", CallingConvention = CallingConvention.Cdecl)] private static extern void fsuipcw_start(); [DllImport("FSUIPC_WAPID.dll", CallingConvention = CallingConvention.Cdecl)] private static extern void fsuipcw_end(); [UnmanagedFunctionP
  6. Now it works perfectly! I have also tried the dll in a C# WinForms application and it works as well. Thank you!
  7. Sorry, copy&paste error there. I can only access 1168 Lvars, as you can see in the log files.
  8. So I've finally tested version 0.4.8 and it finds more LVars than the previous version, but unfortunately not 2044. The CRJ has 1738 LVars and when I create the LVar file(s) it lists all of them (in 14 files), but I've only access to 1738 with the client and using the WAPI in my app. FSUIPC_WASMIF.log FSUIPC_WASM.log
  9. I have gone through all your posts on the forum now but I can't find that description. Could you please give me a link to it?
  10. The app I've built around your module and the API is for saving and loading the cockpit state (switches, knobs etc) in the CRJ (for now, but it should be relatively easy to apply it to other aircraft as well). At the moment one have to do this manually, but I would like to add an option so that it loads the state automatically when you start a flight and saves it when the flight ends. Super! I will look it up. It was just a side note, nothing I expect you to help me with. But I appreciate that you explained a little bit about it. Perhaps I should skip the idea of subscribing to the eve
  11. I've not been at home for a while, but now that I am I will have a look at your latest accomplishments 🙂. I must also learn some SimConnect and figure out a way to trigger the read and write of LVars when the sim is paused and started. I recon it's a pretty basic task, but without any prior experience in this particular department it's a challenge. But hey, who doesn't like a challenge? 🙂 I'll let you know as soon as I've tested.
  12. Unfortunately that didn't go so well. First I tried with the WASM client (see the log files that I for once managed to attach!). Then I compiled my application with the new FSUIPC_WAPI lib and that worked, but when I started the app I got "Microsoft C++ exception: std::out_of_range". I think I might have found the reason in WASM.h: typedef struct _CONFIG_CDA { char CDA_Names[MAX_NO_LVAR_CDAS + MAX_NO_HVAR_CDAS + 1][MAX_CDA_NAME_SIZE]; int CDA_Size[MAX_NO_LVAR_CDAS + MAX_NO_HVAR_CDAS + 1]; CDAType CDA_Type[MAX_NO_LVAR_CDAS + MAX_NO_HVAR_CDAS + 1]; } CONFIG_CDA; And since yo
  13. Hi there! Hope you had a great easter! I will try that right away. The LVar files created by your WASM client gives me 1738 LVars. However, I don't think anyone need access to all of those at the same time so your suggestion to have a file with variables of interest together with the module would be great.
  • 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.