Pete Dowson

I'm afraid I am not well up on aviation GPS units, but let's see ... The functions you see listed for GPS in FSUIPC's assignment dropdowns are merely those listed in FS's "CONTROLS.DLL" module. Most of those can also be assigned in FS itself. FSUIPC presents the complete list, but that may include ones that Microsoft never got around to implementing or testing. FSUIPC cannot make a button/switch work which doesn't work using the correct FS controls. Not unless it is susceptible to "mouse macro" methods, which is unlikely Which aircraft has Garmin GNS 530 and GNS 430 installed? Are you using FS9 (you don't say). The FS9 GPS I can find doesn't look like your picture, and doesn't appear to have a power switch or button. I am using FSX which has a Garmin G1000 as well as a 500 like FS9, and the power for that is the Avionics power switch, I think. There doesn't appear to be a power button on it. If you are talking about addon GPS panels I think you need to refer to their documentation or visit their support forum. By all means try mouse macros. How do you make the rest of the buttons work? Regards Pete

"We oldies"? I'm 69 tomorrow. Does that make me a "Youngie"? ;-) Pete

How have you assigned the flaps axis? This is actually starting to sound like the Saitek problem which needs a Registry fix. Have you calibrated the levers in Windows' "Game Controllers" at all? Does it show full movement there? Because it seems the entire problem is that your flaps lever simply is not providing a full range of values. Well I cannot find any problem with P3D's flaps axis, nor the discrete controls, here. They all work as expected, and as in 1.3 and before. The fact that when you had discrete controls assigned, as in the INI you showed me, you had a similar problem indicates that it cannot be P3D's axis inputs at fault, but the values provided by your lever. Why that should be different in FSX and 1.3 I don't understand, unless there are other differences you aren't telling me. See if a flaps axis assignment to another lever works. Pete

You never assigned axes in FSUIPC? Wow! That's the first thing most users do and what they purchased it for. I don't understand how you got into such a complex way of trying to control the flaps first before doing a simple assignment! The use of separate ranges on an axis to send separate discrete controls is really very advanced and hardly ever used except by experts, so I naturally assumed you knew what you were doing. Please, just delete the [Axes] section for now, go into P3D's controls and assign your axis to the Flaps control. Probably check the reverse option, befause full flaps is towards you unlike full throttle which is away from you. That's really all you need to do. The separate notched methods are really only useful if your lever realy does have notches, but then it is really related to only aircraft with that number of flaps positions. Regards Pete

You can read the Flaps details on the Flaps calibration page of FSUIPC's options dialogue. Please check. What is there is what is supplied by FS. If the aircraft coding in an add-on does its own thing then there is no way for FSUIPC to get such information. You'll have to experiment. Pete

That's an odd way of providing just this bit of information, which is the only relevant part:(to which I've added annotations): [Axes] 0=0U,256 1=0U,B,12544,16383,65595,0 ; Flaps Up (same as F5) 2=0U,B,5888,12544,65597,0 ; Flaps 1 3=0U,B,-2601,5888,65599,0 ; Flaps 2 4=0U,B,-11052,-2601,65601,0 ; Flaps 3 5=0U,B,-16384,-11052,65603,0 ; Flaps Down (same as F) [/CODE] You have no other axis assignments, no calibrations, nothing? You reported that there was a problem with the Flaps Axis, but in fact you are not even using[i] any [/i]Flaps[i] Axis[/i], only descrete controls! I hope you explained this in your report to L-M because they will assume that by Axis you meant Axis! And where you say "only moves between positions 2 and 3" do you mean it only obeys the Flaps 2 and Flaps 3 controls, not the Flaps Up, Flaps 1 and Flaps Down controls? Excepting flaps 1, which presumably may be faulty in 1.4, I find that very difficult to believe -- but I'm testing it now. If Flaps Up and Flaps Down don't work there'd surely be an uproar! May I ask why you are using this strange method of flaps control? I've never used the Flaps 1/2/3 controls and have no idea what they achieve. For instance if there ar 9 flap positions, which are those? What if, like on the Cessna and many of the P3D defaults there are only 4 or even 3 positions? Why not use the Flaps axis assignment and calibrate the detentes (if you have them) in FSUIPC? Why such a difficult method which is harldy appplicable to many aircraft? [LATER] All 5 controls you are using work fine here. I pasted your exact [Axes] section into my INI file and tested with a Saitek Throttle Quadrant. I dn't know which of the default aircraft in P3D provide the 5 flap positions you are assuming, so I installed the FSX 738. My flaps lever easily and correctly selected Flaps up, Flaps 1=1 degree, Flaps 2 = 2 degrees, Flaps 3 = 5 degrees and Flaps down = 40 degrees. So, I think you have something else wrong -- probably a conflicting axis assignment in P3D itself. You evidently have not turned off P3D's controllers otherwise the rest of yout yoke wouldn't be of use (you haven't assigned in FSUIPC). If you don't turn off FS assignments they will occur automatically, as they do in FSX. If you are still doubtful or confused, enable FSUIPC's event logging, operate the lever, and check the log. That may show you what is happening. Pete

