Pete Dowson

I find it quite surprising anything about iVAP worked at all. Pete

FSUIPC5 is as compatible as can be with FSUIPC4. There are some exceptions, but I can't comment on your scripts. Please post here if you have a problem AFTER trying. You can copy over your FSUIPC4.INI file and rename it as FSUIPC5.INI. That will save remaking all your settings. Pete

Sorry, I need some clarification: 1. Does the Cockpitsonic Driver make your switches look like normal Joystick switches to Windows ("game controllers", and FSX? Can you assign them in FSX? 2. Are you saying FSUIPC sees the switches and you can make assignments initially, but not after you load an another aircraft? 3. If so, if that ALL other aircraft, or only a specific aircraft? Project Magenta does not look like a joystick to Windows, FSX or to FSUIPC! FSUIPC itself does not handle displays. Your overhead should come with software to do that, by reading FSUIPC offsets. I'm sure CS have software or scripts to suit Project Magenta! You can't really use the PMDG 737NGX with Project Magenta. The PMDG systems are all separate and different to those in FSX which PM uses. Any program wishing to drive displays for PMDG Boeing aircraft (737, 747, 777) can access the offsets for the information it needs provided they are enabled in the PMDG aircraft ini file, as PMDG instruct. I'm afraid I don't use Cockpitsonic software, Project Magenta, or PMDG aircraft. so I can't help with a lot of details for any of those. Pete

That's the log from a good working sessio, no problem. In that case FSUIPC isn't actually being loaded, as it starts the Log immediately. This is exactly the sort of problem which occurs when the previous session ended with a problem which is somehow attributed to FSUIPC. So my guess is that something you are using is causing a hang or crash in one of the many threads, or possibly in a lower level (driver). Are you saying you don't have admin rights when you run P3D normally? That's a mistake. Many things need it to be run in your main owner-administrator account. So, perhaps that's the solution? Pete

What controls are you using for the other ways yo are moving them? Generally things need to change to be noticed. If the others are using the more usual AXIS ELEVATOR SET and AXIS RUDDER SET controls, then so should your buttons. Another way, which can be applied to any 'SET' control, is to force the change. Assign it with parameter 1 (say) on Press and 0 on Release. Pete

Was iVap running "as administrator"? Generally, either NOTHING should be run "as administrator", or everything related to it must be as well. Pete

I've never heard of any such small limit, and certainly not a cumulative one! Just take a look at the many other posts in this forum with many and larger attachments. Maybe you are using some odd method? I'd check what you are doing if I were you, or if you are being victimised for some reason, post a problem report on your Simmarket account. Anyway, if it is that small why not simply paste its contents into your message? Use the <> button above the edit area and paste it. Pete

Why not just use FSX-SE? It has many improvements over FSX including more efficient code. Pete

Files? Only need the Log. If that's too big there's something badly wrong, as there's not much to it by default. You can ZIP it in any case, it ZIPS up well. No way. That is simply not possible. you are doing something else wrong. Replacing 5.122 with 5.122, no matter whether from here (in the Downloads subforum) or Scvhiratti won't change anything as the exact same file results! Pete

Well, the log does show it gets data about those devices, as shown RED below: 906 Product= Button Box Interface 906 Manufacturer= Leo Bodnar 906 Serial Number= B28218 906 Vendor=1DD2, Product=1140 (Version 1.4) 922 GUIDs returned for product: VID_1DD2&PID_1140: 922 GUID= {0835D8F0-F31C-11E7-8016-444553540000} 922 Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 922 Product= BU0836 Interface 922 Manufacturer= Leo Bodnar 922 Serial Number= B19406 922 Vendor=16C0, Product=05B5 (Version 1.34) 922 GUIDs returned for product: VID_16C0&PID_05B5: 922 GUID= {54768E70-F318-11E7-8007-444553540000} 922 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X638,Y1023,Z488 922 GUID= {54768E70-F318-11E7-800B-444553540000} 922 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V1023,X908,Y889,Z621 922 Product= BU0836A Interface 922 Manufacturer= Leo Bodnar 922 Serial Number= B31477 922 Vendor=16C0, Product=05BA (Version 1.34) 922 GUIDs returned for product: VID_16C0&PID_05BA: 922 GUID= {54768E70-F318-11E7-8003-444553540000} 922 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4093,Y0,Z0 922 Product= BU0836 Interface 922 Manufacturer= Leo Bodnar 922 Serial Number= B17614 922 Vendor=16C0, Product=05B5 (Version 1.34) 922 Product= Po.Joystick id 922 Manufacturer= PoLabs 922 Serial Number= 2.11582 922 Vendor=1DC3, Product=1001 (Version 16.0) 922 GUIDs returned for product: VID_1DC3&PID_1001: 922 GUID= {54768E70-F318-11E7-8005-444553540000} 922 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 922 ------------------------------------------------------------------- Some of the rest of your last message seems to be a duplication of what you said before. Where do you see such advice? I certainly wouldn't deselect any keystrokes in P3D! They are needed for all sorts of things. there is NEVER any need to do so. If you assign a keystroke in FSUIPc it overrides the one in P3D, if that one is used. The manual is clear on this. And I actually said you don't need to do anything with buttons or axes in P3D, just disable controllers. None of this is any different at all in P3D compared to FSX! True, the sim's menus are re-arranged. FSUIPC is exactly the same in all this area, just a 64-bit version of the same logic. It realy cannot be the same in the Calibration sections. THAT's where you calibrate, and THATuses the FS controls, it doesn't read axes at all. it merely intercepts the controls themselves. I think you are looking it the wrong place. It is more likely the difference between Win7 and Win10, though what on Earth is wrong with your Win10 I've no idea I'm afraid. Did you try selecting RAW mode in any of the Axis assignments, to see if using the raw values gives anything? That bypasses Windows calibration. Another way to check the values from the axes you could add more logging options: add these lines to the [General] section in the INI: Debug=Please LogExtras=x1008 Be aware, this will (or should!) make the log much larger. Pete

I have had problems like that, or worse, with other programs. But I'm afraid I don't know what causes them. Sometimes its a rogue system DLL which is being used instead of the correct one to suite the video driver. I think the most usual one responsible is "comctl32.dll" which is the Windows DLL for all those buttons things you see in dialogue boxes. Occasional installers install their own versions which don't necessarily match the Windows version or the video driver. Check that the version of comctl32.dll in "C:\Windows\System32" and also in "C:\Windows\SysWOW64" looks up to date (properties detail). The other system DLL which plays a part is comdlg32.dll, in the same folders. I'm not sure how you repair such problems though. Maybe the Windows repair facility would work, but it would probably need pointing to those DLLs. Another option is to try uninstalling then reinstalling the video drivers, but if your system in Win10 I'm not sure those DLLs are handled by the drivers now. Meanwhile, can the selections be made by clicking the place where the checkboxes would be? Pete

Ouch. The Forum software won't let me. I can move it to other SimFlight forums, but not to any subForums. Seems the MOVE facility is only from Subforums to others or to the main Forum, of from Forum to Forum, but not Forum to SubForum. Which is very odd and restrictive. I'll ask the "powers that be" about that! Pete

Okay ...

Ah, I'd missed that point that you were reading parts of the Log file to get information! That is never a good idea at all. The log file is, well, a log, to enable problems to be diagnosed and fixed. It is always liable to change. Much better to use the provisions made for you to get the exact information you want, reliably! Meanwhile, I checked into what happened to that message, and it was an error that it 'disappeared'. The order of some initialisation code was changed resulting in the message being output before the log was actually created! It will be fixed in the next version, but i'd still prefer you to use the proper provisions for such things. Is there anything else you get from the Log file? If it is something you found no other source for, I would rather look at adding it someplace legitimate. Pete

Two points here. First, there is not yet a "5.22" so I guess you mean 5.122. Second, the Axes tab is for assigning axes, not calibrating. You can calibrate no matter where you assign, in FSUIPC or in P3D. There are 5 devices recognised by FSUIPC: 984 Device acquired for use: 984 Joystick ID = 0 (Registry okay) 984 0=BU0836A Interface 984 0.GUID={54768E70-F318-11E7-8003-444553540000} 984 Device acquired for use: 984 Joystick ID = 1 (Registry okay) 984 1=Po.Joystick id 984 1.GUID={54768E70-F318-11E7-8006-444553540000} 984 Device acquired for use: 984 Joystick ID = 2 (Registry okay) 984 2=BU0836 Interface 984 2.GUID={54768E70-F318-11E7-8007-444553540000} 984 Device acquired for use: 984 Joystick ID = 3 (Registry okay) 984 3=BU0836 Interface 984 3.GUID={54768E70-F318-11E7-800B-444553540000} 984 Device acquired for use: 984 Joystick ID = 4 (Registry okay) 984 4=Button Box Interface 984 4.GUID={0835D8F0-F31C-11E7-8016-444553540000} Where are the "yoke, throttle, etc" connected? I can give you parameters to obtain more logging to see what is going on, but first please go into your Windows Device Manager, find every USB entry, and for those which have power management options in their "Properties" (right-click for that), disable power management. BTW does P3D itself have this problem? Have you tried it? If you only wish to use FSUIPC for calibration, you can assign in P3D instead if you wish. You mean "assignment"! Calibration can only be done after assignment! You never need to "remove" all P3D settings, merely disable the controllers -- one checkbox. Much cleaner and safer! Pete

Check your FSUIPC4.INI file. Whilst it is enabled by default, it can be disabled: OOMcheck=Yes, Quiet or No (Quite is same as Yes but no beeps) OOMcheckInterval=10 (default is 10 secs) Pete

No. You either need to decode the error to determine what is wrong with your program, or, more productively perhaps, ask in Paul Henty's subforum above (he is the author of FSUIPCclient.DLL). I did advise this before! Pete

Exactly. Well obvously is it the Majestic code! The ".FLT" files aren't real FLT files which can be reloaded (FLT is the normal type of non-XML flight files like those used in FSX and earlier versions of P3D). Seems they are just some sort of kneeboard link: [Kneeboard] radiomsg0=C:\Users\Owner\Documents\Prepar3D v4 Files\AutoSave Sat 163418. radiomsgkind0=0 Pete

Sorry, no, I've no idea about iVap. Have you tried asking on their support forum? Pete

I doubt that would help. Win10 seems to be causing all sorts of weird and unfortunate anomalies. I don't know what to suggest. FSUIPC can onlyy send your string on to SimConnect for its action. Pete

For view panning? You can assign that n FSUIPC too. Yes, thank you. We didn't really have any particularly bad winds at all. And we are actually uphill, in semi-moorland and very open. We usually get the worst winds because of this. A couple of our old roof tiles did get dislodged and broken, that's all. Pete

The log doesn't terminate. When was that made, after a bad start or a good one? If the latter you need to let P3D close first. I see it doesn't get as far as even loading the GFDev driver for GoFlight. Also it is a log from 5.122a, whereas the Installer only installs 5.122. How is that? Oh, one other thing: try removing the GFDev64.DLL, see if you get problems without the GoFlight devices. Pete

As Thomas says, the LOG is the most important file. It is made to show what is happening. And check: is a new log being made when youhave one of the failed loads? If so, we need a long form a "normal" run AND the one from the failed run. Usually the reason for a problem on load which is fixed by a re-install indicates that the previous session of P3D did not terminate successfully, so the DLL gets "marked" in the registry. This stops it loading, but SimConnect stupidly doesn't notice this and tries to enter it. The installer clears this 'black' mark. What about when you close P3D, without closing Win10? Pete

That sounds exactly like dual assignments. Don't "disable the axis" in P3D: disable controllers in P3D altogether. What is "joy.cpl"? Pete

That has me concerned. Do you normally mix assignments in P3D and FSUIPC? You should choose one or the other, and if assigning in FSUIPC, disable controllers properly in P3D. Don't rely on delting assignments there. The normal axis logging does not identify the actual source of the value being hanled. It could be from the axis itself, read by FSUIPC, or it could be from somewhere else. To check the values from the axis itself you would need to add more logging options: add these lines to the [General] section in the INI: Debug=Please LogExtras=x1008 Be aware, this will make the log mucvh larger. Pete