Andydigital

Hasn't anyone at the ProSim forums already done this, in passing I've read a few posts over there by customers who say they are already using the VRi MCP Combo and the new MCP2 with ProSim. I do not have the ProSim Avionics suite or Project Magenta so I have no idea what they have available to them as far as functions.

You need to use a toggle rather than specific on and off commands.

Its really simple assign the function you want twice, once in the pressed box and again in the released box, that way you will action the function every time you press the button rather than every other time.

Ahh understood, I've only ever saved a maximum of 10 so had never noticed this in the past.

It's also strange that there are 60 records in the Autosave section when you have 10 specified as the number to retain.

Was FSX closed down when you edited it to remove the line I spoke of before, as the log clearly says 16224 Aircraft="Flight Test Aircraft E1", did you also save the file after editing it?

Try deleting the line highlighted below from your FSUIPC4.ini, is this perhaps the FA18? If it is then it means that YOU have assigned the FA18 to the Cessna profile that you made. With that line removed you should now be able to make a new profile for that aircraft. [Profile.cessna152] 1=C152II LIGHTBLUE G.F. 2=Flight Test Aircraft E1 3=C152II Calypso G.F.

@Mario, but they are Null key presses on release just like the other chap had, so delete lines 3= and 5= and you should be OK then.

If you look in the folder; ....Microsoft Games\Microsoft Flight Simulator X\PMDG\PMDG 737 NGX\SDK and open the file "PMDG_NGX_SDK.h" with something like Notepad. Search for; EVT_OH_LIGHTS_L_ENGINE_START You will see at the end of the line it says; (THIRD_PARTY_EVENT_ID_MIN + 119) 119 is the number you have to add to the number 69632 to get the correct control number to input into FSUIPC. For the parameter I searched nearer the beginning of the file and found; unsigned char ENG_StartSelector[2]; // 0: GRD 1: OFF 2: CONT 3: FLT

119 left and 121 right + 69632 so; Left 69751 Right 69753 Then parameter 0 to 3 depending on what state you want to set the switch to.

From another section of the .h this is mentioned; unsigned char ENG_StartSelector[2]; // 0: GRD 1: OFF 2: CONT 3: FLT[/CODE] Don't know if its of any help but VRinsight do have the start switches working perfectly on their V737 Overhead panel hardware.

Rudder trim is best setup with buttons and not an axis, there is not enough resolution in any joystick axis to work well with rudder trim, I have the similar stick and not even the Warthog has enough resolution. I use a hat switch and use a repeat while held function and also have another button setup to centre the trim quickly for takeoffs etc. I've tried an axis many times in the past for rudder trim and have never been happy with the results. Just use the FS Controls for trim increase and decrease in increments, it's a lot less hassle and works fine in my opinion. Pete is still on holiday, he's not back for a few days yet.

The NGX doesn't support Mouse Macros, you have to use the NGX SDK provided by PMDG and L:Vars, Lua scripts etc. You should also look at the free program LINDA, they already have an extensive collection of scripts that do all the hard work for you, converting the lua scripts to work directly with FSUIPC is simple but tedious, so using them via LINDA itself is far easier. http://forum.avsim.net/forum/424-linda/

Why not just use FS Controls rather than messing with offsets, you are greatly over complicating things, search the document "list of FS Controls" for the word "rudder trim".

There is documentation included in the FSUIPC SDK. Link taken from this page http://www.schiratti.com/dowson.html The SDK is listed under the FS2004 section of the site but its actually the same SDK for all supported versions i.e. FS2004, FSX and Prepar3d. http://fsuipc.simfli.../FSUIPC_SDK.zip

You are welcome.

Yes you need a new code for FSUIPC4, a huge amount of work was carried out to rewrite FSUIPC to work with FSX.

Pete is away on holiday for a little while longer yet so I will try to help. I think the link below will take you to a post that should help you fix this problem.

Maybe that's max, hit the opposite button instead.

Pete is away on holiday still, but the usual cause of problems like this are; 1. Incorrectly spelt name or email address compared to what you stated at the time of purchase. 2. PC clock wrong i.e. date and time on the PC you are trying to register FSUIPC on is set to a date before the time when you purchased the key. 3. You didn't copy and paste the key from the Simmarket website correctly, I.e. an extra space at the end or beginning of the code. 4. You purchased a key for FSUIPC3 and are trying to use it with version 4 or vice versa. i.e. Keys are not interchangeable between major versions. 5. Finally the key perhaps is no longer valid due to it being blocked due to piracy reasons, unlikely if you just purchased yesterday.

Try deleting the wx file associated with the default flight, it may have become corrupted somehow. If you are not sure how to do this the easiest thing to do is delete the line starting with "Situation=" in the fsx.cfg, save it, then run FSX and see if that fixes it.

Do you have the latest version form the page below? The latest version you have may be one from weeks or months ago, please state the version as reported by FSUIPC when you open its GUI in FS, the first page that appears will show you the info Pete will ask you for when he returns from holiday in a week or so. http://forum.simflig...pdated-modules/

The unregistered version if mainly for third party developers to allow them to interface with FS and this is a free service. The are a few major fixes included in the free version too but they just work and need no setting up. The is one other recent addition that was added in the last month or so and that was an optional tweak to the way ground friction works, that is detailed in the documentation that comes with all versions of FSUIPC, registered or not. Reading those documents will provide you with all the info you need to make a purchasing decision.

Neither has precedence, that's why its says in the manual only ever have a function assigned in one or the other, but never both otherwise you will have problems with conflicts. As long as you only have each individual function assigned in only one place then everything will be fine.

But have you installed the latest version from here? http://forum.simflight.com/topic/66139-updated-modules/ Reinstalling FSX is never a good idea as its too intertwined with the Windows OS, it usually gets damaged beyond repair without an OS reinstall (and format) of the OS drive.