Pete Dowson

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

Yes. Please check the "SendKey" facility out, documented in the WideFS documentation included in the package. Pete

The very first control in the assignments drop down list, in FS controls, is <custom controls>. Have you not looked. After you select that you can enter the custom control number (which you have to wok out from the PMDG DDK document I told you about), and, if needed, a parameter to go with it. Their control list (controls are also called "EVENTS") will probably be different for each of the three aircraft, so you probably need to assign them in profiles, one for each aircraft type. Who mentioned anything about Lua in this context? Pete

I refer you to page 36 of the FSUIPC4 User Guide, where it clearly says: "These “mouse macros” do not actually use the mouse at all, but use a set of “mousetraps” to identify how your own mouse use calls routines in the panel coding, and then attempts to replicate it." Now, since they do not use the mouse at all, why would it matter where it was? The whole point of them is to do the same thing as what you can do with the mouse, but even without the relevant switch being displayed, or off-screen in a virtual cockpit. For more information I suggest you read the User Guide, at least. There's also more details in the Advanced User's Guide. You should also note that mouse macros aren't usable on most modern add-on aircraft. Even the PMDG aircraft will not support them on all switches and knobs. But in the case of the three aircraft you mention, pretty much ALL of them are definitely accessible using the PMDG <custom control> numbers which can be worked out from their published SDK -- in the .h file in the aircraft's SDK subfolder. Pete

Exactly as you already said on Sunday -- see your message above, Sunday at 04:02pm. Pete

No. Memory is nothing to do with it. Why would you even suggest such? where does 'memory' come in? Without knowing what "ipcinit.lua" is doing I cannot help at all. I don't know why it is so secret! Nor do I understand why it needs to run before much else is ready in FS -- most everything should be started at ipcReady or later. When ipcInit is executed FS isn't ready at all. All it is suitable for is initialising some FS offsets. Pete

Ah, you mean the DLL.XML file, not FSUIPC4.DLL which is a DLL file!!! All you proved is that something is wrong with that DLL.XML file, or it is loading something bad! Just start with the one made fresh by FSUIPC, and add the items you need one by one and test each time. Do NOT include Vistamare! You've also proved you do NOT have a problem with FSUIPC, but with something else you've added. Pete

Well, you did something wrong because the file was not only written BUT THERE WAS ONE BEFORE -- even though you say you deleted it!!! See: Found Prepar3D.CFG in "C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay The full folder name is C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\ Okay. FSUIPC4.DLL, FSUIPC4.INI and FSUIPC4.LOG, and the FSUIPC Documents subfolder, are all absolutely guaranteed to be there, if it appears in game. So now I'm sure you are not looking correctly. This confirms you are really in a mess when it comes to dealing with files and folders: Exactly HOW did you do this "switching"? Pete