Pete Dowson

Okay. I have received the Airbus X Extended package and installed it, and I am running it in FSX, and all my axes are clearly visible operaating in the FSUIPC4 axis assignments tab, and assignable. So, it looks like there's something very odd with your system. I thought it a little odd that no one else had this problem, or at least reported it. I'm not sure what to advise you now. You could try more logging. The joystick scan (which makes the list of devices in the FSUIPC4.INI file) and the reading and interpretation of assigned axes can be logged by adding these to your INI file, in the [General] section: Debug=Please LogExtras=x200008 but at present I've got no low level logging for the actual reading of the joysticks. Let me see what you get with that logging first. Pete

Not wasted. It was (and still is) an interesting problem. I still don't understand how this occurs, because i really doubt that they hook into DirectX. that just makes no sense. I would investigate it here, out of sheer curiosity if nothing else, if Aerosoft would supply the aircraft. I have asked and I am still waiting - I will chase them up! Best Regards Pete

FSUIPC saves its settings into the folder which it runs from, which will be the Modules folder in the installation of FSX you are running at that time. The only thing which might stop it is if the Permissions on that folder don't allow it to write there. The FSUIPC4 Installer sets permissions correctly, but if you've not used the installer they could be wrong. See if the relevant modules folder contains updated Log files, specifically FSUIPC4.LOG. If so it is writeable. Pete

It's in FSUIPC 4.904 now. I'll put it into 3.999z3 and WideClient 6.996 tomorrow, probably. Pete

The only way you'll find out what it is, then, is to switch to it to look at it. Either use ALT-TAB to switch directly, or ALT+ENTER to switch to Windowed mode then look at it! If EZCA is crashing only the EZCA folks can solve it. But please look at the message you believe is there! Pete

EZCA certainly doesn't use FSUIPC, and FSUIPC is totally unaware of view changes. Furthermore, I do not know of any "typical windows beep sound just as if a window was open in the background"! I don't believe I've ever noticed any sound just when a window is open in the background. Maybe this Window you cannot see tells you why EZCA has a problem. Have you looked? Seems to me that if you do believe that the beep means there is such a window, the main and first thing to do is look at it! The only change in the most recent version was the omission of the signature check. If FSUIPC had a problem with Simconnect then it would log the problem, or FSX would crash. Also, there's no way I know that one SimConnect client can interfere with another. I use EZCA all the time for my views and of course keep FSUIPc up to date. There's never been any interaction. I suggest you contact EZCA support with the details of the error message you do get, and possibly the contents of the Window you aren't looking at. Regards Pete

Right. Pete

Why aren't they smooth? Do you have old dirty controls, or a poor power supply? Have you made sure you have no conflicting assignments, like in both FS and in FSUIPC? You can use either but not both. And don't enasble Filtering in the calibration -- that's only for really bad devices or power supplies If you really mean they are too sensitive for you, not that they are jerky or spiky, then try using the 'slopes' facility in the calibration tab to flatten the response a bit around the central position, and don't calibrate with as much of a null central zone. This doesn't really apply to brakes, though. with toe brakes you should leave a good dead zone near the feet off position so you can use the rudders without inadvertently braking too. Sorry, I don't know what you mean there. Different assignment methofs, in FS or in FSUIPC, are really mostly intended to allow folks to handle different add-on aircraft methods. Generally the most efficient method for normal (default and simpler addon) aircraft is to use the "direct to calibration" assignments, as those use the most direct path. Regards Pete

Of course it does, because as well as the Conditional line 92=CR(+72,0)72,7,C66704,1 you also have 72,7 sending exactly the same control when Pressed and when Released! 93=P72,7,C66704,1 94=U72,7,C66704,1 Pete

Of course it is possible. I'll put it on my list. Regards Pete

It's something i may consider if I ever remove the shelving I have on one side. I need space down that side to reach the cockpit nose because of all the works hidden under the nose cone. And I need space the other side to reach the Windows! ;-) It isn't a priority for me in any case. My severe tunnel vision means I don't really see even all of the projected screen. I only need to switch to side views on that occasionally -- i.e. when taxiing. I do have it installed, and also PM's own, the iFly and the Jetstream one from Prosim737. But the one I use is good, modelled to be very faithful to the real thing and used on at least two professional simulators that I know of. It isn't generally available though due to agreements with those folks, having been made "to order" for them. Regards Pete

