Pete Dowson

AI are only created within the current "reality bubble" in any case, whether by file or injection. That's something like 80km. Traffic due in from firther afiend only pop into existence when near enough. the graphics won't be drawn till they are a lot nearer in any case -- 10 miles or so I think. I use Mytraffic6, which gives me the greatest variety of realistic AI at all the airports I use, even if they don't abide by real timetables and routes (they fly direct departure to destination, UT2 provides routes via airways etc. But UT2 is getting very much out of date now). MyTraffic can provide a higher traffic load than default AI for the same performance. With FSX-SE I am able to run 100% traffic setting even at dense airports like Aerosoft Heathrow. Pete

The list supplied in FSUIPC contains ALL of the controls offered by FS. With add-on aircraft the authors may or may not obey standard FS controls. You'd need to check what that aircraft actually needs in order to operate the switches. For example: does it have keyboard shortcuts for any of those things? Have you checked? If so you could assign to those keypresses. Or maybe it does use FS controls but in an odd way -- enable the Event logging in FSUIPC and operate the switches, see if any FS controls are logged when you do so (you can enable the FSUIPC console log and run FS in windowed mode so you can see the logging in real time). It may use custom controls (PMDG does for its NGX and 777). Or it may be that you can use mouse macros or L:Vars to control them. You'd need to research this yourself or ask other users of that aircraft, assuming the makers don't help. [LATER] A brief search in the User Contributions subforum finds some assistance. I assume you didn't bother to look there? Check this old thread: http://forum.simflight.com/topic/63155-flight1-mustang-commands-upd-15th-mar-2010/?hl=mustang Pete

