Pete Dowson

No. All recent versions of the Installer accept different Email addresses for FSUIPC and WideFS. But the name you use must be identical. Just make sure you spell it the same, letter by letter, punctuation spaces and all.. Regards Pete

That'll be its "GUID". If you have FSUIPC installed you'll find it related to the device name in the [JoyNames] section of your FSUIPC INI file (in the FS Modules folder). For example, [JoyNames] AutoAssignLetters=No 2=Saitek Pro Flight Throttle Quadrant 2.GUID={B0ABDEC0-6DA5-11E0-8001-444553540000} 0=4 axis 13 button gamepad with hat switch 0.GUID={5E542070-4F04-11E0-8004-444553540000}[/CODE] The name of the device identified by the number on the left of the '=' is related to the GUID on the line with the same number to the left of ".GUID=". Pete

Ah, thanks Andy. And I quote my reply from there: So now I have the Log, and all I need to is Windows error data -- which evidently the OP does know how to get hold of after all. I'm afraid too much has changed in the lead up to version 4.86 and I can't really relate the details originally posted to my current code state because of those changes. Let's hope he gets back with the needed information! Best Regards Pete

Okay. Some sort of link to that would have clarified this. Before I go chasing threads in the enormous AVSIM forum, would I find any more information there at all? If not, why should I? What actually references FSUIPC? This information is vital if you want my assistance. If I have the actual crash information then I may be able to help solve it, or at least make sure FSUIPC isn't cited any more when you do get your crash. I need the module offset and crash error code, which will be provided in the detailed Windows crash report in the event log. Let me know if you don't know how to get this, and I'll try to give instructions. Regards Pete

Requested when? Can you please give me a clue as to what this is about? Is it from another thread here? You asked what happens when you remove FSUIPC? Why there? If you remove FSUIPC.DLL from the FSX modules folder, it won't run. That's it! Nothing will "happen". If you are not using it and none of your other add-ons are using it, then why is it there in the first place? I see that you even paid for it: Why on Earth purchase it if you don't use it or want to use it? If you have a problem with it, wouldn't it be better to help me solve it for you than simply wanting to ignore it? If FSX is crashing on you, I need more details. The most important part is the data in the Windows event log. Incidentally, there is at least one thing FSUIPC is doing for you.The last line in your log shows that some bad scenery file you have installed would have crashed FSX at this point: That's 2,459 seconds into the session -- 41 minutes. Did FSX then crash, or is this log a fragment taken before FSX was closed? If FSX crashed soon after this G3D error, then it seems very likely that the scenery or 3D object file responsible for the error which was trapped is more extensively corrupted than the 'normal' G3D error, and that this is what is really causing your problem. Regards Pete

Not as straightforwardly, no. The easy thing to do is simply assign the toggle control to both the "press" and the "release" action of your switch. This works fine except that you need to synchronize the settings at the start -- i.e. your switches off or on when the FS ones are. Thereafter you should be okay. There is another way and that is by using the FSUIPC offsets to turn things on and off. For lights they are all grouped in one offset (0D0C), with one bit for each. You'd use the "offset word setbits" to set specific bits in that offset, and "offset word clearbits" to clear them. See the Offsets list (a document in the FSUIPC SDK, or now included in your FSUIPC Documents folder if you've installed the current version of FSUIPC). Regards Pete

I sspect you are still a bit confused. Offsets for the NGX data readouts are listed in a document installed in your FSUIPC Documents folder. Have you looked? The title of that document should be obvious to you. The specific assignable custom controls for the NGX are listed at the end of the PMDG_NGX_SDK.h file provided by PMDG in their SDK. This is mentioned in the section "Notes for programmers" in the document in the FSUIPC Documents folder I just pointed you at. The controls we have just been discussing, however, are standard FS controls and apply to all jet engined aircraft in FS, so they are of Microsoft origin and you need to refer to FS help and documents. They are specific engine variants of the same controls FS assigns by default to Ctrl+Shft+F1 and Ctrl+Shift+F4. Pete

What key presses? You want mixture controls, "mixture1 ..." for engine 1, "mixture2 ... " for engine 2., etc. Pete

"Lean" is cutoff, "rich" is idle. Pete

First off, please update to the currently supported version, 4.86 that's normally due to incorrect assignment, or assignment to controls being intercepted through an add-on. In the version of FSUIPC you are using there is an option you can change to make that work -- direct assignment to calibration works fine either way. This discrepanvy only occurred in a small number of intermediate rleeases between 4.859 and 4.86, it was actually fixed some time ago. Your 'p' version is rather out of date. The most simple and fastest way generally, at least to start with, is to check that you are using the most up to date release, which you are not. Version 4.86 is current both here in the Download Links subforum and in the main Schiratti download site. Regards Pete

