Andydigital

How would you check your flight controls before takeoff if they are disabled? How would you roll into the wind in a cross wind takeoff/taxi?

Any joystick when it is connected to FS for the first time (in any particular USB port) will cause FS to assign a default set of assignments whether you want it to or not. As long as you only ever plug that joystick into that socket your custom assignments will remain in place, if you plug that joystick into a different USB port however the default set of assignments will be assigned again.

Mine doesn't crash on exit and I use FSX and P3DV2. Perhaps your default flight is corrupted, try deleting it and try again. I had a crash at startup the very first time I used 4.924, it was fine at every start and closure from that point onwards though.

Pete cannot support anyone who is not using the current version of FSUIPC. Remaining current does not cost you anything as all updates within major versions are free. Please update from the page below then ask your question again if it is still relevant. The current version for FS9 at the time of writing is 3.999z9. http://forum.simflight.com/topic/66139-updated-modules/

This is normal and to be expected if you are using ASN, from FSUIPC version 4.924 onwards you will no longer see these warnings as they will be suppressed.

Log into your simmarket account and check your purchase history, look for FSUIPC and check that your registration information is entered exactly the same as at the time when you purchased it. All three fields must be identical.

I noticed that until I removed the SimconnectP3D.dll in the modules folder autosave would not work in P3D V2, with it removed it started working. I wasn't aware that FSUIPC didn't support P3D V2, your logs, installer and info on the forum somewhere seemed contradictory on this point, more likely I misinterpreted what I read. But it is not a problem, everyone knew you were on a well deserved holiday and we managed to fumbled a partial fix in the mean time.

It wouldn't work until you removed the P3D Simconnect dll that came with FSUIPC, I noticed the same.

Copy your .key file from either FSX or P3D v1 to the P3D V2 modules folder.

I think something must have changed as it doesn't work in LINDA either, the default keys still work though, SHIFT + M.

Ah so it does, good find.

Dont copy the whole dll.xml, you need a fresh install of it for P3D. Try this version instead. It wont make the GUI appear but it will hopefully stop the crashes and you can copy your FSUIPC4.ini file over from FSX to get some functionality working. Some parts of FSUIPC will still not work though. <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document>

Seems like there is a problem with the latest release of P3D V2, unfortunately we will have to wait until Pete returns from holiday in a couple of days.

Repeat the process but press max first instead of min.

The latest version in the downloads thread should work. http://forum.simflight.com/topic/66139-updated-modules/

Lol, no worries cobber, glad you got it sorted.

Are you sure you really have unassigned them in FSX itself, you have to specifically choose the Saitek Rudder pedals from a drop down menu first before you will see the assignments for that device. I am away from a PC today and replying to you on a tablet so cannot walk you through the steps without actually seeing the same dialogues on my PC, my memory isn't quite good enough to remember all the correct menu terminology without seeing it. One thing is for sure, if the axis is doing more than one thing at once it has to be assigned in two places at once, either in FSX itself and FSUIPC or perhaps both times in FSUIPC, but you should have ruled out the later being the cause after removing the FSUIPC4.ini file from the Modules folder.

In that case you likely have dual assignments within FSUIPC itself. Try removing the FSUIPC4.ini file from the modules folder (fs must not be running) and put it somewhere safe. Then load FS and try making your assignments again in FSUIPC. If that fixes your problem then you know your old file had the same axis assigned to more than one function.

Check for default assignments within FSX's control assignment interface as FS automatically assigns a set of default axis and button assignments to all joystick devices when they are plugged in to a particular USB port for the first time. If you make sure that the pedals are only ever plugged into that one usb port, then you can safely remove the assignments from within FS and expect them not to be reassigned the next time you plug them into that same port. If you were to plug them into another USB port then FS will assign those commands again.

Sorry I'm not sure what you are asking me for, but the manuals for FSUIPC are located inside the folder called "FSUIPC Documents", which is inside the FSX\Modules folder.

Here is an example from my FSUIPC4.ini [Programs] RunIf1=E:\Microsoft Games\Microsoft Flight Simulator X\Modules\linda.exe //RunIf2=Ready,Close,E:\Program Files (x86)\FS Real Time\FSRealTime.exe //RunIf3=C:\Program Files (x86)\HiFi\AS2012\AS2012_Exec.exe //RunIf4=Close,C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe RunIf5=Ready,Kill,C:\Program Files (x86)\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider.exe RunIf6=Ready,Kill,C:\Program Files (x86)\AivlaSoft\EFB\AivlaSoft.Efb.DisplayUnit.exe RunIf7=Ready,Close,C:\Program Files (x86)\FS Flight Keeper\FSFK.exe RunIf8=Close,C:\Aerosoft\Professional Flight Planner X\PFPX.exe Looking at your example you have spaces where there shouldn't be any, perhaps that is what is causing your error. The lines in my example that begin with // just mean that line is disabled/ignored, its called commenting, or commenting out.

No you wont have to reinstall FSX nor Windows 7. Try deleting the FSUIPC4.ini file in the modules folder after backing it up to a safe location then try making your assignments again. If the problem goes away you will know it was due to something like dual assignments or bad calibration in the previous fsuipc settings file. If it still won't work correctly after doing that then it's likely that you have dirty or worn out old potentiometers. There are tutorial videos on YouTube explaining how to repair/clean them.

Go to the simmarket website and login to your account, then check your purchase history and confirm the registration details there that you recorded at the time of purchasing FSUIPC. All three parts must be identical otherwise the registration will fail. Once you have the correct details run the installer again and enter them when prompted.

To be honest Kiko, I am not sure what to do myself. I only fly FSX and I use the facilities in a program called "Linda" to enable the logging features, its very simple to do in that as there is a specific option that says enable VRi communication logging, which is what you need to do, but I don't know what to enable in FSUIPC directly or even if its the same in FS9. Linda doesn't work in FS9 so that is no use to you. There is a TAB in FSUIPC called logging perhaps if you have a play with it yourself after reading the manual you may be able to work it out. I suspect the EVENTS logging option is the one you need to use, so if you run FS in Windowed mode and also tick the "Send To Console" option it will open another window for you with the log being displayed in real time as you press buttons on the VRi hardware.

I've never seen that error before, the only thing I can think of it make sure FSX really isn't running (rebooting is a sure fire way of proving that), and run the installer again, but right click on the installer and select "run as administrator".