Pete Dowson

No, sorry. AI traffic reloading normally happens if the FS time is being changed by more than one minute. Are you running something which changes the time, like FSRealTime, or the sync option in FSUIPC? Using a heavy aircraft (heavy on performance) like the PMDG 747 may be making sim time run a bit slower than real time and causing more time corrections. Certainly using time multipliers won't help. I'm afraid I can't help at all with Vpilot. The thread title talks about a CTD, but you don't mention a crash at all. Pete

3 buttons, or one button? For just one you can do it in one of three ways: 1. Adapt the Lua plug-in provided in your FSUIPC Documents folder called "tripleuse" so that a single press sends one of those, a double press sends another, and a single long press sends the third. 2. If that's not quite what you had in mind, if can use button flags. But this is complicated when you want 3 conditions (much easier when it is just a choice of 2). So , instead, move on to: 3. Select a free user offset, like the Byte at 66C0. You'll need the three assignments to the same button, one for each of your three values, but each with an offset condition 66C0=n. with n going 0, 1, 2. There's an example of this in the Advanced User's guide, on page 20 or so (search for B66C0=0). That example uses a different button to make the selection between 4 assignments, but you can do it with one button only by moving the first line (the one with the offset cyclic increment code in it) to the end and changing it to the same button. Of course, for cycling 0-2 instead of 3 you change that x00030001 in the parameters to x00020001 Pete

