Andydigital

AFAIK neither the default 737 nor the NGX are amenable to Mouse Macros that's why it's not working and thats why there is an SDK for the NGX. Not many aircraft do work with Mouse Macros these days as the gauges are usually programmed in XML and not C++. Also even if an aircraft is amenable to mouse macros, 9 times out of 10 only the 2d panel gauges will work with them, if you try using the VC buttons and switches they wont work at all, like in the MD11 example earlier in this thread.

http://forum.simflight.com/topic/73967-pete-dowson-is-away-until-april-1st-2013/

No parameters are not needed for those functions as they only have one directive each i.e. decrease the throttle position incrementally or move the throttle to idle (0%). Do the hardware throttles work the correct way around when you move them compared to the throttles in the VC of the aircraft in question? Are we talking about Saitek throttle quadrants? You have seen the REV boxes on the calibration tabs haven't you? Also make sure you are looking at the correct calibration page as there are separate ones for single throttles and a few pages further over more calibration options for multiple throttles. Perhaps you should follow the examples in the FSUIPC manual first and then configure the reverse buttons later, something is just not right with your setup it seems.

Sorry no idea whats going on there then, perhaps you have some conflicting assignment elsewhere or maybe the throttles need recalibrating or something. Pete will have some suggestions for you when he returns from vacation.

It should be, when button pressed "Throttle 1 dec small" (plus tick repeat while held) then on button release you send "Throttle 1 cut". Then do the same thing for the second lever with Throttle 2 dec small etc.

Not really some aircraft have a reverse lock which you lift (pull) the throttle lever up over and pull the stick further back past the idle point.

Try it both ways, nothing is irreversable in FSUIPC Alan, I pretty sure its covered in the manual though. As I said I'm no expert, its not something I use very often at all so I am a little rusty in this regard.

Oops yes, I forgot about the repeat while held for the button press. Fast or Slow depends on the aircraft.

Put 73F8 in the offset box and 0 or 1 in the parameter box depending on which way you want your switch to work. I'm no expert on them but from memory I think that is how it is.

For the reverse switches assign "Throttle 1 decrease small" for on button press and on button release assign "Throttle 1 Cut", then use 2 for the other levers reverse switch. Those names aren't exact but they are close and you should be able to find them.

Assign the parking brake to the button press in FSUIPC and apply the normal brakes function to the button release in FSUIPC. Pressing FS the brakes function i.e. "." on a keyboard will cause the brakes to go on but it will also force the parking brake off. This is how I have my parking switch setup and it only has an on and off position, i.e. a closed or open circuit.

You need to recalibrate the spoiler axis in the calibration tab after you use the REV option, the same is also true if you then change in back to not using the REV option again, you would need to recalibrate again.

That's what I meant in my last reply, yes. You should also check that your throttles are calibrated properly, that's why I mentioned them before, if they aren't calibrated properly and don't get all the way to idle, then it's possible the spoilers will automatically retract straight away. Try pressing F1 to confirm they really are at idle in the sim, then play with the spoiler lever in the VC rather than on your Joystick or throttle quadrant and you will see the spoiler lever retract again the moment you move the throttle out of idle with throttles in the VC. If your hardware throttle is spiking even when in the idle position then your spoilers will retract too, if you disconnect your throttle and the spoilers then begin to work properly with the VC levers then you know you probably have a faulty pot (spiking) and/or incorrectly (un)calibrated throttle lever on your quadrant.

The default spoiler system in FSX does work correctly when you are on the ground testing it (same for the iFly too I think), be sure to only test spoiler operation when in flight, otherwise the lever will jump back to the "lever up spoilers down" position automatically. If the throttle is not in the idle position or if you move the throttles out of the idle detent that will also cause the spoilers to retract automatically. There is no need to tick the "filter" option either, that is only there for very specific reasons, for example you have a very old joystick device that spikes due to dirty potentiometers or you live in an area with very poor electricity supply which can also cause unwanted variation in axis output.

Pete is away on holiday I believe so I will try to help. Looking at the end of the install log we have this; Checking compatibility with installed SimConnect Found SimConnect build 60905 (Original), but this is not correctly installed! ... Failed to find a valid SimConnect needed to use FSUIPC4! [/CODE] Something seems to be wrong with your FSX install, did you run a repair install at some point? 1. Whatever happened you need to try to install Service pack 1 then run FSX and load an aircraft to the cockpit ready to fly, then close FSX. 2. Next install Service Pack 2 for FSX and load the sim to the cockpit and close FSX again. 3. Finally run the FSUIPC installer again and now hopefully it should complete properly and the next time you load the sim FSUIPC should appear in the Addons menu item.

If you are running in windowed mode and you move the mouse to the title bar area when you have finished using the mouse then yes the frame rate goes back up the instant the cursor is no longer overlaying FSX. The more click spots there are in a VC for switches and dials, the bigger the differential in frame rate when the mouse pointer is over the FSX screen. The PMDG NGX and iFly 737 are both pretty bad in this regard, although the NGX is not quite as bad. I got this info from one of the folk at PMDG a few years ago. 2D panel views don't seem to be effected anywhere near a badly, it's the VC view that suffers this problem.

Well you must have the same axis assigned in more than one place then if its only acting strange in FS. Have you tried disabling controllers in FSX and assigning only in FSUIPC, press CTRL + K or it might be Shift + K to disable joysticks on the fly.

http://forum.avsim.net/topic/400609-what-happens-if-i-delete-fsuipc/

I believe you have already found the answer to your question at the iFly forums, if that's not the case please see the post below for details. You need to be a confirmed owner of the 737 to view this thread. http://ifly.flight1.net/forums/forum_posts.asp?TID=9872&title=switch-buttons-vrinsight-problem

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.

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. http://db.tt/wSBcpJ1