Pete Dowson

You missed the point, I think, that (a) I can't read the serial number without adding a heluva lot of code which is not useful except, apparently for these BU0836 devices, and (b) It won't help at all with the two (or more) Saitek throttle quadrants, or most all other devices which do not provide a serial number in any case. Please re-read my last reply which you seem to have misunderstood. Provided you don't keep unplugging things and moving them around i don't see there's a problem. The ID numbers assigned by Windows won't change if you leave them connected. Pete

Sorry, I don't know FSCommunicator, nor anything about any "blue cursor on an FSUIPC Window". There is nothing like that in any of my software. You probably need to refer to FSCommunicator documentation or support. If you are referring to a WideFS (WideServer -- WideClient) connection, then the Log files for both parts would help you find out what is wrong on the Network. Regards Pete

Ah. No autogen, no AI traffic, no ground vehicles. I couldn't fly without all those. I like lots of AI traffic and business at airports! Well, if you aren't interested in the scenery nor the other traffic etc, then you aren't really getting FSX experience -- except possibly for the clouds which can be much better than in FS9 (but there are some alternative weather + graphics products for FS9 which give nearly as good results). So, yes, with your PC FS9 should be marvellously smooth! I only use the outside view -- no cockpits at all (mine is all hardware, via Project Magenta). I'm sure FS9 will run well on W7. Try it and see! Regards Pete

Two problems: 1. So far no other joystick manufacturer seems to make use of the serial number facility at all -- it is blank or a fixed value like 0. So this would be a one-off. 2. At present there is no HID-handling code in FSUIPC. I now know how to get this stuff as shown in that HidScanner program I provided. However it is a lot of code for very little useful return. It won't benefit the Saitek devices you have, for instance -- the two throttle quadrants are indistinguishable. The only overall solution is for you to never swap the USB connections. Provided devices remain connected to the same USB sockets, the ID's will remain the same (unless you re-install windows!). Regards Pete

Phew! What sort of supercomputer are you running that on, or do you have most of the sliders down? Sounds like the processor is getting severely overloaded, or, just possibly, is getting stuck waiting for disk or video access. I have been trying to get rid of micro-stutters in FSX for a long time -- I've even replaced the HDDs with SSDs -- but I think the problem in my system is the memory bandwidth (DDR2). I'm planning to update to an i7 PC with the fastest DDR3 memory I can get. Also I was using Vista 64 but now Win 7 RC 64 -- that provides a noticeable improvement, as does using DX10 mode (with only DX10 compatible AI, such as that in MyTrafficX and UT2). Blimey, you get that performance with a 2.4 GHz processor? I'm running a dual 9775 system, water-cooled at 4Ghz on all 8 processors! I've eliminated everything else and I'm sure the bottleneck is the memory ... As for blurries, I don't really see those, but then I'm only running a resolution of 1600 x 900 (on a 10 foot wide projection screen), so relative to your 2560 x 1600 it would appear fuzzy anyway. Tell me, you say a two-monitor setup? I've found having two monitors for FSX quite a penalty. Do you still get the problems if you change the configuration to be one screen? Maybe the problem is video card bottleneck? Sorry, FSUIPC isn't a performance enhancing program, only an interface for applications and a toolkit for users. If you find your solution, please do let me know. When I get my i7 PC with superfast memory, water-cooled and hopefully running at least 4GHz, maybe I'll have found my solution? ;-) Regards Pete

In the doc it says 5414 bits must be toggled. So, find the FSUIPC control "Offset DWORD togglebits" in the assignments drop down, assign it to your button, enter x5414 for the offset, and the correct mask for the parameter as follows: bit 16 = x10000 bit 29 = x20000000 (bits are counted from 0 at the right. There a 4 bits in each hex digit). Also toggled, according to the document. So, very similar but offset x5410 bit 17 = x20000 bit 18 = x40000 You can use these codes through the by-pass access offset, but the bit toggling should work okay and it is easier. Regards Pete

The problem then is the omission of important information in the Registry. Registry data is probably the main reason for installers in any case. Even an .INF file whicvh you could execute yourself would be better than nothing. All i can do is try to include them as Unknown Devices. Otherwise, you have to avoid using the Joystick Lettering facilities in FSUIPC. Anyway, try 3.914. no need now for the logging, you can remove those extra lines. http://fsuipc.simflight.com/beta/FSUIPC3914.zip Let me know how you get on, please. Regards Pete

