Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    12,277
  • Joined

  • Last visited

  • Days Won

    250

Everything posted by John Dowson

  1. There have been a few other questions on Elite hardware, but from what I understand they will only work work with their own drivers. I do not supply any additional drivers for Elite devices. I will send you a trial key, but I do not know if FSYUPC will be able to see your buttons/axis. You will still need your Elite driver though, and I don't know how that works with MSFS (or any other FS!). John
  2. To assign an axis to an lvar, you need to create a preset. First, you need to determine what the maximum and minimum values that the lvar takes, and you must also know the maximum and minimum values the axis sends. The preset, which you need to add to your myevents.txt file (create this if not present) will then take the form DA62 Aileron#@ <conversion> (>L:lvarname) where <conversion> - is the RPM code to convert the axis input value range to that expected by the lvar lvarname - is the name of the lvar that controls the aileron position You can then check the Select for Preset in the top-right of the axis assignment panel and assign your axis to the preset DA62 Aileron. To see how this works, take a look at this comment where I show how to assign an axis to an lvar for the ATR to control the condition lever: If you have difficulties with this, if you let me know your axis range and the range of values expected by the lvar as well as the lvar name, I can help you define the preset. John
  3. All your settings are stored in the FSUIPC7.ini file located in your FSUIPC7 installation folder, and if using profiles-in-separate-files, then the individual profile files will be stored under a Profiles folder, also with extension .ini. Note that they may need adjusting due to a change in your devices GUIDs and/or IDs if transferred to a different PC. Files also worth backing up, if you use them, are: *.lua - lua script files *.mcro - macro files *.evt - custom event files myevents.txt - your user-defined/private presets myoffsets.txt - your user-defined/private populated offsets *.dll - drivers for certain devices loaded by FSUIPC FSUIPC7.key - your license/key file (although not needed as you can always recreate this if you know your license details)
  4. License sent via PM. John
  5. ok - let me know how it goes... John
  6. If calibrating a throttle axis without reverses, you would normally do this by checking the No Reverse Zone checkbox in the top-left of the throttle calibration tab (page 3)...see the following post on setting up the throttle and reversers (in a button) for the PMDG 737: John
  7. Can you please change the logging in your WideClient.ini under [User] to Log=KeySend and show me your files again please. Also make sure that the files are all from the same session - the last ones toy posted seem to be from different dates: WideClient.log: WideServer.log: Also, please make sure that WideClient is being ran with the same permissions as your WideClient clients - if any require being ran with admin privileges, then all must be ran with admin privileges. Better to run everything with standard privileges if possible.
  8. First, you are trying to install version 7.2.16 which is quite old now. The latest (and only supported) version is 7.3.21. Please download the latest version and install that. Please uninstall your current version first by running this file: C:\FSUIPC7\uninstallFSUIPC7.exe This one: C:\Users\maros\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt That is the UserCfg.opt file for a steam install. Not sure why you have that in this location if you have not installed MSFS via steam... If you remove/rename that, the installer should detect your MS store version and install for that.
  9. Licenses sent via PM. John
  10. You are not running FSUIPC... The MSFS desktop icon is used to start MSFS, not FSUIPC. It looks like that when you installed FSUIPC7 the installer didn't detect your MS store version and so defaulted to a steam install. Could you please show me/attach your InstallFSUIPC7.log file (located in your FSUIPC7 installation folder), and let me know where your MSFS UserCfg.opt file is located. If one exists under <your user account>\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt then the installer will think you have an MSFS steam installation. If this is the case, remove or rename that file, manually run the FSUIPC7 uninstaller uninstallFSUIPC7.exe (in your FSUIPC7 installation folder) to remove FSUIPC7 from your system and then try to install again. After installation, check your installation log file to check that the MS store version of MSFS was detected. You can also try manually starting FSUIPC7, either before or after starting MSFS, by double-clicking the FSUIPC7.exe in windows explorer.
  11. I don't have the 738/739, bur check the SDK for custom controls to control the fuel cut-off levers. For the 737, you would use the following: See the following FAQ entry on how to use custom controls with PMDG aircraft: Alternatively, you could try the following PMDG presets - these are for the 737 but may also work with the 738/9: PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP PMDG_B737-7_FUEL_CUT_OFF_LEVER2_DN Not sure why you would want to bind these controls to axes as they are standard events fir buttons/switches, not axes controls. However, you can assign them to an axis if you wish. You would normally do this using the right-hand side of the axis assignment panel, to send the desired control when entering or leaving an axis range. Yes. You need to create an FSUIPC profile for the v738/739 and make the assignment profile-specific. Please see the provided documentation on using profiles. John
  12. From the websocket server online help (http://fsuipcwebsockets.paulhenty.com/😞 So it can be used, it is just not included or integrated into FSUIPC6 as it is with FSUIPC7. Those are questions for @Paul Henty... John
  13. The standard controls do not work for the G1000 - you need to use Presets. The presets for the G1000 start with AS1000, so for the MFD zoom try AS1000 MFD Range Inc/Dec and the softkeys are AS1000 MFD SoftKeys x (where x is the number)
  14. What aircraft are you using? So your encoders are button-based? This shouldn't be a problem, but the assignments can depends on the aircraft that you are using - please specify.
  15. License sent via PM. John
  16. Have you installed FSUIPC7? You don't say what program is giving that message, but it is (obviously) telling you that FSUIPC7 (on a client) or WideClient (on a server) is not running. This will be available from your SimMarket account. John
  17. What do you mean by 'but it does not communicate with the PMDG and does nothing'? GSUIPC communicates to the simulator. Are you aware that many standard FS controls do not work with the PMDG 737, and you need to use the PMDG custom controls. See the following FAQ entry: What does this mean? Please read the User guide, and familiarise yourself with the Advanced User guide, especially the WASM section in how to use lvars/hvars and presets. There are also many presets available for the PMDG aircraft which you can use instead of the custom controls (which are used by the presets). See https://hubhop.mobiflight.com/presets/ So, for example, the image shows you have assigned the PgDn key to the FS control Taxi Lights On. This will not work in the PMDG 737, You should check the Select for Preset checkbox and assign to the preset PMDG_B737-7_LIGHTS_TAXI_ON - or use the custom control number directly.
  18. Sorry, but what do you mean by this? Can you press the Set button and get the key press registered ready for assignment?
  19. Possibly - you should always extract the installer from the zip file before running it. I have seen strange issues when running the installer from within the zip file itself. You can just install again - this will uninstall the current installation before proceeding,
  20. If you see FSUIPC7 in the task bar after pressing Alt+F then the window must have been opened, and if you cannot see it then it is either positioned off-screen or is being hidden by another window. If you mean the Window entry from the FSUIPC7.ini file, then this is what you need to do, but make sure you do this when FSUIPC7 isn't running. John
  21. Ok. Unfortunately I don't have the PMDG 737 for P3D, so cannot check the offsets here. I can see if Pete has a copy and he can maybe check, but that won't be until later next week now as he is on holiday. Let me know how you get on. Regards, John
  22. Your version of FSUIPC7 is very old - 7.2.0 from June 2021. The latest and only supported version is 7.3.21 - please update before anything else. Your WideClient also needs updating - you are using version 6.999 and the latest version is 7.160. Please always make sure that FSUIPC7 is no longer running before you attach;log files. Can you also please activate logging in FSUIPC7 for Buttons & Keys. Also, in your WideClient.ini this line: Log=Errors+ should be in your [User] section but is currently under your [Sounds] section - please correct this as well. Note also that you are using UseSendInput=Yes which is documented as: So you must make sure that P2A has the focus when using this method. You can try this, but it would be better to direct the key stokes to P2A instead - see the section Directing Key Strokes more precisely in the WideFS Technical manual on how to do this. Note you also have an error in the first line of one of your lua scripts: 155937 *** LUA Error: C:\FSUIPC7\ProSim-doors.lua:1: unexpected symbol Please correct all of the above and try again, and any issues please re-send thise files, with the additional logging enabled, and also please attach your WideServer.log file (from the server). John
  23. Why did you post this question in a completely unrelated topic, and also in the wrong forum? You have already requested an FSUIPC7 trial license, so you must know there is a specific forum for FSUIPC7. Sorry, the lua is for the FBWA320, not the PMDG 737. My mistake. For the PMDG 737 parking brake, you need to use the PMDG custom controls - please see this FAQ entry: However, it may be easier to use the available presets. To use these, check the Select for Preset checkbox (in the assignment panels) and you can assign your buttons/switch/keys to the following presets: PMDG B737-7 PARKING BRAKE ON PMDG_B737-7 PARKING BRAKE OFF See the MF HubHop site for a complete (and searchable) list of available presets: https://hubhop.mobiflight.com/presets/ You generally activate reversers by sending a Throttle Decr control (on repeat) on a button press (once throttle is in idle position) and also send a Throttle Cut (or Throttle Set with parameter -1) on release. See this thread for further info: 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.