Pete Dowson

Please see the FAQ subforum thread entitled "fsx fails to run after fsuipc4 first installed/". BTW you should have started a new thread as you've appended to one entirely unrelated. Pete

I'm very sorry, but I really cannot support PFC's systems myself. I've no idea what sort of hardware you have (you don't say, in fact), but it is really PFC's job to support it. The PFC driver certainly works okay and is in continuous use here in my PFC 737NG cockpit -- but with up to date Project Magenta modules and FSX, not FS9. You do realise that FS9 is now nearly 11 years old? I'm not in a position to help a lot with FS9 these days. Stab trim is called elevator trim in FS, and you can assign a rocker to elev trim up and elev trim down, but you say that works, so I don't really understand youer question I'm afraid. I don't know what "P/A" is -- do you mean Autopilot (A/P)? I can answer specific questions on FSUIPC or the PFC.DLL, but I can't support hardware systems which I know nothing about. Try PFC technical support in the first instance, please. Regards Pete

There's one other thread which mentions something similar as a solution: http://forum.simflight.com/topic/73502-fsuipc-access-violation/ The entry there is: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers delete the key "C:\\Games\\FSX\\fsx.exe"="$~ RUNASADMIN IgnoreFreeLibrary<FSUIPC4.dll>" so it seems pretty similar -- and it was also with Windows 8. It was written up in the FAQ subforum as thread "Possible solution for FSUIPC access violation". Sorry, I should really have remembered that one. I've now made the Installer delete any entries in that Registry Key mentioning FSUIPC. There shouldn't be any there in any case. Version 4.921f of the Installer is now up. Thanks again, Pete

Yes, of course, you can assign buttons or keypresses to Increment and Decrement all those sorts of things. Look through the drop down assignment lists in FSUIPC, or search the List of FS controls which is in your FSUIPC Documents folder. Pete

Hmm. Isn't there something like that in that FAQ thread? I wonder how it gets there? Maybe I should make the Installer remove that, if it is there? Thanks for solving it, at least in your specific instance. I don't know if that applies to many or most. Regards Pete

Not that I know of. I suppose you could use ADF CARD SET with suitable parameters (or even an axis assignment). Maybe a Lua plug-in could process your button presses and accelerate it that way. Alternatively just assign two or three incs or decs to the same button presses. Pete

Hi Stefan, This is the entry point ("DLLStart") from SimConnect. So I believe what you are seeing is not specifically anything to do with Win8.1 but just the same SimConnect bug that affects some folks, where SimConnect's trust checking mechanism runs behind the execution part and the latter jumps into the start place which is not yet actually loaded. Please see the FAQ subforum thread entitled fsx fails to run after fsuipc4 first installed. The title of that turned out to be a bit misleading. The problem is a timing issue and was accepted by Microsoft as a bug right since the original RTM release of FSX. They managed to reduce its frequency in SP1 and SP2 but were still trying to locate the thing when they got closed down. Oddly, it affects some folks’ systems on almost every release, but most others never. If I could actually reproduce it even on one of my 6 FSX systems I might have a chance to devise a work-around, but it has never even happened once here – just as it hasn’t on many other’s systems. The only answers I have ever come up with are all on the thread. However, If this problem is consistent on your system, perhaps I can use you to experiment with small changes in the start-up part (DLLMain). I can't do anything with DLLStart because the crash is actually in SimConnect's call to that routine. but DLLMain should be getting called by Windows' DLL loader before that. As a start, I've emailed you a little updated version. See if it helps at all -- just a 1 second "sleep" in the DLLMain routine, to try to allow SimConnect to "catch up". If no joy I'll try 10 seconds (ugh) and if that helps, wind it down again. If delays here make no difference I can't really see anything else I can do at all ... Regards Pete

Okay. Download 4.921b from the Download Links subforum. Pete

