Pete Dowson

No, those are recoverable errors, they are symptoms, not a crash. The crash is what Windows reports, and there will be full identification of the crashed module (which may not even be FSUIPC4) and the address and type of crash (error code). You can view crash data, and copy it for pasting, in the Windows event viewer. Pete

Try not running it. I still need the error information. Were the DLLs and EXE you copied back copied out when things were working fine? Pete

One other thing. Does UT2 install any DLL (check DLL.XML)or is it just an EXE? Try not running it, in case it's some sort of hooking interference. I really don't know UT2 very well, though I know it works fine with FSX and FSUIPC. Pete

BTW, you didn't say you copied ALL of the DLLs, only two of them. That isn't enough. Pete

Because most things don't do the things FSUIPC does, especially not placing hooks into the code. Exactly. And what was the last change you made? It wasn't me who changed things. You need to get back to when it was good. The best I can do is look to see if I can disable parts of FSUIPC -- maybe functions you don't need -- but I'd need more information. Like the Windows crash data, from the event viewer. Pete

I'm afraid I cannot "fix" a broken P3D installation from here. To save re-running installers, I tend to keep a backup from which I can just copy over all the correct DLLs and EXEs. Try that if you have one. Pete

You should not need to reinstall everything. Just P3D. Don't delete anything beforehand. Pete

My email is quite well known It is petedowson@btconnect.com. Pete

But something is evidently wrong with your P3D installation. Try reinstalling. Pete

Whilst renaming the EXE will certainly cause problems, I see from the log that FSUIPC is correctly recognising the EXE as P3D 2.5. The problem appears to be that your P3D installation is actually corrupt. I don't know what UT2 did to it, but I think you need to reinstall, or at least restore ALL the DLLs and the EXE. That's another big problem. Your registry is pointing to your P3D installation as an FSX one. See here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=E:\1 Simulator\Lockheed Martin\Prepar3D v2 Oh, yes it does, but it is hidden in the 64-bit to 32-bit compatibility system which your 64-bit Win7 uses. The full path is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 32-bit programs are unaware of that RED part -- it's an automatic compatibility implementation in 64-bit Windows. Pete

No, but it won't be due to FSUIPC, so I think you are in the wrong Forum. Have you tried the AVSIM FSXforum? Pete

You have omitted the beginning of the log, which is the part which contains the critical information!!! Please NEVER do that. But my guess is that FSUIPC thinks you are using FSX not P3D. What version of FSUIPC are you using? Have you tried the current one, 4.939t at all? Pete

The installation log shows that FSUIPC4 installed fine, no problems, into your FSX installation FSUIPC4 does NOT install into FS2004 -- you need FSUIPC3 for that! Perhaps you ought to describe the symptoms of your problem, rather than just assume it doesn't install!? Pete

Replied to already in separate posting. Pete

Just assign to <custom control> and enter the control number in the space provided, eg x23432. Pete

No attachment seen ... Well that most certainly shouldn't happen! It should only be active when the FSUIPC offset for VAS is updated, which is once every 10 seconds (though you can make it up to 1 hour in the latest FSUIPC update). Perhaps you should show me the Lua program itself -- paste the contents into a message, don't try to attach texty files, they are better pasted. Pete

Sorry, I don't know this "VAS monitor". The memory check which operated in FSUIPC is only disabled by setting OOMcheck=No in the INI file before FS starts, but I don't see any point in that. What are you trying to achieve? Why do you want FSUIPC to stop measuring memory usage? If you mean you are using some Lua plug-in to display the memory usage on the Client, then, yes, you can program it to hide its screen or display it on some trigger or other. Is that what you want, just to hide a display? Please see the many available functions in the Lua libraries provided. I'm afraid this'll be my last answer for over a week -- back on June 18th Pete

Any macro, mouse or otherwise, can be triggered using the lua library ipc.macro function, as documented. Pete

Did you try FSUIPC 4.939n installer first? I'd like to know that it worked okay in your situation? The registry cleanup isn't terribly easy. I think FSX-SE puts some sneaky marker in there somewhere to tell it whether it's running free-standing or side-by-side, and that's the one you'd certainly need to find. I have one PC system with it free-standing (after a Windows re-install) and one side=by=side. Need both for testing! ;-) Pete

