Pete Dowson

THREAD MOVED FROM "USER CONTRIBUTIONS" SUBFORUM FOR ATTENTION Please note that your post is a support question, but you posted it as a "contribution" as if were useful to others as it is. Please ALWAYS post support questions to the Support Forum! The problem is that the sim really does not provide a brake you can lock on like that, other than the parking brake, so you'd have to assign it to the parking brake. But you say: And why is that? Surely you remove thrust before applying the parking brake? The toe brakes don't apply any more brake pressure than the parking brake. In most aircraft they are the same -- the parking brake merely holds the same brakes on. "Backing up"? Are you setting reverse thrust for some reason? Why would it "back up"? Surely you aren't parking on a slope? You must have the throttle too high. Most aircraft, and especially airliners line the 737, only need any significant amount of thrust to start moving. After that you can taxi around pretty much at idle thrust, with perhaps a little nudge after slowing for corners. I think you just need to sort your use of the controls you have. The PMDG 737NGX behaves almost perfectly with good control. If you want suggestions for using your NGX I think you need to go to the PMDG forum for that aircraft. Pete

That's okay. It is likely the GUIDs have changed. You could simply delete the numerical assignment lines in the [JoyNames] section in your FSUIPC INI file, and let FSUIPC re-generate them, but I see you aren't using JoyLetters (really a big mistake with so many devices), so you'd then get problems with everything assigned to the wrong devices by numerical ID. So, instead, show me the same files as before again so I can see what is now different.Then I would be able to advise on settings to change in the JoyNames section. BTW, best with those files is to attach them rather than paste them into the message proper. You can paste them in, but in that case please use the <> button above the edit area and paste them into the window you then get. Pete

There's no link to a g version in that thread, on a mention in July that is was availbable! It hasn't been available since a week or so after it was first released! Here you said you were running P3D4.1: but the Log proves you still have 4.0 installed: Prepar3D.exe version = 4.0.28.21686 Checking the Registrations now ... User Name="Bert Groner" User Addr="bert.groner@fsmagazin.de" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 05/12/2017 11:34:56 0 FLT path = "C:\Users\Bert Groner\Documents\Prepar3D v4 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 4.0.28.21686 0 api.dll: 4.0.28.21686 0 controls.dll: 4.0.28.21686 0 fs-traffic.dll: 4.0.28.21686 0 G3D.dll: 4.0.28.21686 0 language.dll: 4.0.28.21686 0 sim1.dll: 4.0.28.21686 0 visualfx.dll: 4.0.28.21686 0 weather.dll: 4.0.28.21686 0 window.dll: 4.0.28.21686 That is why you are getting the crash. As is made clear in several places, FSUIPC 5.122 is NOT compatible with 4.0, you must update your P3D! Pete

What version of FSUIPC did you install? It should be 5.122. If earlier than that please update and try again. Otherwise, was any FSUIPC5.LOG file produced? If so please show it to me. Sorry, what "g" version? The only "g" version of FSUIPC5 ever supplied was 5.103g in July, 5 months ago, and well before 4.1 was released. And no such version is now downloadable from this site! If there are "CTD"s (crashes) there will be crash reports in Windows. Please show me the details from those. You can find them in Windows Event Viewer. Pete

That is typical of the results of that Registry problem, I've found. And with them all being identical, they are identified in the order to connect them and assigned their unique GUID accordingly, via the list in the Registry. If you only connect 1 or 2 quadrants, is one lever still acting this way? I notice that you are still using a very early version of FSUIPC5, one which certainly wasn't made for P3D4.1. It won't make any difference to this problem, but please do update. The correct version for P3D4.1 is 5.122. The logs you submit suggest there's only 2 of the 3 Quadrants being recognised, thus Is that the case too when one of the levers gives this odd result? Otherwise, the logs show everything to be fine. The FSUIPC Joycan is working exactly as intended. The fact that the Raw value is the same means that it isn't FSUIPC which is getting the values wrong, but definitely the way they are arriving through the Windows joystick driver. It is possible to read joystick inputs directly via the USB interface. This is used for other HID devices, where the Windows joystick interface cannot cope, and FSUIPC can handle this but currently it depends on the Windows joystick interface which is intended for the purpose. This does make it susceptible to registry entries dictating weird or incorrect calibration values or modes. Saitek installation seems very prone indeed to this happening. The only reason I can think of that it is not happening in P3D is that you have its "direct" mode enabled for joysticks. I think that by-passes the Joystick interface and goes direct to the USB interface. However, I ddn't think FSX did this or had such an option. Anyway, I think the answer is definitely to follow the advice in that FAQ thread I referred you to earlier. Please do that and let me know. Pete