Well the path to where your fake FSX was is still in the Registry, because as the log clearly shows, it is giving the program this path: SetupPath="D:\Program Files\Microsoft Games\Microsoft Flight Simulator X" What can happen with WinVista and later, when a 32-bit program is installed in "Program Files", is that it automatically diverts the Registry paths to a complicated "WOW" registry entry. It's all to do with its protection of Program Files folders from being writtten to --and allows it to present a different folder with the same name. It's because of all that nonsense that most FS users have learned to never install FS in the default Program Files locatin. I always install in something simple like C:\FSX and C:\P3D. So just search the Registry for Data which says "Flight Simulator X". When you find the entry showing that complete now non-existent path, remove both the entry and its parent, the one ending in the/10.0. As far as the FSUIPC4 Installer is concerned, I should have the new version up for download in a couple of hours at most. That's nothing to do with this. Just leave it alone if you need it. Start Menu items are only shortcuts in any case, nothing to do with any of this. Pete

Thanks. And it does show, as I surmised, that your registry cleaner did NOT clear the reference to the FSX Install location, which is why the Installer still had the same problem after you thought you had deleted everything FSX: So, you will either need to delete that entry, or wait for me to release the 4.921b installer some time tomorrow. Actually, I would recommend you delete the entry in any case as otherwise it will certainly mislead other installers in the future. Regards Pete

It isn't FSUIPC but a bug in SimConnect, which is worse in the original "standard" edition without the updates SP1 ad SP2 both installed. There are ways to conquer it but it takes parience and persistence. Please refer to the FAQ subform thread "fsx fails to run after fsuipc4 first installed/". It seems to only affect some folks systems, and I've never been able to reproduce it here on any system. Microsoft knew about it but FSX was closed down before they managed to fix it, as they found it hard to reproduce too. Pete

No, that is the run-time FSUIPC4 log. The install log is the one you showed in a picture earlier. That showed the Registry entry pointing to FSX as being the "SetupPath" parameter in HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator\10.0 Regards Pete

Sounds like at least one of the buttons on that quadrant is both assigned to "pan up" and stuck on or repeating. Use the FSUIPC logging to see what is going on -- check the button and event logging options. The data goes into the FSUIPC Log file, in the FS Modules folder. Note that Saitek uses FSUIPC without permission and without license on FS9, as they refused to pay an agreed fee for this years ago, so I'm afraid I am not disposed to support their devices. So if you want more assistance I must suggest you use their support forum. Sorry. Regards Pete

No, offsets 088C and 0924 ARE the actual throttle values in FS and writing to them cannot be disconnected. That is why i added offsets 089A and 0932, which FSUIPC itself copies to 088C and 0924, if allowed to by bits in 310A. That's the whole point! Why have you suddenly reverted to direct throttle control if you want to be able to disconnect? Pete

The symbol "~" is not correct here. You want "not equals to" which is ~=. I see it was my fault, a typo in my original (now fixed). You'll see in a few lines before the use of ~= for "not equals". Pete

I've worked out a way of coping with this odd situation and will fix it in the Installer tomorrow. It will be version 4.921b, which also copes with P3D V2 as and when that is available to you. Regards Pete

That makes no sense. Please show me the Install log for that. I found the reason for the problem. Because of the false non-install of FSX the installer still believes there is an FSX there. The part that does the registration actually creates the KEY file in the Modules folder of the first sim it detects -- in this case your false FSX. It then copies that file to the ESP and Prepar3D installations. The problem is of course that there is no Modules folder because the installation is not a complete one and the FSUIPC installer refused to complete the FSUIPC4 installtion phase. I found all I had to do was to fool it even more than you did, by simply creating an empty Modules folder in the false FSX folder. Then it all works as it should. I think your registry cleaner did not destroy the pointer to the FSX folder -- the Install log will show this. If you had not been so hasty the solution I mentioned above would have been your easiest way. Now I suspect you need to use Regedit to remove the FSX entries properly. The registry path you need to find and remove is shown in the Install log. I'll have a look at improving the FSUIPC Installer to deal with this strange situation, but I cannot do this at present as I am still working on the changes for Prepar3D version 2. Regards Pete

But is there one in the Prepar3D Modules folder? I'll try to check here, but it seems that to fool one installer to "work" you fool others into failing. I just don't know why at present. Pete Pete

I'm still not clear on where the problem lies. You have not really described it. So, please, to clarify: the problem is that you Register but it still says it is unregistered? Is this so? Can you check the P3D Modules folder for an FSUIPC4.KEY file please? If it isn't there, can you check for it in your Documents folder? Do you run P3D in any sort of "compatibility" mode? The business with the "fake" FSX installation is not so relevant, really, as you can see the Installation proceeds and copes with the P3D installation okay in any case. But why did you not only fake a P3D EXE as an FSX.EXE but also fiddle the Registry to point to it as a genuine FSX installation? Surely all the SDK installer wanted was an FSX.EXE you could point it to? Regards Pete

