Pete Dowson

The correct SCENERY.CFG is always in ProgramData, just as it is with FSX. That's where MakeRunways is looking for it. What does your "runways.txt" file log say? Thanks Thomas. Hopefully the OP can clarify in a similar way. Pete

Sorry, I still don't understand. What on Earth are you doing loading FSX.EXE "from Prepar3D". Surely you need to run FSX from its own folder, not "from Prepar3D". That makes no sense to me! And what do you mean by "legacy mode". I don't understand that either. Pete

Posted twice for some reason? See reply to earlier one. Pete

What version of MakeRunways? Older versions don't understand P3D. If the P3D folder a normal P3D folder, without some migration tool being used to change names and so on? Didn't MakeRunways make a log file, called "runways.txt"? If so, see what that says, as the beginning. It needs to be able to find your SCENERY.CFG file. Pete

All that happens which you select the FSUIPC menu item is that FSUIPC asks Windows to open up a standard dialog. If it doesn't appear it means something wrong with Windows -- usually an old or bad video driver install. Try switching FSX to Windowed mode (ALT + Enter). Then try it. If that works it will definitely be a video driver problem. Pete

My name is DOWSON not DAWSON. The current version of FSUIPC4 is 4.939e, not 4.938e. There's no way FSUIPC itself will affect the flight characteristics of any aircraft. What do you mean by "set weather off" in any case? What are you using FSUIPC to do with the weather? Pete

Your problem is all due to a corrupt WX file being loaded, or a corrupt wxstationlist.bin file. All you are doing by setting FSUIPC's weather read interval to zero is telling FSUIPC not to even ask SimConnect to read these things. The files are binary and unchecked, so when read they can play havoc inside SimConnect and WEATHER.DLL. Just delete your .WX files in your Documents folder (where your flights are) -- they are not needed in any case when using a weather program -- and also delete the wxstationlist.bin file.(in the same folder as your main P3D CFG file) -- P3D will make another copy automatically. Pete

The only way that sort of thing can happen is though multiple assignments of that same axis, probably both in FS (P3D?) and FSUIPC. If you assign in FSUIPC you MUST disable controllers in FS (P3D). Why can't you assign in P3D? Have you reported such a serious bug to L-M? Pete

I don't have or use any PMDG aircraft and I am not on any mailing list of PMDG so I wasn't aware of these until recently, when another PMDG user kindly sent me the details. I will take a look as soon as I get time, probably later in the coming week. Pete

Sounds like you are using Windows 8? See all the other user problems with Win8! Not sure why you ask this here though, this is FSUIPC Support, not FSX Support. There are answers around. Check for instance post #4 in this thread: http://forum.simflight.com/topic/78814-paid-version-of-fsuipc-p3d-controller-issues/ Pete

There have been many things which caused Prepar3D to hang on exit, like that, and, yes, with no Window showing. They appear to have eliminated most of them. With FSUIPC the only thing I know of which might possibly still do it (though it is very unlikely) is if some Lua plug-in was doing something critical at the time and its thread hung pending so action which then never happens. And you should be installing P3D hotfiles, as they do actually fix things. Pete

Show me your FSUIPC.INI file, from the Modules folder. Paste into a message using the <> button above the edit area to enclose the file contents. Pete

On the left you have nothing? Where are you assigning to Spoilers, then? It is on the RIGHT you should have nothing! Okay, that all sounds good, and exactly what I do. Is this with a default aircraft? If not, test with default aircraft, not with Add-Ons. Add-on aircraft may do their own thing, ignoring the FS values for the Arm position. Also always test with the aircraft off the ground. The way FS is written makes the spoilers deply on the ground if armed. I've no idea how a such a device works through a PS/2 connector -- isn't that just for keyboards? Pete

You are making a mistake when entering your registration details. All three parts must be exactly correct. In the FS or P3D Modules folder, of course, where everything from FSUIPC resides. Nothing is ever placed anywhere else. Pete

Sorry, what do you mean by "i run fsx.exe "legacy mode""? What "won't load"? If you mean FSUIPC4.DLL, then you need to look at your DLL.XML file -- it is that which tells SimConnect to load the assorted DLLs you have installed. It is nothing at all to do with what "mode" you might adopt. Pete

Okay. I am away with limited Internet access till Monday now, so apologies for any delays in my response. Pete

