Pete Dowson

That is a BAD idea, if you wanted FSX and FSX-SE to coexist! You have destroyed the link to FSX! Additionally, you are trying to install an old version of FSUIPC. the installer with the current version, 4.939e, might just overcome the registry mess, but really I would also suggest you restore the FSX application path entry to point back to FSX, not to FSX-SE. Why did you mess around in the registry in any case? Pete

I think your main problem is that the P3D installation is in a bit of a mess. According to the install log your P3D main program is at version 12944: SetupPath="P:\Program Files (x86)\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.5.12944.0 (Need at least 1.0.677.0) but when FSUIPC connects to Simconnect, the latter reports that your version is 12942: 28533 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12942.0 (SimConnect: 2.5.0.0) I think something must have gone wrong when you tried to apply the "hotfixes". Try updating your P3D again. If that doesn't sort it out, I'd report it to L-M and see if they know how the above discrepancy can happen. It certainly doesn't look like that here. The line in my FSUIPC4 log reads correctly: 26146 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12944.0 (SimConnect: 2.5.0.0) Regards Pete

I have an interim test version of FSUIPC4 available in which there's an option to log all those added plug-ins and macros which should appear in the assignment drop-down lists. If you'd please use this and let me see the results. Steps to take: 1. Download FSUIPC4939f_test.zip 2. Copy the FSUIPC4.DLL found inside the ZIP into your FS Modules folder. 3. Edit the FSUIPC4.INI file (the one you pasted in this thread earlier) by adding these lines to the [General] section Debug=Please LogExtras=x40 4. Now run FS, then go to one of the FSUIPC assignments tab for keys or buttons and use the dropdown. You don't need to assign anything,just operate the dropdown for assignment. 5. Show me the FSUIPC4.LOG file. It will log all the plug-ins and macros it is adding the the drop-down list. (It only does this once, mind you -- you can carry on using FSUIPC then without worrying about a larger and larger Log file). Regards Pete

"Previous flight" should be stored automatically by FS itself. FSUIPC does try to help this, but if an add-on aircraft then tries to save its own data to suit this may take so much time that the sim closes first, before FSUIPC gets notified. See if you get Previous Flight saves if you change to a different aircraft before closing down. Pete

Ouch. Why didn't you say that in the first place? That nasty system in a right pain in the ***! The problem is you've renamed the EXE, so all the files FSUIPC uses are renamed accordingly -- take a look at your INI file, for example, and LOG file. Rename your KEY file to suit. There is a section in the FSUIPC documentation dealing with renamed copies of FS. [LATER] Ah, I see Thomas has also given the same answer. Thanks Thomas! Pete

Okay. You do have the absolute maximum Macro files listed, 127 of them: [MacroFiles] 1=1 afuel cut 2=1 cut off fuel 3=1 run 4=1apu bleed 5=1apu 6=2 fuelcut 7=2 run 8=2run 9=3fuel cut 10=4 cut off fuel 11=4 cutt fuel 12=4 13=4fuel cut 14=apu start 15=apu 16=at dis 17=auto dis 18=auto thr 19=auto throttle 20=button four 21=dis a throtle 22=frun3 23=toga 24=trottle dis 25=tog 26=auto throttl 27=auto thrott 28=747-400 29=747 30=747-400 1cut 31=747-400 fuel 32=togaa 33=autothrotle 34=toga 1 35=toga1 36=toga747 37=b744 38=b744 fcut 3 39=b0eing 744 fuel 40=boeing 744 41=b744 run1 42=b744 fuel 43=b744 fu 2cut 44=b744 fue run 3 45=b744 lights 46=b744 land 47=b744 landr off 48=b744 land in off 49=b744 land in on 50=b744 rwy on 51=b744 rwy off 52=b744 taxi off 53=b744 taxi off 2 54=b744 taxi on 2 55=b744 strobe on 56=b744 strobe off 57=b744 tcas- 58=b744 tcas + 59=b777f1 off 60=b777 f1 cut 61=b777 fuel 1 62=b777 fue cut2 63=b777 run1 64=b777 run2 65=b777 tooga 66=b777 toga 67=b737 fuel cut1 68=b737fuelcut1 69=b737fuel2cut 70=b737run1 71=b737run2 72=b737toga 73=b737 athrotle 74=b777-300 75=b707 fuel cut 1 76=b707 fuel cut2 77=b707 fuelcut 3 78=b707 fuel cut4 79=b707 fuel 1 run 80=b707 fuel run2 81=b707 fuel run 3 82=b707 fuel run 4 83=b747 rto 84=b744rto 85=b744 rto off 86=b744 on 87=b744 ab 88=b747400 89=1 747400 90=2 747400 91=3 747400 92=4 747 400 93=5 747400 94=6 747 95=7 747 96=8 747400 97=9 747 98=10 747 99=11 747 below 100=12 747 101=13 747 400 102=16 747 103=20 747 104=1 747 105=2 747 106=3 747 107=4 747 108=5 747 109=9 747 400 110=b744 outbd 111=b744 app dis 112=b744 warn 113=b744 auto pilot 114=toga 747 115=tcas test 116=b747 run one 117=b747 fuel 1 cut 118=1747 ifly 119=2 747 ifly 120=3 747 ifly 121=3 747 fuel ifly 122=4 747 ifly 123=747 apu st 124=747 apu start 125=b747 abv 126=tecas ab 127=tecas blw Of those, any which actually exist in the Modules folder, as "name.mcro", which are properly constructed will most certainly be listed in the drop-downs and be assignable. So next you must look in the Modules folder and see what .mcro files are there. Alternatively, so you can show me, temporarily rename your FSUIPC4.INI file -- don't delete it -- and rerun FS. Then show me the MacroFiles section from the new FSUIPC4.INI file. It will then only list those which are there. Don't forget to delete that new INI file afterwards and rename the original back, or you'll lose all your assignments. Pete

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