Pete Dowson

I don't know about "quick ILS", but providing you are using the latest MakeRunways, then there's no problem with any version of P3D. Although they've changed some files around in version 2.5, the scenery.cfg file is still in its correct place. Maybe you are one of the folks who are using P3D renamed to FSX, for some complex migration or installation reasons? If so, then MakeRunways will be looking in the wrong place, for sure! Pete

Hmm. I don't think that's an FSX message, it'll be one of your other Simconnect client programs. There's nothing wrong there, either. If you want to check that FSUIPC is doing what you ask, simply enable Button/Key logging and it will make entries in the log revealing the button pressed and the action taken. Ah, thanks for the clarification Paul. Pete

What is the "Simconnect error has been detected ..." message? Sorry, that's a new one on me. Can you be more explicit? How about showing me the contents of the FSUIPC4 log file? You'll find it in the FSX modules folder. Don't reinstall FSUIPC unless you are using an old version. Current is 4.939e. Pete

Sorry, I've no idea because I don't know why they disconnect in the first place. Nor do I understand why or how FSUIPC could possibly help in such matters as it uses precisely the same Windows API methods as FS and P3D. On the first point, again, I don't know. Those are questions best directed to L-M on their Forums. But on the second point, I and many others have dual installs of FSX and P3D (in my case, FSX, FSX-SE, P3D1.4 and P3D2.5+hotfixes), and there is really no way I see they can interact with each other. No. The joystick reading is direct via Windows, no SimConnect relationship at all. And each SimConnect DLL can be used independently according to how the application has been built. FSUIPC is flexible and uses any version, but for P3D it normally uses the one it installs itself in the Modules folder. It does that because by default P3D didn't use to install any Simconnect DLL in the Windows SxS system Regards Pete

I have received this advice for Win8.1 users, from my good friend Thomas. He says that with thse changes in Windows he has solved the spontanjeous disconnection of joystick and other USB devices: Action: - Open Energy Options (might be Power Options like in Win7) in Control Panel - Then go to change Energy Saving Options of the selected Energy Saving Plan - There like always everything should be set to always ON … - Then select Advanced Options on that page - On that new panel (Energy Options) under the selected Energy Saving Plan there are two setting to take care of o Energy Saving, again everything should be set to No saving/ Always ON .. o USB-Settings -> Selective USB Energy Saving -> Deactivated/ Disabled The first Energy Setting is just global and makes you to believe it includes USB but it doesn’t. The second one, Selective USB Energy Saving doesn’t give you any idea for what it really is or what it does but it needs to be Disabled to keep the devices alive. Not even the Help button does give any help about those settings … Hope this helps ... Pete

Yes, of course, though I didn't study every line in the attached files. I don't think I "assumed" that, I read it the words you wrote! But if you believe your USB connections are perfectly fine and something else is going on, perhaps you can explain what you really think? Okay. So what do YOU think could be going on? Well if you never updated P3D either then I suppose it doesn't matter so much, but certainly I cannot support old versions. I can only report on what I got from my friend, to stop USB disconnections. If really you are not getting any such problemsthen you need to be more explicit on what the problems are, because your message was explaining exactly that! Here is his recommendations for steps that have worked perfectly for him: - Open Energy Options (might be Power Options like in Win7) in Control Panel - Then go to change Energy Saving Options of the selected Energy Saving Plan - There like always everything should be set to always ON … - Then select Advanced Options on that page - On that new panel (Energy Options) under the selected Energy Saving Plan there are two setting to take care of o Energy Saving, again everything should be set to No saving/ Always ON .. o USB-Settings -> Selective USB Energy Saving -> Deactivated/ Disabled The first Energy Setting is just global and makes you to believe it includes USB but it doesn’t. The second one, Selective USB Energy Saving doesn’t give you any idea for what it really is or what it does but it needs to be Disabled to keep the devices alive. Not even the Help button does give any help about those settings … I will probably make a FAQ subforum entry for this, but do please let me know. Pete

I do not use PMDG aircraft, but I think they are one of the problem add-on aircraft I mentioned, and for some of the aircraft controls they intercept the FS controls at the same sort of level as FSUIPC, and therefore use the uncalibrated values. If you calibrate in FSUIPC as well, then two different values get sent and this can cause conflict in the aircraft. Also, because they take these values early, using FSUIPC's "direct to calibration" method may well bypass the add-on aircraft interception at the level they want it. All this is mere speculation on my part based on folks reports here from time to time. You need to choose the method which works best for you and your controls. Pete

