aua668

Hi Glenn, I solved my problem with the limit of 127 LUA files very pragmatic: I made a sub-directory per plane type with all my necessary plane-specific LUA modules and one with the generic LUA modules. I start P3D with a CMD file. In this file I delete all *.LUA files in the FSUIPC directory. Then I copy the generic modules and the plane specific modules into the FSUIPC directory. In the FSUIPC.INI file I delete the LUA files section and add a plane specific section to the INI file. Then I start P3D. So I simulate something like profiles for LUA files. By that simple method I can use the maximum number of possible LUA files per plane without breaking the limits if I use different planes. I also decide out of a config file, which LUA modules I have to start for a specific plane type. @Pete: As I have a solution, for me there is no immediate need for the profile based version, if it's complicated. But It would be very elegant, as the profile specific setting are a really good way to define things differently per plane. So if this comes in future versions, this would be a nice enhancement of this already great piece of software. Rgds Reinhard

Hi, Just one idea for the LUA path as planned. It would be great, if this could be combined with the profiles implementation. If we could get the active LUA path and the LUA modules out of the profiles INI file instead out of the FSUIPC INI file (if profiles are used) like you do this for buttons, axes etc., this would allow to have several setups dependent on the plane used. This would be really great! Rgds Reinhard

Hi, Just to provide some information about LUA modules. I have a similar setup with around 80-90 LUA modules running fully event driven to connect my GoFlight Hardware to some complex airplanes. I wrote them for being able to run them independent per function. So one module is for transponder, one for COM1 etc. I can start and stop them independently, which is good during development phase. I once tried to combine them in one single LUA module. As I use naming conventions in my code, which didn't create conflicts, this was quite easily done. Interestingly the modules have been working but the responsiveness to events have been worse compared to the single modules. You typically won't see this with single switches, but if you have radio knobs creating a lot of fast repeating events you could see, that they are reacting much slower. So my experience out of this experiment was, that it's better to have more small and independent LUA modules compared to have only a few big ones with a lot of event triggered functions. And of course the code can easier be maintained. Rgds Reinhard

Hi, Mouse macro creation in P3D 3.4 works as expected in my configuration. So it must be something locally in your installation. Rgds Reinhard

Hi, For the scroll wheel check the FSUIPC documentation for mouse macros and the parameters, which you can apply. Rgds Reinhard

Hi, Did you already use the function ipc.testbutton(joynum,btn) in LUA to check the sate at the beginning and set the simulator equivalent to the current position of the hardware switch? Rgds Reinhard

Hi, The Feelthere E195 can only be programmed via mouse macros. So record a mouse macro for the knobs you want to press. An then assign these macros to your joystick buttons. Rgds Reinhard

Hi, You are right ;-) The first article I ignored, as I thought that this was - according to your comment - introduced by FSUIPC5. I am still on FSUIPC4. And the user used the syntax in the same way I tried (parameter within the string). And this was not working for me. The second article I also found. But the error in that case was simply, that the user specified a wrong path. That was not the case with my problem. Anyhow - it works perfectly now. Rgds Reinhard

Pete, Thanks for looking into that topic. I will go vor the BAT solution as proposed. I searched prior to my posting but I didn't find a similar problem. But I will try to find the topic. Rgds Reinhard Edit: I tried now first RunIf1=READY,CLOSE,"C:\<complete_path_here>\vpilot.exe" -host and BINGO - it did work. I would never had thought, that this will work. Great idea!

Hi, I use FSUIPC 4.974b with P3D v3.4 under Win 7-64bit. I tried to start vPilot (a VATSIM client) on my P3D PC via RunIfN in the host mode, as I run the user interface of vPilot on a second PC. Starting vPilot in host mode is accomplished by adding the parameter "-host" after the program name. As written in the documentation for the RunIfN command, I enclosed the command by ". This should enable the usage of parameters and blanks in the command line. RunIf1=READY,CLOSE,"C:\<complete_path_here>\vpilot.exe -host" BUT: vPilot is not starting and in the FSUIPC log it shows an Error #2 telling, that the program couldn't be started. As soon as I remove the -host parameter, the program is starting fine - of course not in the host mode. It's not a critical issue, as I can start vPilot out of a command file used for starting P3D too. But maybe you could check, why it's not possible to pass a parameter with a "-". The same command in a CMD file works perfectly. Best regards Reinhard