I don't think FSUIPC being "unloaded" is an FSUIPC crash. If your Concorde is causing a CTD you need to report it to FSL support. What, in FSUIPC? Haven't you ever used FSUIPC calibration? You can calibrate as you please and control the sensitivity across the entire range using slopes. What else could possibly be needed? Please do refer to the documentation. This is nothing to do with FSUIPC! Why not refer to FS documentation? You can reassign Shift+P and Shift+Z if you like -- they ARE the default "hot keys". Or maybe you really mean FS control names or numbers? If you want to relate an FS action to a named control, just enable Event logging in FSUIPC, operate the action, and refer to the Log file where the FS control name ad number will be shown. Or simply look up the control in the list of controls provided in your FSUIPC documents sub-folder! Pete

Rather than wait on L-M I purchased an "Academic" license so I could test. I'll be making some changes to make things like wind smoothing work again, but with 4.851 installed I cannot make anything go wrong with the flaps axis. I've tested all three methods of assignment -- Axis Flaps Set, Flaps Set, and direct to FSUIPC calibration. So perhaps you should show me exactly what you've done (the Axes and JoystickCalibration parts of the INI file) and which aircraft you are trying it with, please. Regards Pete

Neither really work correctly with P3D 1.4. I'll be releasing version 4.852 tomorrow (Sunday) which is tested okay with 1.4. I actually paid for a copy of P3D rather than wait to get in touch with whoever has replaced John Nicol. I don't actually use P3D -- my FSX installation is running far too well for any changeover at present. There's no way FSUIPC4 should ever be used with a version of FS it hasn't been written for. There are too many hooks in it which depend on inner structures and code positions. I do try to make it fail-safe rather than crash, but that doesn't mean it is working correctly. I didn't know about 1.4 until yesterday. I think a two day delay isn't bad. If and when version 2 of P3D comes out, I would expect it to take me a good bit longer! Pete

Whilst a different email address is allowed for wideFs, the name must be identical. You should really have read the details before purchase. Now the only way is to raise a problem ticket with SimMarket and explain your predicament. Regards Pete

Maybe they only accept flaps INC and DEC, or the old Cessna type 4 flap position settings. I assume you can operate them with the keyboard or mouse? Just enable Event logging in FSUIPC's Logging tab and look at the Log after using the relevant flaps controls. Pete

Thanks! Pete

