Pete Dowson

So the INI file with your settings, attached to your first post, wasn't the one actually in use! Durhh! No wonder we couldn't figure it out! 😞 Glad you finally discovered the error. 😉 Pete

Ah ... one is always learning! 😉 If it really is the FSUIPC blending which is occurring (and adrem has cast doubt on that), then just removing the calibration of the tiller in FSUIPC will do it, or you can adjust it for speed with the parameter as I said. I see Adrem is using FSUIPC6 whilst you are using FSUIPC 5.156. However, the coding in this area is actually identical, so at present I fail to understand how you have different results. Adrem has calibrated his Rudder and Tiller as follows: Rudder=-16380,-581,768,16380 SteeringTiller=-16380,165,512,16380 Yours is: Rudder=-16380,-512,512,16380 SteeringTiller=-16380,-512,512,16380/8 The values in the gasparr calibration are all default, so no actual calibration setting have been made -- apart from the option /8 which actually means "Direct" ... ... so, somehow, gasparr's assignment is known as a direct assignment. Apart from that choice in the Axis assignments tab, that occurs if it is assigned via an external application to specific offsets! So the plot thickens. I think we may need more inforamtion from gaspar. First, please gasparr delete that calibration line and try re-calibrating. Then see what happens and show us the INI file again. Pete

Hmm. I'd have to check that. But for a real airliner surely the rudder has no effect at taxi speeds? The tiller would always be used I thought. The blending action was implemented to provide more realism, and it was mainly in answer to user requests. The same action is more recently also provided in the cockpit system software I use (ProSim737). Pete

So if it works so well, why aren't you using it to taxi instead of the Rudder? I'm pretty sure FSUIPC hasn't changed. Maybe previously you hadn't calibrated the tiller in FSUIPC. Of course, in order to provide more realistic operation of the tiller and rudder on the ground! That's not really normal unless you are taxiing at speeds well above the maximum allowed. Why not use the tiller all the time until you need the rudder for takeoff? That's how it is designed and appreciated by most airliner flyers. If you don't want FSUIPC's blending at your "straight section" taxiing speeds, then either remove the calibration of the tiller from FSUIPC (which will disable the facility altogether), or decrease the MaxSteerSpeed parameter, so that the rudder takes over earlier instead of the tiller. However, either step seems very odd indeed to me. Removing the calibration won't change much as the values you've set (or left be) look pretty much default. OR, if you just want less sensitivity of the steering for the more gentle adjustments on straight sections you should consider flattening the slope in the centre (choose a suitable slop in the calibration tab). Pete

You are using the very first buggy release of FSX. The first thing you need to do is update it. There was an SP! release a few months later, then an SP2 about 18 months later (as far as I recall). I think both are still available on-line, so download and install the SP2 update. Then try again. If there's still a problem then, we need different information. You only supplied the Install log for FSUIPC, so it doesn't really help. You need to describe what you mean by "doesn't start", and also look in the Modules folder to see if FSUIPC made a Log file. If so, that is the log we need to see, not the Install log. If there is no log then you need to use the Event Viewer in Windows to see what might be responsible for crashing the sim. But update FSX first. Also make sure you are using the latest release of FSUIPC4. Unfortunately to cut the start off the Log so I can't tell which version you tried. Pete

Why? Why not the FSUIPC direct steering tiller like the others? When taxiing you need to use the steering tiller. That is what it is for. the rudder takes over at higher speeds, as on the take-off roll. Why have you got a tiller assigned if you want to use the rudder for steering? Rudders may be effective on light aircraft for steering assistance, but no way can they turn an airliner at low speeds. You have both tiller and rudder calibrated in FSUIPC, so FSUIPC cleverly balances the use of the tiller and rudder according to ground speed. The crossover speed is dictated by the MaxSteerSpeed in the Calibration section of the INI. You have that defaulted to 60, so at 30 knots GS on the ground the tiller and rudder have equal effect. The rudder takes over completely at 60. This is all described in the documentation. See the boxed section on page 34 in the User Guide, and for more details on the parameters involved, page 11 of the Advanced User's guide. There you will also find details of RudderBlendLowest. You didn't think of looking in FSUIPC documentation, though? 😞 The RudderBlendLowest affects the lowest speed when the blending of the two inputs starts. it defaults at 1 knot mainly so that you can check visually that the pedals move the rudder before setting off -- i.e when static. As soon as you start moving you don't want the rudder steering until you are over normal taxiing speeds. So, it isn't a "problem", it is exactly as designed -- to make things more realistic. I don't understand. What is your tiller assignment for, then? Why is is assigned for the FSL profile and calibrated if you don't want to use it? If you aren't using the tiller then the best I can suggest is that you simply delete both the assignment and the calibration, and find another use for that axis. Just delete these lines in your INI: 3=1R,256,F,66818,0,0,0 -{ TO SIM: STEERING_SET }- and SteeringTiller=-16380,-512,512,16380/8 Pete

