Pete Dowson

Assuming you have the numbers right, then they should do something, but it might well depend upon the parameter. Unfortunately the PMDG SDK does leave a lot to guesswork and experimentation. One idea is to try using the mouse emulating controls values -- see the thread near here entitled "Offset3110 and ngx problem" where the OP ended with "Then I go back to read the pmdgsdk PDF again,find out there is another way to control.Not write 1 or 0 to the parameter offset3114,but write 0x20000000 or 0x40000000 (etc) to 3114,these numbers mean some mouse operations ,like left click and so on.". Maybe that's the way to go? (Offset 3114 holds the same as the parameter in your assignment). Regards Pete

I don't have a list of all the special controls PMDG added for the NGX. If you look in the SDK folder, in the PMDG 737NGX folder in your FSX, you will find a file ending in filetype ".h". That is the definition of all the data which FSUIPC or other programs can extract, and also, nearer the end, a list of all the "custom controls" which can be sent to it to do things. You need to find the control you want, and work out the number it needs -- it will be a base number plus another. The base number is also defined, near the top of that list. Once you have the number you just assign it, in FSUIPC, to a keypress or button as "<custom control>" with that number, and any parameter it may need. Regards Pete

The fonts and so on are set by Windows. Either choose a larger size standard Windows font, or, better generally, reduce the screen resolution. That will make everything big enough. If things are too small you are likely using too high a resolution for your eyes. Pete

Sorry, I really don't know what that means. Again, I am very sorry, but I cannot relate what you say with anything I know. This certainly sounds like a fault in the controller board or its firmware. You only need to select the 737NG settings. Everything else is then assumed. I would have hoped that the system and software was supplied to you already configured correctly. Do you not have any PFC support at all? I think that the motor controlled trim was not installed on all of their 737 cockpits. I can send you a copy of my PFC.INI file for you to test with, but I really don't think that will help -- and it will need some editing to work on a different system in any case. I really think you need PFC support. I would do myself in the same circumstances. Regards Pete

Okay. That is certainly a log. But unfortunately you forgot to enable the Button logging in the FSUIPC menu as I suggested. (I said, if you look back far enough, "use FSUIPC's button or key logging to see what you are getting."). If you don't know where to look, and perhaps haven't read any of the FSUIPC documentation supplied, then try pressing ALT then D then F, in turn, to get you to the FSUIPC menu, and selecting the logging page and check the options on the left -- not all of them, only the buttons one. Then press your buttons, the ones you think are not being dealt with correctly, and get the log to paste here. Okay? The documentation for all these facilities is provided in the FSUIPC Documents folder which is in the FSX Modules folder. The Installation document you would have seen in your download would have told you this. Regards Pete

Sorry, but I certainly wasn't "having a go"! If you had just said you didn't know where to find the log file I would have told you straight off! I assumed that because you found the INI file with your settings you would have seen the LOG file right next to it! There aren't many files named FSUIPC4 -- the DLL, the INI, the KEY and the LOG, all in the same place, all in the FSX Modules folder! When you do find it, please simply paste it here like you did with the INI file. And where was that ever made clear before now? You never said you couldn't find the log file! You managed somehow to find the INI file without all this fuss. Sorry, I don't understand where you are coming from with these accusations. :sad: I really take great objection to that! I provide almost immediate help to every one no matter how simple or complex the problem. I do it 12 hours or more a day every day, excepting only when I'm away or out -- which isn't very often owing to my eyesight problems. But I cannot read your mind. I you can't find something you need to just say so, not simply ignore the request for data as you appeared to have done, twice. That said, though, there is no way I can help diagnose faults in PMDG aircraft. I can only tell you if FSUIPC is doing what you are asking of it, and if not then why not. Regards Pete

Thank YOU for your appreciation! Regards Pete

Are you sure it isn't a problem with the way the PMDG controls work? That would seem to be more likely to me. I'm afraid I can't really help much more than that, because I don't use the NGX and I don't know C# or the DLL you are using -- for support of Paul Henty's DLL you should really post to the FSUIPC Client DLL for .NET subforum. For PMDG support try the PMDG support forum. One other way to test would be using a Lua plug-in. Try this: ipc.writeUD(0x3114, 1) ipc.writeUD(0x3110, 70193) Save that as, say, "test.lua" into the FS modules folder, then assign a keypress or button to "lua test" in order to execute it. Using Lua to test and develop ideas is very useful. It is a good "prototyping" method. [LATER] I had a peek at the list of controls in the PMDG SDK header, and it appears there's a different control for each character you wish to enter into the scratchpad. I don't see there's a reason for the parameter in 3114. That would explain why your sequence: {test2.Value=1; test1.Value=70193; FSUIPCConnection.Process(); test2.Value=0; test1.Value=70193; FSUIPCConnection.Process();} displays '11'. Why not just try writing to 3110 only, maybe clearing 3114 to 0 initially in case it does change the meaning of the function (i.e. in case the '1' was the reason it didn't work). Regards Pete

