Pete Dowson

Ah. It'll be disguised by the "WOW" system which is new in Win 64. Try HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 That 'Wow6432Node" is a way of Windows mapping 64 or 32 bit programs seaparetly to what they think is the same Registry key. Very annoying! So, are you saying you NEVER EVER had FSX installed, or you did and deleted it without properly uninstalling it from the Registry? If the only FSX.EXE you have is on the desktop, then that's where the Registry should say FSX is installed. How did the Registry get to point to P3D for FSX? Are you fiddling it or using some horrible migration tool? What's this "actual one"? I have no idea what you are really seeing and doing, I need the proper Install log for the CURRENT installer, 4.939i. Please find that, or, if you think it isn't being saved, save it yourself using the menu on the on-screen log. Pete

It only needs an Installer update. The actual DLL isn't really affected. But it'll need to wait till I've been able to also check the imminent FSX-SE beta release. Pete

Newest? How do you work that out? Installer for FSUIPC4.DLL version 4.937 4.937 is very old and unsupported. You need 4.939i (soon to be 4.939j). And the log shows that the path for FSX actually points to your P3D, look: INSTALLATION FOR FSX: SetupPath="D:\P3D\" Since FSX.EXE won't exist in a P3D installation, it isn't surprising you have a problem! If you don't actually have an FSX installation, then how come you have Registry entries saying you have? You'll need to delete the section in the Registry for key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Pete

Okay. Good then. Pete

Well normally you'd install it into a folder, eg D:\P3D. I've never heard of anyone not doing so. A lot of add-ons like placing their products in a folder OUTSIDE of the simulator folder, so, for example D:\Aerosoft. They cannot do that on your set up. So either they will fail during installation stage, or, if you are lucky, allow you to install on a separate drive. Or maybe they will allow you to install INSIDE the sim folder. Maybe it'll all work, it just all seems a little odd. Pete

You are reading an Unsigned DWORD (32-bit integer). If you actually refer to the Offsets list, as of course you should, you will see that it is a character string, not a binary number! After all it may also contain the airline prefix which is not numerical. Please do use the documentation supplied. Pete

What, in D:\, not something like D:\P3D? Doesn't sound a good idea. I think a number of add-ons will have problems with that. The one installer installs into FSX, FSX-SE, P3Dv1 and P3Dv2, in the one session. You don't need to run it 4 times! No, the Installer needs to install it in each and every instance. You don't! You let the Installer do it. Please read the Installation document included in the ZIP! Pete

Haven't you tried it? The installer will grumble, but the DLL looks okay, though I've not had a chance to delve into it fully yet. I only saw 12945 was available last thing last night, just before retiring. Pete

How can your Modules folder be in the root of drive D:? It must be within the FS folder!!! If you want help with anything to do with Installing, I need to (a ) be told the version number, and (b ) see the Install Log. That is why a log is produced, to resolve installation problems quickly and easily! In that case you obvious have FS or P3D still running, probably in the background with no Window. Check in Task Manager and terminate it. There is no way any program can ever be replaced when it is actually running at the time! Pete

Hmm, I've really never heard of such a problem then. There are lots of folks with this equipment and no such problems. Are you sure the drivers are installed correctly? Perhaps you'd better show me your FSUIPC4.INI file. Paste its text content into a message here. One question before that. When you click "rescan", what happens? If nothing is jittering then it should show nothing until you move a lever. Maybe your main quadrant is jittering so badly that the addon one never gets a look-in. If so you can use the Ignore button to get past those. Pete

In that case there should be no difference in FSUIPC, as it uses exactly the same method reading the device as FS. Perhaps it isn't being given an ID number. I've heard of that problem from others, though I assume it must be new (in Win8.1 perhaps?). There is a utility you can use to assign an ID. See this thread http://forum.simflight.com/topic/78816-rudder-and-brake-axis-not-recognized/ Pete

If the mode switch is seen also as a button or two, you could program 6 x 3 = 18 different actions by using the conditional facilities in FSUIPC. See the button programming section of the FSUIPC Advanced User's guide. I'm sure others have done this before. Take a look in the User Contributions subforum, or do a bit of searching. Pete

Why did you post a support question in the Download Links section? That's, oddly, for download links. You are lucky I notced your question. What are modes 1, 2, 3? Pete

Does anything else (eg FS) pick them up? Check especially the calibration facility in Windows (game controllers). Pete

Have you checked for ideas on the AVSIM CTD forum? http://forum.avsim.net/forum/262-crash-to-desktop-ctd-forum/? Just search there on the word stackhash. You'll find many suggestions and potential solutions. Pete

