Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,282
  • Joined

  • Last visited

  • Days Won

    271

Everything posted by John Dowson

  1. Ok, thanks for the update. Please also note that you should consult the documentation for such issues before posting, if you didn't already, as 99.9% of registration issues are covered in the installation and registration guide. John
  2. That does sound strange! Do you know what offsets the ATC map is using - possibly 0x0560 (Plane Latitude) and 0x0568 (Plane Longitude) or 0x6010 (GPS Position Lat) and 0x6018 (GPS Position Lon)? Whichever offsets it is using, try logging those offset using FSUIPC7's offset logging feature, and see how they change both with and without Spad.Next runnning. If Spad.Next is changing those for some reason, you will have to ask Spad.Next support about this - I don't think there is anything i can do if something else is changing the sim variables used... John
  3. No - that section is automatically generated by FSUIPC, and should not be touched unless assigning your own "joyletters" What type of device is this X-Touch Mini controller? FSUIPC should recognise all HID joystick type devices. If its a HID / USB device but no a joystick type device. you will have to use lua. There is a demo script provided called HidDemo.lua which you can adapt and try. If its an XINPUT type device (as opposed to DirectInput) then you need to download and install a conversion utility called XInput Plus, available from https://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/. With XINPUT devices, FSUIPC will only detect button presses when it has the focus.
  4. You seem to be using the .Net framework. I have no experience with this and cannot help you with .Net. Also, if using .Net, you should use the dll instead of the lib. or Paul Henty;s client dll for .Net which includes a wrapper for the WAPI - see
  5. You just add the header files to your project, and include the WASMIF.h file in the source files where you want to use the WAPI, and specify the WAPI include folder (as well as maybe the SimConnect one, if you are planning to use that) under the C/C++ Additional Incude Directories. Also add the FSUIPC_WAPI.lib to your project. Then you need to set the VC++ Directories -> Library Directories to add locations for both the WAPI and SimConnect libraries, and then add the following libraries to the Linker -> Input -> Additional Dependencies: FSUIPC_WAPI.lib;SimConnect.lib;Ws2_32.lib;Shlwapi.lib (and debug versions for the debug configuration. Take a look how the build for the WASMClient is set-up and try and follow that. I haven't got time to clone/download and look at your project, or to help with building standard apps, but if you can explain what your problem actually is maybe I can point you in the right direction:
  6. As I said, the next available id is just allocated on lvar creation. so an lvar could have a different id in a subsequent run of MSFS, but it will not change in the same session, even if you switch aircraft and back again. This is actually a bit of a pain as it means that lvars are never cleared and so the number of available lvars is always increasing, even though many are of no use as they are for previous aircraft loaded. John
  7. Ok, so the rocker is an actual axis - interesting. Ok, good. For the T-28? Did you try with the Rudder Trim Left and Rudder Trim Right controls? Ok - will take a look at them tomorrow - finishing now...cheers, John
  8. Yes. You can use either, but using the id is better/faster. The methods that accept an lvar name are provided for convenience - they will just get the id for that name and then call the method that uses the id. It is permanent for the duration of the MSFS session, i.e. until it exits. Lvars are never dropped, so every aircraft loaded will create more lvars. Due to this, not all lvars that are available are actually in-use, and there is no way to determine which are in-use. The id is assigned to an lvar when created, so the id order is the creation order of the lvars. The ids should be hidden from users as they are not really relevant. However, I include them in the WASMClient (and in the FSUIPC log) as they were/are useful to me when tracking down issues. Really they should be hidden from end-users. The id is assigned when the lvar is created, so it is a sequence in lvar creation order. If you are interested in specific lvars, you should get the id of those lvars from the names and then use the id. You can also flag those lvars for callback in your registerUpdateCallback using flagLvarForUpdateCallback. Cheers, John
  9. Probably better to ask here... The WAPI should be relatively straightforward to use: 1. First get an instance: WASMIF* WasmPtr = WASMIF::getInstance(); (you can also pass in a pointer to a logging function if you like, otherwise the WAPI will create and use its own log file). 2. Set any config options required, using, for example, to set the log level to DEBUG, use: WasmPtr->setLogLevel(LOG_LEVEL_DEBUG); Other config functions: WasmPtr->setSimConfigConnection(connectionNo); // to set the SimConnect connection number - only needed in certain circumstances, e.g. running on a client PC WasmPtr->setLvarUpdateFrequency(freq); // sets the frequency for the WAPI to request lcar updates/values. Recommended NOT to use this, and configure frequency in the WASM WasmPtr->registerUpdateCallback(availableCallbackFunction); // register a function to be called when lvars are loaded/reloaded and available for use. Recommended to USE this function WasmPtr->registerLvarUpdateCallback(lvarCallbackFunction); // register a function to be called when lvar values change. You also ned to flag lvars for this callback 3. Start the WAPI: WasmPtr->start(); Once started, you can use the other functions to get/set/list lvars and hvars once they are available, which is indicated by the ca;;back to the function registered with the registerUpdateCallback method. If you have registered an lvarUpdateCallback, you should also flag the lvars for callback with the registerLvarUpdateCallback method in the registerUpdateCallback method. 4. Close/terminate the session: WasmPtr->end(); // Terminate the WASM connection Thats it really... Note that you shouldn't need to use the reload method any more as this is now done automatically (by the WASM), but can still be used.
  10. It isn't a valid Win32 application. Its an API, and builds the FSUIPC_WAPI.lib. You cannot run it - has no main. If you want an application that uses it, that is what the WASMClient is, also available on github. Btw, I will move your post to the FSUIPC7 support forum, as the FSUIPC WAPI is only valid for MSFS / FSUIPC7. x86 is 32-bit, x64 64-bit. You should build it as x64. You should be able to just built it (not run it!) with the VS solution file provided. John
  11. You currently have to re-run the installer to register. It will uninstall first but you won't lose any settings - just click through to the registration page and enter your details there. You should check for updates and should be re-installing every 4-6 weeks or so, if you want to keep up-to-date. You can just edit the FSUIPC7.key file with the new details, but the registration won't be validated, so if you make a mistake then FSUIPC7 will run as an unregistered version, and you will have to try again. Note also that re-installing will install the current released version again (7.3.19), and you will have to replace the FSUIPC7.exe with the 7.3.20a (or 7.3.20b) version. John
  12. Note you can also use FSUIPC7 on a client PC instead of WideClient, with no need for an additional license. This does not duplicate WideFS/WideClient functionality, but provides most functionality available in FSUIPC7. See the appendix in the Advanced User guide on how to set this up. John
  13. You can, or you can use your own FSUIPC7 key with the details of the trial WideFS key (name, address, WideFS key) - just check the box for different WideFS registration details and copy the trial license details into the relevant fields. Cheers, John
  14. First check you are using the latest beta of FSUIPC7, 7.3.20a, posted above - this won't work in the current released version (7.3.19). You need to register the hot-keys being used - I'm not sure how this is done with PF3 - whether this is done automatically by PF3 or via a lua script or something else. Check the PF3 documentation or maybe @bobsk8could advise. John
  15. I can see the rudder trim working in the Trojan T28D: But when the offset is changed with the MilViz DHC2 Beaver loaded there was no monitoring of the offset, and only the offset control is logged: It would be useful to see the offset monitoring with the MilViz DHC2 loaded, but I suspect that the simvar RUDDER TRIM PCT is not being used by that aircraft. You could try the axis control Rudder Trim Set, or the standard controls (i,.e, not axis controls) Rudder Trim Left and Rudder Trim Right in a specific profile for that aircraft. Still not sure how the rocker is controlling an axis, but you could just change the offset control you are sending in the ranges to use those left/right trim controls instead. Otherwise, remove the axis range controls completely and try assigning the rocker directly to the Rudder Trim Set axis control. John
  16. Do you have a reference? Noy sure how you can get an axis value from a rocker switch,,, Both are needed, and you shouldn't add them manually - if you remove them, FSUIPC will automatically add the joystick id lines back. It cannot work without them. It is difficult to tell what is happening from such a large log file...its far easier for you to see what is logged in real-time (with the logging console window open) when you perform the action. When you adjust the ridder trim in the VC, what do you see logged? Any controls? Does offset 0C04 change value, and if so through what range? When you move the rocker switch, do you also see offset 0C04 changing value?
  17. As you are using the C152, if you look at the presets to control the ADF mode (C152 ADF Mode Selector BFO/ADGH/TEST/REC) (see https://hubhop.mobiflight.com/presets/), these use the lvar L:XMLVAR_ADF_Mode but the description on these presets says: Knob in sim is controlled by O: var so it won't move. So the lvar controls the ADF selection but won't move the log in the sim. For the cabin lights in the C152, you can use the standard controls Toggle Cabin Lights, Cabin Lights On, Cabin Lights Off, or Cabin Lights Set. You should always try standard/default controls before resorting to lvars. Note all lvars are writable, and many do not work on their iwn and may require the use of a hvar or kvar (event). Please also note the following: - the WASMClient is not supported. This is only provided as a test client sample for developers who want to use the WAPI. You shouldn't need to use this - all the WASM functionality you need is available from the Add-ons->WASM menu in FSUIPC7. - please attach log files rather than pasting their contents. And please only enable relevant logging - or no logging if you are not sure. I will ask for a log file with specific logging activated, if needed. - I only provide access to lvars (and hvars and presets) - I do not control what they do, and do not know what most of them do. Some are not even writeable/updateable. Its better to check for a MF preset before using an lvar directly (or if it doesn't work as expected) , and check the code and description - it may be fine to just use the lvar, or sometimes something more complicated is needed, and better to use the preset. You should also check for standard controls before looking for presets or lvars. John
  18. Is the rocker switch an axis then? I am not sure how that works - I would expect a rocker to trigger buttons... Your ini file is quite strange as you only have the letter assignments under [JoyNames] and no lines with the joystick ids - did you remove those? For the MilViz DHC-2, as you are using inc/dec controls on offset 0C04 for the rudder trim, create a specific profile for this aircraft and switch around the controls, so perform the decrements in the range you are currently performing the increments and vice versa. For Ant's T-28's, check what the rudder trim in the aircraft is using by logging events and also set logging for offset 0C04 as S16. Then load the aircraft and adjust the rudder trim in the virtual cockpit and see what event (if any) is logged, and if the offset value changes (which I expect not). If the rudder controls Rudder Trim Left/Right are logged, you could try using those. Otherwise, if the Axis control Rudder Trim Set is logged, you could try assigning to that as an axis. You can also attach your FSUIPC6.log and latest FSUIPC6.ini files here and I can take a look. John
  19. We always recommend not using/installing the Saitek drivers (or any additional software) if using FSUIPC, as these invariable cause issues. Just let windows install the default drivers. I have the X55 (not the X52, but should be similar), and the mode switch on the throttle is recognised by FSUIPC as buttons 31, 132 and 133. John
  20. This depends on what models they are... You should just try it. A trial license for FSUIPC7 is available from here: For the GoFlight mofules, you can check what is supported and download the 64-bit driver from http://fsuipc.com/. You can also download the PFC driver from the same location - use either the PFChid64.dll or the PFCcom64.dll, depending on whether it is one of the more modern USB HID devises or an older COM-port connected devices respectively. User manuals are provided with the PFC drivers, and both the GF and PFC driver dlls should be copied to your FSUIPC7 installation folder. John
  21. Thanks @fabio777 for the detailed investigation and explanation for this issue - hope that helps others. Regards, John
  22. Flight simulation is a pretty small market compared to xbox gaming.... A couple of other interesting posts on MSFS weather access: https://forums.flightsimulator.com/t/what-weather-data-exactly-does-the-api-provide-precip-wind-turbulence/533447 https://forums.flightsimulator.com/t/how-to-query-the-metar-information-for-dest-origin-airport-throught-wasm-or-simconnect/562648 John
  23. This is very strange! I've checked here and have no issues with the rudder in any of the PMDG 737 variants. FSUIPC makes no distinction between the variants as your PMDG 737 profile will be used for all of them. I can only presume that your PMDG 737 installation has been corrupted somehow. Try uninstalling and re-installing the aircraft to see if that helps. John
  24. Note that Ambient Visibility has also been reported as not working - see https://devsupport.flightsimulator.com/questions/16304/bug-aambient-visibility.html John
×
×
  • 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.