I don't know that program, but the official ways to monitor offsets are: 1. Use the built-in Logging, via the Monitor facility on the right hand side of that options tab. 2. Use the utulity FSInterrogate2, which although a little more complicated to use is very feature-rich. Pete

The INI file actually has nothing at all to do with registration. It contains the settings you make, but no registration details. The explanation must only be that you made a slight error in entering the Registration details the first time. All three parts -- name, email and key -- must be correct. Best always to cut and paste to avoid errors. Pete

Ah, flaps calibration -- that was the entry you removed (same as pressing "Reset" on the Flaps entry in the FSUIPC calibration tab). The axis input from FSUIPC was presumably coonflicting with the setting in the PMDG aircraft. Most axes are read directly by PMDG aircraft and so, if you calibrate in FSUIPC, there are two possibly conflicting values getting into the Sim -- one from FSUIPC and one from PMDG. This is a pretty well known thing with PMDG aircraft, but mainly with the main flight controls. I think most folks use the Flaps Inc and Dec controls rather than an axis. Pete

Yes, but if your "PTT" (Push to Talk) button is on a joystick connected to the Simulator then you need to do some assignments and settings to enable it to broadcast correctly. There is help for this on the Pilot2ATC support forum. Pete

I see Thomas replied just before me. Thanks Thomas. Just adding to this: I use Pilot2ATC quite happily on a WideFS client PC. I like it that way because the sound from it is directed to different speakers, or my headset, and of course the speech recognisition is easier to get set up and running well on a spearate PC to the Sim. BTW the Server is the one which needs registration, not the Client, and it has it's own log called "WideServer.log". There's always two ends to a connection! 😉 Pete

Autosave merely calls the SimConnect function to save a flight. Nothing else. The action then is exactly the same as when you save a flight manually, for example by using the ; keypress and entering a name for the flight. PMDG aircraft are programmed to detect the saving of a flight and freeze the performance temporarily whilst collecting the data relating to the aircraft state. Sometimes folks report that this causes a slight hesitation. Of course it should not actually change any of the values being collected. If it is doing this then it is a bug in the PMDG code and should certainly be reported. Pete

If you are using a method that has to invoke a control to change a dial or value in a gauge, this is because the updates are flowing too fast and a queue has built up. For a dial or gauge in a cockpit there are usually better ways. If you have direct control over the local cockpit display, then make the increments there, NOT updating the Sim until there's a pause in the rotation of the encoder. Then write the value reached. The pause need not be very long - eg 1/2 second maybe. I've used this method in cockpit display drivers for many years. I'd need to know a lot more about exactly what you are doing to even have a guess at that. Pete

Correct, though it isn't a "backup". All of FSUIPC5's settings are in the FSUIPC5.INI file, in the Modules folder. There is no relation at all between FSUIPC settings and P3D settings. It is up to you to make a backup for safety, by copying the file and any Lua plug-ins, Profile files and macro files from the Modules folder to a backup place of your choosing. By resorting to default P3D settings you have probably re-enabled all of its controllers and the resulting default P3D assignments would interfere with any joystick settings you made in FSUIPC. You'll need to go into P3D and disable controlers (again). Pete

Before your query I had never heard of such a facility. Looking through the Controls list I do see it, but I've never used it. The controls list, for assignment, is generated automatically by requesting the list from the Sim. Whilst FSUIPC does add a few of its own (as listed near the end of the Advanced User's document), it isn't responsible for the built in ones, nor their names. As an FS control that one is simply sent to P3D for it to deal with. If there's any way to make the text size larger then it will be in P3D settings somewhere. However, I suspect that the only way would be to make text size larger in Windows' settings (eg. 100% to 150%), but this depends on whether P3D is generating its own font for those labels, or using standard Windows facilities. I think the Windows scaling facility does affect menus and so on. Pete

No. Those offsets are solely under control of the application -- FSUIPC only scans them to flag keypress occurrences. Pete

