Pete Dowson

They remove registry entries which should have been removed anyway when you uninstalled the controllers and drivers using the Windows Device Manager. That's what that step should have achieved (the one I advised on the 29th August). Strange that it didn't manage to do that -- there must have been something up with the registry itself. Thanks for the report and the links. Pete

Offsets 66C0-66FF are free for users to do with as they wish. Pete

I've investigated and found the reason. When the instant replay dialogue is selected, P3D correctly signals that the sim state is "stopped", but then it doesn't indicate that it has started again until the replay is finshed or exited by ESCape. When the Sim is stopped, FSUIPC doesn't scan buttons or joystick axes, and to enable these actions all the time, even when in option dialogues, is not healthy. It is quite easy to have assignments which do things which either go wrong in such modes or crash the sim. I've tried to find some indication that it is in Instant Replay mode, but there seems to be nothing provided in either SimConnect, or in the lower level PDK facilities. I've asked L-M whether they can provide such an indication. I don't hold out a lot of hope, at east not quickly anyway. Pete

It looks like FSUIPC never sees the button presses in Instant Replay mode. It is being told by SimConnect that the sim is STOPPED, as when it's in menus: 102781 -------------------- Starting everything now ---------------------- 102797 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N <<< Okay here, after loading and ready to fly 103984 Advanced Weather Interface Enabled 259578 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y <<< stopped here as if in a Menu 259578 Sim stopped: average frame rate for last 164 secs = 39.7 fps 259578 Max AI traffic was 114 aircraft (Deleted 0) And it isn't started again till you press ESCape then exit: 301812 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0 301812 .. Key not programmed -- passed on to FS 301812 *** EVENT: Cntrl= 66268 (0x000102dc), Param= 0 (0x00000000) USER_INTERRUPT 301890 KEYUP: VK=27, Waiting=0 302031 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N <<< ready to fly again after using ESCape 305719 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT 305781 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 307922 === Closing session: waiting for DLLStop to be called ... I'm not sure what I can do about that, but I'll take a look. Pete

Seems that FSUIPC doesn't receive any button events during instant replay, or if it does it doesn't process them. if it is the former, then it would be a function of SimConnect -- but then you'd expect it not to work with FS assignment either. I think I need a little more logging before trying to reproduce this. Please enable "Button" logging too, in the Logging tab, and also "Extras". Then send a revised "instant replay" log. Pete

I dont't think I did. I actually said There are EYEPOINT controls in P3D. I don't think they are available in FSX Those Eyepoint controls were another set, which I happened to see first: EYEPOINT SET LATERAL 66988 EYEPOINT SET VERTICAL 66989 EYEPOINT SET LONGITUDINAL 66990 EYEPOINT MOVE LATERAL 66991 EYEPOINT MOVE VERTICAL 66992 EYEPOINT MOVE LONGITUDINAL 66993 And I think those are Axis controls -- at least the "SET" ones. But you want to move around in the cockpit. Camera selection is just changing to different camera views, not moving in the cockpit1 If you have cameras set up, or just want to use the default ones, then those selection controls might be useful. But the default ones tend to be "Cockpit", "Virtual Cockpit", "Spot", "Fly-by", "Top-Down", and so on -- those views you can also select from the menu. if you look in the CAMERAS.CFG file in your FSX in your AppData\Roaming folder, then the camera entries sometimes have: HotKeySelect=number where the number is 0-9. That tells FSX that that view is to be selcted by the View Camera n control. But I don't think this is anything to do with what you asked about. Pete

Looks good. Do you have P3D going straight into flight mode, or displaying the selection menu first? I ask because there's something going on between 120 seconds in and 298 (i.e. nearly 3 minutes). Was that in the Menu, or all loading time? Nothing to worry about though. My system takes several minutes to load up too -- I have lots of added scenery layers! Pete

See if there are FSUIPC5.INI and FSUIPC5.LOG files in the Modules folder. if so then, no, it won't cause any further problems. If you do find the LOG file you could show it here so i can verify the installation is now really good to go. Pete

Good. Probably that's because you set the permssions okay, though there's still that ACL failure logged when the Installer tries to do it too (it will do, just in case, as it doesn't read them). Or it was just another of those odd windows 10 quirks! 😉 Pete

Please use the Weather logging in FSUIPC's Logging tab, and show the part you think is wrong. Weather logging shows both the METAR strings received and their decoding. Pete

Ah, a hardware problem! Often the last thing I think of! 😉 Glad it is sorted. Pete

Ah, good. Then you should be able to assign to those. Yes, I see them in the LIST OF CONTROLS document (you have one in your FSUIPC Documents subfolder): EYEPOINT UP 66524 EYEPOINT DOWN 66525 EYEPOINT RIGHT 66526 EYEPOINT LEFT 66527 EYEPOINT FORWARD 66528 EYEPOINT BACK 66529 EYEPOINT RESET 66530 I don't understand. What controls (by name) did you assign? What was different about FSUIPC sending them and you sending from the keyvboard? Did you ever try assigning to the same keypresses (though that's less efficient than assigning to the same controls as assigned in FS)? Ah, are they not available in FSX? I'm sure they are. My list shows them t be: VIEW CAMERA SELECT 1 66851 VIEW CAMERA SELECT 2 66852 VIEW CAMERA SELECT 3 66853 VIEW CAMERA SELECT 4 66854 VIEW CAMERA SELECT 5 66855 VIEW CAMERA SELECT 6 66856 VIEW CAMERA SELECT 7 66857 VIEW CAMERA SELECT 8 66858 VIEW CAMERA SELECT 9 66859 VIEW CAMERA SELECT 0 66860 But they aren't axes. just button or key press activated, and I think the selection numbers, 0-9, need to be assigned in the Camera definition file (which may be aircraft specific?). Pete Pete