Well, that's just the INI file. Where's the log showing the buttons being pressed, which I've mentioned twice before? Sorry, no. I do not use any PMDG aircraft. Maye the PMDG support forum can help? Regards Pete

Well, assuming you can't make head nor tail of it, I'd need to see the log with your button presses recorded. The [buttons] section of your FSUIPC4.INI file would also be useful, to see the actual assignments you made. Pete

Have you tried using Logging as I advised? Something is obviously not set correctly, but without more information I couldn't say. Pete

FSUIPC doesn't care what's connected -- that only matters when you start doing assignments or calibratins It's because you answered 'yes'. And it is generally useful to do that unless you really want to start afresh with the new profile, with different controls. Just deleting the lines will probably be less confusing at a later time. Yes, starting with the [Profile.Joystick] section itself. Pete

I'm afraid I have no idea what that 'reset' does so I can't really help further. There's no specific facility in FS called "reset". You can reload (or 'reset') the current flight (maybe this is what you mean?), or load a different flight, or load an aircraft, or simply close the current flight in which case it goes to the menu. Pete

"The Sim" being what ... FSUIPC or the PMDG aircraft or SB? Are you using an FS9 version of a PMDG aircraft? Are you using SB3 or SB4? I don't think SB3 works on FSX. Use FSUIPC's button or key logging to see what you are getting. There's not enough information here for me to help. Pete

Correct. I'm not sure what you mean by a "reset", but if you mean a Flight file loading, you could have it triggering on an event. For example, enclose the whole existing code as a functin, i.e. function initswitches() ... end then add this afterwards: event.sim(FLIGHTLOAD, "initswitches") Then it will stay resident and be executed each time you load a flight. I'm not sure if this will operate initially, for the first flight 9as it might be loaded too late), but if not just also inster initswitches() before the event line so that it will run at least once initially. You can do the same for aircraft changes (but not same aircraft re-loading) by using the AIRCRAFTCHANGE event type instead. See the Lua library document. Pete

FSUIPC is an FS module, it runs only INSIDE FS. You cannot install it on the non-flying PC -- there is no point in doing so! Regards Pete

In that case be very sure to use the faciklity in FSUIPC to have joysticks identified by letters rather than numbers, so that there's no possibility of cross-assignments. You must also disable controllers in FSX altogether because otherwise it will make automatic assignments each time it sees the newly connected joystick. Yes. If the yoke isn't only assigned in a Profile then the buttons on the yoke will also still apply, but not the axes. -- buttons can be general and specific, but axes, because they are always active, are only applicable where assigned. The axes for those, and their calibrations, yes. You could do that by copying stuff in the INI file. No, because axes andcalibrations for a profile exclude non-specific ones. The buttons will still apply, but won't matter if you don't use them. Just don't assign it to anything, or find another use for it. If you don't mind FSUIPC assigning letters A, B, C ... by itself, that's the easiest way. But you might want letters you recognise easier, like Y for Yoke, J for Joystick, R for Rudder pedals, T for throttle. For your own letters just reproduce the joystick list and change the numbers to letters, as illustrated in the chapter on this in the User Guide. FSUIPC will automatical do all the asignment lines when it next starts. Regards Pete

Posts from new posters have to be approved, and I sleep sometimes at night. Sorry. I saw two identical entries from you awaiting approval and automatically deleted the older one, on the basis that posters often post the same thing two or three times. So, apologies, this time I appear to have dleeted the one with a question in it. Pete

