Andydigital
-
Posts
1,227 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Andydigital
-
-
You should look at LINDA too, if you enable Developer mode there is a brilliant L:Var tracer built into it too.
-
PMDG does have lights on the actual overhead in the VC but there is no way as yet to monitor there state externally.
-
The SDK for the NGX isn't complete and door annunciation on the overhead doesn't work at all, VRInsight can't get it to work either. PMDG told VRi at a flight sim convention in early 2012 (it may have been late 2011 actually) that they would be adding more functionality to the NGX SDK in the future when they have finished and released the 777. Hopefully at some point they will fulfill the commitment they made at the conference.
-
The email address is only used to uniquely identify you, so there is no need to change it, just keep a note of your registration information somewhere safe for future reference.
-
Didn't it (Linda) use the same module for Prosim and Project Magenta? Have you tried assigning to the functions in the project magenta lists?
The version of Linda that I have has Project Magenta included, you are welcome to download it from my dropbox.
https://dl.dropbox.c...LINDA-v1.11.zip
You can get your own free dropbox at the link below.
-
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.
-
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.
-
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.
shift+ctrl+X
in FSUIPC Support Pete Dowson Modules
Posted
It doesn't matter what order the modifier keys (CTRL SHIFT) are in, they should still action the function in FSC. Try it the other way around with the keyboard and you will see it still works regardless of the order of the modifier keys are pressed. As long as the non modifier key comes last it will work either way.