Pete Dowson

Assigning a button to just "Brakes" in FSUIPC is identical to assigning it to BRAKES in FS -- there's no advantage or difference. You'd want to set the "repeat" option, otherwise hold it down won't keep the brakes on. The "BRAKES" control is exactly the one used by the default "." keyboard assignment, but of course keys auto-repeat on the keyboard. Pete

I am having difficulty remembering any of that, but I think there was a whole world of difference between the ISA version and USB version -- with my code, at least. On ISA I used assembly code via my EPIC95.VXD. For the USB version I interface to RR's EPICIO.DLL. I'm afraid I don't even know where my documentation is for this stuff now. Your best bet really lies with the EPIC forum (is it still Ray's green side up?) or with RR or FlightLink. Regards Pete

No, because I have no information. If you want me to look, please get me a full log. Be sure to use the 2.00 version as appended earlier in this thread, and set "Log=Debug" in the FStarRC.INI file [settings] section. Then run a session including pronting the report. The FStarRC.Log file it produces will be quite big, but it should help me work out what to change -- you'd then have to test any changes for me. Send it ZIPPED to petedowson@btconnect.com. Regards Pete

FSNavigator is NOT an FSUIPC client application, but an FS DLL (i.e. a Module, like FSUIPC, which installs INTO FS itself). It is one of the main examples of add-ons which cannot possibly be run on any machine not running FS! FSCommander works fine through WideFS, but you must run WideClient on the client PC first. Pete

I'm not aware of any specific problems with this feature. But can you give me more details so I can check? Specifically: which messages, and what updates have you applied to FSX? Regards Pete

You have made an error then. Please show me the actual SimConnect.INI file you have made and tell me EXACTLY where you placed it. Regards Pete

Where is this "returned"? Please describe what you are seeing. None of those things apply to an FSX installation because if any part of that was wrong FSUIPC4 should never get loaded by FSX in the first place -- if it has an incorrect signature it is immediately suspected of virus infection and not loaded. The only way I know of for the signature check that FSUIPC itself applies to fail is that it has been stripped altogether of any signature. That would mean someone had deliberately interfered with the file. Please right-click on the FSUIPC4.DLL (in the FSX Modules folder), selection Properties and check the signature details there. Please show me the Install and FSUIPC4 logs from the FSX Modules folder. Regards Pete

There is no reason why you should not. There are many many cockpits built with proper on/off latching toggle switches. In fact in many cockpits they are the norm, not the exception. Regards Pete

Sounds like those settings are loading from your "start up" flight. Just set everything they way you want to start, then save a flight flagging it as the start-up one. FSUIPC only acts on axis inputs when they change. Your initial positions are set by your start-up flight. Regards Pete

I'm not sure if it got corrected in FSX SP2 (have you installed the FSX updates?), but it was a known bug in FSX that when an ATC window is open some of the keypresses (notably most of those using the numeric keypad) don't work. This is actually disastrous for keyboard fliers as thoseinclude all the main flight controls. It certainly doesn't make any difference at all HOW the keypress arrives -- whether from the real keyboard or from FSUIPC or other programs. Of course the best way of using FSUIPC assignments anyway is to use FS controls, never key pressess. Why don't you use controls? Regards Pete

Without also seeing your Install log for FSUIPC4 I can't be very specific, but it is either a bad installation of SimConnect itself, or you have a copy of the SimConnect DLL itself installed either in the Modules folder (delete it) or somewhere where it is being loaded by another add-on -- check other SimConnect-using add-ons you have. The SimConnect DLL must only ever be loaded from the Windows WinSxS folders. If they somehow get found and loaded elsewhere they don't work correctly. Regards Pete

Sorry, I don't know. That will depend upon whether the whole device is a standard HID joystick, in which case most if not all should be usable with just a default Windows driver and FSUIPC, or whether it is more sophisticated and has stuff that is only understood by their software. Sounds like they are either terribly calibrated, or have an incorrectly set sensitivity and null zone in FS (the sensitivity should be full right and null zone full left for all axes), or, just possibly, have something set in Windows registry which tells Windows that they are digital not analogue. I believe that was one of the problems with one of the Saitek installers too, so it is a little suspicious. There's nothing specific -- FSUIPC is just a generic calibration and assignment utility, mainly operating on the FS end (i.e. it understands what FS needs and adjusts for that, not specifically for whatever the inputs come from). The instructions in the FSUIPC User Guide apply to all. Happy New Year! Pete

Not sure why, but of course FSUIPC's dialogue occurs as a result of Menu selection, so it may simply be due to FSX still being in menu-related suspension. I remember I had extreme difficulty getting AdvDisplay's window showing on top of FS2004's screen in normal flight or slew modes, as FS keeps drawing over it. In fact it never worked correctly wiith some video drivers/cards. Sorry. In your circumstances I'd have to keep experimenting to find a solution. Have you tried asking in http://www.fsdeveloper.com? Happy New Year! Pete

Uninstalling FSX, removing the SimConnect folders as described in the FSX Help Announcement, then re-installing everything should work fine. I don't know of any case where this has not worked, especially on WinXP. Try testing things after re-installing FSX but before installing SP1 just in case it is some sort of corruption on your copy of the SP1 update. Happy New Year! Pete

