Pete Dowson

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

That's nothing whatsoever to do with what we were discussing. What have you changed? When you say "you see the menu" what do you mean now? You always "saw the menu" according to what you've said!. You seem to be changing the subject. I only asked you to add some logging. Crashes in WEATHER.DLL are usually caused by corrupt .WX files in your Documents folder, where FS flitghts are stored, or sometimes WXstationlist.BIN gets corrupted, in the same folder as your FSX.CFG file. But why would you ask me silly questions like "now what!" as if I'm causing you grief? I really object to that. I'm just trying to help you fix your FSX installation by getting more information, I'm not corrupting your files for you!!! :sad: And please don't post all that rubbish which is no use whatsoever to me. I cannot support FSX myself, such dumps are for FSX developers, now defunct. Pete

But the log will only show that stuff when you've added those two lines to the INI file [General] section, as I keep telling you!!! It is no good you posting all this stuff until you do that. Pete

I have 4 simulation setups all maintained with the add-ons I like. These are FSX, FSX-SE, P3D 1.4 and P3D 2.5. Currently I only use FSX-SE as for me it looks the best, performs by far the best, and has the greatest compatibility with all the things I like. A lot of folks have moved over to P3D v2 because of the allegedly improved graphics. Certainly autogen coming up slowly rather than popping up is an impovement, but many of the visual improvements are wasted on me -- things like cockpit shadows, ground shadows, water reflections. If you fly VFR I expect you'd notice these things, but for airliner flying in a hardware cockpit I don't. And I don't get anywhere near the performance and smoothness in P3D that I get in FSX-SE. Pete

Please check the FSUIPC Advanced User's manual, search for ButtonRepeat. Pete

No, the log file shows nothing useful at all, only that you have not added the lines to the INI file as requested! Did you even go into the FSUIPC menu and use a dropdown? I said: What is it you don't understand about this? How to edit a file? How to load a file into an editor? Please explain the problem! The two lines you added to the wrong section aren't doing any harm, they are just a waste, so yes, delete them, or simply move them to the correct place. Pete

All looks perfect, no problems at all. Yet you say theres an FSUIPC entry in the Add-Ons menu which does nothing? This is an extremely strange and possibly unique problem. I've no idea what is going on. It has got to be either a problem in the Simconnect installation, or just possibly another Simconnect add-in or add-on which is interfering somehow and blocking the message from SimConnect to FSUIPC telling it that you pressed its menu item. The first thing to do is eliminate that latter possibility. The easiest way to do that is to temporaily rename noth DLL.XML and EXE.XML files (or just move them to safety out of the user AppData\Roaming\Microsoft\FSX folder in which they reside, then re-run the FSUIPC4 installer, so it makes a DLL.XML loading only FSUIPC4, and run FSX to see if that fixes it. If it does then it's a matter of finding out which of the programs or DLLs being loaded by EXE.XML and DLL.XML is responsible. There is some logging built into FSUIPC which might also help. To enable this please add the following to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x8000 Run FSX, try the FSUIPC menu entry, close FSX, show me the log. Pete