Pete Dowson

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

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