Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,463
  • Joined

  • Last visited

  • Days Won

    279

Everything posted by John Dowson

  1. As I said, it has always been this way - nothing has changed. Please re-read my previous response...I said I would look into changing this the next time I update the WAPI. Or is this something that you cannot live without? Later: I seem to get them listed in id order anyway:
  2. You can check the pause state in offset 0x0264: Note that MSFS can be in multiple pause states. Also, Offset 0x062B can be used to determine if MSFS in the main menu or not. John
  3. That must have always been the case...although I thought they were sorted alphabetically in the main window, but checking the code, that is just for lvars. The WAPI getHvarList function returns an unordered map, which is why there is no order. I can change this the next time I update the WAPI if you like, but not for the next release. You can check the FSUIPC7.log file if you want them sorted by id, as they should also be logged there but in id order. John
  4. Btw, this will only work if the folder names for the various liveries share a common base (which hopefully should be the case...) that you can use for the hvar file name. So, for example, for the FBW A320 I have the following folders: _FlyByWire_A320_NEO-LIVERY-XMAS FlyByWire_A320_NEO FlyByWire_A320_NEO-LIVERY A hvar file named FlyByWire_A320_NEO.hvar would match all 3. John
  5. Please try the attached. To use the air file folder for hvar matching, you need to set the following ini parameter in your FSUIPC_WASM.ini (better to set this in the ini file in the WASM local storage area, not in the one under your Community\fsuipc-lvar-module folder): UseAirLocForHvars=Yes John FSUIPC7.exe FSUIPC7_WASM.wasm layout.json
  6. This depends on what aircraft/auto-pilot system you are using. You can try the standard controls: Flight Level Change AP Airspeed Hold Ap Airspeed On Ap Airspeed Off Ap Airspeed Set For some aircraft, you would need to use lvars.hvars or calculator code. For example: Working Title CJ4: use hvar H:WT_CJ4_AP_FLC_PRESSED Asobo Cesna 172: use calculator code (>K:FLIGHT_LEVEL_CHANGE) (A:AIRSPEED INDICATED, knots) (>K:AP_SPD_VAR_SET) etc A good resource to determine what to use, if the standard controls/events don't do what you want, is the MobiFlight preset list: https://hubhop.mobiflight.com/#/list If you are not familiar with lvars/hvars/calculator code, it may be easier to install the MobiFlight WASM module and use the provided MobiFlight event files, which are located under the EventFiles folder of your FSUIPC7 installation. There is an event file there to use with the G1000 (called G1000.rvt), which has the event: MobiFlight.AS1000_MFD_FLC_Push which may be appropriate. This MobiFlight preset is mapped to the calculator code shown above for the C172. Also, a hvar file for the G1000 is also provided in the HvarFiles folder of your FSUIPC7 installation, although I cannot see anything specific in that file for the FLC button. To use hvar files, please see the provided documentation (Advanced User Guide). John
  7. You will have to purchase FSUIPC6 as it is a different product. If you have already purchased FSUIPC4, you should automatically get a discount of 5euros on checkout. If you have already purchased FSUIPC5, you should get a discount of 20euros. If you already have WideFS6, you can continue using that as it is compatible with FSUIPC4, FSUIPC5, FSUIPC6 & FSUIPC7. John P.S. I have only just added the 5euro discount so you may need to wait a while before it is approved by SimMarket and available. This wasn't added before as this product was still with Pete until very recently.
  8. I think I'll look into updating the WASM to allow hvar files to be loaded in the same way (and via an ini parameter). May as well get this out of the way before I look into other things... I'll post the updated WASM here when done.
  9. There was one change in that version that I'm not sure of, although it seemed ok in my tests. However, I've decided to revert that in the attached version, v7.2.15d. In this version I have also added code to stop the WAPI when going back into the MSFS menu system. Not sure why that wasn't done before.... FSUIPC7.exe
  10. Do you mean 7.2.15b? Don't think I have got as far as d yet... Anyway, that will be in the next release, hopefully in the next few days. Just looking at using the air folder name for profiles (not for hvar access!) as I thought this should be relatively straightforward... but there are some complications due to the different timings when receiving the aircraft name and the air file location and the various different actions that are done on each (e.g. starting lua autos). Hopefully I have fixed this now, so could you try the attached version, v7.2.15c. To use this new feature, you need to add the following to the [General] section of your FSUIPC7.ini file: UseAirLocForProfiles=Yes I suggest that once you have done this, keep your existing profiles and load each aircraft (for which you have a profile), then go into one of the assignments panels and check for profiles and select your existing profile for that a/c, then click 'Ok'. This should add the air file folder to your profile section. Once you have done this, you can then remove the other aircraft names from the profile if you so wish. John FSUIPC7.exe
  11. I am not considering an option for improving the hvar assignment (at the moment), just the profile assignment. I thought that this was the main update that you are requesting. An update for hvars is possible, but this is more work as the WASM has no access to FSUIPC offsets, and so no knowledge of the air file location. I can, of course, request this, but there are also other issues related to the timing of when various events are received which complicates things somewhat. But this does not restrict you from using hvar files with the other liveries. You just need to copy the hvar file and give it a substring match (or just the complete aircraft name) for the aircraft with the livery loaded. For the example you gave: You would need one hvar file for the FBW A320: A320neo.hvar And 2 for the Asobo A320: A320 Neo Asobo.hvar, OperatorLand468.hvar I would think it is also possible to just use one hvar file, and use appropriately named links/shortcuts for the other names that point to the original file, although i haven't tried this. I can look into using the air folder name to also match on hvar file names, but not sure when I can do this at the moment. I will add it to my feature request list to be looked into. John
  12. If you look in the axis assignment dialog you will see a Raw checkbox - just tick that. Please see the description if this option on P36 of the User Guide. However, before doing that, please check the calibration of that axis both in windows (game controllers) and in FSUIPC. Also, check your throttle documentation (which throttle are you using?) - some throttles have specific calibration or software set-up that needs to be done before it can be used correctly. You can also post your FSUIPC log file and I can take a look to see if anything looks amiss. Would also be useful if you would let me know which FS and FSUIPC version you are using. John
  13. Could you add the following to the [General] section of your FSUIPC7.INI file, generate another log and post that: Debug=Please LogExtras=x200000 We will try removing all device registry entries + drivers, then adding them back one by one, checking the files each time. Btw, did you try checking the ports/hubs used and switching your G13/rudder to a different port/hub?
  14. As I have said, the reg file only removed entries for specific devices and can no way affect MSFS installation. Did you take a registry backup of your registry before you started to make any changes, as advised? You should ALWAYS back-up your registry before making any changes. If you have this back-up, try reverting back to that. But something very strange is going on in your system. The last registry change should just have removed the entries for your G13 joystick, but now your rudder and stick have also disappeared. I will look into providing you with additional logging flags to log the registry matching. Can you also please check (again) that you are not using any logitech or saitek drivers for any of your devices, and if so remove them. Also, please do not run/install any software for these devices - unless absolutely needed. Always best to try without any additional software running.
  15. It will be in your purchase email and also show in your SimMarket account. If its not there, you need to ask SimMarket. I can see your order - I will PM you your registration details. John
  16. Yes of course - you can also use the Axis Throttle Set control on a button press, with an appropriate parameter. Custom controls need something to understand them at the other end (i.e. in the FS) - you cannot just create your own custom control in FSUIPC. Also, you could try calibrating some "sync" points - see the section CALIBRATING MULTIPLE THROTTLE, PROP & MIXTURE AXES TO "LINE UP" on P45 of the User guide. John
  17. Just use the latest lua, or create a lua file with the contents in my last post. This is basically what that script does, although the value is not written but 'spoofed', so any external program that reads the offset will read the spoofed value. Is the lua actually running? i.e. have you added it to the [Auto] (or profile [Auto.xxx]) section of your FSUIPC7.ini file? Have you installed the FSUIPC WASM module and enabled it? Otherwise, try enabling lua debug logging and generate a log file where you load the aircraft, apply and release the parking brake, and then exit. Do not start a new log - I need to see the full log file. Note also that lua is only available to registered/licensed copies of FSUIPC.
  18. Where have you installed FSUIPC6? If you have installed in the add-ons folder (under Documents), or in any other windows protected folder (such as Program Files), then please try installing in a different location. Otherwise, please show me your Installation log (InstallFSUIPC6.log).
  19. Still an issue with your G13 joystick. Can you disconnect, and run the following as a .reg file, then reboot and reconnect. Before starting FSUIPC, delete the contents of your [JoyNames] section in your FSUIPC7.ini file and let that get rebuilt. The log also reports an error reading the details of your joystick: Not sure if this is an issue, but try connecting it to a different USB port/hub - if its in a USB2 port try moving it to a 3.1 port (if you have any), and if its in a 3.0 or 3.1, try moving it to a USB 2.0 port. Once thats done, start FSUIPC7, exit and then show me the files again. If there are still registry issues after this, I will give you instructions for logging the registry matching FSUIPC performs - there may be some other registry entries that need removing. Hows it going with the MSFS re-install?
  20. I did say I would look into this. I just have other things that are of higher priority at the moment. I have a backlog of requests pending, as well as planned improvements on how to access lvars, hvars and calculator code. The current profile mechanism has been around for 10+ years and so I'm sure it can wait another few months before I get around to looking into this. John
  21. You are reading the values as a signed double, which us 4 bytes, but your offsets are only spaced by 1 byte, so they are overwriting each other. How are you writing them? If writing them as Dwords (32-bit, 4 bytes) then if the first is at offset 0x66C0, the next should go at 0x66C4 and not 0x66C1. John
  22. Ok, but still very strange... Thanks for reporting back. John
  23. You can try that, using offset 0x31F0. Try logging that offset first to check its holding the correct state for the aircraft you are using. You can start a timer to call a function to play the wav when the offset value changes from 0,1 or 2 to 3 (pushback off). Regards, John
  24. It will be in the FSUIPC6 installation folder, where you selected to install FSUIPC6. The Documents\Prepar3D v5 Add-ons\FSUIPC6 folder is where the add-on.xml file resides. If you do not know where you installed FSUIPC6, use the Open Folder button in the FSUIPC6 Logging tab. John
  25. By the way, does the Aerosoft A320 have a flypad/efb? If so, you may need to configure there before you assign in FSUIPC. But, as I said, the aerosoft forums may be your best resource for this issue.
×
×
  • 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.