For new posters messages have to be "approved" before they appear. I do that when I see them, but I'm not looking 24/7. ;-) Hmm. Interesting. It could be capturing the mice and sending the messages to the relevant Windows, I suppose, but dealing with the automatic focus change that induced would be problematic. Thanks for the link, though. I don't have a use, but I might look at it to see what it is actually doing. I was using an i5-2500K overclocked to 4.8GHz with a 3Gb GTX 580 card. With UK2000 EGLL and realistic amounts of AI and English weather the frame rates were just between 12 and 25. Adding a second window makes it unfyable I assure you. My new PC is a 4770K currently clocked at 4.3GHz with a 3Gb GTX 780, and whilst that does raise my "test" framerates to the 18-30 range, I would still not dream of opening another window. Of course, although I'm projecting ontp a 10 foot wide screen, I wouldn't really want two different views on it -- it would spoil the illusion through the cockpit glareshield! ;-) Unless there's a program which will do the specific rapid focus switching, or direction of control (if that can be done -- not sure the separate Window views actually process the messages themselves), like your "Pluarinput" program, or you write one, I really don't think that's going to be possible. You'd think that if they can do it with the mouse they could do it equally well with the keyboard -- both are focus related, though of course with the mouse it is the click whch changes the focus, whereas with keypresses the focus needs changing first. Just a different order of events. Regards Pete

Amazing! And do the buttons work on their respective positions properly? On the same, or separate windows? It's probably down to what Windows knows as "focus". The one window with focus gets keyboard and mouse actions. That's why I said 2amazing2 for your two mouse pointers -- if they operate simultaneouisly on separate windows, then surely you can get another program which will do the same for keyboards? Both really surprise me. I have a 737NG cockpit with two complete sets of controls, but we don't use mice or keyboards, only 737-type switches and so on. For views I do have switches programmed for that on both yokes, but both pilots look at the same (projected) screen. I would never consider having more than one view open at a time in FSX because the frame rate would plummet. There's no panels on scren of course, only the outside scenery. Regards Pete

Thank you for the appreciation! Pete

Aha! Yes, sorry, I see now. It must be due to the addition of those Radio events which can be followed by a KEY_SELECT event in order to determine which radio is being addressed. This applies to these events: KEY_NAV_RADIO, KEY_COM_RADIO, KEY_FREQUENCY_SWAP, KEY_XPNDR, KEY_VOR_OBS, KEY_ADF, KEY_DME, KEY_JET_STARTER, KEY_COM_STBY_RADIO_SWAP, , KEY_NAV1_RADIO_SWAP, KEY_NAV2_RADIO_SWAP, KEY_ADF1_RADIO_SWAP, KEY_ADF2_RADIO_SWAP The event is batched with the SELECT and sent to SimConnect using the Macro facility ("macro begin" and "macro end"). Of course this can only be done if FSUIPC holds over the main event for a short time to see if a KEY_SELECT occurs. This is the facility in FSUIPC to prevent those add-on panels which constantly send events to FS from stopping these select actions operating correctly. It's actually an option in the Miscellaneous tab in FSUIPC. It defaults to 4 seconds. You could try setting it to zero. It's saved as the "TimeForSelect" parameter in the INI file. The radio stuff was added to this facility when a user pointed out that the facility was not working correctly on these events -- version 4.91, August this year. Sorry that this action didn't occur to me earlier. A SimConnect log would have shown the macro facility being used here. Regards Pete

You either need to assign everything in FSUIPC instead of in FS, or you need to be very careful to ensure there are no conflicting assignments. If you enable joysticks in FS you would need to go through every button and axis assignment to delete those which you want to assign in FSUIPC. Even then, FS has a nasty habit of automatically re-assigning things behind your back -- it especially will do this if it thinks the device is newly connected, or you have unplugged it and plugged it in again. It can even do so at other times too, usually if the device "goes to sleep" and is re-awoken by use. Generally it is better to assign everything in one place or the other. Makes life more predictable! Regards Pete

Does the Registration get rejected saying 'invalid key'? If so you are making a mistake. Your name and email and Key all must be EXACTLY correct. Use cut and paste if you can't copy manually. Regards Pete

Sorry, I don't understand. Are you assigning U and D letters on the keyboard, not the Trim Up and Trim Down FS functions? You talk about three things -- Hat, keyboard and FS trim up/down functions. How do the three work together? I don't know what you are trying to say. Have you even checked that the PMDG 777 operates its trim using default FS trim controls? Test your assignments on a default aircraft, not such an advanced one which may be doing its own thing completely separately. Sorry, I don't have the 777 and don't know how to program it. Does it come with any documentation at all? Have you checked PMDG support? Both those aircraft are unique to themseves. Sorry, I can't advise. And I don't know this "SST" at all I'm afraid. If you know how to make things work in those PMDG aircraft, by keypress or by custom control, or even possibly (but less likely) by mouse macro, then, yes, you can probably do those things via FSUIPC. But I can't say definitely one way or the other because I don't have those aircraft, and I don't know what SST is. Sorry. BTW have you checked through the User Contributions subforum? There mifght be some solutions there. Also check out Linda, which I think is supposed to make a lot of this stuff easier. Regards Pete