Pete Dowson

Please see my reply to your separate thread. You seem to be a little confused. There's no INI folder and you do not need to refer to any files other than the User Guide to make a profile. Pete

There's no INI folder, never was. Perhaps you mean an INI file? You do not need to access any files in order to "construct a prtofile". You just use the in-sim FSUIPC options, exactly as described in the documentation. Please refer to the User Guide. There are pictures to help. Pete

I've fixed this for BGLs compiled with the usual tools, but I found that the reason it didn't work in 4.82 was that I was trying to cope with BGLs compiled using the latest P3Dv4 SDK tools, and made an error. For now, it won't find threshhold offsets, VASI and Approach Light information for such newer BGLs. Until the new formats can be worked out this is probably one of several areas which will not work. Luckily, 99% of all scenery currently in use, including the default P3D4 sceneries, still use the older tools. Pete

The file selection there is NOT performed by FSUIPC. FSUIPC doesn't see the selection until you make it. All it does is call a Windows API function to provide a standard file selection dialogue. That doesn't return to FSUIPC until you either make a sleection or cancel/escape out. So, it seems something else in your system is trapping mouse operations and trying to do something. My main suspect would be the aircraft, the Carenado C337_Skymaster. Can you test with a default aircraft? BTW for some reason you have enabled Event logging. If you don't actualy need that it would make the logs a lot shorter by turning it off. Pete

Hmm. and the same file read by different MakeRunways versions, produceds those differences, both with the same Sim? That is indeed strange, as nothing has been changed in its actual BGL processing, only in the file identification. I'll make time to check this out later today, or maybe tomorrow. Thanks for the example. Pete

Version 5.11 is way out of date. There have been several new updated versions since then. Please always check that you are up to date. Download the latest and try again. Pete

Comparing P3Dv4 results to what? Default airports or add-ons? MakeRunways hasn't changed at all, except to enable it to determine where the SCENERY.CFG file is, or using the Lorby add-on manager to generate the version placed into the P3D folder which then includes scenery layers added by the new XML files. Also, most if not all of the default airport BGLs are unchanged in P3Dv4, so it should surely give the same results -- same data, same program reading it. Can you find an example which was correct in P3Dv1-3 or FSX but which, for the same BGL files, is not? Pete

That's where the keys for FSUIPC and WideFS are used. It is the Server which is so licensed. You can have as many clients as you like. Pete

Different PC's running Flight Sim, or just WideFS clients? If the former, are these just for your use, or multiple users on one Project? BTW you posted a Support Question to the FAQ subforum. "FAQ" means "Frequently Asked Questions" and is a repository for answers to those, not a general interactive support forum. I've move it for you. Pete

5.121a is released with a full install in any case. It is the current release. When you said this: You never mentioned anything about FSUIPC "not showing", which is a completely unrelated matter to your described Install error on checking your registration. FSUIPC does not have to be registered to have it installed and showing in the Add-Ons menu. So, the thread is confused and I still don't understand what this was about. I did ask what you meant by I asked: "Sorry, Where are you entering a key? The "check" merely reads the KEY file and checks that it 's a valid registration." So what were you doing? Why run a check in any case? And if the key was not being generated, how was it Registered cotrrectly now, just by replacing the DLL? Or is it? I'm afraid nothing in this thread makes any sense to me. :-( Pete

