Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 You knew it, Pete, v4.963_TEST crashes!! ********* FSUIPC4, Version 4.963b (26th February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.3.5.17625 Reading options from "F:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=5AD70000 User Name="Igor Petrov" User Addr="petrovigor@umail.ru" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 27/02/2017 17:19:31 15 FLT UNC path = "\\I6\Prepar3D v3 Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 3.3.5.17625 15 api.dll: 3.3.5.17625 15 controls.dll: 3.3.5.17625 15 fs-traffic.dll: 3.3.5.17625 15 G3D.dll: 3.3.5.17625 15 language.dll: 3.3.5.17625 15 sim1.dll: 3.3.5.17625 15 visualfx.dll: 3.3.5.17625 15 weather.dll: 3.3.5.17625 15 window.dll: 3.3.5.17625 15 ---------------------------------- 15 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 15 Found it: trying to connect 15 FS UNC path = "\\I6\Prepar3D v3\" Going back to v4.963 official. Thanks, Igor PS: Is there any other log somewhere that I should provide?
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 10 minutes ago, Sabrefly said: I don't think I'll have any after 4.963 )) 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
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 38 minutes ago, Sabrefly said: You knew it, Pete, v4.963_TEST crashes!! 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! 38 minutes ago, Sabrefly said: PS: Is there any other log somewhere that I should provide? 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
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 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
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 2 minutes ago, Pete Dowson said: Really odd. But in that case 4.963 should too. 4.963 seemingly works OK, nothing to report. 3 minutes ago, Pete Dowson said: 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 I don' know where to start from: I have no Event viewer, I don't run it. Should I install it? I have no Application Logs folder. Thanks,
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 10 minutes ago, Pete Dowson said: 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. Talking about USB Joysticks and HID devices I'm one of your worst cases, there are so many, 16 connected. Please explain how to extract the crash log. Prepar3d just disappears from the taskbar, Ezdok is still running, and I can see Prepar3d.exe (32 bit) running in the Processes in TaskManager. 20 minutes ago, Pete Dowson said: ---------------------- Joystick Device Scan ----------------------- before crashing! I've posted it already (after v4.963 installation) a few posts above. Thanks, Igor.
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 I mean I can't get you a newer (than 4.963) Joystick Device Scan, because Prepar3d launches and then hides in the processes (where it runs until I stop it in Task Manager) instead of launching its GUI. Thanks, Igor. PS: I'm going through this now http://www.dummies.com/computers/operating-systems/windows-10/how-to-use-event-viewer-in-windows-10/
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 Here's a photo of the screen with Event Viewer. What do you want me to do with it? Thanks, Igor.
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 31 minutes ago, Sabrefly said: don' know where to start from: I have no Event viewer, I don't run it. Should I install it? I have no Application Logs folder. 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
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 27 minutes ago, Sabrefly said: Prepar3d just disappears from the taskbar, Ezdok is still running, and I can see Prepar3d.exe (32 bit) running in the Processes in TaskManager. 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
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 Yes, Pete, from what I've gathered all ERRORS point to EZCA.exe only. Thanks, Igor.
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 5 minutes ago, Sabrefly said: Here's a photo of the screen with Event Viewer. What do you want me to do with it? 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
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 1 minute ago, Sabrefly said: Pete, from what I've gathered all ERRORS point to EZCA.exe only. 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
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 I've turned off EZCA.exe in EXE.xml now it's not running, but same thing with Prepar3d, it just jumps into processes away from the screen and stays there! I think I saw a similar behavior when P3D didn't start with FSUIPC V4.960 or 61 (I can't remember now). Attached is Application log picture, I launched P3D at 6:58. No errors, but no P3D on the screen. Happens only in v4.396b
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 9 minutes ago, Sabrefly said: Happens only in v4.396b 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
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 See if you can see something unusual #1: Thanks!
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 12 minutes ago, Pete Dowson said: 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 Downloading! Thanks.
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 No, same thing with FSUIPC4963c_TEST. I've noticed this time that P3D splash screen (standard) jumps inside into the desktop exactly when my GoFlight instruments light up! Thanks, Igor.
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 11 minutes ago, Sabrefly said: No, same thing with FSUIPC4963c_TEST. 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
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 Oh, and also, can I see your FSUIPC4.INI file please? Pete
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 This is what I run alongside, nothing else: [General] Debug=Please LogExtras=x200000 UpdatedByVersion=4963c History=BTCKA6KU9SEWPUDSBVO9C InitDelayDevicesToo=No Annotate=Yes NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No NewDeleteVehiclesForAES=No AutoScanDevices=Yes AssignJoystickIDs=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No ThreadAffinityMask=x0 LuaAffinityMask=x0 InitDelay=0 GetNearestAirports=Yes OOMcheck=Yes OOMcheckInterval=10 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=20 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No LogOptionProtect=Yes TimeForLuaClosing=2 WideLuaGlobals=Yes [JoyNames] AutoAssignLetters=Yes A=CH Control Manager Device 2 B=Saitek P8000 C=CH Control Manager Device 1 D=CH Control Manager Device 4 E=CH Control Manager Device 3 F=F16 MFD 1 G=CH Throttle Quadrant USB H=CH Throttle Quadrant USB J=CH Pro Pedals USB K=CH Pro Throttle USB L=CH Fighterstick USB 1=Saitek P8000 1.GUID={6353CB80-18FC-11E6-8003-444553540000} 0=CH Control Manager Device 2 0.GUID={C82A9610-1924-11E6-8001-444553540000} 6=F16 MFD 1 6.GUID={E21EB120-1927-11E6-8001-444553540000} 2=CH Control Manager Device 1 2.GUID={C82C6AD0-1924-11E6-8002-444553540000} 3=CH Control Manager Device 4 3.GUID={C87A3CB0-1924-11E6-8003-444553540000} 4=CH Control Manager Device 3 4.GUID={C87B2710-1924-11E6-8004-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=AZ,256,D,4,0,0,0 -{ DIRECT: Throttle }- 1=CX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 2=CY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 3=DX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 4=DY,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 5=DZ,256,D,3,0,0,0 -{ DIRECT: Rudder }- 6=ES,256,D,6,0,0,0 -{ DIRECT: Mixture }- 7=ET,256,D,5,0,0,0 -{ DIRECT: PropPitch }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=PB,0,K74,10 -{Key press: ctl+J}- 2=PB,7,C1009,0 -{traffic density toggle}- 4=UB,7,C1009,0 -{traffic density toggle}- 5=PB,31,C1092,0 -{Re-SimConnect}- 9=PB,12,C66846,0 -{BAROMETRIC_STD_PRESSURE}- 10=PB,11,C65584,0 -{BAROMETRIC}- 11=PB,27,C1085,0 -{traffic zapall}- 12=PB,20,C1079,0 -{traffic zapper}- 14=PB,14,K123,10 -{Key press: ctl+F12}- 15=RA,1,K48,10 -{Key press: ctl+0}- 16=PB,5,K69,9 -{Key press: shft+E}- 17=UB,5,K49,8 -{Key press: 1}- 18=PB,6,K69,9 -{Key press: shft+E}- 19=UB,6,K50,8 -{Key press: 2}- [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [Sounds] Path=F:\Lockheed Martin\Prepar3D v3\Sound\ Device1=Primary Sound Driver Device2=???????? (Realtek High Definition Audio) Device3=Realtek Digital Output (Realtek High Definition Audio) [Programs] [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16254,0,128,16127 SlopeAileron=2 Elevator=-16384,0,128,16255 SlopeElevator=1 Rudder=-16254,-512,512,16255 SlopeRudder=2 LeftBrake=-16384,4224/16 RightBrake=-16380,4992/16 Throttle=-12223,16383 PropPitch=-16384,16254 Mixture=-16384,16383 [ClientNames] 1=KAT 2=LENA 3=F4 [VRInsight] 1=com3 [Auto] 1=Lua ASAirbus [LuaFiles] 1=ipcReady 2=linda 3=ASAirbus [Profile.AS A320] 1=Airbus A320 British Airways G-EUUU 2=Airbus A319 British Airways BA-GDBCF 3=Airbus A321 British Airways G-EUXG 4=Airbus A320 British Airways G-GATK 5=Airbus A320 British Airways G-EUUK 6=Airbus A320 United Airlines N405UA [Window.LUA display] Docked=7352, 2745, 3549, 2470 [Profile.A2A C182T] 1=C182_N516DM [Window.Radar Contact] Docked=198, 2457, 3571, 1308 [MacroFiles] 2=E190 1=EMB190 3=EMB195 [Profile.E190] 1=Embraer 190 BA Cityflyer G-LCYL [Profile.E195] 1=Embraer 195 Britsh Airways CityFlyer (G-LCYZ) [Profile.LEGACY v2] 1=RealAir Lancair Legacy V2 N323DE [Traffic Limiter] TrafficLimit=250 AirportPreference=0 GroundPreference=0 NearerPreference=0 TargetFrameRate=0
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 This is the newer log: ********* FSUIPC4, Version 4.963c (27th February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.3.5.17625 Reading options from "F:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=567C0000 User Name="Igor Petrov" User Addr="petrovigor@umail.ru" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 27/02/2017 20:26:09 0 FLT UNC path = "\\I6\Prepar3D v3 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 3.3.5.17625 0 api.dll: 3.3.5.17625 0 controls.dll: 3.3.5.17625 0 fs-traffic.dll: 3.3.5.17625 0 G3D.dll: 3.3.5.17625 0 language.dll: 3.3.5.17625 0 sim1.dll: 3.3.5.17625 0 visualfx.dll: 3.3.5.17625 0 weather.dll: 3.3.5.17625 0 window.dll: 3.3.5.17625 0 ---------------------------------- 0 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 0 Found it: trying to connect 0 FS UNC path = "\\I6\Prepar3D v3\" 78 #### Initialising Dlrectinput Axis Scanning ... Thanks,
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 2 hours ago, Sabrefly said: Talking about USB Joysticks and HID devices I'm one of your worst cases, there are so many, 16 connected. 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
Sabrefly Posted February 27, 2017 Report Posted February 27, 2017 13 minutes ago, Pete Dowson said: You only seem to have 6 joystick devices connected, though, not 16. The others won't feature in this stuff FSUIPC is doing. Right, I meant 16 USB devices, 6 of them are joysticks and the rest are GoFlight panels and VRINSIGHT FCU Airbus. Thanks,
Pete Dowson Posted February 27, 2017 Author Report Posted February 27, 2017 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
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now