MOVED TO THE SUPPORT FORUM FOR ATTENTION! Please always post questions and support requests to the support forum, otherwise it may not be answered. GAUgue files written in C/c++ rather than XML are just DLLs which are loaded with the aircraft rather than at the start of a session. And many such in add-on aircraft used to use FSUIPC for access to assorted internal sim variables in FS9 days and before. There are still some add-on DLL and GAUges which do, but not many these days with SimConnect being the more direct route which also does not require another 3rd party addition. But nowadays, when 99% of everything FSUIPC offers actualy being accomplished through Simconnect in any case, any new such add-in would really be better off going direct to SimConnect. However, the FSUIPC SDK does still contain a section for module Users of the its interface. For many users a much easier solution is simply to use Lua plug-ins, which also run internally -- if running internally is the important thing. In that case it definitely isn't a good idea to try implementing a module for either FSUIPC or SimConnect. Best look at Lua, which is intended to be an easy-to-use scripting lanaguage, a sort of one-up over a CFG or INI parameter file. But LabView is presumably running as a separate process, so the DLL calls you make also operate in that process. Calling things in a separate process is an entirely different kettle of fish. Pete

That symptom is normally related to having the "mode" of the axis defined as "digital" in the Regsitry. Is this with just one axis or all three? No idea, though, why it doesn't affect FSX or P3D. They also read the axis values in the same way. A few things to check though: 1. See what you get if you select "raw". That makes it report the real hardware value, not the one processed by Windows' "Game Controllers" calibration. 2. See this in the FAQ subforum: Anyway, I also need to see your FSUIPC INI file, the LOG, and the file called FSUIPC Joyscan.csv. Pete

Why not? How did you get 4.0? You need to keep P3D up to date, it is being developed all the time and many add-ons will change to suit. [LATER] If the size of the full release is the problem, just download the Client installer. That's only 201Mb, far less than another FSUIPC Install package! Pete

If you need a keystroke for the G1000 and the MFD can be set to send keystrokes, what would you want to assign in FSUIPC for? Keystroke converted to keystrokes? What's the point of that? Just assign one to the other. So, there's something wrong with the MFD sodtware, surely? Since it was custom build and interfaces to USB, why doesn't it provide standard button presses in any case? I'm not sure of the relevance of your mention of the network to all this. How are the keystreokes fetting from one to the other in any case? Oh, I see! Didn't you refer to the WideFS documentation at all? Look up "KeySend". Pete

"Axis throttleN set" I assume you mean? And, yes, there are a number of aircraft which don't work with the older controls which FSUIPC's "direct" mode uses. I presume the value it sets is insufficient. Can you check the actual value being set when you operate the throttle on screen (by mouse or whatever)? Just use the axis event logging option in FSUIPC's Logging Tab -- you can enable the Console log and temporarily run P3D in Windowed mode so you can see the changes in real time, on screen. Then compare with what is being sent by your controls. That's because the calibration converts the controls to the older ones, so it's actually the same as the assignment restriction. In order to make it use the newer controls, provided you are using the "no reverse zone" option, set "UseAxisControlsForNRZ=Yes" in the relevant Calibration section of the FSUIPC5 INI file. you can do this whilst P3D is running, then just go to the Calibration tab and select the Reload button. Note that this only applies to "no reverse zone" mode because the newer controls don't provide a reverse range at all. If this doesn't work, then, provided you only want specific throttle values to be set, you can use the right-hand side of the assignment, instead of the left, and have zones calibrated there which send specific values, using the same controls but with a specific numerical parameter value for the position. You'd need first to use the logging again to determine what values fit each notch correctly. Pete