If it is to agree a license for commercial use of FSUIPC, then simply write stating the name and purpose of your application and suggested financial arrangements. If it is that you wish to become a reseller of FSUIPC and WideFS to end users, then I'm afraid that is out of the question as SimMarket have exclusivity, outside one small supplier in Japan. For commercial use write to petedowson@btconnect.com. Pete

They are all with 4.939d, not 4.939e though. Not sure what it proves. Pete

No, that's not likely. I'm afraid I've no idea why the wind smoothing and text message hooks don't work for you but I suspect it's to do with trying to run a version of ASN which isn't compatible. Try without the ASN modules and EXEs loading (they are in the EXE.XML and DLL.XML files). I notice that the text window hook didn't work for you with 4.939d too. but perhaps you have NewInterceptTextMenu set to "No" in your FSUIPC4.INI file? Oddly, the only difference between 4.939d and 4.939e is the support for the upcoming FSX-SE 62610. The P3D stuff is identical. But the order of actions between ASN and FSUIPC, hooking the same weather places, can vary. The only other changes are in the Installer for FSUIPC4, not the DLL. I've just re-applied the Hotfix myself, and the relevant section of the 4.939e log looks like this 9without ASN): 561 LogOptions=00000000 00000011 561 --- CONTROLS timer memory location obtained ok 561 --- SIM1 Frictions access gained and basic values patched 577 --- FS Controls Table located ok 577 --- Installed Mouse Macro hooks ok. 577 --- Wind smoothing fix is fully installed 577 --- SimConnect intercept for texts and menus installed ok 577 SimConnect_Open succeeded: waiting to check version okay 577 Trying to use SimConnect Prepar3D 12246 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12944.0 (SimConnect: 2.5.0.0) The red confirmations are missing in yours, even for 3.939d, though the second one, the text menu one, is optional of course. I'm afraid I'm out now till Monday. Luckily your "problem" isn't at all serious. I'll think about what might be going on next week. Pete

Event viewer isn't a command, it's a Windows facility. Just use whatever search Win8.1 has. In Win7 it's just a matter of pressing the Windows key on the keyboard, then entering 2Event viewer" in the "Search programs and files" box bottom left. Pete

Sorry, I don't know much about SimMarket's sales side, only what I see on their web pages same as you. But you could try throwing yourself on their mercy, saying it was an honest mistake. You'd need to raise a problem ticket through your account. Pete

Hmm. Strange. The ASN Beta doesn't work here with 12944. Pete

Where's the crash details from Windows? That will tell us both more. The log shows it crashed when you load a flight. It could be that the weather file (.WX) for that flight is corrupted. That would do it. For regular FSX, as you are using there, there's no difference in any of the last few versions of FSUIPC. The updates have all been for new versions of FSX-SE and Prepar3D. Go to Start-Run edit place, bottom left corner of screen, enter 2event viewer" and press Enter. Then find the entry from the crash in the error logs there. Alternatively of course you can make a note of all the details shown on request on screen at the time the crash occurs. The main needed info is module name, error code, and offset. Pete

I can only help if you supply some information. For example, let me see the Install log and the run-time FSUIPC4.LOG, and also the crash details from Windows event viewer. It would also always help if you stated what actual version of FSX or FSX-SE you are using. Also explain what you mean exactly by "a little bit later"? Like whilst flying, at the opening menu, when, exactly? And what other programs are you using? How do you know it is FSUIPC which is causing this? Pete

I've just tried the Beta ASN release with P3D 12944, and FSUIPC 4.939e. This version of ASN definitely doesn't know 12944. It comes up with an error which, if you press OK, will terminate it. But checking my FSUIPC4 LOG afterwards, I get this: 546 LogOptions=00000000 00010011 546 --- CONTROLS timer memory location obtained ok 546 --- SIM1 Frictions access gained 546 ASN active function link set 546 --- FS Controls Table located ok 546 --- Installed Mouse Macro hooks ok. 546 Wind smoothing may be by ASN, not FSUIPC, if it is running 546 Will switch smoothing action when ASN starts/stops 546 --- SimConnect intercept for texts and menus installed ok 546 SimConnect_Open succeeded: waiting to check version okay I've highlighted the crucial differences in RED from your log. I think this indicates that your 12944 installation is incomplete or corrupt. Try applying the hotfix again. Pete