Use the aircraft name, from the "title" parameter in the aircraft.cfg file -- offset 3D00. The title is how you select the aircraft in FS, and is the name used for FSUIPC's Profiles and Aircraft-specific settings. It's the only unique identification for the aircraft (FS doesn't allow duplicates). It's historic. FSUIPC dates back to FS98 days, and then the offsets were actually offsets directly into an FS Module. All of the values identified were therefore in the sizes and units FS which FS used, directly. Because one of the main purposes of FSUIPC was to allow applications written for FS98 (and later) to carry on working correctly in later versions of FS (FS2000, FS2002, FS2004, FSX, P3D) those original offsets are still the same, even if they don't need to be. The unused spaces in between were taken up with new values, and the size was increased from 8192 bytes (hex x0000-x1FFF) to 65536 (x0000-xFFFF),. With the added ones like 3102, I could choose the size and units as needed, because now the offsets are NOT directly into FS but in memory maintained by FSUIPC whilst it ferrets them out (in the case of FS2004 nd before) or receives them from SimConnect (FSX and P3D). You can use the Byte versions if you like, it really makes no difference in these cases because the only change from FALSE to TRUE is 0 to 1 in the first (lowest value) byte of the 4. Pete

No, there's no time-dependent or timing facilities available with mere parameters in the INI file, even using macros. Lua was added to avoid having to make all that stuff even more complex and arcane than it got to, as it is! ;-) Pete

Please note, I originally said "button 5 on joystick 1" but the example showed button 1 on joystick 5. Corrected now. Pete

Probably. You'd need to use the same macro, but edit the result in the file to give it an appropriate parameter (a "mouseflag"). The format and parameter values (at least the ones I am aware of) are described in the FSUIPC4 Advanced Users guide. Search for the section on Mouse Macros, around pages 33-34. Pete

I cannot help with old versions. Please first run the installer for version 4.939u and then replace the FSUIPC4.DLL in the Modules folder with 4.939v which you can find in the Download Links folder. "Dropping down" the Add-On menu is not an FSUIPC function. Nothing happens in FSUIPC until you see and select the FSUIPC entry. If FS is crashing when only dropping the menu then it's definitely a problem with your FS installation, no matter whether it occurs or not with other versions of FSUIPC. All the change of versions does is change the memory arrangement, but it cannot affect FS's ability to drop a menu. What is "FSX-A"? Of course, but only with the current version. First off, what other entries would there be in a successful Add-Ons menu drop-down? Second, what other programs are loaded by your DLL.XML and EXE.XML files? Third, and always most important, you need to provide the actual crash data, that which is recorded on any crash in the Windows Event Viewer. Pete

I think you misunderstand the technology. ALL traffic programs except UT2 merely work by replacing the default FS traffic file with their own (or several, not just one).files. Once the traffic BGL files are compiled and accepted by the next FS load (you can't change things whilst FS is running), they operate in the same way as any other "scenery" BGL. It's just that the instructions they contain tells FS which aircraft and what route, instead of, for example, what building and where to put it. There's no programming outside of FS for this. UT2 is the only one I know of which operates differently. Its EXE program operates as a process outside of FS and injects the traffic using SimConnect facilities to do so. the aircraft it uses must be installed beforehand into FS, but otherwise I would have though the injector would run on a Network. (Though I can't really see any reason to run it so, being a separate process). There are other programs which do this traffic injection, but they are not purely traffic add-ons --for example: VoxATC which I think adds traffic because it doasn't like working with traffic it cannot control, and On-Line ATC programs for VATSIM and the others which inject traffic representing the other fliers logged into the same service. Hope this helps, Pete

Yes, you can assign as many as you like to one button press, and add conditions based on other buttons or offsets. but this can only be done by editing the entries in the settings file, FSUIPC4.INI (or in the Profiles file if you are using the seperate Profiles files in folders). There's a whole chapter on all this in the FSUIPC Advanced User's manual (see "Button Programming", as listed in the contents list on the first page), and probably lots of examples in the User Contributions sub-forum. For something as simple as two different controls or keypresses sent on alternate presses (in other words imitating a latching toggle switch with a momentary button), you would simply need to make the action dependent on the button's own 'flag', which is changed on each press. So, for button 1 on joystick 5, something like: 1=CP(-F5,1)5,1,K<keycode>,<shifts> 2=CP(+F5,1)5,1,K<keycode>,<shifts> where you'd need number the lines to avoid clashes with others, ans fill in the correct keycode and shift values -- they are listed in the Advanced User's guide too. Pete

Okay. Bug verified! It's a very good catch -- thanks for reporting it. The code is explicitly checking for 0 as the lower limit, not the limit you give! This is an original bug, dating back many many years, probably to when the controls were added! I'm amazed no one has reported it before. The signed versions work fine -- maybe folks have always used those -- they'd do the same job when the range of values never use the top bit of the byte/word or DWORD. Please download version 4.939v which is now available in the Download Links subforum.. Pete

Why? Why did you not just use the tools to investigate L:Vars, like I advised? That's the Mouse Macro logging. Why did you bother with that again after you already determined it didn't work with that aircraft? Do what I said in my earlier message. Pete

I just found this older thread where someone else had problems with Foxy programming and the Cougar: http://forum.simflight.com/topic/60759-cougar-problem-with-the-new-fsuipc-450/?hl=cougar Note this paragraph in the final message: "The Thrusmaster Cougar were programmed through his software FOXY, with 2 files, one is Joystick controls, the other is Macros controls. The controls are downloaded into the ROM of the joystick through software, and emulation for FS or Windows is then made. For some strange electrical reason (component dead or ROM program delayed), the ROM does'nt give any command yet. As soon as I have disabled the emulation, I have seen all my buttons recognized from FSUIPC, and programmable through it. So I have all reprogrammed trough FSUIPC interface, and everything is allright to fly FSX, now. So thank you for your help one more time . I have now to understand what is wrong with the memory of the joystick, perhaps to flah the ROM..., but nothing to do with FSUIPC. " Pete

Er, this is going in circles. Please read this slowly and carefully so you understand! If the buttons result in keypresses then they are not seen as buttons, neither by FSX or FSUIPC. They are seen as keypresses. In FSUIPC you assign keypresses in a different tab, NOT the Buttons and Switches tab! If there is no software running in the PC which is converting the buttons to keypresses, it must be in the firmware in the device.. In that case your device looks like a keyboard NOT like a joystick button device. I really cannot help you further. You either need to assign the keypresses, or find out whatever it is which is converting the buttons into keypresses. I can't do that for you. I don't know the hotas cougar nor this "foxy", but I suspect the device is programmable and retains its programming in its own memory. If so it would not matter if you weren't running this "foxy" at the time. The programming would still operate. If this is the case and you want the buttons to be buttons you'll need to reprogram it. Pete

I'll take a look tomorrow, but first can you please tell me the version number of the FSUIPC you are using? If it isn't the latest (4.939u) please try that first. Pete

So, you have some (Thrustmaster?) software running which is reading the hat buttons ad converting them to key prresses long before any sother software like FSUIPC or FSX can read the actual button presses. If you want to assign buttons in FSUIPC you have to remove that software. Or of course you can program the keypresses instead. Pete

XML gauges often use local variables ("L:Vars") for their switches and read-outs. As a quick check you can assign a button or kreypress to the FSUIPC added FS control " List local panel variables" (or similar name), and use it when the relevant panels are showing. It will list the L:Vars available and their current values. There is also a Lua plug-in provided (see the exmple plug-ins ZIP in your FSUIPC Documents folder) which will do more -- it will log /list the values in real-time as they change. You can control numerical L:Vars by assignment to macros. Details are in the Advanced User's manual. And you can read values from L:Vars by using a Lua plug-in. Pete

According to the Rgistry you still appear to have TWO installations of FSX-SE, see: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=E:\Steam\steamapps\common\FSX This is causing the installer a problem, You need to tidy up your Registry by deleting the entry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX Note that with a 64-bit Windows, the path will actually appear in Regedit as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 What are you seeing which states it is not registered? Check the contents of this folder: E:\Steam\steamapps\common\FSX\Modules There should be FSUIPC4.DLL, FSUIPC4.INI, FSUIPC4.LOG and FSUIPC4.KEY. (Change the Windows Explorer options to NOT hide extensions from you if you cannot identify them). Check that they are all there, and show me the FSUIPC4.LOG file. Pete

No, the throttle quad, via Windows device manager. Uninstall it and driver from Device Manager remove device, reboot, reinstall. If that doesn't help visit the CH-Hangar website. Pete

That's usually a result of those axes being deined in Windows as "digital" (i.e. on/off) rather than analogue. You'd probably need to uninstall ad reinstall. Otherwise it's a Registry editing job. There's a website called CH-HANGAR which will help. Er, I'm not sure CH's control manager is compatible with FSUIPC. From what I've heard you want to use one or the other. Anyway, if they are now fine, what is the remaining problem? Pete

The original offset dating back to FS98 days is 0C48, Did you check that too? In FSX & P3D, it derives from the SimConnect variable, "NAV CDI:1", and as the name and description in the offsets list implies, it is associated with NAV1, not necessarily also the GPS. Have you checked the HSI CDI needle value, offset 2F88. In FSX and P3D that's from the SimConnect variable "HSI CDI NEEDLE", so it may well reflect what the instrument should show rather than what the NAV / VOR signal tells it. Otherwise, sorry, Sorry, I have no ideas. You need to talk to someone who programs gauges to see what information they get. Maybe there's an aircraft design forum on AVSIM? Pete

If you assign in FS it tells you which button it recognised (it numbers from 1 to 32, FSUIPC numbers from 0 to 31). Have you never tried assigning in FS? Why did you switch to FSUIPC? Hmm. Seems like a general problem with the device. You need to find out what FS recognises them as -- it may actually be a program associated with the device which is interpreting the button presses and converting them into FS controls -- there are Thrustmaster, Saitek and GoFlight drivers which do that. I don't know your device nor what you installed for it. Er, that makes no sense. If FSUIPC doesn't see anything it cannot act on anything, no matter when they were "bound" (assigned?). I think you need to explain that much more carefully! I don't think changing disks or the registry wil have anything to do with it. It will be all to do with the drivers or other software associated with the device. Try unindstalling it completely, drivers as well, then reinstalling but without any of its own assignment software. SSD's are nothing to do with it. They are just disks. I've been using SSDs ever since they were rare and expensive. they are indistinguishable to other disks as far as all this stuff is concerned. You are chasing down a blind alley. Pete

That sounds like a useful program! Thanks for the link. System debugger? Hmm. I wonder what that does when you press F12. Thanks for all the info, and I'm glad you solved your problem! Pete

Not directly, that I know. Try pressing F12 and see if anything happens. Review your list of processes and services in Task Manager, try stopping any which might be responsible. For instance, Geforce Experience can assign hotkeys automatically to control its recording facilities. And there are many FS add-ons which use hotkeys. Pete

The only way I know that the "RegisterHotKey" function can fail is when that keypress is already taken as a hot key by another program. Pete

If the GoFlight software is being used, then it's a question for GoFlight. Not sure why you are posting here, this is support for FSUIPC and WideFS. FSUIPC only sees GoFlight buttons and switches if you install the GFDEV.DLL. That is also GoFlight software but bypasses the configuration in the normal GoFlight driver. I thought that the LGT was handled okay by the GoFlight software? Try GoFlight support. Pete