The bits in the result are the flags used in Windows. The values aren't treated explicitly by FSUIPC. I think it works the same either way, with or without that bit, but it was defined that way in the Windows programming references at the time. Things in Windows changed over the years, but i like to keep FSUIPC compatible with its user applications rather than force changes with new versions of FS or Windows. It all started in the days of Windows 95 and Windows 98. FSUIPC was a continuation of Adam Szofran's FS5IPC which was for FSW95 (FS5) and FS6IPC for FS98 (FS6). FSUIPC (U = Universal0 has worked with the same interfaces since Win98 times, through FS2000 (FS7), FS2002 (FS8) and FS2004 (FS9). Expanded, yes, but what was there already has continuity throughout. Not just strange, but annoying, especially at the time when I realised this difference -- too late. The interface into Windows is different -- one derives from arriving Windows message flags, the other are bits defined for a keyboard emulator. You could blame different arms of Microsoft not talking I suppose, but certainly I could have shifted the bits around internally before checking / sending them. It was too late after applications had been written to use them. Also, for 90%+ of users it doesn't matter as both assignments to and from keypresses are more normally done using the Options dialogue, where you don't need to see the technical data in the INI file. Pete

As well as using Profiles for automatically selecting one or the other according to the aircraft loaded, you can also leave them both connected and assigned all the time. Folks with both Captain and First Officer controls do this. If they are both assigned in FSUIPC, then the input with the biggest diversion from "centred" will be the control invoked at that time. If you do this it is best to have a well defined central "null" zone so that no input is given from either when hands are off both. Also, don't disconnect either at all, as then its driver can send spurious values, usually at one extreme or the other. Pete

Really. Oh, sorry, I certainly didn't notice. might have been a good idea to start a new thread then? The 15 year old facility was the "KeySend" for WideFs, which you say is now irrelevant!! On your other point here, one is talking about the encoding for how FSUIPC DETECTS keypresses for assigning to controls, the other is about ASSIGNING keypresses to controls to send to FS. They are both described and documented correctly in their respective sections. All you need to do if refer to the correct section for whatever it is you want to do. Pete

Okay. This has occurred before. There's a thread somewhere. I think it turned out to be a registry problem and was fixed by uninstalling the X55 altogether (using the Windows Device Manager, and including any drivers when the option is offered), then re-booting the system. Otherwise, please check the FAQ subforum thread about what to check if FSUIPC doesn't see your joystick. ... I just searched. Both the X55 and X56 throttles are prblematic. Seethese threads http://forum.simflight.com/topic/82017-saitek-x55-throttle-unable-to-set-axis/?do=findComment&comment=494485 http://forum.simflight.com/topic/82703-fsuipc-saitek-x56-issue/?do=findComment&comment=498511 http://forum.simflight.com/topic/81462-fsuipc-49x-not-working-with-saitek-x55-and-p3wd25/?do=findComment&comment=491085 http://forum.simflight.com/topic/81985-fsuipc-not-seeing-x56-buttonsaxis-anymore/?do=findComment&comment=494426 Pete

By "not recognised" do you mean not seen in the Assignments tabs? If so, and you are using Windows 8, or 10 then it seems like a common problem on those operating systems with Saitek devices. If you mean only in the aircraft, then nothing in FSUIPC itself or its settings can possibly change what it sees and does in relation to assigned actions from joystick devices. The only possibility I can think of is that you assigned things in a specific aircraft profile then loaded a different aircraft not assigned to that profile and so without those assignments. Without more information, especially your FSUIPC4.INI and LOG file I cannot really help further. Pete

Okay. That sees the device as about 8 distinct USB devices. I've never seen anything like it! The only one with the correct name AND with any buttons signalled is this one: Device at "\\?\hid#vid_1532&pid_0208&mi_02#8&172de645&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1532, Product=0208 (Version 2.0) Manufacturer= Razer Product= Razer Tartarus Chroma Serial Number= Razer Tartarus Chroma Device is a mouse Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 0 Feature Report Byte Length: 91 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 4 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 3 at indices 0 -> 2 Value 0x40 at index 3, range -127 -> 127, using 8 bits Value Wh at index 4, range -127 -> 127, using 8 bits Value Y at index 5, range -32768 -> 32767, using 16 bits Value X at index 6, range -32768 -> 32767, using 16 bits This USB data says it has only 3 buttons (which FSUIPC would see as 0-2), plus a wheel and two axes, X and Y. How are there 15 buttons? Do you not see buttons 0-2 in FSUIPC? Does FSUIPC see the axes at all? Have you looked? Looking further down the file I see there is another device with the same Vendor and Product codes,, but a corrupted name, with more buttons and axes: Device at "\\?\hid#vhidjs#9&10090989&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1532, Product=0208 (Version 1.1) Manufacturer= Raduct=0208 (Version 1.1) Product= Rar= Raduct=0208 (Version 1.1) Serial Number= Rauct=0208 (Version 1.1) Usage Page: 1 Input Report Byte Length: 12 Output Report Byte Length: 521 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 7 Number of InputData Indices: 31 Number of Output Button Caps: 0 Number of Output Value Caps: 4 Number of Output Data Indices: 4 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 24 at indices 7 -> 30 Value R/RZ at index 0, range 0 -> 255, using 8 bits Value V/RY at index 1, range 0 -> 255, using 8 bits Value U/RX at index 2, range 0 -> 255, using 8 bits Value Z at index 3, range 0 -> 255, using 8 bits Value Y at index 4, range 0 -> 255, using 8 bits Value X at index 5, range 0 -> 255, using 8 bits Value POV at index 6, range 0 -> 7, using 4 bits That has 24 buttons, 6 axes and a POV hat. Maybe the first one is obliterating this one? Do you see 24 buttons, not 15, in FS? I'm afraid this device looks way different from anything I've seen before, so I'm not sure what is going on. FSUIPC is very dependent here upon the data it gets from the Registry. Could that be in a mess? It might be worthwhile uninstalling the device completely, from the Device Manager in Windows, and re-booting, to see if that helps. Otherwise it could be complex to resolve. I might need you to run tests with extra logging enabled. But it won't be tonight. I check back here tomorrow ... Pete

NO NO NO! In FSUIPC you assign a button to KeySend, with a unique parameter 1-255. Then you define the Keystroke you want in the appropriate KeySend parameter in the WideClient.INI file!!! The Keysend can be assigned to any button or any keystroke, just like any other control in the drop-down list! Why on Earth do you want to send a keypress to FS? Are you changing the subject? I thought you wanted to send a keystroke to an application on a WideFS client PC! PLEASE PLEASE PLEASE read the documentation! This facility has existed now forabout 15 years and no one so far has completely missed the point like this! Pete

As the "Changes" document said, the one accompanying FSUIPC 4.963 in the same ZIP file, this is already covered in the FSUIPC Offsets document actually installed for you! I really do recommend reading the documents accompanying each new release! Pete

There are now offsets for every value in the Limiter, so, yes, you can do what you like with a Lua plug-in or external program. Traffic Slider in FS? You can certainly assign a button or keypress to toggle it or set a value. It's a long-existent FSUIPC control. Pete

And did you run the Sim afterwards? The INI cannot be updated until FS is actually run! Anyway, you can add it manually. All those parameters are manually set in any case -- only the Limiter value can be set in Sim. [LATER] I'll be making the Limit options appear more readily in 4.964, released today. Pete

Er, you are completely wrong there! The KeySend facilities have log been documented in the WideFS Technical document -- way back to FS2000 or FS2002 days I think. See page 16. I just did a simple search on "KeySend" and it came up immediately! The "hardware button" is assigned in FSUIPC on the FS PC! The KeySend assigned there is then actioned in the Client, which sends a keystioke! But in FSUIPC you assign to a "KeySend" control, NOT a keystroke! That is the whole point! If you assign to a keystroke it gets sent to FS, not to a WideFS client! Please PLEASE read the documentation! That is why it is there! Pete

Have you asked me about this beofre, at all? Pete

Okay. Most of that isn't useful information. Out of that the infrormation I asked for was the button numbers that FSX actually sees. I take that is 1-15 -- correct? In that case FSUIPC should certainly see them too. It should see 0-31 but FSX numbers them from 1 instead. Now, to find out why it doesn't see them, I need to see the log produced by HidScanner ehich you can find in the "useful additional programs" part of the Download Links subforum. I'd also like to know if you bothered to refer to the thread in FAQ I asked you to look for, and perhaps run JoyIDs to set the joystick ID? That was the first step I advised, if you look back! It is rather pointless you carry on replying explaining the same problem over and over. I would like to help solve the issue of FSUIPC not seeing the buttons, but I cannot do that without your help! Surely you can see that? I don't have all these devices sitting here waiting for me to try them! Pete

You said that already! Please read my previous suggestions and questions. Pete

I don't think the view of the graphic position of a throttle lever would be that good in any case. Just move your real throttle to engage the mode and look in the FSUIPC CALIBRATION tab to get the OUT value. Pete

It may not be seeing it as a normal Joystick. Keyboards are different so that's irrelevant. They are NOT joystick type devices! Please refer again to my previous reply! Also you could run my HidScanner to check properties. Oh, and what button numbers do you see in FSX? Pete

See the FAQ subforum. There's a thread there about joystick type devices which are undetected. Pete

The limit has always been just a number, not a percentage like the preferences. Pete

The "middle" values are 50% for the preferences, of course -- that's what will be set by default. I like to see more at the airports and enough landing and taking off to be realistic. So I decrease the PlannedAirports and Airports preferences, and increase the Ground and Nearer ones to compensate. I can't tell you my current figures as my cockpit is not on at present, but I usually make them something like 20-25 versus 65-75. I adjust them occasionally according to experience. Don't forget these are only percentage probabilities, not rigid requests. The actual limiter needs setting according to how much you can tolerate before performance (and VAS usage) is a real factor -- mine currently is at 250, but it would have to be lower in P3D. It also depends of course on how much traffic you allow in UT2 itself (there are sliders there -- mine are at about 40 and 30 at present, but they are only that low because I also use MT6). If you use MT6 or WOAI then the value of the slider in FS/P3D is also a major control. Mine is usually at 50 or 60. The new value, "TargetFrameRate" is best set a bit below your set frame rate limit, or left at 0 if you want to disable it because of VAS concerns. My frame rate limit is currently set to 32 and I set this target to 28, but i am changing to a surround screen with 3 projectors so I'll have to accept lower frame rates in future I think. Pete

So, can you assign controls to the button? Are their such assignable controls supported by the aircraft, or do you need to set throttle levels to do that? If the latter you can set a throttle level by using AXIS THROTTLE SET with an appropriate parameter (-16384 is zero, +16383 is 100%). If you want to do it through sequential button presses you'd use the Flag setting control as well, and the flag testing. Two button flags would do the job for 3 different actions. This sort of multiple assignment to one button has to be done by editing the FSUIPC4.INI file, and is described in the Advanced User manual. Pete

Sorry, that's a bit confused. Do you want the throttle to change modes for you, or buttons on the MCP? With the throttle, if you assign in FSUIPC, you can define zones of movement in which controls can be assigned. This is done on the right hand side of the assignments tab. You would need to find out how to configure thos for yor particular aircraft. Doesn't the A320 automatically select modes according to throttle position? If you assign to buttons on the MCP, just assign them as you need, assuming FSUIPC sees those buttons. Pete

Why my settings? What you want to set depends on what you want to see happen. I might like my traffic differently to you, and currently I am using FSX-SE not P3D, which makes a lot of different. P3D performance seems to be much more adversely affected by AI than FSX. Also your list of parameters is out of date. In the currently supported version of FSUIPC (4.963) there's also "TargetFrameRate", which can turn off the limiter if the frame rate is better than the given value. Don't use that if AI Traffic using VAS is your main concern, but on FSX-SE I would mainly be concerned with frame rates and smoothness, because AI seems to use hardly any memory. Incidentally, I use MT6 and UT2. Pete

Buttons can be assigned to KeySends which can be configured to do whatever you want on the client PCs. Please see the WideFS documents. The keyboard focus needs for key presses aren't relevant for buttons. Pete