You posted twice. I already replied to the first one I saw. Regards Pete

You only had to look in the FSUIPC4 History document installed on your PC to see that it was version 4.88, which was the immediately preceding main release. Here is the entry in that document: This has not changed. The ONLY change in 4.90 is the removal of the signature check. Regards Pete

This is because the routine used to make the display packs several parameters into one. One of those options is enabled by bit 14, which is 0x4000, or decimal 16384, and that is "white messages". I suppose i could document this. You don't need a large number of seconds, just add 16384 to the number of seconds. Regards Pete

Well, it means somehow that they have code in their aircraft which somehow hooks into DirectInput and prevents the axis values being read directly from Windows! I find that quite amazing and almost unbelievable that any aircraft maker would go to such an extent! Pete

Just copy over your FSUIPC4 INI ("configuration settings") file. All files connected with FSUIPC are in the FS Modules folder, nowhere else, so are easy to find and copy. Pete

It sounds like the SimConnect timing bug. Please see the FAQ subforum thread on the subject. Persistence does pay. Once it gets through once it will get through every time. If not I shall need to see the FSUIPC4. LOG it produces -- if there is never a new one written, then FSUIPC is not actually getting loaded. FSX accumulates those forever. You can delete them if you wish for a smaller CFG file. It will then ask you to trust everything again, as you use it. But the entries don't do any harm in any case. Pete

Er, if the button 72,7 action has to be conditional on another REAL button, why on Earth are you using buttons flags? The condition can just be on the button directly, surely? What's the Flag for? Falgs are for remembering states of things, not for detecting the actual current state of a real button or switch! And why do you want to make things so complicated when all the simplere examples are direct conditions on buttons? It wouyld save a lot of effort if you'd simply paste the relevant part no the who;e file! Here: Apart from the fact you are trying to use Flags for no good reason, the flag you are using is denoted by the parameter 1 on the button 72,0 flag assignments. 1 = 0 x 256 + 1, so the flag is actually F0,1, but you are testing flag 72,0 which doesn't even exist! (Flags are only available for the standard joystck numbers, 0-15). Not only that, but on line 95, the one with the invalid flag reference, you don't specify any action! You end with the button number only. What od you think that could do? Why not follow the examples in the documentation? Don't use flags, which you obviously don't understand and which cannot be used with vitual joystick numbers in any case. Pete

Not really a good idea to have Windows set to auto-restart programs after a crash. If it tries to do that on my system I intervene immediately. Yes, it doesn't accumuate logs, creating a new one each time. Since it's unlikely to be of relevance in a crash saituation it isn't that important, and it has been that way for 14 years now without any problems arising because of it. Regards Pete

No idea. You can play passenger screaming wave files using the Sound facilities in a Lua plug-in. I've no idea how to simulate the air mouthpieces dropping from the overheads. What do you want to happen? Pete

Check the New Weather Interface stuff in the SDK. The NWI handles about 12 visibility layers. Pete

What Flight Sim? What version of FSUIPC? What offsets? There are three different ways of handling weather in FSUIPC. I'm away now till Monday, so you may need to wait for more help. Or you could help yourself and go through the documentation a little more thoroughly. You could also play with WeatherSet2, supplied explicitly for folks with weather reading/writing questions. Regards Pete

Version 4.903 is now available in the Download Links subforum. Regards Pete

Sounds like you don't have an FSI file loaded, or only an empty one -- the FSI file contains the list of the offsets you want to show. FSInterrogator comes with a default set, suitable for default FSUIPC offsets (though a bit out of date). Did you open t? Maybe you need to specifically select it from your collection of FSI files. Pete

Ah, sorry. Yes. A typo in the code. Sorry. I'll fix that in 4.903 later today. Meanwhile you CAN get this display every TEN seconds by adding these two lines to the [General] section of the INI: Debug=Please LogExtras=4096 The "Debug=Please" allows the Log Extras option in the Logging tab to contorl a lot of different logging options, mainly used to debug folks' problems. You can change the value "4096" in the Logging tab once "Debug=Please". Change it back to 1 for the normal LogExtras=Yes option. Regards Pete