Jump to content
The simFlight Network Forums

John Dowson

Members
  • Content Count

    3,723
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by John Dowson

  1. I don't know what video you are talking about. Have you tried looking at and following the documentation? Start with the User Guide, especially the section The Easy Step-by-Step Way to Calibrate Your Controls. If you still have issues, then post what you have tried, what problems you have, and also include your FSUIPC7.ini file. Be patient! John
  2. Yes its working - although I don't know why you would want to use this function. Its a hangover from a previous implementation. The files are created under your AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work folder (which is the WASM persistent storage area for the FSUIPC WASM module).
  3. I also noticed this in the 747. There is an lvar (on the 747) for standby power: XMLVAR_StandbyPower_Selector. However, I've just tried this and it only seems to work switching between AUTO and BAT, and cannot switch to or from OFF. As for lvars in FSUIPC7, I have just released an early-access version with lvar support. For documentation on how to use lvars with FSUIPC7, you have to look at the FSUIPC6 documentation for the time being (and also have the WASM module installed - just download, unzip and move to your community folder, instructions on the WASM announcement page). I wi
  4. I'm not sure about the 748 as its an add-on that I don't have. Enable event logging and activate the controls in the UI and see what events are logged. For the stock 747, it has been reported that the Master Battery Set event (as well as offset 0x281C) only work to switch the battery off but not on. When clicking in the UI, it sends the event ELECTICAL BUS TO BUS CONNECTION TOGGLE with a parameter of 17, however assigning to this does nothing. But, using a parameter of 0 seems to turn all power off/on, but doesn't change the UI switch state. For the Standby Power (again, in the 747)
  5. Did you try re-installing the VC++ redistributables as advised? Sorry, no refunds. You can download and try before purchase, and I also offer time-limited licenses for those who wish to try the registered version before purchase. We do not provide refunds as once the license is issued, it cannot be revoked (no real-time license validation). The issue is that you do not have the correct windows files installed to use the software. This is easily fixed by following the advice I have already given.
  6. Try removing these from the [JoystickCalibration] section of your ini files: then reload you assignments. You should then be able to calibrate those axes separately, or use the mapping checkboxes.
  7. 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 🙂 Sorry, I meant that you can use fsuipcw_getLvarIdFromName first to get the id. You should be able to use the API either on name or id really. I think I'll also add some convenience methods to let you use the name directly.
  8. Yes, but you can just use fsuipcw_getLvarNameFromId first to get the name.
  9. FSUIPC receives the aircraft name from Simconnect via the TITLE simvar. It will most likely be an issue with the mod you are using. Maybe try with another mod (i.e. stable if using development, development if using stable).
  10. Yes, sorry - had to switch to using basic types and remove the need for the c/c++ headers for use with other languages.
  11. Issues like this after many hours of flying using various 3rd party add-ons (including FSUIPC) is usually due to an old SimConnect bug (since ESP days) where SimConnect runs out of client connections. This seems to affect all versions of SimConnect. There is further information on this issue in this forum, so search for that. There's no real solution, but you should increase the MaxClients parameter in your SimConnect.xml to at least 128 (or the maximum, whatever that is). You also posted in the User Contributions sub-forum, where it explicitly states NOT for support requests. I have mo
  12. You can disable controllers in Steam can you? I didn't know that! In MSFS, in the controllers page (where you edit your assignments) you can create profiles for each of your controllers. If you create a new MSFS profile there, it will automatically be empty, meaning that nothing will be assigned to your controllers.
  13. Thats the general Axes section, where you want to copy the assignments from your [Axes.TBM] (or whatever your TBM profile is called) to.
  14. This is because you are mapping your mixture 1 settings to 2,3 & 4, as indicated by the message 'Axis copied from mix 1'. It looks like its not copying the reverse to the other axis. What version of FSUIPC and what FS are you using? Could you show me your FSUIPC.ini file please, as well as a .log file. Thanks.
  15. Please find attached v7.1.0d of FSUIPC7 that has lvar support via macros and lua scripts. (i.e. as in FSUIPC5/6). This is an early 'pre-release' for testing. I am planning on updating the installer (to add the WASM) + the documentation this week, and when that is done I will release as a full beta later this week (or early next week).. To use, you must have the FSUIPC WASM module installed. When FSUIPC7 is started, if the WASM is detected there will be a new LVAR menu under the Add-ons menu. To activate lvar functionality, you need to Enable through this menu (you only need to do this o
  16. And don't forget, I have only included a hvar file for the A320, so they will only be available for that aircraft, unless you have some hvar files for other aircraft. If you do, please share!
  17. You can only access hvarsfrom the new lvar menu at the moment (Activate Hvar...). As well as the new controls above (which are still to be implemented), I also need to add lua/macro functions for hvars....
  18. Please find attached v7.1.0d of FSUIPC7 that has lvar support via macros and lua scripts. (i.e. as in FSUIPC5/6). This is an early 'pre-release' for testing. I am planning on updating the installer (to add the WASM) + the documentation this week, and when that is done I will release as a beta. To use, you must have the FSUIPC WASM module installed. When FSUIPC7 is started, if the WASM is detected there will be a new LVAR menu under the Add-ons menu. To activate lvar functionality, you need to Enable through this menu (you only need to do this once!). Once I have updated the install
  19. The message will be a false positive. Try disabling your ant-virus software before installing, or add an exception to allow it to be installed.
  20. Here it is: https://forums.flightsimulator.com/t/simconnect-mega-thread/116305/78?u=impolitegem5317 If you can't access let me know and I'll PM you the details. John
  21. So you are using MSFS, not FSX? I will update the title of your post.... The first think to do is to check your assignments in MSFS. If assigning in FSUIPC, make sure you create an empty profile for each of your controllers (just create a new profile for each, which, by default, will be empty). If you don't have any assignments in MSFS, please show me your FSUIPC7.ini file and an FSUIPC7.log file and I'll take a look.
  22. What happens if you start (or restart) your ACARS one the engines are running? If this occurs with just the FBW mod (which one - have you tried a different one?), you should probably report to FBW. How is your ACARS system determining the flight position - using FSUIPC?
  23. There was an error in this function, corrected now. Also, the dll posted on the 7th is not build against the latest WAPI. Please try the attached:FSUIPC_WAPID.dllFSUIPC_WAPID.lib FSUIPC_WAPI.h You may get better results with those, but I don't think its fully functional but I'm not sure why.. Thats interesting...even the list functions?
×
×
  • 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.