I'm sorry, I don't understand, What is the question? You seem to say you solved a problem, but then have one. What problem? Pete

Yes, and you get it too., as everyone here does, and in a timely manner as well. In fact EVERY visitor gets questions answered, whether they paid for use of the program or not, so there's no need to even mention the fact at all, let alone get so stroppy. And what are the pics for? NONE of the Lua plug-in library or language is part of the FSUIPC SDK, which is a tool not for users making plug-ins but programmers writing add-ons programs. The offset lists are provided with the user install of FSUIPC not as programming assistance but only as a reference list in using the FSUIPC offset controls, in assignments, or in the Lua plug-in facility. The Lua facilities are all thoroughly documented in the Lua package installed in your FSUIPC Documents library. Please use the documentation provided for the aspect of FSUIPC you are using! Pete

This is nothing to do with FSUIPC, and I never understood why folks think that using FSUIPC assignment prevents this problem which is something all Windows 8 users seem to suffer from. I'm really glad I stuck to Win 7! I am told there are things you can do in Windows 8 settings to alleviate the problem, if not actually cure it. One is, as it was in Win7, to make sure power management is turned off on all the USB devices and hubs you find listed in the Control Panel - System - Device Manager list. But there is also another setting which helps, which I cannot remember and cannot at present find for you. I will ask a friend who is using Win8.1. Perhaps he could post a FAQ subforum entry about it. Pete

Sending direct to FSUIPC is more efficient. The axis value is fed directly into the calibration option and only after the value has been manipulated there is is sent on to FS for action. Sending as a normal FS control is no different to what assignment in FS itself does. It sends the input value to FS, and the calibration, if enabled, operates by intercepting the value FROM FS before it is actioned. This is the original way FSUIPC calibration always worked, before axis assignment facilities were added. The method is retained because some add-on aircraft do not work correctly if you use the "direct" method because they like to see the actual FS control at a higher level, above where FSUIPC's intercept operates. Pete

If you go to your SimMarket account, you cant retrieve the registration details for everything you've ever purchased from SimMarket! Pete

Ah, that's because I didn't put an installer up for it. Sorry. It isn't relevant in any case because I tested it here, and it doesn't do any different to the one you tried. You can either try what I suggested, which I'm sure will work, or wait till i can release the next updated installer. Pete

That is no excuse for it reporting that it is build 12942 when the exe is 12944. There is devidently something very wrong. I can only suggest you take it up with LM. Pete

Okay. I've simulated your problem by messing about in my Registry. I'll see if I can make the Installer handle this, yet another variation on what folks seem to achieve with this FSX / FSX-SE muddle. That's at least 4 variations already of what's been achieved in the way of a mixup! Meanwhile, the work-around i suggested above will work fine. [LATER] I've changed the Installer to cope with your variation too, but it can't be released till the current FSX-SE Open Beta is finished, so I can finalse the FSUIPC changes. The workaround I gave you will work. There are now 4 cases of mixups folks can get into, which FSUIPC has to try and deal with: FSX.CFG being used in FSX-SE folder FSX_SE.CFG being used in FSX-SE folder (the correct situation for a dual install) FSX.CFG being used in FSX folder (the correct situation for an FSX-SE only install, no sign of FSX) FSX_SE.CFG being used in FSX folder The first and last are actually wrong (i think yours is the last), and i don't really think FSX-SE can work like that -- it will make a new CFG file when run, I think. However, I will make the FSUIPC4 Installer work even in the wrong cases, to alleviate the hassle i otherwise get. Pete

