Pete Dowson

You posted this twice! I deleted the other one. I cannot help without any information. If an "appcrash" occurs there will be details -- in the Windows event viewer. There will also be an FSUIPC4 log file in the Modules folder. I need both, please. Paste into a reply here. Pete

Or, for a Hat assignment, assign to "Pan View". Pete

Why not just rename AFR-FriendlyD3D.exe to Prepar3d.exe? Or does that new file in turn need to load the original EXE? Pete

It sounds like the "Enter" key is being trapped by something in the Mindstar programming. Try using FSUIPC's logging (Buttons/Keys) to see whether your Enter key is being logged. Also try both the main keyboard Enter and the one on the numeric keypad. Pete

I'm afraid FSUIPC 3.81 dates back to April 2008 and has not been supported for a very long time! You need to update to 3.999. Pete

Ah, the problem is a failure in DirectInput: The last time i saw this it was due to an extra unwanted DLL in the FSX foolder. Here's what the user reported: "I searched for all Directinput8 files and found only one. It was found in the main FSX folder so I deleted it. I have no idea how it got there, my guess is it was tagged in with a freeware addon I installed at some point. I deleted it out and I can now get axis assignment information, as well as Button + Switches Assignments." Please check for this -- let me know. Pete

Hmm. Very strange -- FSUIPC uses the same methods, once it has identified the device. Is this the correct device? 0=T.Flight Hotas X 0.GUID={654E4AC0-8775-11E3-8001-444553540000} Are there any buttons on the device? Are they seen in FSUIPC's button assignments tab? Please edit the INI file, adding these lines to the [General] section: LogAxes=Yes Debug=Please LogExtras=x200008 LogButtonsKeys=Yes Then run FSX, go to the Axes tab and give each lever/axis one movement each in turn. And press each button once. Then close FSX and show me the FSUIPC4.LOG file. Pete

Please try 4.931. There was a bug in 4.93 and it was replaced within hours. since then everytime I try to open FSX the message as described in the FAQ post comes up and FSX will not open. By "will not open" can you explain, please. Does it crash or hang? If it crashes I need the details from the Windows even log. The is probably a different matter. For that I'd need to know whether a LOG file was produced or not. FSUIPC might be loading but having other difficulties. There should also be an Install log in the Modules folder. I'd need to see that too. But before anything please install 4.931. Pete

I assume you actually moving the lever you wish to assign to? Does FSX see your axes? Please show me your FSUIPC4.INI file from the Modules folder. You can paste it here. Pete

If you use an EXE with a different name, then all of the FSUIPC files also use a different name. This is a facility used to enable different configurations to be used with one install, which is what FSUIPC assumes you are doing. Look in the Modules folder. You will see FSUIPC4.INI, FSUIPC4.LOG and FSUIPC4.KEY. Those files are only used if you run the proper Prepar3D.EXE. You may also see another .LOG and another .KEY which include the name of the other EXE. You will have to make a copy of your KEY file and rename it in a similar fashion. Pete

It works fine here on both Academic and Pro versions. and the problems before weren't hanging but a definite crash (but only on some configurations with registered installs). Can you supply any more details at all? Like whether FSUIPC4 creates a log file? If so please show it to me. Pete

The "ThrottleN_set controls are the oldest ones supported by FS, and the only ones which have a reverse thrust range. The idle is at 0, with negative values being reverse. FSUIPC uses them for the separate throttle calibrations unless you set "No Reverse Zone" in which case it may use either variety by INI file option. Some aircraft add-ons don't like the old controls. FS only provides assignment to the Axis_ThrottleN_set controls. Their IDLE is down at -16384, no reverse range at all. The same sort of considerations also apply to mixture and prop axes, though the results of negative values for those depends very much on the specific aircraft (eg conditioning settings and prop-based reverse thrust and feathering). Pete

I did that and found mention of an IE option "Allow Programmatic Clipboard Access" Make sure that is enabled. I've been a Firefox user for years, just changed recently to Chrome because it's faster. I'd never go near Interbet Explorer again, i had nothing but problems with that. Pete

Sounds like you are using a recent version of Internet Explorer. Seems there's an option somewhere you need to select to allow pasting. Hopefully you can find it. there's another thread explaining it somewhere, otherwise someone might come to the rescue. If not I'll try googling for an answer. Pete

The released version is 10437 which I got n the 14th when I returned. The hotfix is 10438, but it is buried deep in the Forums. LM have only just pinned it to stop it sinking without trace. They replaced all of the DLLs even though most were actually not changed. Trouble is I still have to check each one FSUIPC depends on, just in case. Pete

Let me know if you can get it to fail that way and I'll work out what logging parameters you might try. I'm still doubtful that it will show much. WideClient itself is very protective of itself, trapping errors (even access violations) and logging them. It just can't trap stuff deep in Windows, especially not in the Networking stuff. Pete

Okay, thanks. I just felt that an explanation was warranted. Regards Pete

Hmm. I'd like to what that program is doing. Can you set things up so you ONLY run ProSim737, no other clients? Then it might just be worth doing some logging. Of course that might be a waste of time too if it never fails that way. Pete

Okay, so if it consistently works when the MCP connects after the other, try to set the timings and load order to reflect that. Maybe even put some of the other loads between the two? Ah, wait a minute. I see that the order at the start WAS the same in the "OK" log. It was just that you reloaded the MCP much later (0ver 10 minutes later, in fact), so it might be a red herring. I think it must be some problem occurring when several programs simultaneously try to do things on the network. Do other ProSim users have problems? You could enable more logging in WideClient, but with 8 clients it would be a massive log and is unlikely to show anything useful because the crash is deep into Windows code. Pete

As of today the currently supported version is 4.931. FSUIPC4 is not FSUIPC3, it is a different product which involved a great deal of work (and still does, with Prepar3D developments). FSUIPC3 dates back late 2003, nearly 11 years ago. And all updates and support was included in the original price all these years. Even FSUIPC4 is now 8 years old and the same level of support has been maintained for that. Same for WideFS6 to WideFS7. You need to go to SimMarket and purchase new keys. I think you will find it is worth it. Regards Pete

No, not without information. FSUIPC4 log file, Windows event data please. Pete

Those log lines aren't registering launches of programs, since they aren't actually being launched by WideClient. They are registering the point where the application connects to FSUIPC via WideClient. So the crash could actually be when ProSimMCP starts. However, your comment does seem a little odd in relation to this log because the order shown is ProSimMCP first, then ProSim737. Should they be the other way around? In the example without the crash they were! If you were loading these programs by WideClient parameters you could insert delays between each one loading, experimenting to get it right. Can the loader you are using do that? It might be worth trying to get the MCP module starting a few seconds later than the main ProSim module. Pete

FSUIPC treats them the same. 8.1 is merely an increment over 8.0, like the SP's on the Win XP, Vista and Win7 version(s). he warnings don't really matter in the end, but they are definitely occurring because there are entries in the Registry pointing to a non-existent P3D v1. It is looking it here: SetupPath="C:\Lockheed Martin\Prepar3D\" because of the Registry entry at: HKEY_CURRENT_USER\Prepar3D Parameter"AppPath" ... >>> OK! FOUND Prepar3D! <<< ... Pete

Please use 4.931, now available. Pete

Okay. Windows does funny things here -- it translates some of these keys. In that case the one you need to delete it HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D but check the HKEY_LOCAL_MACHINE one again, please, because it might get reset there when you are the current user. I've always been confused over when it does what in this area. No. That part is where it is trying to locate the now deleted details for your P3D v1 installation -- as pointed to by the entry you've not yet deleted. It's the last section for v2, and that works okay. Pete