Hi, You should look for the documentation of the Majestic XML interface. Search for the file "MJC84_XML_IF_1008.zip" . The interface works in a way, that you specify the parameter in one L:Var variable and the call the function (via a hash value generated with a provided program) in a second L:Var variable. This only can be realized via LUA code. So to use the Majestic interface (only if you own the PRO version), you must be able to program in LUA. Then you are able to mapt this via events to buttons. Rgds Reinhard

Hi, Check in the Advanced User Manual the section about MaxSteerSpeed. There you will find the solution and the reason for the behaviour. Rgds Reinhard

Hi, You could use or Android tablet as a second monitor to your PC as described here: https://www.howtogeek.com/279069/how-to-use-an-android-device-as-a-second-monitor-for-your-pc-or-mac/ Then move your wideFS button window on that display and you can use the touch functionality on the Android tablet to trigger the WideFS buttons. I have not tried this solution, but it should be simple and working. Rgds Reinhard

Pete, Thanks - I also have no idea, how the aircraft can influence this. I could at least identify one single gauge, which is programmed as a DLL, as the reason. When I remove this gauge from the panel, everything is loaded as planned (of course with the missing gauge). Also an aircraft id is shown. adding this gauge again produces this strange error. So it must be something in this DLL. With your input on reason for the error message I will contact Blackbox Simulation. Best regards Reinhard

Pete, I have a problem with a third-party addon (Blackbox Simulation Airbus A2320). When I try to load this aircraft imn P3D 3.4 (latest hotfix) under WIN 7/64 P3D crashes. Crash log shows sometimes ai_player.dll but sometimes no crashlog is generated at all. P3D just terminates. I use FSUIPC 4.966c. This is obviously not a problem of FSUIPC but a problem of this specific aircraft. Analyzing the FSUIPC log file I have one difference compared to the other aircrafts I use, which work without problems. I found this entry in the logfile: User Aircraft ID not supplied -- trying default With other planes it shows an ID number. Under which circumstances this message is generated? Any hint from your side might help me to track the problem down on the BBS side. Many thanks in advance for your information. Reinhard

Hi, In the P3D Forum there is a link to a good viewgroup tutorial: http://www.prepar3d.com/forum/viewtopic.php?t=119668 Nice feature introduced by P3D, if you have several screens. Rgds Reinhard