The driver I wrote replaces all the software CS supply. It allows me to do additional things with some of the switches which CS didn't bother to program because Project Magenta's pmSystems doesn't use them -- like most of the toggles and 3 way switches in the left hand column, and the pressurisation control bottmo right. I'm not using pmSystems but other software not available generally. The modifications included wiring up some of the lights and switches not actually wired by CS and routing them through Leo Bodnar control boards, again to my own driver. The complete set of changes is too numerous for me to list and I won't try -- I'd have to open it up again and look at them all again because it dates over three or four years now. Some of the original changes were actually done by the UK reseller of CS hardware, who has since completely discontinued his relationship with that company. I really have never had direct dealings with the original firm in Germany. Oh, I also made my own driver for the aft overhead from Sismo, and of course all of the other cockpit hardware from PFC. I simply like to have full control over every switch, gauge and inidicator! ;-). But all my software works together. It isn't something which could apply piecemeal to other folks' installations. In fact even most of the main PFC parts are unique, a combination of modified original parts and one-offs they did for me. The only modifications I really still need to do at some time are: 1. Replacment of the duct pressure gauge with a dual needle one 2. Replacement of the cabin pressurisation gauge with a dual needle ne 3. Hinging the front nose cover (under which I have several controller boards and 4 mini PCs) to make access a bit easier The first two are very difficult as the CS gauges are effectively parts of boards doing other things -- and also because the only dual needle gauges available (eg Flight Illusion) to replace them are too large for the space and cutout available. In both cases, CockpitSomic had promised these as enhancements to be available later, and these promises, which I believed, were part of the reason I went with CS. Very disappointing! The third is something I may do soon with help of a friend who is more practical than I! Regards Pete

WideFS is ony for linking applications to FS across a network. Why are you connecting the multipanel on a different PC to FS? No. FSUIPC 4 and WideFS7 are most certainly for FSX and Prepar3D, NOT FS2004. For FS2004 you need FSUIPC3 and WideFS6. Saitek support seems to be very poor, and they are als not on my list of companies I care to help as they refused to pay an agreed fee for the use of FSUIPC in FS2004 days. As far as I know, for FSX no Saitek equipment uses or needs either FSUIPC or WideFS. I think you might hasve wasted your money. Regards Pete

No. The "toggle master alternator" control will ignore the parameter. All Toggle controls do is toggle. If you want a definite on or off action you'd either have to control is by writing to fSUIPC offsets, or at least determine its current staste by reading FSUIPC offsets. The offset list is provided in your FSUIPC Documents folder. I just searched for Alternator and came up with:offset 3101, a 1 byte offset. So you could try: ipc.writeUB(0x3101, 0) -- turn alternator off ipc.writeUB(0x3101, 1) -- turn alternator on "UB" here means "Unsigned Byte". Other types of values have their own abbreviations as described in the Lua library documentation. You'll find similar solutions to most other toggle controls. Pete

The only error appears to be that you have a Prepar3D.EXE version 1.4 renamed as FSX.EXE and residing in the Registry-confirmed installation path for FSX. Naturally FSUIPC's installer does not like a version of FSX.EXE called 1.4.4747.0! I've no idea why you are doing such a strange thing, but at least it doesn't throw the FSUIPC installer as It then goes on to do a successful install of FSUIPC4 into Prepar3D proper, as confirmed by the message you even showed, and by your showing of the options screen. So, what is the actual problem you wish to report, as you've not shown one so far ...? Pete

You appear to have posted the same question twice. See my earlier reply. Pete

089A is throttle 1 control and the disconnect bit in 310A is bit 6. Similarly 0932 is throttle 2 and the 310A bit is bit 7. You are confusing the "all throttles" assignable control (AXIS_THROTTLES_SET or THROTTLES_SET) with direct individual control via offsets. I don't understand your script at all. Where does it show you controlling the throttles via offsets 089A and 0932? Well it does work because it is in use by many applications, including in my own cockpit. Sorry, but many of the provisions in those columns simply haven't bee updated. Regards Pete