Andydigital

No problem Mariano, glad to hear the problem is resolved.

Make sure you are using the latest version of FSUIPC from the page below then test again. http://forum.simflight.com/topic/66139-updated-modules/ Also make sure everything is run with the same rights level, i.e. FSX, SerialFP2 or VRiSim all run as administrator or everything NOT run as admin, do not try to mix some with and some without as Windows will not allow those program's to communicate with one another.

Try unplugging the joystick and rebooting the PC then try deleting the file again. It may also be a permissions problem, right click on the windows explorer icon and select run as administrator then navigate to the file and see if you can delete it then. It was so long ago since I had to do this I can't remember if I had any problems or not deleting the file.

The fix is still the same though, any buttons not working after removing the file mentioned above are not programmable at all, I seem to remember there might be one or two that aren't.

Pete is away on holiday for 3 weeks so I will try to answer your questions. 1. Yes its automatic with the Dynamic Friction LUA nothing else is needed to be done by you. 2. Yes you should be able to use it in P3D, whether it is recommended or not is no different than if you asked the same question in regard to FSX. Try it and see if you prefer it or not.

I fairly certain that this isn't possible because CTRL is a modifier key, its not supposed to be used on its own normally, its a rather strange key for FS2Crew to use in all honesty. Perhaps you should ask FS2Crew to make the key re-assignable if that's not possible already, problem solved for all then.

Those buttons are not meant for general assignment, they are supposed to be used with Saitek's joystick programming software as a mode changing system. It is the large chrome wheel on top of the joystick that you are talking about not being able to assign, am I correct? If so then you need to seek advice on the Saitek forums and ask them how to make the mode selection dial assignable via Windows joystick interface. I seem to remember it involves you deleting a particular file from the windows system32 folder, I cannot remember the name of the file though as I no longer use that particular Joystick.

And of course make sure you are using the latest version of FSUIPC from the page below. http://forum.simflig...pdated-modules/

Did you turn off UAC as I suggested? Try changing your VSPE pair to 21 - 22 then try this below instead. Also before loading FS9 check that SerialFP2 is still reporting that it is using COM3 to connect to the VRi panel, if it's not then change the COM3 below to whatever it says it is now. [VRInsight] 1=COM3, COM21[/CODE]

User Account Control, a quick google will tell you what it's about and why you need to disable it especially with old program's like FSX and FS9. Pete is on holiday for 3 weeks so he won't be able to help you till then. In the mean time please copy and paste the relevant section of your FSUIPC.ini file so we can see what you have put in the VRinsight section.

Try disabling UAC in Windows 7 and also make sure you are running FS, VSPE, SerialFP2 or VRiSim with the same user rights, i.e. all must be run as administrator or all not run as administrator, do not try to mix them otherwise Windows will stop the programs communicating with one another. Please also see the program called LINDA (if you are using FSX) which is much better for setting up the VRi MCP Combo with new aircraft, it is more user friendly. Please see their forum linked to below for more details. http://forum.avsim.n...orum/424-linda/

I've answered you over at the VRinsight forum where you posted first Fredrico, please follow my instructions there and respond there too if you need to, thanks. Here is a link to the reply; http://vrinsight.com/phpBB3_en/viewtopic.php?f=13&p=6182 No need to answer here Pete its probably an out of date VRinsight software package, many folk seem to not bother checking the website for the latest software and just install what is on the DVD that comes with the device, these are usually months out of date.

I'd research the Saitek Trim Wheel a lot more before you decide to purchase, especially for use with complex aircraft like the PMDG NGX for example. The fact that it has end stops and its a real axis has many drawbacks even with 9 rotations lock to lock. You will find other topics discussing the very subject here in this FSUIPC forum. Just using two buttons on a yoke or a joystick is far more compatible and more realistic even for a Boeing. It may be usable in small GA aircraft but you will always have problems when turning off the auto pilot (the FS auto pilot uses trim to fly the aircraft) because it will very rarely be in sync with your trim wheel. If there is any jitter from the Saitek pot this will cause the trim in the aircraft to sync with your trim wheel once again and this could result in a large change in trim angle which may lead to a big pitch up or down movement. I've seen a few people complain about that issue before and that's why they came here asking for a possible solution from FSUIPC. Food for thought.

You need Wideclient for client machines not FSUIPC.

Sounds like you need a pint Pete :razz:

Just use your key again all updates to FSUIPC are free as long as you are using the same major version number i.e. 3.xx Your key won't work with the FSX version of FSUIPC because that major version number is different i.e. 4.xx

4.858 is the latest at the time of writing. Updates are in the "updated modules" thread in the fsuipc download links sub forum. http://forum.simflig...pdated-modules/

You asked the same question in another topic and I gave you the answer there. Here it is again. Please see the post below in the FAQ (frequently asked questions) section of Pete's FSUIPC sub forum, that post contains the information you require to fix the problem. By the way, Pete is away on holiday and won't be back for a couple of weeks.

Please see the post below in the FAQ (frequently asked questions) section of Pete's FSUIPC sub forum.

What did FSDreamteam say when you asked them for the option? Surely they are more likely to have an answer for you than Pete. They do seem very amenable to adding new features, certainly more so than AES ever has been.

Pete is away on holiday for 3 weeks as per his announcement on the forum a few days ago, he'll get back to you on his return.

Pete is away on holiday for 3 weeks as per his announcement on the forum a few days ago, he'll get back to you on his return.

All FSUIPC settings are saved in the file FSUIPC.ini (FS9 and earlier) or FSUIPC4.ini (FSX/P3D) located in the same folder as FSUIPC itself i.e. the \modules folder which is inside the main FSX or FS2004 folder.

You need to check FSX in its own control assignment interface, FSX automatically assigns a default set of buttons and joystick axes for any USB HID type device when it is connected to your PC for the first time. It is probably there where you will find these trim controls assigned.

The DODO uses some very sophisticated FBW techniques and flight model tricks to enhance the very poor helicopter flight dynamics in FS, this is probably why you are seeing strange outputs in the FSUIPC logs that Pete asked for. I've been using the DODO since 2009 in FSX with the axes assigned through FSUIPC with no problems at all. Here is my AXIS section for the DODO, you will see that it uses all the standard "AXIS Elevator Set" etc, control surface commands. [Axes.Dodosim B206] 0=BX,256,F,65763,0,0,0 1=BY,256,F,65762,0,0,0 2=RR,256,F,65764,0,0,0 3=PX,256,D,4,0,0,0 4=PY,256,D,5,0,0,0 5=AZ,256,F,65765,0,0,0 6=AR,256,F,66291,0,0,0[/CODE] [i]EDIT: Deleted last paragraph and replaced with this.[/i] You should have always assigned to the general throttle command, Throttle 1 is not used by the DODO, you should only ever assign to the throttle 1 command in a single engined craft when specifically told to so. Otherwise you should always use the general throttle command as a preference in single engined aircraft.