[PMDG 777 and Throttles]

Sorry, I guess I misunderstood that. Right now, the throttles aren't being handles by FSUIPC at all because no options I tried worked with T7, and PMDG's answer was to just use FSX's.

 

Which means I can't set the reversers up with the throttles either, because FSUIPC is essentially "ignoring" the throttles.

[PMDG 777 and Throttles]

Because it means I can't set up the reverses correctly. And because I have it set to calibrate with FSUIPC for every other plane, but now I have to undo that, too, because I had to turn on FSX controllers.

 

Basically because I want FSUIPC to handle everything.

[PMDG 777 and Throttles]

Option 1 with no calibration is what it's set to now, as directed by PMDG. I just hate it. :p

[PMDG 777 and Throttles]

It may simply be the way you are assigning or calibrating in FSUIPC.  Sometimes the calibration itself throws the A/T off because they may read the axis directly and then the calibrated value dsagrees.

 

If you told me how you've assigned and calibrated the throttles i might be able to suggest something. Either way there are these choices, still using FSUIPC only:

 

Assignment:

 

1. Assign to FS "Axis ThrottleN Set".

2. Assign to FS "ThrottleN Set"

3. Assign to FSUIPC Direct ThrottleN

 

Only in the last case there is it vital to actually calibrate in FSUIPC.  If you do calibrate in FSUIPC there are further options:

 

1. Normal, no options changed.

2. No Reverse Zone

3. No Reverse Zone with "UseAxisControlsForNRZ=Yes" set in the INI file (in the relevant JoystickCalibration profile if not wanted universally).

 

That gives 11 combinations to try (4 each for assignment methods 1 and 2, including no FSUIPC calibration,  and 3 for assignment method 3). One of those should work. Else there may be other ways yet to be determined, as was the case with the Aerosoft AirbusX (which needed L:Vars written to to control throttles!).

 

 

No, but the symptoms sound familiar. Don't you have the PMDG 737NGX or the Aerosoft Airbus Extended? I think one or the other of those had similar problems and solutions were found. It might be worth browsing a bit.

 

Regards

Pete

 

I'll have to look at how I had it set, but I've tried every combination I can think of. I'll try some of the ones you listed, too.

 

Right now, to get it to work, I have it sending directly to FSX, but I hate that. I'm pretty sure it was 3/2 from above, but I can't say until I check the non-profile-specific options.

 

As far as the other craft, I never had any problems with the NGX that were throttle related, those were more the weird way they were doing mouseclicks in some areas (I have a problem in the T7 with the landing lights that's like that, but it's nowhere near as big a deal as not being able to use throttles).

[PMDG 777 and Throttles]

PMDG's other suggestion is exactly what you said, to set them in FSX and not use FSUIPC, which I find rather annoying.

 

They seem to work perfectly fine from FSUIPC if the Auto-Throttle switch is off, otherwise they get all wonky. Of course that's not really a solution, either.

 

I realize it should be on them, and I wish they'd fix it, but I suspect they won't. Is there any data I can provide for you Pete to at least figure out what's going on? I hate to burden you with looking at something that's not really your fault.

[PMDG 737 NGX and FSUIPC]

Yes, i'm using SPAD instead of original drivers. But it's not working correctly.

When i turn wheel - nothings changes (digits on panel display are changing, but in FS - not), but if i turning wheel in FS (for example - HDG) - digits changes in FS and on panel display.

Unfortunately i should wait for some updates from pmdg or saitek...

Did you go through the SPAD control panel and change everything to an FSUIPC Virtual Button?

[PMDG 737 NGX and FSUIPC]

Sorry for my question, but i can't understand what i should to do.

I have registered FSUIPC, i have PMDG NGX and i have SAITEK MULTI PANEL.

And in 737 NGX only CRS switch is working, but when i turn it in HDG or ALT - it's doesn't responding.

I have try to create macro file, put it near fsuipc.dll, then i have create profile for NGX, but nothing changes.

May be i doing something wrong?

Are you using the SPAD drivers?

Saitek's panels are not "joysticks" or even input devices of any sort, at least not with Saitek's drivers, so FSUIPC can't see the panels at all.

If you download these instead: http://fstools.weebly.com/

You'll find it works just great.

[FSUIPC Mouse Macros for PMDG 737NGX]

Whether it's a GAU or a DLL which is called isn't your choice, but depends only on where the mouse click leads to in the code.

If the same DLL is used for both MCPs then they will probably be calling different entry points, so you should be able to create macros for both in the same Macro file -- just give them different names.

Regards

Pete

Alright, that makes sense, thanks.

I'm trying it now, but some button clicks aren't recognized. For example, clicking on any of the MCP buttons or using the wheel on the roatries doesn't come up with anything in the logs. Obviously there's a way to get those, since edfair has them from the Honeywell....

EDIT: Sorry I'm asking so amny questions, I'm just trying to learn how to do this so I can contribute as well.

EDIT2: Oh! If I use it in 2D mode it works much better.

[FSUIPC Mouse Macros for PMDG 737NGX]

Quick question, since I'm trying to get a macro file for the Collins MCP going....

These MCRO files here are using the DLL, but in the documentation, it looks like we can use a .GAU file? So if it loaded the Honeywell .GAU it could use one set, and the Collins .GAU another?

Assuming there is one, of course, I haven't actually checked.

[FSUIPC Mouse Macros for PMDG 737NGX]

Just an FYI these work fine in the older Honeywell MCP, but some of the functions (like the FD and CMD buttons) don't work under the Collins MCP, because they're in a slightly different spot.

[PMDG 737 NGX and FSUIPC]

Wow, thanks, that's exactly what I needed to get the panels to work through SPAD.

Unfortuantely, it seems like the F/D and CMD A and CMD B aren't working properly, but maybe that'll just take some tweaking?

EDIT: Figured it out.

These work fine with the Honeywell MCP, but not the Collins MCP.

[PMDG 737 NGX and FSUIPC]

I can do that.

Either way, I'd rather have some kind of MCRO file as opposed to using mouse stuff, but I guess it could work.

[PMDG 737 NGX and FSUIPC]

Is there a way (an easy way?) to take the Lua file for the NGX from LINDA and make it in to a MCRO file for FSUIPC?

I like LINDA quite a bit, but it doesn't work with my Saitek panels. I have the SPAD drivers, so FSUIPC will see it as a joystick, but LINDA will not, and I'd really like to get that working in the 737.