Pete Dowson

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

Yes, assuming you've got no Kodiak;s you don't want included! ;-) Pete

My offsets list only details offsets which FSUIPC itself, or WideFs, maintains. Checking my list I see this: 9400-94FF = Jouni Tormanen for IFlyToFsuipc How he uses those offsets I've no idea. You need documentation for "iFlyToFsuipc". Pete

Well, FSUIPC4 is installed okay. You appear to have set both FSX and FSX-SE pointers to point to FSX-SE. Are you not intending to use FSX at all from now? The DLL.XML file is corrupted, missing a big chunk at the beginning and instead has an extra < at the start. Delete that extra < and instead insert the header, thus: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> When you post files, please use the <> button above the edit area to enclose them. Pete

If that small screen, as illustrated in the documentation, doesn't appear, it simply means that the gauge or whatever which handles that button or switch is not amenable to mouse macros. For a mouse macro to be possible at all, the aircraft gauges must be written in C/C++ using the standard Microsoft panels and gauges SDK. Very few add-on aircraft are written this way these days. It used to be pretty standard in FS2002/FS2004 days, but even then Microsoft itself didn't use it in the default aircraft except in a few instances. Pete

You only use the dialogue to start macro making. It lets you specify the macro filename, then you OK out, make all of the macros you want in that file, then go back into the dialogue and select end mouse macro to confirm and finish the file. What does "no luck" mean? You need to actually describe what happens. "No luck" means nothing useful. Pete

They MUST be identified in the INI or they cannot possibly work! You are not looking properly. If you have "UseProfiles=Files" set, then the settings themselves will be in the Profiles subfolder in their own INI files, but there will still be the main [Profile.xxxx] sections in the main FSUIPC4.INI file with the assigned aircraft listed. Pete

I remember FlightLink stuff which I used and programmed many years ago, with FS4 and FS5 (on DOS originally). I did make a Windows version (EPIClink), but development on that stopped long ago. At that time EPIC was a serial (COM port) card. I don't know whether the USB connection is just a serial port emulator (i.e. looks like a COM port with a suitable hardware driver) or a true USB device. If the former you might get it working with FS using my software, but probably only on Windows XP or before, not Vista, Win7 or Win8. And I'm afraid you'd be on your own as I have long forgotten all about such stuff. As for X-Plane, I'm afraid I know nothing about that. You'll probably need to ask in the X-Plane forums. You could also try http://www.mycockpit.org/forums as a lot of hardware experts frequent the places there. Pete

FSUIPC's settings are saved in the FSUIPC4.INI file. Your registration is in the FSUIPC4.KEY file. Those are your most important files. If you are using the Profiles in separate files facilities you need to backup the entire Profies subfolder too. You should also save any macro files (.mcro) and plug-ins (.lua) files you might have created or installed. Nothing changes the assignments, randomly or otherwise. More likely your USB devices got assigned different Windows ID numbers, probably because you plugged them in a different way, or in a different order, or maybe because you used a different version of Windows. This is the whole purpose of using Letters instead of ID numbers for USB devices. There's a chapter about this in the User Guide. FSUIPC can then keep track of devices which move and change IDs. Pete

Since I've no idea what "9=Kodiak" is doing, I can't say. Is that the line in the Profile list to which the aircraft is assigned? Pete

If you want to make a separate profile for an aircraft already assigned to a profile then, yes, you have to edit the INI file and remove that aircraft from that Profile list. Not sure why you are now asking about aircraft specific. Pete

The option is only grayed out when the current aircraft is already assigned to a profile! You cannot assign to a profile when you are already assigned to a profile. Look at the title bar of the options dialogue and it will tell you what profile it is assigned to! Pete

The FSX screen always turns black when SimConnect is asked to put FSX into dialog mode. FSUIPC has to do that to use a modal dialogue. It is supposed to work that way! Pete