Did you change the path "E:\Prepar3D v4" to match your P3D location. I did find your path from the log you sent and edited my post, but it looks like you are reading my posts almost before I finish them! Did I say "annoying"? And, yes, I don't understand either. But if the Modules folder has write access, and the DLL.XML is put right, you should be good to go. Pete

Oh, researching some of last years reports of the ACL error, I found this "As noted in another thread here, there's a bug introduced by a recent Win10 update, and that's in the "ACL" functions" Now that was in November last year (are related to fSUIPC4 not FSUIPC5). Are you using Win10 and is it perhaps out of date? Pete

Please see my revised reply above, crossed with yours. If everything you say is true, and I believe you, your system is unique. I've not come across one where any installer cannot do its job, being completely prevented by Windows despite the user taking appearently adequate steps. something is wrong with the system somewhere. Try the manual install and see if that works. Pete

Error 1332 is documented as meaning "No mapping between account names and security IDs was done.", whatever that really means. So my next question would be: what does the Security tab in the modules folder properties show? Is "Everyone" included as a user name, and if so, when selected, are there ticks below against "Full control" and "Modify"? If not you will need to set it yourself (again) as already mentioned. Something is wrong as Windows is evidently preventing access. You can get FSUIPC itself loaded by editing or creating a DLL.XML file yourself, since you can write to the AppData folder. with just FSUIPC loaded there is should be: <?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> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>F:\P3D\Modules\FSUIPC5.dll</Path> </Launch.Addon> </SimBase.Document> However, if FSUIPC cannot write to the Modules folder then it will not be able to save settings. Pete

Well, that message does indicate otherwise. Can YOU see and edit the DLL.XML file? Can YOU see and edit files in the P3D modules folder? Being the Administrator isn't the same thing. Running "as administrator" gives more elevated privileges. If you can access both the modules folder, and C:\Users\Arcbirds\AppData\Roaming\Lockheed Martin\Prepar3D v4\ then you personally can allow full access by right clicking on the folder properties: Security-->add Everyone as a user name, then check 'Full Control' access below. Pete

That line in the Log indicates that you are not running the Installer "as administrator".(a right-click option). Pete

Third party add=ons do not always use the built-in controls and options. They are mostly diferent. Does the Mindstar add-on have contorls or keyboard short-cuts for those functions which you can use? Sorry, but FSUIPC supports all of the in-built sim facilities, but there's no way it can have built in facilities for all add-ons. Please refer to the Mindstar documentation, see if there's somehing you can use. If it is only controllable by Mouse, see if it will work with mouse macros. More likely you have to work with L:Vars.(local panel variables). Pete

There's no way it is changing it. It just receives what is supplied. is this with P3D? P3D itself is supplying the data. Sorry, are you saying one menu isn't actually ended before the next is displayed, or one is missing altogether? If so this sounds like a but in P3D. Is it P3D? Which version? Do you have the latest version installed, of it and of WideClient? Pete

Usually you have ProSim displays set to display "on top". maybe you can change that? I don't know. Mine are most certainly always on top of anything else. Right-click on it and see what options you have. Pete

Which part, looking in the FSUIPC log file? I don't know exactly what they are (they are P3D controls), but normally "select" controls just select something, not move it. Are you sure they are listed in Axis assignments, not buttons assignments? Sounds like they view different existing camera views. Pete

Even just attempting to install the Saitek software can mess certain registry entries up which FSUIPC depends om. First thing to do is use Windows Device Manager to uremove the devices altogether -- software and hardware. Then re-boot the PC and let Windows reinstall them using the default drivers. NEVER have assignments in FSUIPC if you have the device enabled in P3D. Disable controllers in P3D if you want to assign in FSUIPC. If all you want to do is calibrate in FSUIPC, you can assign in P3D instead of FSUIPC. If removing completely and reinstalling doesn't help, I need to see three files from the P3D modules folder: FSUIPC5.joyscan.csv FSUIPC5.LOG FSUIPC5.INI Pete

That's what calibration is for Could be. I have heard such stories about Win10 updates. FSUIPC uses no registry entries at all, except in the initial search to find and identify devices by thier IDs and GUIDs. All of its own settings are in your files, in the modules folder (INI file and any separate Profile files you might have created if using "UseProfiles=Files". There could only be other device handling software, or controllers not being disabled in FSX. Of course some add-on aircraft (notably PMDG ones) do their own thing with some joystick axes. Pete

There are EYEPOINT controls in P3D. I don't think they are available in FSX. Find out the names of the controls when you used the keypresses. To do this just enable Event logging in FSUIPC and look at the LOG file.. Then you can assign to those in FSUIPC. FSUIPC allows a POV to be treated as an Axis (eg to assign to PAN VIEW), or as up to 8 buttons, one for each 45 degree angle. So, just assign to the controls you want there, in the buttons tab. Pete