It looks like SimMarket updated one line to mention P3D, but forgot the later one. It's been like that for years, evidently no one even noticed before you. But WideFS7 works with P3D and has done since it first appeared (also ESP before it). As I said, there's no difference as far as WideFS can tell. All of them look like FSX in any case. Right. WideFS7 + FSUIPC4 is for FSX,FSX-SE and P3D. Maybe, but I'm on holiday soon, till June 18th. I think someone was working on a utility to edit profiles. In FSUIPC the facilities are in menus, as documented. No pop-ups (ugh, horrible thought! ;-) ). Regards Pete

Unfortunately, that "corrects" the path for some programs, but it will surely mess it up for those programs whose installer already understands the difference between a stand-alone and a side-by-side install of FSX-SE. So you've now got conflicts. The FSX-SE installation will be running as if it is side-by-side with FSX, with its own FSX-SE.CFG rather than an FSX.CFG, which it would have if it were stand-alone. AND the folders for the CFG and the Scenery CFG files will be different too. I have modified FSUIPC's installer several times to try and cope with this sort of mess which folks seem to make in their desperation to install programs which don't understand what is happening. Unfortunately you have been trying to install an older version of FSUIPC -- 4.939e. The earliest currently supported version of FSUIPC4 is 4.939n, which should, I hope, cope with the mess you have. I cannot guarantee that, but until you try it I won't know. I tried to cope with all the combinations folks are cobbling together, but I can't swear they are all covered. Even if the correct version of FSUIPC installs okay, I wouldn't be surprised if other programs you try to install later have problems, especially if they need to find the SCENERY.CFG or FSX.CFG files! Yes, but in a free-standing install of FSX-SE it would be in C:\Users\FlightSim\AppData\Roaming\Microsoft\FSX\fsx.CFG This is part of the mess you have arrived at. The current version of FSUIPC4's installer actually tries all 4 combinations: C:\Users\FlightSim\AppData\Roaming\Microsoft\FSX\fsx.CFG C:\Users\FlightSim\AppData\Roaming\Microsoft\FSX\fsx_se.CFG C:\Users\FlightSim\AppData\Roaming\Microsoft\FSX-SE\fsx.CFG C:\Users\FlightSim\AppData\Roaming\Microsoft\FSX-SE\fsx_se.CFG each of which can arise through separate ways of messing up the registry! Regards Pete

Opus FSI doesn't use WideFS or FSUIPC, it has its own networking, but Flight Commander would use it. Before buying your software I have read that it is only for FSX. A version is planned for P3D soon? Or the spec about only for FSX is outdated and I can run WIDEFS on Prepar3d? The Server part of WideFS is actually built into FSUIPC4, for efficiency, and FSUIPC4 works on FSX, FSX-SE and P3D (versions 1.4 and all 2.x versions so far). So, yes, WideFS works will all those. The Client part of WideFS (WideClient) was actually written for FS98 and probably still says it is an "FS98 Eliminator" in its title. But it is universal, not caring what FS version is at the other end. It just relies on the Server. Pete

You evidently have some conflicting or additional assignment, possibly in FS but more likely in FSUIPC. Hat switches are programmed as axes for "pan view", but FSUIPC also allows them to be programmed as 4 or 8 buttons. So, check the Buttons & switches tab in FSUIPC as well. If neither of these things I can only think that the hat operation is also causing one of your other buttons or switches to operate. To check that, try enabling Button logging in FSUIPC and look at the log when the problem occurs. If you also enable Event logging it would show the actual FS event or control being sent. Pete

Well, it's only about one page in the User Guide. You never need to "know" it all, just know that it is documented, as I said when I mentioned it. Anyway, the main problem was your use of 4.939p instead of the update I provided a link to. Paul's method of writing all 24 bytes at once is correct too. It's only when using separate writes that 86A0 needs to be last. Pete Pete

Your log shows you are using version p still!!!! ********* FSUIPC4, Version 4.939p by Pete Dowson ********* To use a later version you have to put it into the Modules folder BEFORE running FS!!! Additionally, you are monitoring the offsets as type S8 (8bit signed) when as you surely know they are 32 bit floats (FLT32). Pete