Okay. It is as intended, 1-4, no 0. FSUIPC definitely sets offset 0x3124 as follows: FSX build <= 60905 (ie RTM) == 1 FSX build <= 61357 (ie SP1) == 2 (the Russian version was 61357, all others 61355) FSX build <= 61472 (ie SP2) == 3 else == 4 (Acceleration = 61637) So please check the build number on your FSX.EXE. It is a bit odd if you think it is SP2 yet the EXE has a build number less than 61358! Pete

Ah, did I write that up wrongly? I'll check. It might be 0-3 not 1-4 as I put. Certainly Acceleration will be one up from SP2. On the other hand I might have deliberately started at 1 to distinguish it from the earlier FSUIPC builds where the value would not have been provided. In that case SP2 should be 3 not 2. What FSX build is reported in the FSUIPC4.LOG file? I'll get back to you when I've checked it out. Pete

No, you have not folowed my instructions at all. To start with you added the two lines to the [buttons.iFly 747-400 RR (Wide screen) BA] section, NOT the [General] section, so they won't have any effect, and then you've posted the INI file when I said I needed to see the LOG file. Pete

Not sure what folks are doing, but Google using "VAS display FSX" and you will find lots of alternative methods, mostly more useful than having to have the title bar in view all the time. Pete

If you want a reverse range on the levers you can calibrate with one. But you'd need to put a mark or a notch somewhere on the device so you can set idle easily. Many throttle systems actually have a button built in which is pressed by bringing the lever right back. If yours has this then you could simply assign that button to "throttle decr" (or "throttleN decr" for engine N)with repeat enabled. That what many folks with Saitek throttle quadrants do. Otherwise you'd need a button elsewhere so assigned. Make sure the idle zone on the throttle lever is defined with a little latitude, so you can always guarantee to set true idle, as else you won't get a reliable reverse capability. Pete

It therefore can only be a SimConnect problem, though I've never heard of any problem doing such a thing before. FSUIPC really has no control until the dialogue is displayed. What was this change "After making download update, last night" you did? Please show me both the FSUIPC4.LOG file and the FSUIPC4 Install LOG file. Both are in the FS Modules folder. You can paste their contents into a message here. Use the <> button above the edit area to enclose the texts. Pete

A "lot of the FSUIPC download sites"? What are those? There's only two places for download -- the "Dowson" page maintained by Enrico Schiratti at www.schiratti.com/dowson (this is pointed to by the SimMarket FSUIPC pages), and the Download Links subforum here. Both actually merely contain links to the same files which are always up to date -- and at present 4.939e if the only one they point to! If you have found other wedbsites hosting FSUIPC can you please give me the links? And why would you think of going anywhere unofficial in any case? The Schiratti page has text which is sometimes out of date -- I can't change that, it isn't my page -- but the links ALWAYS point to the current release. That path looks wrong in any case. "Program Files(x86)" should be "Program Files (x86)". Always check your entries thoroughly! And that error would only have stopped the install of FSUIPC into FSX, not to FSX-SE. The installer will continue if you let it, and do the further installations. I assume you simply aborted it instead? Why? Out of panic? Yes, because the updated FSUIPC installer for 4.939e recognises the mess your Registry is in as one which folks who try to uninstall FSX before installing FSX-SE make. But without the correct path for FSX you have no way to install things (FSUIPC included), to FSX -- so why, now, maintain a parallel installation? BTW I have parallel installations and all my scenery is shared. I just made all the paths in my FSX scenery.cfg complete, including drive letter, etc. Then used the same SCENERY.CFG for both FSX and FSX-SE. All my sceneries are then common to both installations and I don't have to reinstall anything at all. Did the same for SimObjects in the main CFG file, and just copied over the Gauges and Effects folders. Two complete installations, FSX and FSX-SE, all with everything installed, done and dusted in 20 minutes or so! ;-) Mind you, I don't have any complex aircraft. The complexities are in the harware simulator and its software (Prosim737). The aircraft added are for AI Traffic. Pete