Pete Dowson

This is the exact same problem Sabrefly has. Can you check the last few messages in the pinned thread about new Joystick Scanning at the top of the forum please? i'm actively trying to sort it out. I need extra logging: Debug=Please LogExtras=x200000 and running 4.963d -- link at the end of that thread. Then show me the log please. Pete

Ah, it'll be COUATL. I use GSX and find I get problems with COUATL or BGLMANX regularly. The secret is always to download the latest AddOn Manager for the Virtuali / DreamTeam site and run that. It will make sure all those bits, and SODE too (another problem one) are correct and up to date. I've never quite got the same problem as you, mind, but doing this has always solved things for me. Pete

Okay. I've been throughthe code thoroughly and i just can't see where it is going wrong. it may be that one of your attachments doesn't take nicely to the inquiries I'm sending out, but that seems rather unlikely. So, here's a version with a lot more being logged. The gogging option you previous added is still needed. Download FSUIPC4963d_TEST.zip please. This is the logging I get in this area with just two devices attached: 280 #### Initialising Dlrectinput Axis Scanning ... 280 EnumDevices: 0.GUID={521A4280-6D1D-11E5-8002-444553540000} 280 EnumDevices: 1.GUID={D1A5BF50-AFA6-11E4-8001-444553540000} 343 EnumDevices: found Microsoft SideWinder Freestyle Pro (USB) 343 EnumDevices: GUID matches our device 1 343 EnumDevices: found Saitek Pro Flight Quadrant 343 EnumDevices: GUID matches our device 0 421 ---------------------- Joystick Device Scan ----------------------- 421 Checking: \\?\hid#vid_045e&pid_000e#a&2f08f23c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 436 Product= Microsoft SideWinder game controller 436 Manufacturer= Microsoft 436 Vendor=045E, Product=000E (Version 0.153) 436 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_000E\Calibration\0" 436 ... and a "GUID" value 436 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_000E\Calibration\0" 436 ... and a "GUID" value 436 Assigned joystick id 1 (Registry okay) 436 ... okay, Acquired device as #1 436 GUID= {D1A5BF50-AFA6-11E4-8001-444553540000} 436 Registered Product Name= Microsoft SideWinder Freestyle Pro (USB) 436 Checking: \\?\hid#vid_045e&pid_0772&mi_04#7&18350873&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 436 Checking: \\?\hid#vid_06a3&pid_0c2d#7&23aeb000&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Product= Saitek Pro Flight Quadrant 452 Manufacturer= Saitek 452 Vendor=06A3, Product=0C2D (Version 2.0) 452 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0" 452 ... and a "GUID" value 452 Assigned joystick id 0 (Registry okay) 452 ... okay, Acquired device as #0 452 GUID= {521A4280-6D1D-11E5-8002-444553540000} 452 Registered Product Name= Saitek Pro Flight Quadrant 452 Checking: \\?\hid#vid_0835&pid_8501#7&1c27f73b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_0835&pid_8502#8&164c5fe6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_09f3&pid_0020#7&2314e6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_09f3&pid_0020#7&59f0683&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_09f3&pid_0028#7&11239ddd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_09f3&pid_0028#7&19612c8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_09f3&pid_0030#7&11ea791&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_09f3&pid_0030#7&13d85836&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_413c&pid_8505&mi_00#7&3b8b17c4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_413c&pid_8505&mi_01&col01#7&17b3da02&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_413c&pid_8505&mi_01&col02#7&17b3da02&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_413c&pid_8505&mi_01&col03#7&17b3da02&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_413c&pid_8505&mi_02&col01#7&2f776647&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vid_413c&pid_8505&mi_02&col02#7&2f776647&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vwhid&col01#1&2d595ca7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vwhid&col02#1&2d595ca7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vwhid&col03#1&2d595ca7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vwhid&col04#1&2d595ca7&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 Checking: \\?\hid#vwhid&col05#1&2d595ca7&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030} 452 ------------------------------------------------------------------- 452 #### Completed Dlrectinput Axis Scanning 452 ---------- Making INI JoyNames Section ---------- 452 Joy#0: Name = "Saitek Pro Flight Quadrant" 452 Joy#0: GUID = {521A4280-6D1D-11E5-8002-444553540000} 452 Joy#1: Name = "Microsoft SideWinder Freestyle Pro (USB)" 452 Joy#1: GUID = {D1A5BF50-AFA6-11E4-8001-444553540000} 483 ------------------------------------------------- Thank you! Pete

You only seem to have 6 joystick devices connected, though, not 16. The others won't feature in this stuff FSUIPC is doing. That last log at least narrows it down a bit for me. i'm just adding more logging in that area. don't remove that logging option -- I'll post a link to a version with more logging. Thanks for helping with this. I don't know what is going wrong yet ... Pete

Oh, and also, can I see your FSUIPC4.INI file please? Pete

Oh, dear, I was sure I must have fixed it. I'm not going back to the joystick scanning of 4.963, as the new way does fix a lot of problems with Joystick IDs. Can you try again but first add this to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x200000 Take care to get the right number of 0's! ;-) This should provide logging in the crucial area, though I might need to add more. Shame it doesn't actually crash. Can you also tell me what else you are running apart from FSUIPC and EZCA, please? Pete

Please try FSUIPC4963c_TEST.zip Pete

