Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    12,251
  • Joined

  • Last visited

  • Days Won

    249

Everything posted by John Dowson

  1. Yes, that will be your problem! If you left-click the filename and hold for a second or so before releasing, you can change the filename and extension (or right-click and 'Rename'). You will have to confirm the change. Notepad++ is a good free source editor that a lot of people, including myself, use for this type of thing. Btw, your FSUIPC version is quite old now - the latest (and only supported) version is 5.152. please update at some point. Cheers, John P.S. Its a good idea to set the AutoAssignLetters ini parameter to Yes (or manually assign them - see the "Joy Letters" section of the User Guide, p24 in latest version). This will prevent possible problems if your USB device numbers change for some reason.
  2. Hi Scott, to have different functions on your joystick buttons depending upon whether a key is pressed or not, you can try the following: 1. First select the key to use. Unfortunately this cannot be just a modifier key (shift, ctrl, alt, etc). For this example, I will use the '|\ key (which is the key next to the leftmost shift key on my keyboard). 2. Program this key to send a 'BUTTON FLAG Toggle' event, using the FSUIPC 'Key Presses' tab. For the parameter, choose a joystick (and button) number that you do not use (<16) and multiply this by 256. I only have 2 joystick devices, so I choose joystick 10 (button 0), so my parameter will be 2560. Set to send the same control/parameter on both key press and release, and check for 'No repeats!'. This will set a button flag (joystick 10, button 0) on keypress, and clear the flag on key release. The entry in your ini will look something like: [Keys] ... 6=N220,8,1005,2560,1005,2560 -{\|key: Press=BUTTON FLAG Toggle: Joy 10 Button 0, Release=BUTTON FLAG Toggle: Joy 10 Button 0 }- 3. Modify your ini file to add the conditional on any buttons for which you wish to use this feature. For example, I have the following button entry in my ini file: [Buttons] ... 9=PS,0,C65752,0 -{PARKING_BRAKES}- ... To make this conditional on holding the key I defined ('\'), I would modify this to the following: 9=CP(F+10,0)S,0,C65752,0 -{PARKING_BRAKES}- and now I can add a new entry for using this button without the key modifier, e.g. [Buttons] ... 9=CP(F+10,0)S,0,C65752,0 -{PARKING_BRAKES}- ... 19=CP(F-10,0)S,0,C66079,0 -{GEAR_UP}- Hope that makes sense! Full details on button flags and compound button conditions are in the Advanced User Guide. Cheers, John
  3. Its normal for prop aircraft to pull to the left during take-off - see this post an explanation: https://www.boldmethod.com/learn-to-fly/aerodynamics/why-you-need-right-rudder-on-takeoff-to-stay-on-the-centerline/ You need to compensate with a bit of right rudder. John
  4. Roman already corrected this for you in the above post - it was this line: ipc.readLvar("L:QW_AFT_Transponder_Knob"} and the log gives the line number where the error occurs, as Roman said: John
  5. Hi Art6, 4.5.12.30293 is the P3D version number. The latest version of FSUIPC5 is 5.152. Your log indicated that you are using version 5.112 - this is quite old and no longer supported, please update to the latest version. This is not related to FSUIPC5. Do you not have the P3D option 'Show Scenario Startup Screen' selected? John P.S. You posted in the FAQ section. I have moved this post to the Support section - please post all support requests here.
  6. Hi Lars, the file should be called <something>.MCRO, e.g. A320.MCRO. Any macro files find should also be listed in your .ini file - could you post/attach this please? John P.S. I moved your post from the FAQ section - please post all support requests here, in the support section. Thanks.
  7. Hi Sunny, your GUIDs may change again with an OS re-install. After you re-install, use your original ini and start P3D, load an aircraft on a runway (to initialise FSUIPC), then exit. Then check your log an ini files - if your device GUIDs have changed, simply replace the new GUIDs for each device in your original ini. If you have any difficulties/issues, attach your log & ini files here and I'll take a look. Cheers, John
  8. Hi Scott, Pete has retired from FSUIPC development, although he is still active on the support forum. I've taken over development of FSUIPC5 since the beginning of the year (I'm Pete's son). I'll discuss this with Pete and have a think about it, but as Pete mentioned it looks like it could be quite a complicated/involved update. For your example though, a standard way of handling this using one rotary is with a lua script, which would time the requests and send different controls depending upon the delta between them, allowing you to rotate slowly for fine control and faster for course control. Cheers, John
  9. Did you manage to get any values for "L:Eng1_ThrottleLever,number"? Check out this post for monitoring specific lvars: John
  10. Hi Urs, is there a way to launch WideFS, which resides on a client PC, via FSUIPC on the main PC? No, this is not possible. Unfortunately, when WideFS starts at Windows startup, the program does not start what I want when launching WideFS. Do you mean that WideFS is not starting external programs correctly when it is automatically started at Windows startup? Does it work ok when you start WideFS manually? You could try adding Log=Debugallto the [user] section of your WideClient.ini (or add the [user] section if not already there), then let WideFS autostart (and exhibit your problem), and then post your log file. Cheers, John
  11. Sorry, FSUIPC4 is now closed for future development. Cheers, John
  12. Hi Alhard, here's a minor update to remove that 'quirk' mentioned above - now the permanent ignores (from the IgnoreThese ini parameter) are maintained in a separate list from the temporary ones from the 'Ignore' button. Cheers, John P.S. Its 'Dowson' not 'Dawson'! FSUIPC5.dll
  13. FSUIPC5 works with P3Dv4, you don't need anything else if you have one PC. WideFS works with all versions of FSUIPC, and allows connection to FSUIPC from slave/secondary PCs. What you need to buy depends on your set-up and what you want to achieve really... Cheers, John
  14. Hi Alhard, please try the attached version (5.152a). It will accept the IgnoreThese ini parameter in the [Axes] section using he same format as the one in the buttons section, except that you specify the axis letter after the '.'. Note that there is one 'quirk' in the way I have implemented, in that if you clear or change this parameter when FSUIPC/P3D is running, and you reload the assignments, the initial axes you ignored will still be present and so still ignored. To clear this completely, you need push 'Clr Ignores' button. Please try this and let me know how it goes. Regards, John FSUIPC5.dll
  15. *** Moved from Download Links - please post support requests in the Support forum *** All sales are handled by SimMarket - please contact them directly. If you have a WideFS license, that will work with FSUIPC4 and FSUIPC5.
  16. Please see section 'Changing or removing Profile assignments' in the User Guide (page 22). John
  17. No problem - I'm glad that its now working for you.
  18. 0x654c is a 4-byte float32, so you need to use ipc.readFLT and not ipc.readSD. Presumably you have enabled these offsets as described in the offset mapping document for the PMDG 777X? That document also contains the size and type of each offset, which will help you to determine which ipc.read function to use. John
  19. Hi, you can log the COM data by adding these lines to the [General] section of your FSUIPC5.ini file: Debug=Please LogExtras=x40 The data will be in hexadecimal of the ASCII byte values. John
  20. Then thats an lvar! You will need to log that with a lua script. There is one provided (called 'log lvars.lua') that will log ALL lvars for you. You can try that, or as you know the lvar name, should be pretty straightforward to write a short script to read the value (using 'ipc.readLvar') and then logging the value returned. John
  21. Please try the following: FSUIPC5.ini
  22. As Pete says, I'll take a look at this later this week, and I'll post an updated version here for you to test. John
  23. Could you attach your original/backup ini file please. If its too big, you can try zipping/compressing.
  24. Hi Sunny, please post/attach your latest FSUIPC log and ini files, and also your joyscan.csv files (all in your Modules folder), and I'll let you know how to update... 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.