I could look to see where in FSUIPC the crash is occurring (though if, like last time, it is really deep inside the Lua interpreter I'm not sure whether I can do much about it), but I need a crash log when using the currently released version of FSUPC. Otherwise the compilation map doesn't match. The current version on full release is 5.121a. Remind me. What were those? Are you saying this was not a problem in some preceding version of FSUIPC? But unfortunately with no Event Viewer details . I do of course have the correct map for 4.971 as that is a current version and it might be easier tob track it down in the 32-bit version. Have LINDA users never changed aircraft before, or is this a new problem? Or some other development in LINDA use? Is it something you cvan reproduce? Is there only one user with this problem? Pete

It sounds like it is reading the axis imput and not directly affected by the actual value that it creates internally. Some add-on aircraft are like that. For those you probably need to simply assign to the FS control (not "direct to calibration") and not calibrate. Pete

Something else just occurred to me. There is a problem, especially with Saitek devices, where a registry error causes 50% of the axis movement to be missed. Viewing the "IN" values in the Axis Assignments tab, Instead of going from -16383 smoothly to +16383, it starts at -16383 but with a verysmall movement, jumps directly to 0. Then smoothly to +16383. There is a fix in the Registry for the (see FAQ subforum thread Fixing problems with 50% (or digital on/off) action with Saitek levers but you can also get around it by calibration: just find the zero spot, just above the one place giving -16383, and calibrate that as you minimum input instead. I've just tried this and it works fine (I used the default King Air). Pete

I don't see anything "condescending" in Thomas's pos! Is it just one explamation mark which upsets you? In that case many of my posts will be more upsetting to you. And "you need to show" was NOT capiralised, as you have done (=SHOUTING!), and is quite true. In any problem report you do need to show things like the INI and LOG files, as these contain things relevant to you being assisted. Thomas helps fill in for me, especially when I am away, and it is completely voluntary. He has a full time job too, and spends his own time helping. It's a shame you don't appreciate this. Normally, for nearly all aircraft, the actual mixture axis value inside the Sim -- the value being written by FSUIPC -- does go from 0% (zero fuel or full lean)) to 100% (full rich). Internally these values are represented by 0 and 16383 respectively. A negative mixture value does not mean "reverse" -- there's no sucking fuel back out! ;-) Looking at the INI file you posted (still no LOG?), you seem to have assigned Mixtures 1 and 2, direct to calibration, yet only calibrated Mixture 1, not 2. For the only profile you have, "Comanche", you have Mixture 1 assigned, but with no calibration at all. So, it is now time to ask what add-on aircraft you are using, because maybe it is a property of the aircraft? One other thing: P3Dv3? Why didn't you simply copy over your existing INI file? There's no difference in FSUIPC5 from FSUIPC4 in this area. If it was okay in P3Dv3 it will be okay in P3Dv4, assuming it isn't a bug in P3D or the aircraft. Pete

Actually the latest is 5.121a. Just with POV or just with Pan View assigned? Because FSUIPC doesn't distinguish between axis or assignment, in the sense that they are all treated the same way -- just numbers. If that one specific instance doesn't save then none of them will, for any axis to anything. Is that the case for you? Pete

Remove the "No reverse zone" selection! With that selected the whole range of your axis is calibrated to a 0 to +16383 range. That is needed for all sorts of axes, including those mixture controls which don't have an are below "cutoff". For a range of -16383 to + 16383 you are using the reverse xone which for some reason you have specifically selected! Pete

Thanks. Thanks. This confirms that the latest Beta SimConnect LIB is incompatible with the previous Beta SimConnect LIB, though neither are on public release yet! The reference to version number 60905 though is insane! I've reported all this to L-M because I'm not sure how to handle this in the future. Pete

Further on this, I have checked the VS manifest settings for FSUIPC4 and 5 installers, and they are identical (except of course for pathnames). So, I really don't this the difference is related to manifests. Or, if it is, I can't see where. Pete

Here's a link to a rebuilt DLL. Can you try it for me and let me know. i'd like to see the first part of the log, until tings start running, even if successful please. FSUIPC5121a.zip This is only the DLL, for replacing in your P3D4 Modules folder. I've reported this problem to L-M separately, because the version of SimConnect actually returned by the latest Beta is identical to the previous, from which I was using the LIBrary. This is not easy to manage. Pete

I don't have a manifest for FSUIPC4! Whereare you seeing this? If you don't extract from the archive, where does the log it generates go? Since I'm not sure how a manifest got generated for FSUIPC4 I don't really know what to do for FSUIPC5. Can you explain more please? I was actually under the impression that Windows automatically elevated any thing with "Install" or "Setup" in the name. Is that not true? I though the change was that this didn't get applied to 64-bit programs -- something to do with the 64-bit registry stuff? I do that in the History document, but not in the interim changes updates. Normally there would be a new History document with each full Installer update, but i've been too busy recently working 18 hours a day on development and support alone. And yes, I know, this is because of taking holidays. But I think I'd be killing myself if i didn't. Pete

That is really weird. Version 60905 of SimConnect is the original FSX version, from its first release. FSUIPC5 doesn't seek any Simconnect versions -- it has the P3D Library file built in and connects directly into P3D, not via any DLL. And it works perfectly here on 3 different systems. 5.121, unlike 5.12, is compiled using a slightly later version of the SimConnect LIB -- the one from a new Beta from L-M, only just installed here. I don't know what they've done in order to get a 60905 return from Simconnect. That is unreal. I'll reinstall the previous version of the P3D SDK and re-build. juyst the DLL file. I'll place a link here for you to test for me. I need to take that retrying action out too. In the event of this happening again it whould just terminte itself with an Error Message. It hasn't arisen before. Pete

Sorry, Where are you entering a key? The "check" merely reads the KEY file and checks that it 's a valid registration. Pete

Why are you checking it? Are you unsure of your registration? Most folks just use the "Not now" option when not entering a new Registration. But I'll check ... maybe it's just a bug which has never been discovered because no one uses that option. [LATER] No, it is fine here. The log shows: Checking FSUIPC registration ... Registration check for FSUIPC5 was successful! (result code 00) Looking ay your log, the result code simply means "No FSUIPC entry to check", which in turn means there was no FSUIPC entry giving the Key in your FSUIPC5.Key file. Did you delete it before installing 5.12? You never need to delete anything when updating FSUIPC. BTW 5.12 is replaced by 5.121 now -- please update. There were a couple of quite serious issues with 5.12. Pete

Your log shows you are using FSUIPC version 4.921f. I cannot support such old versions. Please update to 4.971. If your Trim Wheel is only writing to offset 0BC0 then it cannot possibly change the throttle unless something is wrong in the aircraft modelling or the sim. I think it is more likely that you didn't actually disable controllers in the Sim, and it has picked up your trim wheel axis and automatically assigned it. This is a danger unless you actually disable controllers in the sim -- it is thinking it is being helpful! These log entries do indicate that your Throttle is ittering, BTW. Correct calibration should fix that, and in fact for jitters less than the Delta (default 256) it would be eliminated by assignment in FSUIPC. 127203 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 128264 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 128264 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 128373 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 128389 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 132289 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 132304 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 133131 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 133131 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 133225 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 133256 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 135471 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 135502 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 136735 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 136766 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 137016 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 137031 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 137125 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 63 (0x0000003f) AXIS_THROTTLE_SET 137140 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET Pete

There is friction table access available in FSX-SE, and it can be changed using the Lua plug-in installed in your FSUIPC Documents folder. Or you can make your own plug-in with your own figures. If you do a searc you'll find lots about all this (for any aircraft). Also over in the AVSIM FSX forum. Pete