I'm pretty sure that this one is fixed in the next FSX-SE release. The Beta proved pretty well bomb-proof for both TERRAIN and G3D crashes. But if, when it is released, you still get the error, the details need to go to DTG, via the Steam FSX-SE forum, not to me. Whilst FSX-SE is still being developed and fixed I am not going to attempt any more patching. The next release may be pre-released as an Open Beta -- i.e. for feedback.If so you won't get it then automatically, you'd need to opt in. Look out for details within the next week or so. Pete

Right. Terrible coincidence then, and easily leading to misunderstanding. Also the "HALT" you refer to is always referred to as a "hang". I've never heard it called a halt before! You said:: so pretty obviously either something in or associated with FS has become corrupted, or something else you've installed is not right. I don't think the hang is anything specifically to do with FSUIPC button assignment. The fact that it can happen with no button touched proves that. Also, it looks like it must be a CRASH not a HALT or a HANG, else you'd not get the AppCrash data. Hangs are notorious, as you never get any information at all. The AppCrash details say it's a Stackhash problem. the only time I had those regularly was down to a faulty memory module, as I found by removing each in turn. I suspect they can also be caused by faulty or corrupted drivers or presumably other system hardware. You don't say whether using buttons programmed in FS instead of FSUIPC generates the problem, but as you also say that the system can be used (normally I assume) for a longish time before it crashes then either way it would be difficult to narrow down even if you did. So, sorry, I don't know any way to help you. It certainly isn't FSUIPC, and I doubt that it's FSX, but you could try reinstalling things. Start with the joystick devices. Uninstall them using the Device Manager, including drivers, then re-boot with them connected so that the drivers get reinstalled. If that doesn't help, try video and other drivers. Finally, just to eliminate FSX corruption, FSX. After that I'm afraid it might be a Windows re-install. I've had to go that far -- not recently, thank goodness. Pete

That is the normal way in Windows 7, and I have always replied in that vein when asked. The above is new to Windows 8 and apparently works alongside the changes you mention. That's why it became a FAQ.entry. Pete

Sorry, FSUIPC can only trap and fix one very specific G3D.DLL crash in FSX or FSX-SE. There are many others which cannot be so trapped. . Since you are using FSX-SE you'll probably find this error is already fixed in the next version (currently in Beta testing)., but nevertheless it would be very worthwhile reporting these details to DTG as they are very actively trying to fix all these things. It may just be one they missed. Regards Pete

Key press 80 is "P" which is normally assigned to PAUSE toggle in FS. And control 65561 is Pause Toggle, so should I assume by "FSX Halts" you really mean "FSX Pauses"? If this is what you mean, and if it is being activated without you really pressing the assigned button, then evidently the button press is being seen nonetheless. You have either a button stuck, or one with bad connection and so causing jitter. Or is it a sheer (and very unfortunate) coincidence that both of the examples you give are for the Pause control? With button logging enabled you would be able to see if any buttons were being apparently pressed without any action on your part. If you temporarily run FS in Windowed mode, and enable FSUIPC's console log, you will be able to see this in real time, on screen. If you want me to check things like the Log and INI files, you should paste their contents into your message here. Just use the <> button above the edit area to enclose the text for pasting. Not sure why you mention an AppCrash file. What is crashing? Pete

I don't think there's any way of telling FS to save a different position for that window. But try re-positioning it, then saving a flight. Theoretically it MAY just get restored to the same place on a flight reload. But don't hold me to it. If the ATIS and other messages can't be so re-positioned, then neither can these! Pete

Who says SimConnect values, directly reported by FS to FSUIPC, are "wrong"? Surely your add-on reported values are much more likely to be wrong! FSUIPC cannot "invent" values just to please you! It simply reports what it is given, no more, no less! Pete

You are making a mistake. All three parts - name. email and key MUST be exactly correct. Registrations are NEVER cancelled, unless you have distributed your key irresponsibly! Pete

Why not use the WidefS option, then? Okay. Hope you find a solution. Unless a port name can be found, there's really no solution. I'm sure serial port support can't have been withdrawn completely in Win8! Pete

So, does Win8.1 not support serial ports -- COMn etc? Maybe it does but there's no way to ennumerate those from the Registry? Have you tried entering the port explicitly, for instance in the INI file? If your device is a USB type device then maybe you can use the USB type string name for it? FSUIPC only needs to be able to use a device name in its opening call to Windows. All the comms code is standard Windows API. You just need to determine the name of the port you are using. Is there a Device Manager in Win8.1 (usually part of the System Control Panel applet)? I usually work out which COM port something is connected to by watching the list in that whilst connecting/disconnecting the device. Pete