John Dowson

As I indicated, your [Auto.Lear35] section in your FSUIPC5.ini file, should be in your Lears5.ini file but as an [Auto] section. John

There is also a separate document you should read if you are using profiles in separate files, called (unsurprisingly) Profiles in Separate Files.pdf. I suspect that your problem is that the [Auto] section in your Lear35.ini should just be called [Auto] and not [Auto.Lear35] - the latter is used in your FSUIPC5.ini file when you are using profiles but NOT in separate files. John

Hi Renato, no need to re-purchase - you should be able to retrieve your existing registration from SimMarket. If you are having problems with your SimMarket account, you need to contact them - we have no control over SimMarket accounts. Regards, John P.S. Did you try the 'Forgot Your Password?' link in the login box? This should allow you to rest your password using your email address.

Hi Ramon, Yep, looks useful and pretty simple to add so I'll schedule for the next release. I'll post you a dll to test when done. Cheers, John

I'll take a look when I get a chance - I'm a bit busy for the next few weeks so it won't be until December sometime. John

I'll be looking at providing a version of FSUIPC for the new MS FS, once the SDK is published (with help from Pete!). A bit too early to provide any details on a beta test release though! John

Are you sure this is FSUIPC, and not the FS? FSUIPC will not automatically assign an axis (or 'recognise as a throttle') on a new device. Maybe check the assignments in the sim (or disable controllers in the sim, which is recommended if you are assigning axis in FSUIPC). Note you can also delete any assignments directly in your FSUIPC ini file, but best to do this when the sim is not running. John

uncheck your assignment (in the axis assignment tab) and save - this will remove the assignment. John

Hi, first, you posted in the User Contributions forum - please post all support requests in the Support Forum. I have moved your post for you. I see Pete has just replied...as he says, just re-assign from FSUIPC assignments tab.... John

Does it work when you activate the fire warn cut out switch in the UI? You are probably better off contacting the Project Magenta support., but you could try logging non-axis events, to check that the event/control sent when activating your switch is the same as the one sent when you activate in the UI (if that one works!). John

How are you trying to do this? Are you using the macro file (provided in the first post in this topic) to access the A320 lvars? What is your actual problem - is the macro file loaded? Can you see the lvars in the FSUIPC assignment dropdown? Check the Advanced User guide, starting from section Gauge local variable access (L:vars), by macro. John

Hi Booley, If you still have problems, forward or pm me your registration details (please don't post them publicly!) and I'll check them for you. John

No problem. Its worth taking a look at both the User Guide and the Advanced User Guide, both should be available in the FSUIPC Documents folder, located under the Modules folder, where FSUIPC is installed. John

Use the logging features (in FSUIPC's logging tab) - you can activate non-axis events to see what controls are being sent when you activate your button or switch, and then use that. John

Your rudder axis is assigned to 'Send direct to FSUIPC Calibration', so you need to go to the Joystick Calibration tab and calibrate your rudder. There you can also add a slope to to the rudder calibration - please see the User Guide section starting 'The Easy Step-by-Step way to calibrate your controls'. Note that any axis sent to FSUIPC calibration must be calibrated in FSUIPC!. You can have multiple actions on one button by editing the FSUIPC ini file. You need to first program one of the actions on the button. If you program the second option on a different button (temporarily), you can then edit the ini to change the assignment on the second button to be on the first button number (and make sure the joystick numbers match). Please see the Advanced User guide for the description of the button definitions. I'm not sure how you use custom controls with the Maddog X, maybe someone else can help you there, but for the lvars you can use either lua scripts or macro files. Please see the Advanced User Guide, section starting Gauge local variable access (L:vars), by macro. Cheers, John

Its now available again. John

It looks like its available again. John

Hi Matthias, to start your lua automatically, it must be added to the [Auto] section of your ini file. See Automatic running of Macros and Lua plugins, on p40 of the Advanced Users manual. John

Ah, ok - thanks for the update. John

Ah, ok. That makes sense. But presumably for only the first 32 buttons (0-31). The remaining buttons would only send via the virtual device. I don't think the repeat rate will be a problem using virtual buttons, but, as you say, just try and see. John

You have to program under the device the button press is received. Not sure what you mean by this, but I would expect a small delay if the button press is going via lua + virtual buttons. Probably not! You could look into tuning the ButtonRepeat rate if the delay is an issue, but this would affect all buttons. Best just to try and adjust for your needs if needed. John

Sorry, I've not used this program and can't really help you with this - maybe try posting on the support forum over at http://www.hidmacros.eu/forum/. John

As previously posted, you could try the log lvars.lua plugin (see the FSUIPC Lua Plug-Ins manual) which will list all lvars (and their values) available for any loaded aircraft. John

You posted in the wrong forum - your post was moved here, which is the correct forum for all support requests. In this forum! John

These should be Vender = 0x294B Product = 0x1900