P3D is still in development, unlike FSX. Report all bugs in their Support Forum with full information (NOT the FSUIPC log which isn't relevant -- they need the Windows crash data). They have to fix bugs in P3D, not I! Pete

I'm surprised FSUIPC works at all with 1.4. The first I heard about it was yesterday. As stated in the documentation, FSUIPC4 works with P3D up to 1.3. As far as I can see from the details of the changes in 1.4, the only G3D.DLL crash that FSUIPC4 patches is the one they say they've fixed. They certainly should have fixed it as I provided them full details a while back. However, there are lots of other G3D.DLL crashes which FSUIPC4 never patched and cannot patch. It only did the most common one as they turned out to be easiest. I'll release a version of FSUIPC4 for P3D 1.4 soon, but I don't think it will fix any additional G3D crashes. The current version is 4.851 in any case -- you are out of date and unsupported. Regards Pete

All the "_SET" controls set a given value, though sometimes it is only a 0 for Off and 1 for On. The Axis_XXXX_Set controls are the current axis controls as used by FS itself. the axis controls without a preceding "Axis_" are old ones, dating back to FS98 or before. For most things both work fine. The Axis controls have parameter values from -16383 to +16383, but they don't have reverse thrust, reverse prop and so on. The non-"Axis_" axis controls either run from 0 to 16383, or, where there is a reverse (throttle, props) use a negative value for reverse (eg down to -4096 for an aircraft defined with max 25% reverse thrust). Yes, for the "Flaps_Set" control (-16k to +16k for the axis one), but a flaps control with detentes will move to the nearest actual detente value. You'd have to adjust if you have detentes on your lever. If it is just continuous just move to to get what you want. There is an offset providing the number of detentes and the write up tells you the computation. Be aware though that the PMDG 737NGX detentes aren't quite in the place computed, unlike the defaults. You will have to check which of the controls (Axis_ or otherwise) works with the aircraft you want to use. If they are intercepting controls, they may only work with the newer ones (Axis_ ...). Pete

You write the parameter for the control (eg axis value) to 3114 then the control number to 3110. Look up the control numbers in the List of Controls installed in your FSUIPC Documents folder. The controls added by FSUIPC are listed in the Advanced User's guide. Surely you can easily look up the value of the Axis Flaps Set or Flaps Set controls yourself! Please do try! It isn't hard -- there's an alphabetically ordered list and a Numerically ordered list! If you are doing all this as a Lua plug-in you don't need to use offset 3110 to send controls, just use the ipc.control function. But you still need to look up the value of the control. Pete

The FSUIPC offsets listed in the FSUIPC SDK are all related to FS functions. Many of the more complex add-on aircraft do their own thing for several, and in some cases, most of the subsystems. I'm surprised you have managed so well that you have only a few omissions, expecially with the PMDG aircraft. One thing for those specific functions would be to try sending the appropriate Axis controls instead of trying to control directly via offsets. This is because their actions are likely to be determined by the state of other subsystems which are being simulated specifically. The add-on code often intercepts the controls you'd normally assign via FS or FSUIPC and interprets it accordingly. You can use offset 3110 to send FS controls. The PMDG 737NGX also has a vast number of its own add-on controls -- see the Header file in the SDK installed with their recent update. You might also benefit from checking the assorted user contributions for these aircraft -- see the User Contributions subforum. Regards Pete

Which are unlikely to make any difference if it was okay in 1.3. As I said, please also test the flaps axis with P3D assignment and if wrong report it to L-M. I won't be able to fix P3D bugs. Regards Pete

I only just heard of P3D 1.4 yesterday. I've downloaded it and will install it over the next days and try to make FSUIPC4 work with it. There are lots of things in FSUIPC which are very dependent on specific code in FS and I'm rather surprised much works at all as it is. I cannot support versions of P3D at the date of release because, unlike Microsoft, L-M do not provide me with pre-releases. In fact I've not even got a license since John Nicol left L-M.. However, that said I have never seen any change in the normal controls since FSX SP2, even through ESP and P3D versions 1.0 to 1.3, and the code in FSUIPC4 is identical for all, so it actually sounds as if L-M have introduced a new bug in 1.4. I suggest you submit details on their Support Forum and see what they say. (Test with Flaps axis assigned in P3D too, to be sure). BTW the current version of FSUIPC4 is 4.851. Regards Pete

In that case the "old annoyance" should vanish if you used the Flaps Set control with appropriate parameters as I suggested. The syntax is wrong. Try 21=CP(F+0,10)0,4,C65698,9365 ; not commas, not points, and (F+0,10) Do the flaps move at all? If so, where to? Don't forget the offset 0BE0 read-out (from which you derived the 9635) does not correspond to the control values you need to send -- the read-out is related to the angle, I think, whilst the control relates to lever positions. See where the flaps go to and adjust accordingly. Try 8192 for example. If it doesn't move at all with values other than 16383 and 0 then the implementer of the aircraft has evidently done some very strange programming and is avoiding the FS methods altogether. You would need to check Flag 0,31 was not set in any case: 21=CP(F+0,10)(F-0,31)0,4,C65698,9365 Best to do this instead: 22=CP(F+0,10)(F-0,31)0,4,C1003,31 Both values 0 and 16383 do the same thing? That's very weird! I am very confused by the implementation. Does the author have any explanation? Regards Pete

I think the GPWS calls are all built into PM. Are you only using pmSounds and none of the PM modules, perhaps? I'm not sure which of the PM offsets each of the sounds are linked to. Maybe PMsystems? PM offsets are listed in documents provided by PM on the PM site. FS / FSUIPC offsets are listed in the documents in the FSUIPC SDK. PMDG 737NGX offsets are listed in a document installed into the FSUIPC Documents folder if your FSUIPC is up to date. Regards Pete

I don't think there are any specifically "PMsounds offsets". PM sounds are either triggered by changes it recognises itself (those in the INI file) or by offsets you choose yourself from those available, whether FSUIPC default ones or PM modules (the SoundList file). Regards Pete

Try 4.85 or 4.851, rather, now, without the loader (just rename the loader and re-run the Installer). The other changes I made to FSUIPC4 initialisation may help. Let me know if it does. The problem I've been trying to fix is really more related to the trust checking which once done for a new version is not done again unless you remove the "trust" entry in the FSX.CFG file. Regards Pete

Try version 4.851, now available. Pete

Try 4.851, now available. Pete