What dd you try? Did you look in the documentation for mouse macros? There's a section in the FSUIPC for Advanced Users document, a whole section on Mouse Macros. On page 38 there's the list of mouse actions: 1 Right single click 2 Middle single click` 3 Left single click 4 Right double click 5 Middle double click 6 Left double click 7 Right button & drag 8 Middlebutton & drag 9 Left button & drag 10 Move 11 Right elease 12 Middle release 13 Left release 14 Wheel up 15 Wheel down 16 Leave 17 Count In your macro line: you can see that the "3" means left single click. The list shows 13 as "left release", so you just needed 11=AP Up release=RX400000b9,13 or similar (your choice of name). If line 11 is already used just pick a free number. I suppose you tried assigning to the normal FS controls first? Much easier if they work: AP ALT VAR INC AP ALT VAR DEC Pete

You buy it on SimMarket. Just search for FSUIPC4. Pete

So on this joystick you are trying to program a button to do this? So you want button press to be assigned to that mouse button being pressed and button release to the same mouse button being released? Is that correct? If so, then in your macro file duplicate the line you have with a different line number and name, and change the mouse action code at the end to a 'release' instead of a press. Then program the first to your button press and the second to your button release. As I said, mouse macros are there to try to duplicate the actions of the mouse with a button or keypress. But when creating the macro in the first place it is only told about the first mouse action, which is the press. What you call a "clcik" is a press and release. When asking for support it is always quicker to provide as much information as possible right at the beginning to avoid us having to keep asking questions to find out what it is you want to do and with what. Pete

How do you do it on screen, with the mouse? By "keystroke" do you mean button press and release? Or are you programming your joystick to send keystrokes? Pete

You need hardware and some sort of programmed interface to drive an LED. If you can determine what conditions you deem a 'crash' and find suitable values in the FSUIPC offsets list, then you can get your harware driving software to read it and operate the LED. If you are not a programmer I assume you have already supplied software for your LED? There is of course offset 0840 which is the 'crashed' flag. that shows when the Sim itself detects a crash. Otherwise for a landing hard enough to be possibly deemed a 'crash' i think the relevant offsets to check are 11B8 (as Thomas suggested) and 030C (vertical speed). I have one of those somewhere but I don't remember how to program one. But it should do the job, and from offsets. Pete

I assume you are talking about a mouse macro? Made in which flight sim and for which aircraft? Aslo your question seems to have a self-contradiction in it. you want the button to 2bounce back" but "stay pressed". How can it do both at the same time? In P3D4 or 5 the mouse macro records whatever it is you do with the mouse. So, left click, right click, whatever. With earlier Flight Sims you usually have to experiment with the mouse action codes (they are listed in the Advanced Users guide). But not knowing what you are trying to replicate, nor in what or for what it is difficult to advise further. Pete

You should really read the offsets list as I just did. For 3210 it says: 56 DWORDs containing zero (when free for use), or a Hot Key specification. Notice that zero (when free for use)? There are 56 DWORDs starting at 3210. You must scan them to find a zero one which you can use. Other applications or plug-ins may be using others. THEN, you can write the specification of the key you want detected. Well, 0x42 is 'B', but how do you work out that 0x08 is bit 4? Bit 4 = 2^4 = 16 = 0x10. If you do not understand hexadecimal and bits please see this thread in the FAQ subforum: About bits, numbers and hexadecimal Probably because of your error above. But don't forget the offset address will be whatever slot you found empty and so used + 3, not necessarily 0x3213. Best to keep a note of it. Also after detecting it remember to write zero to that byte offset so it can be triggered again. Pete

Assuming users haven't made their own assignments or changes in the Sim's key assignments, there are plenty of combinations of Ctrl + Shift + another which aren't defaulted in the Sim. The only problem with the choice of TAB + G was that TAB isn't used as a shift key in the Sim. I don't remember details of the 3210 method, but they are documented and i can look them up. But it would be better for you to ask specific questions about things you don't understand than for me to basically write the code for you. Pete

The HotKeys dialog is not the one you should be compaing it with. That's just for special actions. They general Keys assignment tab is the one you should have used, as I said. The FSIOPC HotKeys are trated completely differently. Anyway, I've had a quick look and the Lua key event has always worked at just detecting the key presses not trapping them. So that's many years with no problem. I'll discuss it with John (who has taken over onward development from me), but my personal opinion is that it should stay as it is, as it was designed to be. If it were to be changed I think it would have to be an option, enabled by a special [General] parameter in the INI file. And it would only apply to current versions of FSUIPC (6 and maybe 5). Surely it would be better to just use keys not assigned in the Sim by default. Ctrl+G, Shift+G, Shift+Ctrl+G are okay. The "TAB" in "TAB+G" isn't counted as a shift by the Sim, so it will treat it as a TAB press and a G press. Pete