John Dowson

Thomas has indicated a way to check in FSUIPC. We do not support XPUIPC - its from another developer, . You will need to ask on the XPUIPC support forums. Regards, John

The <shift> key is a modifier key and needs to be held down when you press the other key (i.e. together, not before), so maybe you got it the wrong way around? Log files looks ok, as does your ini, but you don't have any assignments - or much of anything! Probably a good idea to change the AutoAssignLetters parameter to Yes, to enable the JoyLetters facility, which would preserve any assignments to your joystick devices if the ids change (please see the User Guide for details). Anyway, glad its now working for you. Regards, John

Hi Hans, could you try activating FSUIPC logging for Buttons and key operations and Events (non-axis controls). Try each of the key combinations and post your resulting FSUIPC log file, together with your ini file. Thanks, John

No problem - glad its now working for you. Note that if you want to use the new beta version, you need to download and install a special version of FSUIPC4 provided here: Cheers, John

P3Dv4 require FSUIPC5, not FSUIPC4. You will need to purchase a new license for FSUIPC5 to work with P3Dv4.1+. John

To add to what Pete has said, your (old) email address is only used to validate the key, doesn't matter if its no longer used - just use that to generate your key file. Once you have that, it doesn't really matter if your actual email has changed - just use the key file generated with the email used to purchase your license. John

Which version of FSX-SE do you have installed - is it the latest beta release?

You posted in the FAQ section - I have moved your post to the correct location. Please post support messages here, in the main support forum. Are you running as admin? Could you please post your install log file FSUIPC4 Install.log - should be located in the folder where you ran the installer and in the Modules folder (under your FSX folder) if that has been created. John

Why write a c# program when you could just use the lua event.timer function to call your lua function every 50ms? John

No problem. The documentation is not too clear on this - I'll update it for the next release. Happy flying! John

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