I think it is due to some weird return from one of your devices in its Product Name identification. Please try: FSUIPC4963c_TEST.zip Pete

Yes, it is all sync actions. They are all the same. I think I've fixed it properly here. I'll upload a fixed version for testing soon. The other way of appyling reversal to axis inputs, through the add/multiply options via parameters on the axis assignment itself, wouldn't have been a problem because the values already reversed before trying to sync it. When done at the calibration stage it's a lot more complicated! 4.963c_TEST, soon. I'll post a link here. Pete

Aha! Try not running EZCA. I've seen lots of problem reports with that on P3D. I gave up on it and set all my views using Opus. Pete

As I said, Application logs -- "Application" in the left, under Windows Logs!!! The program just offers a Window like Explorer. Have you NEVER used Explorer at all? How do you find files? Pete

So, that's not a crash at all. I don't know what it is. I'm just about to upload 4.963c_TEST for you you try, please. Pete

Oh dear. Event Viewer is, like Task manager and all the other basic Windows facilities, part of Windows. You have HELP available,in your Windows, surely? Press the Windows Start button, or whatever way you get to ask questions etc in Win10 if that's what you are using. Enter "Event Viewer" and press ENTER. You'll get an Explorer-like Window. The folder for Application Logs in in one of those on the left, Windows Logs I expect. In the log, actual crashes are called Errors and highlist with a red icon. Pete

On second thoughts, I'll upload a TEST copy of 4.963c for you to try . I'm wondering if your crash is just a bad USB "Product" name being read. I've seen that here a couple of times, and have taken steps to avoid it making a problem. I still need to see the crash details please, first. Pete

I need the crash details. The log is just telling me how far it got, not why it crashed! In fact I've never seen a crash at that stage of logging. The fact that it IS just before the revised Joystick Scanning is suggestive that it may well be related to the 4.963b chages, but it should at least have logged ---------------------- Joystick Device Scan ----------------------- before crashing! Of course! The windows crash details which tell me which module and what location the crash occurred at. If you can get it on screen when Windows notifies you of the crash and offers them via a button, you can find the complete history of all your crashes and other problems in the Windows Event viewer. Look in the Application Logs folder when you run Event Viewer. I am holding back 4.963c for proper release until i see what yours is doing. I also still want the list of other addons being loaded at that time -- DLLs and EXEs. Pete

Well, I'm not so sure. 4.963b was only different from 4.963 in the USB joystick scanning area. 4.962a to 4.963 added fixes to Lua terminations using exit functions, mapping of offsets for PMDG 747, and the addition of the planned airport and frame rate target options in the Traffic Limiter facility. I can't think of any reason why the ancillary files and installer actions would change things so much. but we'll see. I'll keep an open mind! ;-) Pete

And crash details / Log please. Pete

Oh, of course, when I send "maybe keystrokes" I forgot -- you just want to send Axis Throttle Set controls with specific parameters. You'll need to look up the control numbers in the Controls List installed in the FSUIPC Documents folder. Pete

No, it cannot be anything to do with these changes, which are completely unrelated to FS or P3D. Why were you still on 4.962a many days when 4.963 is the currently supported release? Have you not yet run the 4.963 installer? Please never install interim updates without first running the correct up to date Installer. Sorry, but it is certainly no help at all telling me P3D crashes with no information about the crash at all. Please get 4.963, install that and test. Don't test the new Joystick Scanning changes till 4.963 works okay. If 4.963 crashes your P3D I need you to report this in a new separate thread, with Windows crash details, FSUIPC4.LOG file (as far as it got), and details of other addons being used. Thanks Pete

Yes. Change the joystick + button numbers to the one you want, and the controls it sends to the ones you want, maybe keystrokes? You'd place it into the FS Modules path and get it running by using an [Auto] section in the FSUIPC4.INI file, like [Auto] 1=Lua TripleUse If you use Profiles and only want it running for certain aircraft, just make the section [Auto.<profile name>] You should really read up about plug-ins in the Lua document included. You'll find plug-ins useful for many things. Pete

Okay. I've verified this problem here. Looks like it has ALWAYS been like this! Weird, no one spotting this all these years. Too late for FSUIPC3, but I'll fix it in 4.963c which will be up for download later today (DLL only -- in the Download Links subforum). [LATER] Arrggghhh! This is awful. The code for doing the syncing is very old. And it simply bypasses the REV option! And, yes, it has always been this way! The clue was the fact that the normal axis logging doesn't show anything when SYNC is active. It gets the axis value written directly to the offsets instead, like an external throttle control program. I think this was to avoid unnecessary recursive calls back into the calibration routine I'll add the REVerse check (only on Throttle 1 because that is the value copied to all of the others) before it writes to the offsets. It still won't be logged though. Pete

Strange. All throttle sync does is copy one throttle value to all the others. Is this something new in FSUIPC, or have you only just started using throttle sync or reversing your throttles? Pete

Interesting. I don't know ChasePlane. I wonder how it manages to defeat a simply SimConnect menu mechanism? Anyway, glad you solved it! Pete

Good. thanks for letting me know. Pete

You mean you don't even have it linked up yet? It would be automatic if your Network connection was good and both PCs are in the same Windows Workgroup. Otherwise you have to add both ServerName or ServerIPAddress AND the Protocol patameters. All this is pointed out in the WideFS User Guide, in the part which requests you to please read it! It isn't very long! Pete