Pete, Back from skiing I tested the 4.964f Version with my WIN 7/64 bit OS and P3D 3.4. Everything worked as before and my devices are recognized. Also the order of entries in the INI file has not been changed anymore: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={35A598E0-AAF5-11E1-8002-444553540000} 1=TQ6 1.GUID={317A1330-B07D-11E1-800C-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={35A598E0-AAF5-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 249 ---------------------- Joystick Device Scan ----------------------- 249 Product= Saitek Pro Flight Rudder Pedals 249 Manufacturer= Saitek 249 Vendor=06A3, Product=0763 (Version 1.0) 265 Assigned joystick id 3 (Registry okay) 265 GUID= {35A598E0-AAF5-11E1-8001-444553540000} 265 Product= Saitek Pro Flight Yoke 265 Manufacturer= Saitek 265 Vendor=06A3, Product=0BAC (Version 3.2) 265 Assigned joystick id 0 (Registry okay) 265 GUID= {35A598E0-AAF5-11E1-8002-444553540000} 280 Product= Saitek Pro Flight Quadrant 280 Manufacturer= Saitek 280 Vendor=06A3, Product=0C2D (Version 2.0) 280 Assigned joystick id 2 (Registry okay) 280 GUID= {7EC7D4F0-B1C3-11E1-8001-444553540000} 280 Product= TQ6 280 Manufacturer= GoFlight 280 Serial Number= 00080 7 280 Vendor=09F3, Product=0200 (Version 2.0) 280 Assigned joystick id 1 (Registry okay) 280 GUID= {317A1330-B07D-11E1-800C-444553540000} 280 ------------------------------------------------------------------- Rgds Reinhard

Hi, It's an old comment - lazy programmer ;-) It was copied from another module, where I have to check LVars for change. Rgds Reinhard

Hi, These are typically modules waiting for buttons or switches. Most of them are hardware related to my GoFlight equiment and tie These modules to the Q400. I tried once to merge them into a single module, as I also wanted to see, if this is more efficient. But this was much less efficient. So typically things like rotaries for radio frequencies etc. reacted very slow. By putting them in small modules in their own LUA thread is much better in terms of responsiveness. And during development you can start and stop them individually, which makes testing much easier. Here a typical example setting the landing altitude: -- Q400_GF_LdgAlt.lua -- V1.1 -- Q400 implementation of the GF landing altitude knob -- define GF variables local GF_JoyLetter = ipc.get("GF_RP48_Joy_1") -- define Joystick/Button local GF_JoyButton = 20 local lLdgAlt = 600 -- define XML interface require "Q400_Write_XML_IF" function LdgAlt (pAlt) local lAlt = 65535 * ( 1 -( pAlt + 2000 ) / 16000 ) if lAlt > 65535 then lAlt = 65535 end if lAlt < 0 then lAlt = 0 end return lAlt end writeXMLIF ( Q400_XML.LdgAlt () , LdgAlt(lLdgAlt) ) function SetLdgAltDec(joynum, button, downup) -- LdgAlt Down if lLdgAlt > -2000 then lLdgAlt = lLdgAlt - 100 else lLdgAlt = -2000 end writeXMLIF ( Q400_XML.LdgAlt () , LdgAlt(lLdgAlt) ) end function SetLdgAltInc(joynum, button, downup) -- LdgAlt Up if lLdgAlt < 14000 then lLdgAlt = lLdgAlt + 100 else lLdgAlt = 14000 end writeXMLIF ( Q400_XML.LdgAlt () , LdgAlt(lLdgAlt) ) end -- track every change of the AilTrim toggle switch and check every 500 msec event.button( GF_JoyLetter , GF_JoyButton+0 , 3 , "SetLdgAltDec" ) event.button( GF_JoyLetter , GF_JoyButton+1 , 3 , "SetLdgAltDec" ) event.button( GF_JoyLetter , GF_JoyButton+2 , 3 , "SetLdgAltInc" ) event.button( GF_JoyLetter , GF_JoyButton+3 , 3 , "SetLdgAltInc" ) Rgds Reinhard

Hi, For reference here a normal shutdown with all LUA modules killed as intended. Rgds Reinhard 387288 === About to kill any Lua plug-ins still running ... 387428 Lua threads being terminated: 387428 0 = "E:\P3D\Modules\Q400_GF_ADF.lua" 387584 LUA: "E:\P3D\Modules\Q400_GF_ADF.lua": killed 387584 1 = "E:\P3D\Modules\FSX_InitPanel.lua" 387740 LUA: "E:\P3D\Modules\FSX_InitPanel.lua": killed 387740 2 = "E:\P3D\Modules\FSX_CheckList.lua" 387881 LUA: "E:\P3D\Modules\FSX_CheckList.lua": killed 387881 3 = "E:\P3D\Modules\FSX_InitGF.lua" 388286 LUA: "E:\P3D\Modules\FSX_InitGF.lua": killed 388286 4 = "E:\P3D\Modules\Q400_InitCold.lua" 388692 LUA: "E:\P3D\Modules\Q400_InitCold.lua": killed 388692 5 = "E:\P3D\Modules\Q400_GF_Bat.lua" 388832 LUA: "E:\P3D\Modules\Q400_GF_Bat.lua": killed 388832 6 = "E:\P3D\Modules\Q400_GF_ExtPwr.lua" 388988 LUA: "E:\P3D\Modules\Q400_GF_ExtPwr.lua": killed 388988 7 = "E:\P3D\Modules\Q400_GF_Avionics.lua" 389144 LUA: "E:\P3D\Modules\Q400_GF_Avionics.lua": killed 389144 8 = "E:\P3D\Modules\Q400_GF_BusTie.lua" 389300 LUA: "E:\P3D\Modules\Q400_GF_BusTie.lua": killed 389300 9 = "E:\P3D\Modules\Q400_GF_Yaw.lua" 389441 LUA: "E:\P3D\Modules\Q400_GF_Yaw.lua": killed 389441 10 = "E:\P3D\Modules\Q400_GF_FuelPump.lua" 389597 LUA: "E:\P3D\Modules\Q400_GF_FuelPump.lua": killed 389597 11 = "E:\P3D\Modules\Q400_GF_Hydr.lua" 389753 LUA: "E:\P3D\Modules\Q400_GF_Hydr.lua": killed 389753 12 = "E:\P3D\Modules\FSX_GF_ParkB.lua" 389893 LUA: "E:\P3D\Modules\FSX_GF_ParkB.lua": killed 389893 13 = "E:\P3D\Modules\Q400_GF_Askid.lua" 390049 LUA: "E:\P3D\Modules\Q400_GF_Askid.lua": killed 390049 14 = "E:\P3D\Modules\Q400_GF_LdgAlt.lua" 390205 LUA: "E:\P3D\Modules\Q400_GF_LdgAlt.lua": killed 390205 15 = "E:\P3D\Modules\Q400_GF_COM2.lua" 390346 LUA: "E:\P3D\Modules\Q400_GF_COM2.lua": killed 390346 16 = "E:\P3D\Modules\Q400_GF_Xpdr.lua" 390502 LUA: "E:\P3D\Modules\Q400_GF_Xpdr.lua": killed 390502 17 = "E:\P3D\Modules\Q400_GF_NAV2.lua" 390658 LUA: "E:\P3D\Modules\Q400_GF_NAV2.lua": killed 390658 18 = "E:\P3D\Modules\FSX_GF_SelAlt.lua" 390798 LUA: "E:\P3D\Modules\FSX_GF_SelAlt.lua": killed 390798 19 = "E:\P3D\Modules\FSX_GF_SelHdg.lua" 390954 LUA: "E:\P3D\Modules\FSX_GF_SelHdg.lua": killed 390954 20 = "E:\P3D\Modules\Q400_GF_SetMCP.lua" 391110 LUA: "E:\P3D\Modules\Q400_GF_SetMCP.lua": killed 391110 21 = "E:\P3D\Modules\Q400_GF_NAV1.lua" 391250 LUA: "E:\P3D\Modules\Q400_GF_NAV1.lua": killed 391250 22 = "E:\P3D\Modules\Q400_GF_EFIS.lua" 391406 LUA: "E:\P3D\Modules\Q400_GF_EFIS.lua": killed 391406 23 = "E:\P3D\Modules\Q400_GF_EngStart.lua" 391562 LUA: "E:\P3D\Modules\Q400_GF_EngStart.lua": killed 391562 24 = "E:\P3D\Modules\Q400_GF_PanelLt.lua" 391703 LUA: "E:\P3D\Modules\Q400_GF_PanelLt.lua": killed 391703 25 = "E:\P3D\Modules\Q400_GF_NavLt.lua" 391859 LUA: "E:\P3D\Modules\Q400_GF_NavLt.lua": killed 391859 26 = "E:\P3D\Modules\Q400_GF_BeaconLt.lua" 392015 LUA: "E:\P3D\Modules\Q400_GF_BeaconLt.lua": killed 392015 27 = "E:\P3D\Modules\Q400_GF_TaxiLt.lua" 392155 LUA: "E:\P3D\Modules\Q400_GF_TaxiLt.lua": killed 392155 28 = "E:\P3D\Modules\Q400_GF_LdgLt.lua" 392311 LUA: "E:\P3D\Modules\Q400_GF_LdgLt.lua": killed 392311 29 = "E:\P3D\Modules\Q400_GF_StructIce.lua" 392467 LUA: "E:\P3D\Modules\Q400_GF_StructIce.lua": killed 392467 30 = "E:\P3D\Modules\Q400_GF_PropIce.lua" 392608 LUA: "E:\P3D\Modules\Q400_GF_PropIce.lua": killed 392608 31 = "E:\P3D\Modules\Q400_GF_FuelSel.lua" 392764 LUA: "E:\P3D\Modules\Q400_GF_FuelSel.lua": killed 392764 32 = "E:\P3D\Modules\Q400_GF_Flaps.lua" 392920 LUA: "E:\P3D\Modules\Q400_GF_Flaps.lua": killed 392920 33 = "E:\P3D\Modules\FSX_GF_ElevTrim.lua" 393076 LUA: "E:\P3D\Modules\FSX_GF_ElevTrim.lua": killed 393076 34 = "E:\P3D\Modules\FSX_GF_AilTrim.lua" 393216 LUA: "E:\P3D\Modules\FSX_GF_AilTrim.lua": killed 393216 35 = "E:\P3D\Modules\FSX_GF_RudTrim.lua" 393372 LUA: "E:\P3D\Modules\FSX_GF_RudTrim.lua": killed 393372 36 = "E:\P3D\Modules\Q400_GF_LGear.lua" 393528 LUA: "E:\P3D\Modules\Q400_GF_LGear.lua": killed 393528 37 = "E:\P3D\Modules\Q400_GF_WARN.lua" 393668 LUA: "E:\P3D\Modules\Q400_GF_WARN.lua": killed 393668 38 = "E:\P3D\Modules\Q400_GF_TOGA.lua" 393824 LUA: "E:\P3D\Modules\Q400_GF_TOGA.lua": killed 393824 39 = "E:\P3D\Modules\Q400_GF_AFTHR.lua" 393980 LUA: "E:\P3D\Modules\Q400_GF_AFTHR.lua": killed 393980 40 = "E:\P3D\Modules\Q400_GF_MFD1.lua" 394121 LUA: "E:\P3D\Modules\Q400_GF_MFD1.lua": killed 394121 41 = "E:\P3D\Modules\Q400_GF_MFD2.lua" 394277 LUA: "E:\P3D\Modules\Q400_GF_MFD2.lua": killed 394277 42 = "E:\P3D\Modules\Q400_GF_EmergLt.lua" 394433 LUA: "E:\P3D\Modules\Q400_GF_EmergLt.lua": killed 394433 43 = "E:\P3D\Modules\Q400_GF_SeatBelt.lua" 394573 LUA: "E:\P3D\Modules\Q400_GF_SeatBelt.lua": killed 394573 44 = "E:\P3D\Modules\Q400_GF_NoSmoking.lua" 394729 LUA: "E:\P3D\Modules\Q400_GF_NoSmoking.lua": killed 394729 45 = "E:\P3D\Modules\Q400_GF_COM1.lua" 394885 LUA: "E:\P3D\Modules\Q400_GF_COM1.lua": killed 394885 46 = "E:\P3D\Modules\Q400_GF_Bleed.lua" 395026 LUA: "E:\P3D\Modules\Q400_GF_Bleed.lua": killed 395026 47 = "E:\P3D\Modules\Q400_GF_GenOff.lua" 395182 LUA: "E:\P3D\Modules\Q400_GF_GenOff.lua": killed 395182 48 = "E:\P3D\Modules\Q400_GF_Pitot.lua" 395338 LUA: "E:\P3D\Modules\Q400_GF_Pitot.lua": killed 395338 === Closing global Lua thread

Ahh - that's why I didn't see these messages in the past. Anyhow a good Information. You can keep this as the default. Rgds Reinhard

Hi, This is just one out of 48 modules running for my Majestic Q400. It's controlling my cockpit camera giving me several views on part of the VC. But it's no specific one. And I did not experience this in the past. But also now I couldn't reproduce it anymore. Rgds Reinhard

Hi, Did now several start-ups and shut-downs of P3D. Everything was working fine. So let's classify this single event as an one-time errror. Killing is always brute force and might have some side effects. But INI file and numbers are ok now. Rgds Reinhard

Hi, Wow this was quick !!! I did the test with the new version. Now the numbers didn't change anymore. So this seemed now be solved. Also the registry was fixed and at the second run it says, that the values are ok. But there was another problem, which occured at the first test. Shuting down, the simulator got stuck at that point in time, when you try to kill running LUA modules. I have added this in the log. The second time it closed the sim, all LUA procedures and P3D was shutting down as usual. Obviously you have changed something here, because comparing to my LOG file in the backup, I don't see these messages there. And this getting stuck I also didn't experience in the past. I will try to start and stop the sim several times and report back, if it happens again. Rgds Reinhard ORIGINAL INI: ============= [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={35A598E0-AAF5-11E1-8002-444553540000} 1=TQ6 1.GUID={317A1330-B07D-11E1-800C-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={35A598E0-AAF5-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 Log of the 1st run: =================== 344 ---------------------- Joystick Device Scan ----------------------- 344 Product= Saitek Pro Flight Rudder Pedals 344 Manufacturer= Saitek 344 Vendor=06A3, Product=0763 (Version 1.0) 344 Serial Number= 344 Using existing joystick id: 255 344 Using existing joystick id: 255 344 Using existing joystick id: 255 344 Assigned joystick id 3 (fixed Registry) 344 GUID= {35A598E0-AAF5-11E1-8001-444553540000} 344 Product= Saitek Pro Flight Yoke 344 Manufacturer= Saitek 344 Vendor=06A3, Product=0BAC (Version 3.2) 344 Serial Number= 344 Assigned joystick id 0 (fixed Registry) 344 GUID= {35A598E0-AAF5-11E1-8002-444553540000} 344 Product= Saitek Pro Flight Quadrant 359 Manufacturer= Saitek 359 Vendor=06A3, Product=0C2D (Version 2.0) 359 Serial Number= 359 Using existing joystick id: 255 359 Assigned joystick id 2 (Registry okay) 359 GUID= {7EC7D4F0-B1C3-11E1-8001-444553540000} 359 Product= TQ6 359 Manufacturer= GoFlight 359 Vendor=09F3, Product=0200 (Version 2.0) 359 Serial Number= 00080 7 359 Assigned joystick id 1 (fixed Registry) 359 GUID= {317A1330-B07D-11E1-800C-444553540000} 359 ------------------------------------------------------------------- P3D got stuck shutting down: ============================ 302455 Sim stopped: average frame rate for last 178 secs = 29.6 fps 302455 Max AI traffic was 0 aircraft 302736 LUA.4: Error reading MJC interface for function 143112 303079 LUA.4: Error reading MJC interface for function 41047 317884 LUA.4: Error reading MJC interface for function 91735 341752 === DLLStop called ... 341752 === Getting Lua plug-ins to close ... 343249 === Closing external processes we started ... 344248 === About to kill any Lua plug-ins still running ... 344404 Lua threads being terminated: 344404 0 = "E:\P3D\Modules\Q400_GF_ADF.lua" 344560 LUA: "E:\P3D\Modules\Q400_GF_ADF.lua": killed 344560 1 = "E:\P3D\Modules\FSX_InitPanel.lua" <<<<<<<<<<<<< Here it got stuck ?!? INI after 1st run: ==================== [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={35A598E0-AAF5-11E1-8002-444553540000} 1=TQ6 1.GUID={317A1330-B07D-11E1-800C-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={35A598E0-AAF5-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 LOG of the 2nd run: =================== 343 ---------------------- Joystick Device Scan ----------------------- 343 Product= Saitek Pro Flight Rudder Pedals 343 Manufacturer= Saitek 343 Vendor=06A3, Product=0763 (Version 1.0) 343 Serial Number= 343 Using existing joystick id: 255 343 Using existing joystick id: 255 343 Using existing joystick id: 255 343 Assigned joystick id 3 (Registry okay) 343 GUID= {35A598E0-AAF5-11E1-8001-444553540000} 343 Product= Saitek Pro Flight Yoke 343 Manufacturer= Saitek 343 Vendor=06A3, Product=0BAC (Version 3.2) 343 Serial Number= 343 Assigned joystick id 0 (Registry okay) 343 GUID= {35A598E0-AAF5-11E1-8002-444553540000} 343 Product= Saitek Pro Flight Quadrant 343 Manufacturer= Saitek 343 Vendor=06A3, Product=0C2D (Version 2.0) 358 Serial Number= 358 Using existing joystick id: 255 358 Assigned joystick id 2 (Registry okay) 358 GUID= {7EC7D4F0-B1C3-11E1-8001-444553540000} 358 Product= TQ6 358 Manufacturer= GoFlight 358 Vendor=09F3, Product=0200 (Version 2.0) 358 Serial Number= 00080 7 358 Assigned joystick id 1 (Registry okay) 358 GUID= {317A1330-B07D-11E1-800C-444553540000} 358 ------------------------------------------------------------------- INI after the 2nd run: ====================== [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={35A598E0-AAF5-11E1-8002-444553540000} 1=TQ6 1.GUID={317A1330-B07D-11E1-800C-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={35A598E0-AAF5-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6

Hi, I have a backup. So no problem. And if you can tell me, which registry entries to remove, I can also try to repeat the test later. Rgds Reinhard