Okay. This is ILS mode selection for the ND, is it? Sorry, but this is confusing again. Is the Flight director not separate from the ILS mode on the ND, as it is with Boeing? Can't you switch the FD separately? I'm afraid I'm out of my depth for Airbus questions. Please please do look at the Project Magenta documentation on the Project Magenta website. Check the list of PM offsets. For example,: 04F4 2 Glass Cockpit ND Modes (Write Only) (*was* Read as well) Sending 100+(value) controls First Officer Display (e.g. 170 enables weather on Copilot ND) Only last three digits are used, you can use the thousands to indicate the key has been pressed again (state change), i.e. 2150 and 5150 do the same Please note, these commands go directly to the Glass Cockpit, if you do not want the MCP or FCU to override them, then please use the MCP commands in 0x4F2 or 0x5520. (Values, not bits!) Airbus 1 MAP (Captain Side, 101 F/O side) 2 NAV (Captain Side, 102 F/O side) 3 VOR (Captain Side, 103 F/O side) 4 PLAN (Captain Side, 104 F/O side) 5 ILS Mode ... etc I assume the ILS mode can be +100 (i.e. 105) for the F/O side too. Not sure how your reference to the FD comes in though. Once you've identified what function it is in PM you want to operate, I can advise you how to do it. But at present I'm afraid I've no idea. Regards Pete

Okay. The interesting thing is not simply that there's no OEMName parameter in the Registry, but there's actually no entry at all in the Registry for the BU0836 devices! Did you not receive any sort of installer for those devices? I don't understand why there can be numerical IDs assigned (4, 5, 6) yet there be no way of relating them to anything in the Registry. Can Mr. Bodnar help at all with this, do you think? Yes, it will do. I'll look at that, see if I can at least add the lines 4=Unknown Device #4 5=Unknown Device #5 6=Unknown Device #6 which might make it less confusing. But without registry information there's no full fix at all. Regards Pete

That has to be done every 10 seconds or less. There's a timeout on it. How are the controls connected? What is doing what? Maybe the program scanning them is not getting enough time when FS is running? Maybe it's a priority thing? I really cannot picture what you are doing or how anything is connected. I can't really advise on anything more without knowing the bigger picture. Test on a default aircraft, like the Cessna. Does the same thing happen there? If not, it is something to do with the way your add-on aircraft is programmed, and you need to deal with the author or support. Regards Pete

The reason is as logged: Server: 79326 Broadcasting service every 1000 mSecs 89045 Restarting service due to total lack of use Client: 2453 Trying to locate server: Need details from Server Broadcast 2453 Failed to connect: waiting to try again So, the broadcasts aren't being received by the Client. Either your Client is using an operating system so old it is not supporting broadcasts, or your two PCs are no in the same workGroup (the workgroup names are different). If you cannot fix it by renaming the workgroups to be the same, you can, as documented, get around the lack of broadcast reception by providing the ServerName and Protocol parameters to WideClient in its INI file. Regards Pete

No, Microsoft did not introduce AI aircraft until FS2004. Before that anything moving was dynamic scenery only. Regards Pete

Ah, so you are not writing the interface program to FSUIPC? You could instead use a Lua plug-in. The keyboard will not influence any values unless you press the keys to do so. But, yes, if you have a joystick connected, being processed by FS or FSUIPC, then of course that will overwrite values in normal unpaused mode unless you disconnect using 310A. However, values from joysticks are only used when they change. Maybe you have a jittery joystick pot? If assigning via FSUIPC you can set a larger Delta to overcome any jitter, but be aware that larger deltas give lower resolution. Regards Pete

By program? Read the existing value, add the extra, write it back. But this seems so obvious I am obviously misunderstanding the question. They are exactly the same information, populated at exactly the same time, in different formats. It doesn't matter which you write to. The 08xx offsets date back to FS95 and FS98 days and the others from FS2000 or later. All in the name of compatibility! ;-) No, sorry. FSUIPC and its Lua interpreter make no differentiation whatsoever between what they do when FS is paused versus unpaused. The only times when FSUIPC may not be updating things is when in menus and their modal dialogues. Even then the Lua threads might be continuing. Regards Pete

Not via FSUIPC, which only provides aircraft data for TCAS purposes. If the carriers in FSX are AI objects, then you will be able to read all of their data from SimConnect. If they are implemented as dynamic scenery objects, as in previous FS releases, then there is no way I know of. No way. They are most certainly just dynamic scenery objects. Sorry. Regards Pete

I'll explain both words: "Activated" means that the Marker radio signal is being received and the sound (if enabled) is heard and the O M or I light is lit or flashing. If you are not receiving a marker signal then the Marker receiver is currently inactive, i.e. "not activated" by a signal. Okay? Note that you have to be pretty much overhead a marker to receive it and so activate the receiver into providing the sound and flashing light. "True" is a BOOLEAN expression, the opposite of which is FALSE. In FS (and most programming) terms, TRUE is represented by a non-zero value, and FALSE by a zero value. Ok? Regards Pete

If the throttle is doing this of its own accord, without you moving the throttle at all, then you most certainly have something else doing it, not FSUIPC when doesn't touch anything whilst the inputs aren't changing. Where are you ASSIGNING the throttle? In FS or in FSUIPC? Do NOT assign anything in FSUIPC without unassigning it in FS or you will have conflicts. Also check that nothing else is also assigned to the throttle. However, if it is slowly returning, and not simply jerking back, then it sounds like there is some specific software running which is doing it. Check all your other add-ons. If it only does it with one specific aircraft, check that, obviously. Pete