Don't do that. Delete it. AdvDisplay is only for FS2004 and before, it won't work with FSX. It hasn't even been supported on FS2004 for some time. Regards Pete

Yes, you have something repeatedly sending that button indication. As Thomas says, it is one of your GF modules. I think button #157.6 will be the GoFlight MCP Pro, and I think the left-most knob. Try disconnecting that module. If that fixes the problem, you most likely have a misbehaving unit. Happy New Year! Pete

Thanks. (Never heard of Net Nanny before -- a type of firewall presumably?) Happy New Year! Pete

Ersorry, we must be talking at cross-purposes here. If both devices, plugged in at different times, are seen as Joystick 2, then plus one set in, and assign the axes on Joystick 2 as "aircraft specific" to one or other of the aircraft you want to use that joystick with. Do the same when calibrating. Then unplug those, and do exactly the same for a different aircraft, one which you want to use that joystick with. It doesn't matter that they have the same number because, being aircraft specific FSUIPC will only do the axis assignments actually specified for the loaded aircraft. Then, to save having to repeat all this for every aircraft, edit the FSUIPC INI file to make the Axes and Calibrations sections apply to everty aircraft you want them to. Using the ShortAircraftNameOk facility should help there. Actually, even simpler, if 90% of the aircraft use one set, don't make that set aircraft specific for assignments. Only make the lesser-used set aircraft specific. FSUIPC swaps the entire asignments, it doesn't mix them. But that's the point. It doesn't NEED to if your assignments are specific to specific aircraft. All the axes can do completely different things on each aircraft if you want to. Why? Just do it for one then edit the INI, either reproducing the same subsection with different aircraft names, or better using a substring of the full name, just enough to differentiate them,, via the ShortAircraftNameOk=substring facility. One easy way might be simply to make sure all of your helicopters have the part-word "heli" in their title. Or if you mean you are using the same joystick for fast jets too (and Airbuses?) you could possibly add the word "Joystick" to their titles and use that as the substring. Regards Pete

If they are never plugged in at the same time, why is there any need to differentiate between them? The only requirement is that, when they are connected they are consistently seen as joydtick number whatever. Just use aircraft-specific facilities in the axis assignments of FSUIPC to automatically use a completely different set of assignments according to the aircraft loaded. You can do the same for the calibrations. Regards Pete

Yes you can. See offset 0020. Pete

Not even the bit in English, saying "By reading all 8 bytes from 0570 into an __int64 it becomes a doddle", and ".. read 8 bytes from 0570 into alt, then ..."? That's hardly programming language. You already understood my "__int64" because you found the VB equivalent! Even if some of it (little as it was in any case) was more C than VB, you could see in English that the was only the one read into the one 64-bit variable, because I said so, in English. Three times! I really don't understand how it could have been stated simpler, at all. :-( Pete

Ok. Have a good Christmas. I'll be back just before New Year! Best Regards Pete

Why oh why? Only 0570 is a 64 bit value. You only needed to get 0570 and 0574 separately when reading them into two separate 32-bit values. See the digits 0 and 4 at the ends of the offset addresses? That's the number of bytes between them -- 4 bytes = 4 x 8 = 32 bits! You don't need both values -- the one you are reading from 0574 is rubbish, as it will have half of the altitude and half of the next offset (0578) in it! Why don't you please just READ what I WRITE and copy that? I repeat it here for the THIRD time! I really cannot understand why you are repeatedly and completely IGNORING what I am showing you! The WHOLE POINT of using the 64-bit value is that you get it exactly as you want it all in one go!!!! :-( Pete

You should have just done it for one, then edited the FSUIPC INI file, changing the "ShortAircraftNameOk=No" to "Yes" or "Substring", then found the [buttons.xxxxx] section for the PSS 777 and shortened it to suit all the models available -- or pick a common part of all the names like "777" (setting "substring" for the parameter). It it actually toggled on or off with one button push, or have you a real toggle action for it? If it's a one-button toggle then perhaps you have the "repeat" set? Otherwise it could be that you have the button programmed twice somehow. Enable button logging in the FSUIPC Logging options, and check the FSUIPC log after you've pressed it once. Anyway, it might be a good idea to edit your FSUIPC.INI even now, as I suggest above. If you would like to sent it to me, Zipped, at petedowson@btconnect.com, I could edit it for oyu. But it would have to be today, Friday (UK time) as I'm then off;ine till the 31st. Regards Pete

I'm off tonight, not back on-line till New Year's Eve, probably. If you can do it today and get it to me pronto, let me see if I can find anything in the detailed debugging logs. Do this please: Edit WideClient.INI, change "Log=Errors+" to "Log=Debugall". Edit FSUIPC4.INI. Find the [WideServer] section and do the same (or add the line if it isn't there). Run FSX just long enough to prove the problem. No longer or the logs get too big. Close FSX. ZIP up the WideClient log, the WideServer log and, for good measure, the FSUIPC4.log. Send to petedowson@btconnect.com. If I get them in time, today, I'll try to get you an answer -- assuming I can find one. Regards Pete