This was if you are starting from scratch, just a precaution so that the rest of those instructions make sense! If you delete it you lose ALL of your settings made to that time! That is what you want to happen if you are in a mess and want to start again! How is it applicable here, to you? If it is, go ahead, but don't expect either P3D or FSUIPC to rebuild all your settings again. You have to do that yourself! BTW that Appendix was a contribution from a user (Peter Hayes) trying to help folks who somehow got into a mess, or don't understand what they are doing. Pete

Yes, thank you. What you say is very interesting indeed! Pete

Yes, but everything 'below' idle 9i.e nearer to you) is reverse. Well, if the calibration shows the "no reverse zone" unchecked, and the OUT value going negative, then FSUIPC is definitely telling the sim to engage reverse. Some add-on aircraft implementations don't provide an axis-settable reverse, and for those the only way tou can engage it is be sending "throttle decr" controls instead (like F2 on the keyboard). But I think you said you were talking about turbo props. Don't they implement reverse by altering the prop pitch to blow the air the other way? I didn't think they had a verses like a jet, with a cowling coming down to redirect the air flow. Maybe you want prop pitch, not throttle control? Pete

As well as what Thomas said, I think you should find that DLL.XML file, as the most likely thing is that the one which FSUIPC added itself to was corrupted in some way. Why did you "uninstall and reinstall P3D"? What were you trying to do by that? I presume when you did it you didn't delete the DLL.XML file or other P3D settings, so using the old ones still? Pete

Wherever you want the normal idle to be! It doesn't matter where. Just be sure to set a small zone around it in case of slight variation (temperature, etc). Not sure where you read something so odd. FSUIPC's INI file is nothing to do with P3D. Nothing can re-build it if you delete it -- next time FSUIPC runs it will make a default one, with none of your settings at all! Pete

PLEASE NEVER POST SUPPORT QUESTIONS INTO A REFERENCE SUBFORUM! Always post them here, the Support Forum! I have moved it for you, else it will never be answered! Anyway, sorry, but such crashes are completely unrelated to FSUIPC. You need to look elsewhere. And crashes with "uiautomationcore.dll" were very frequent some time back and are due, I think (though my memory may be failing here) to a video Driver installing an incompatible version of that DLL into Windows. Do a search on the FSX Forum over in Avsim using the DLL name as key. I think they gave the version number of the best version of that DLL you need. Pete

Yes, it is. Pete

Well, you have something else going on then. See if you can operate rudder from keyboard. I am moving this thread to the FSUIPC support forum because you posted in the Programming Support forum for users of Paul Henty's DLL. I don't understand why you did that, but I'm moving it in any case ... Pete

Well, they are usually not included here, in P3D4. They seem to be much more reliably included if they are loaded at the start-up menu, not via the "go to airport" menu entry. Pete

Sorry, I don't recognise this message. Did you run the Installer "as administrator" as instructed? Can you describe what you are actually doing? And isn't there a Window showing the activities being undertaken? And see if there is an Install Log file. That would be more useful. Pete

did oyu not even try using the forum Search faciklity? i did and found it directly, here: Pete

Uncheck the FS or P3D option for "auto-rudder"! Pete

I don't think their email address accepts incoming emails, or at least it won't be read in any case. You need to raise what they call a "problem ticket". Pete

Well, currently I only subscribe to the one, so that's not really the case. I have got both DoveTail and L-M looking at it, probably at quite a low priority (after all, it's been like this since the function was added in FSX-SP2). But I'll keep track of it. Even if L-M do fix it, I think it will be for P3D4 only. I doubt whether they'll do anything more now with P3D3. Pete

You'll have to go into your account (one of your evidently TWO accounts) with SimMarket, point out and apologise for your mistake, and ask if they can re-issue a registration in the other name. Hopefully, Simmarket will help. Pete