Good. Let's see: >>> OK! FOUND FSX! <<< ... SetupPath=C:\FSX SE\steamapps\common\FSX\ You have the FSX pointer in the registry pointing to FSX-SE instead. Have you uninstalled FSX? >>> OK! FOUND FSX-SE! <<< ... AppPath=C:\FSX SE\steamapps\common\FSX\ and you have the registry FSX-SE pointer pointing to the same FSX-SE installation. Fine. FSUIPC should now cope with that mixup now, though it's odd. ************ BUT this is the same path as for FSX! Will only install for FSX-SE ************ Okay so far. But this entry is odd: Cannot find FSX_SE.CFG. Looking to see if installed with FSX.CFG instead ... It looks like it is saying that without even looking for it! That, I don't understand at present. I will check into how that can happen, but I'm afraid I'm busy over the weekend, so it won't be till Monday now. Meanwhile, what you can do is make a copy of your FSX_SE.CFG file, found in folder C:\Users\Marco\AppData\Roaming\Microsoft\FSX and/or C:\Users\Marco\AppData\Roaming\Microsoft\FSX-SE depending on how you got things into this state, then rename the copy as FSX.CFG. Then rerun the installer. The copy won't do any harm. Meanwhile, you still haven't answered this question: ... you supplied a log showing you were using FSUIPC 4.938e in FSX-SE quite successfully a few days ago (on the 9th). So, what happened? The answer to that should help determine why your registry is in a mess. [LATER] Ah, I see a possible answer in your later message: Why did you uninstall and reinstall? Did you ever have FSX installed, or do you still? I still don't quite get how you have a pointer for FSX pointing to FSX-SE. Pete

Okay. So? Right, fine. But you supplied a log showing you were using FSUIPC 4.938e in FSX-SE quite successfully a few days ago (on the 9th). So, what happened? Why are you not wanting to answer my questions, which are only designed to try and elicit information to help you, after all. Okay, but that still answers no questions. Do you actually want any help, or not? Please review my original response. I fail to understand why you are so insistent on your history, rather than wanting to fix a problem you think you have? Pete

No, that is NOT the Install log, that is the run time log, showing FSUIPC 4.938e was installed and ran perfectly well on the 9th of this month, i/e just a few days ago. So what on Earth are you doing? Why, for instance, are you trying to reinstall FSUIPC4 when it was working fine? If you want help with the Install I need to see the Install log, but it looks like to you did it okay once, so what are you messing with? Pete

What does the FSUIPC log show, though? That is the point. If part of your P3D installation is wrong, then FSUIPC cannot function correctly., The earlier log shows that something is most certainly wrong -- and any crash will because FSUIPC is being misled into believing your P3D is not the one it purports to be, at least in whole. I cannot help until you get your P3D installation correct. I have no other reports of such a mixed up P3D version as yours. Pete

The answers are in the FSUIPC4 Install log file, found in your FSX Modules folder. Without that I can't help. Make sure you press OK to such messages to make sure things continue, and please don't post pictures, They are not needed and rarely informative. Pete

Hmm. Strange. It appears to be something to do with the ASN WXradar facility. Can I see your FSUIPC4.INI file please? Pete

Not sure what the ones you found are. FSUIPC doesn't provide any failure instigating facilities whatsoever. There maybe several built-in FS controls which you are seeing, and you might get others triggered by using Offsets (there are assignable controls for changing offsets), but most decent Instructor Stations and add-on aircraft which support proper failures which realistic symptoms do their own thing. The built in ones are pretty useless really, and programmatic access to them is limited, to say the least. Pete

That's what event.offset and event.offsetmask are for. Please do use the supplied documentation! Pete

I must apologise. You must remove FSUIPC4.DLL from the Modules folder. FSUIPC4 is for FSX and later, not FS9. This thread got so long I got the context wrong. I'm afraid I have no answers for FSUIPC3 which is impossible for me to develop and support these days. FS9 is now 12 years old and the FSUIPC version used with it is even older, as it is basically the FS98 version I developed in 1999. I'm afraid I really don't know why none of your macros appear in the drop down list and I have no way of finding out. I am amazed you have accumulated as many as 127 -- there's something wrong with the way they are made if you need that many. You should only need one per aircraft type. Each macro file can actually contain just as many macros. It may simply be that there's a bug in FSUIPC3 which only happens when there are too many macro files. If I were you I'd try and prune your system radically. Remove all the stuff you don't really need and try to merge all the macros associated with the same aircraft. You might find it easier, in fact, to delete them all, and the INI file, and start again. Apologies again for going down the wrong path for so long ... Pete

But what I asked you to do changed NOTHING, it only logs extra details to the log, doing nothing else at all! Something else has happened on your system. I suspect your FS installation is corruppt. Pete