Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,041
  • Joined

  • Last visited

  • Days Won

    267

Everything posted by John Dowson

  1. Mouse macros do not work well with PMDG aircraft, you are better off using custom controls. Please see this post:
  2. There is no 'best response curve' - it is totally up to personal preference, and may also vary from aircraft to aircraft (via using the 'profiles' mechanism). FSUIPC is hardware independent - there are no recommended settings for particular hardware. Just try different slopes and stick with what feels good for your hardware/aircraft. John
  3. Hi, generally it is not recommended to use the SAITEK drivers when using FSUIPC. Try uninstalling them and see if your device is recognised by FSUIPC without them. John
  4. Hi, usually such issues are caused by the editor adding a .txt extension to the file name - check the file extension is correct, and if not then rename. If thats not the issue, can you attach your FSUIPC4.ini file and your 1F111.mcro file. Any macro files found in your directory should be in your ini in a [MacroFiles] section. John
  5. Hi Ray, looks like it was due to the size allocated to the drop-down entry (composing macro file name + lvar name) being too small. Please try the attached version. Cheers, John FSUIPC5.dll
  6. You are also using an old (unsupported) version of FSUIPC5 - please update to the latest version, 5.152. John
  7. Hi Ray. I just checked this and it worked for me, although I invented an LVAR name that didn't exist. This is what I got in my ini: 11=PT,0,CM1:1,44 -{Macro longMacro: L:MyExtremelyLongLvarNameToCrashP3DWhenUsed set}- The lvar name is truncated in the UI, but can still be selected and used. I'll need to investigate further. John
  8. Hi Ray, Ok, thanks - sorry I didn't have time to check this last night. I'll take a look and get back to you with a new version later today (hopefully!). John
  9. Hi, presumably, from your ini, your taxi lights are assigned to a button that stays in when pressed (i.e. no release), and then releases when pressed again? i.e. 112=P4,9,C69749,1 -{Custom control: <69749>}- 113=U4,9,C69749,0 -{Custom control: <69749>}- You have the same on your 777 but on a different button, which, as you say, works for you, which is strange. Also, if the same happens when you activate in the sim overhead, then it does sound like a PMDG issue. There are no events in your log - did you activate this as advised by Thomas? If not, can you activate logging for 'Button and key operations' and also 'Events (non-axis controls)' (from FSUIPC's Logging tab), and produce another log file that shows the taxi lights being activated. John
  10. Hi Mark, for install error 1332, you can manually edit the Modules folder permissions yourself to allow full access, by right clicking on the folder properties: select Security-->Edit-> Add, enter Everyone as the object name, then 'Check Names' and 'OK'. Then give 'Full Control' to the Everyone group just added. John
  11. Hi Ray, please try the following dll (5.152c) - I've increased the max space for LVAR names from 32 to 64 characters. I haven't tested this yet, so please let me know if there are any issues. Cheers, John FSUIPC5.dll
  12. Hi, sorry for the late reply... What version of MakeRunways are you using? Did you check the MakeRunways documentation? For P3Dv4, MakeRunways uses a special version of the Lorby-Si add-on manager (included with MakeRunways) to generate a scenery.cfg file that it can use that contains the scenery from various add-on xml methods. Therefore, please check that you are using the latest version of MakeRunways and check the documentation. John
  13. Hi Stu, please try the attached version (5.152b). John FSUIPC5.DLL
  14. Hi Stu, Thomas, I'll take a look at the changes and build a new version for you to try. I'm a bit busy at the moment so it may take me a couple of days. John
  15. Hi Daniel, do you have anything in the windows event log for the crash? If so, could you please post it. Thanks, John
  16. Hi Rodger, your FSUIPC license for FSX-SE is for FSUIPC4. This license is also valid for P3D version 2.5, 3-3.4 (all 32-bit). If you are using P3Dv4 (64-bit), you will need to purchase a license for FSUIPC5, available from SimMarket. Regards, John
  17. You could also compile your jar as a 32-bit "one-jar" and provide that. But it does look like your users would need to install a 32-bit JVM as well.
  18. Hi Crazz, According to the documentation, the FSUIPC java interface was provided by Mark Burton (mark.burton@zenobyte.com). All sources are provided, so it should be possible to update this to a 64-bit dll. I can add to the SDK if anyone wants to take this on, otherwise I could take a look at some point but it will be quite a while before I have time to look into this. Cheers, John
  19. Could you try activating axis logging (from the FSUIPC logging tab). Generate a log file that exhibits your problem (i.e. disconnection, reconnecting and going haywire). It will be quite large, so zip it up and attach to a post and I'll take a look to see whats happening.
  20. Hi Steve, sorry for the late reply - I was hoping someone else who has tried this would jump in and advise. I can only tell you that we generally advise against installing the Logitech/Saitek drivers as these can create problems with FSUIPC. I can only suggest that you try to see if it works for you, and if not then uninstall. Maybe be a good idea to take a backup copy of your registry before you install, as their drivers have been known to leave registry entries after uninstallation that may affect behaviour (although I don't know if this is still the case with their latest drivers). Regards, John
  21. I don't think that "input spike suppression" will help. Its not a 'spike', its caused by your wireless joystick device reconnecting and being re-scanned, so the axis values will be reset until it receives a new input value. I'm not sure there is anything you can do - I've asked Pete to see if he has any ideas that may help. Regards, John
  22. FSUIPC can't help you with this. For USB sleep problems, its generally a matter of configuring the power management settings for USB hub. However, it seems to be your wireless device itself that is going to sleep (to save battery), so I don't think there is much you can do, apart from maybe contact Logitech support to see if there is a way to turn off (or extend the time of) this 'feature' of your device. John
  23. No problem - glad its now working. John
  24. Hi Roman, thanks for that - thats very interesting! As Bob is using a rotary switch, and its sending both a release (for previous position) and a press (for the current position), I thought he could add the MAGNETO*_OFF controls to the button release, but it looks like the release/press order is not consistent, i.e. it generates a release then press going clockwise, but a press then release going anticlockwise (for your Magneto1 only?!!). Therefore I think your solution of having multiple controls (i.e. sending an 'OFF'' first) is the thing to try. So Bob, following Roman's advise, can you edit your ini file and try the following [Buttons] section: John
  25. Hi Bruce, I've no idea what 'Sync Pos' is, so can't help you with that. What aircraft are you using? Some add-ons, such as those by PMDG, don't work very well with FSUIPC calibration and you should send as FS command if you are using those. Also check that you have controllers disabled in P3D if you are assigning your axis in FSUIPC. Cheers, 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.