Landing switch? What is that? Sorry, I know little about Airbus. If this is for Project Magenta, have you checked their documentation and/or support? I'm not really able to support well all the products for FS. However, if you tell me the technical name I can look it up in the PM offsets document -- you could look there too, it is on the PM site. Perhaps it is APP or APR (approach mode), like on Boeings? Regards Pete

Okay, thanks. That makes sense, looking at the HidScanner log. I've no chance of reproducing this problem here, so I'm going to have to look at ways of getting information logged from FSUIPC itself about what is going on. I'll start on this tomorrow (Thursday). Meanwhile, so I can send you test versions to get the extra info, and you can send me the logs, which might be larger than usual, could you reply to this via email, please. Send to petedowson@btconnect.com. Regards Pete

Hmm. That looks okay. One moreyou are using FSUIPC3, which doesn't use the HID interface to windows except to get the device names. I'd like to check the IDs. Can you run the attached program, JoyView, and write down which entry (0 to 15 I think, or it might be 1-16) corresponds with each of your devices? That will give me the IDs. After that I can only think to add more code to FSUIPC3 to log what it is seeing. Regards Pete joyview.zip

Here's a program called "HidScanner" which produces a log file containing all the data about Windows-recognised HID devices (Human interface Devices), which includes joysticks. Could you run this please and show me the resulting HidScanner.LOG file? Thanks, Pete HidScanner.zip

Some of the assignments are made to devices in the E to L range, but since there are no Windows-assigned IDs for them, they cannot work. I need the IDs to operate them. But the "clean" INI file clearly shows that only the 4 Saitek devices are detected by FSUIPC. I am lost here. I cannot imagine how you can assign in FSUIPC if it cannot see them. The non-detection of the BUO836 devices cannot really impinge on the Saitek ones. Are you sure you don't have things being assigned in FS too? Yes, with no sign of any devices other than the 4 Saitek ones. That's what I don't understand. Evidently the USB implementation of those devices is completely non-standard, and the process I use to access them and obtain their names is not working, despite it being drawn from standard Microsoft references. But how you can assign to them when they have no ID listed I don't know. what numbers do they come up with (if you omit changing to use letters)? I don't have any of those devices so it is going to be a problem finding out how they are so non-standard as to mess normal microsoft-approved methods up. I'll think about what I can do and get back to you. Pete

Odd. not seen that before. Does it happen without you actually going into the options and changing things? Could you show me a good copy, please? Also, I do really need to know what version of FSUIPC you are talking about. If it isn't the very latest (4.52 or 3.912), please try that first -- there have been quite a few changes which might affect this sort of thing. Also, can check the file Properties of the INI file (right clcik - Properties) and tell me the exact size of the file, please. No, I don't see that there. It most certainly correctly lists 1 Yoke, 1 Rudder Pedals and 2 Throttle Quadrants. don't forget that the numerical lines are the ID numbers Windows is using, and the letters are the assignments made. That's how the letters are translated into numbers. If you read about this facility you'll understand. Here, look at the "good" part, which is perfect: [JoyNames] AutoAssignLetters=Yes 0=Saitek Pro Flight Throttle Quadrant 1=Saitek Pro Flight Rudder Pedals 2=Saitek Pro Flight Yoke 3=Saitek Pro Flight Throttle Quadrant A=Saitek Pro Flight Throttle Quadrant B=Saitek Pro Flight Rudder Pedals C=Saitek Pro Flight Yoke D=Saitek Pro Flight Throttle Quadrant There are none of those listed. If they are not recognised by windows as joystick devices they won't be processed by FSUIPC in any case. It looks like the lines from E= onwards are spurious rubbish. In fact they shouldn't do any harm at all as there are no numerical lines to correspond with them. How muddled? They can only be assigned to A, B, C or D and those lines are fine. The E, F etc letters cannot be assigned as they have no numeric IDs. Ah, that was the information I needed up front. Tell me the size of the file please, and explain what is getting muddled, as I don't see anything which could muddle anything. BTW what is build 7229? I am using Win7 x64 RC, which says it is build 7100. Do you have something later than the RC available to all, and if so how do I get one? Regards Pete

Okay. So the fact that the FMC software is working on the client menas the question of FSUIPC doesn't arise, right? Sorry, I am lost again. If the software is working, how can it not respond? Surely that means it does not work? Are you meaning something different when you use the term "keys of the keyboard" and "FMC keys"? I cannot at all imagine what you are asking. Sorry. Isn't this something needed in the FMC software. If the keyboard and the FMC are both running on the same client PC, as you say, where does FSUIPC come into it? It isn't your English, which seems very good. It is the omission of a description of what you are trying to do, which i still do not know. i cannot see how any of my software is involved between your client keyboard and the FMC software running on the same PC. Regards Pete

Yes, those are the FS controls for the values. But as I said, neither PMDG nor Level D use those -- they programmed their own autopilot. No. In FS itself there are assignments for keyboard. FSUIPC contains no default assignments, you can assign whatever you like. But that isn't your problem. You need to assign the keystrokes which PMDG and LevelD need to see. I can't tell you what they are, or even if they exist -- you should be able to find out from their documentation. They won't both be the same. Regards Pete