You are a bit mixed up here! Offsets are locations, or references for data. They are not controls. The numbers you quote are NOT offsets, but controls -- and custom controls at that, only used by the 737NG (after the PMDG update providing the SDK). Just assign in FSUIPC to <custom control> and put the number in as the parameter. BTW usually, on all jets in FS, the fuel idle/cutoff levers are controlled by the FS Mixture controls -- i.e. Mixture1 lean/rich and Mixture2 lean/rich. Are you sure they don't work for the NGX? Pete

Well, yes, except that the crossover point does not HAVE to be in the middle -- that's determined by how you calibrate, i.e. where the lever is when you press the centre calibration points. You HAVE calibrated, haven't you? There are easy NUMBERED steps to calibration! Just follow them. If you want the whole axis range to be for forward thrust, with a small idle area near your "detent", then you need to check the "No reverse zone" (NRZ) option. Your "indent" is NOT part of the axis range at all, but a button! I think many Saitek users assign this button to "Throttle Decr", repeating whilst held, which will engage reverse, then "Throttle cut" when released, in order to regain idle. Pete

Did you intend "n\" to mean new line (which would be \n)? The escape character is \, not n. The letter 'n' is just the letter 'n', and "\ " would be just space I think. Pete

No registrations or settings are affected by installing new versions. WideClient.EXE is just that (only copy that file in), and even the FSUIPC installer only updates the program itself plus the documentation and examples. Pete

No! Do NOT enable all log options! Do not touch the Log options tab! EITHER assign a keypress to "List local panel vars", which as I said earlier is one of the added FSUIPC controls in the drop-down assignments list, then, each time you want to log the state of the LVars, just press that key, OR find the Lua plug-in called "log lvars.lua" in the Lua examples ZIP in your FSUIPC Documents folder, put that file in the Modules folder, and assign a key to "Lua log lvars" (if FS is running when you install the Lua file, prress the Reload button first to make FSUIPC rescan the files). The latter option is more useful as that will stay operating and log changes to the variables, whilst the former option will simply log all of them each time you press the key. The FSUIPC log file in in the Modules folder, next to the INI file, the DLL and the KEY file. ALL FSUIPC related files are ALWAYS there, no where else! Pete

Sorry, I cannot support Saitek hardware. There's a program called SPAD which might help. Pete

Sorry, I can't really help much with XML -- not my language at all. I think you are making it more compicated than you need to by looking there. Why not simply run the LVar logging as I suggested to see if the mode is stored in an LVar? If it is then I can help with a Lua plug-in to read it and update an offset. If it isn't then there's no way to do what you want, as I suggested might be the case. Pete

The source of the LIB is provided, though, and you can simply include that source in your own program if building a LIB is too complex (though I think it is only a matter of degining that as the output format, and possibly declaring the exports). The end result, in your program, will be the same. The code is included one way or the other. Regards Pete

I don't. I use MS Visual Studio 2003, 2005 and 2010, depending which programs I am compiling. But they are all possibly incompatible with that LIB as MS keep changing formats too. Pete

Sounds like the axis inputs interfere a bit, though I don't understand why if you are not moving them. I don't have motorised throttles, unfortunately, so i always advance them to the designated N1 whilst TO/GA is doing the same. All of the airliner cockpit videos i've seen show the pilots doing the same, even with mororised throttles (i.e. keeping their hand on the levers). you do NOT let go of the levers till AFTER V1, in case of RTO. Pete

Sorry, no idea. But LIB file formats are often different for different compiling systems. You will probably need to build your own, or simply include the source in your program. Everything is there, in the SDK. The LIB is just a convenience for those using Microsoft C/C++ -- and it may not even be compatible with all versions of that! Pete

There are no pre-defined offsets for transponder modes because there is no internal simulation of these inside FS. You'd need to find a way of detecting your add-on aircraft's transponder setting -- and there may not be a way, because, as on the default panels, it may simply be a cosmetic detail with no real effect other than on the graphic. If it does have an internal effect it might be in a local panel variable, or "L:Var". You can read those in Lua plug-ins. You can make FSUIPC log L:Vars for you -- see the drop-down control assignments list for buttons or keys. Or you can log them by running a Log LVars Lua plug-in provided in your FSUIPC Documents folder. Regards Pete

"Slope" you mean? Really not much use on throttles unless you want finer control at lower settings, for taxiing for example. Pete

I've read things about joysticks and Win8 which suggest that all is not well -- joysticks seem to disappear suddenly. This is only with Windows 8. Some folks have said that they fixed it by assigning in FSUIPC instead of directly in FS, but I really don't understand why they are disappearing in the first place, so I cannot guarantee that FSUIPC fixes anything. However, it does provide more options and facilities than FS itself. Regards Pete

Maybe others can advise. I don't use any Saitek devices myself. There are many Saitek users using FSUIPC satisfactorily, however. If no other Saitek users see your message here, I suggest you browse (search) some of the Saitek-related threads here, and maybe post on the FSX (or FS9?) forums on AVSIM, or the Saitek forum wherever that is. Saitek devices should really be at least usable "out of the box", so the latter is probably the first place to go. BTW you should probably have put "Saitek" into your thread title, to attract the right other users. Regards Pete