remcosol Posted February 6, 2017 Report Share Posted February 6, 2017 Dear Peter, The rudder trim is giving me issues again.... i think it is the way i have configured it. What offstes should i use for aileron , rudder and elevator, and rudder trim. Right now im using: 0BB2, 0BB6, 0BBA for flight control inputs and the standard rudder trim (fsuipc) . I think they are conlficting. I get a stackhash error after a while. If i disable the ruddertrim then no issues.... Best regards, Remco Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 6, 2017 Report Share Posted February 6, 2017 3 hours ago, remcosol said: What offstes should i use for aileron , rudder and elevator, and rudder trim. Right now im using: 0BB2, 0BB6, 0BBA for flight control inputs and the standard rudder trim (fsuipc) . They are the standard flight control inputs, yes. They result in direct writes to SimConnect variables unless "WrIteAxesDirect=No" is set in the INI file. In the latter case they invoke controls ("events"). With rudder trim I assume you mean the rudder trim control. There is a rudder trim input offset, 0C04 which is direct and not affected by the INI file setting. Why such a mix? Why use offsets for control in any case? 3 hours ago, remcosol said: I think they are conlficting. I get a stackhash error after a while. If i disable the ruddertrim then no issues... They are separate, no conflicts. A stackhash error where, in your program? Pete Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Hello Pete, Thank you for your answer, P3d v3.4 crashes , only when i use flightillusion software via widefs to connect to fsuipc. The flightcontrols are writen via the above offsests directly as axis and calibrated in fsuipc. That is the rudder aileron and elevator. The ruddertrim is connected to p3d directly , not via widefs. Stand alone they work fine, it is when i use both direct (rudder trim) and via widefs the rest off the flightcontrols. The stackhash error is always the same and is a memory error, the fsuipc log does not reveal much , only that p3d has shut down. I will add them later on ( different computer ) There is a conflict somewhere. All off the controls are calibrated and set via fsuipc by the way. Does it make a difference if the allow joystick in p3d is on or off? Bets regards, Remco Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2017 Report Share Posted February 7, 2017 21 minutes ago, remcosol said: The flightcontrols are writen via the above offsests directly as axis and calibrated in fsuipc. Those offsets cause direct writes into P3D. To calibrate values sent to offsets you should use those in the range 3BA8-3BC4. 23 minutes ago, remcosol said: The stackhash error is always the same and is a memory error, the fsuipc log does not reveal much , only that p3d has shut down. What about the Windows crash data? That's more relevant! Please show me that. 24 minutes ago, remcosol said: Does it make a difference if the allow joystick in p3d is on or off? Only that if it is on you'll probably get conflicts in any case. Always use one or the otther. But you should never be able to cause a crash. Pete Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 HI Peter, I have used the above offsets as well. Still causing a crash. I dont get why there is a conflict eventhough everything is configured via fs uipc.... Here some data: Prepar3D.exe 3.4.9.18400 57d9b14e ntdll.dll 10.0.14393.479 58256ca0 c0000374 000d9d11 15e0 01d28135fe65de7e D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe C:\WINDOWS\SYSTEM32\ntdll.dll d9a6d0b0-0e70-4dd5-8db5-d746b0dc61ee Prepar3D.exe 3.4.9.18400 57d9b14e ntdll.dll 10.0.14393.479 58256ca0 c0000374 000d9d11 1360 01d280c3c43af3e7 D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe C:\WINDOWS\SYSTEM32\ntdll.dll 908ec58d-93cb-4b6d-b019-38178bf62548 Prepar3D.exe 3.4.9.18400 57d9b14e ntdll.dll 10.0.14393.479 58256ca0 c0000374 000d9d11 4e8 01d280bdf11e3627 D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe C:\WINDOWS\SYSTEM32\ntdll.dll 6c235b90-c4cc-4ce2-94ff-098ebe9c6933 Prepar3D.exe 3.4.9.18400 57d9b14e ntdll.dll 10.0.14393.479 58256ca0 c0000374 000d9d11 1a60 01d280a0be705288 D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe C:\WINDOWS\SYSTEM32\ntdll.dll 4c769aa2-6419-4200-8079-cc7e8aaf6ca7 They are from different days. They only happen with both the flightillusion and the standaolone ruddertrim controls connected..... Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 This is from the reliability page from windows: Pad naar toepassing met fout: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Probleem met handtekening Naam van probleemgebeurtenis: APPCRASH Naam van de toepassing: Prepar3D.exe Versie van toepassing: 3.4.9.18400 Tijdstempel van toepassing: 57d9b14e Naam van foutmodule: StackHash_a3d4 Versie van foutmodule: 10.0.14393.479 Tijdstempel van foutmodule: 58256ca0 Uitzonderingscode: c0000374 Uitzonderingsmarge: PCH_4A_FROM_ntdll+0x0006EB8C Versie van besturingssysteem: 10.0.14393.2.0.0.768.101 Landinstelling-id: 1043 Aanvullende informatie 1: a3d4 Aanvullende informatie 2: a3d43165139bdf3e0ea2c72a5558c8a5 Aanvullende informatie 3: 3d3f Aanvullende informatie 4: 3d3fde7bf97f525fce7ec9001a0d63bd Extra informatie over het probleem Bucket-id: bfce9c245b6b0c085ea044b7f5fea0c1 (108615200304) Always the same one .... Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 ********* FSUIPC4, Version 4.96 (26th January 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.4.9.18400 Reading options from "D:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=5EE00000 User Name=xxxxxxxxx User Addr=xxxxxxxxxxxxx FSUIPC4 Key is provided WideFS7 Key is provided 47 System time = 07/02/2017 12:33:32 47 FLT UNC path = "\\P3D1\Users\P3D\Documents\Prepar3D v3 Files\" 47 ------ Module Version Check ------ 47 acontain.dll: 3.4.9.18400 47 api.dll: 3.4.9.18400 47 controls.dll: 3.4.9.18400 47 fs-traffic.dll: 3.4.9.18400 47 G3D.dll: 3.4.9.18400 47 language.dll: 3.4.9.18400 47 sim1.dll: 3.4.9.18400 47 visualfx.dll: 3.4.9.18400 47 weather.dll: 3.4.9.18400 47 window.dll: 3.4.9.18400 47 ---------------------------------- 47 Trying D:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 47 Found it: trying to connect 63 FS UNC path = "D:\Lockheed Martin\Prepar3D v3\" 141 ---------------------- Joystick Device Scan ----------------------- 141 Product= Pro Flight Cessna Trim Wheel 141 Manufacturer= Saitek 141 Vendor=06A3, Product=0BD4 (Version 1.6) 141 Serial Number= RD001533 141 Product= USBAXES-PLUS 156 Manufacturer= Opencockpits 156 Vendor=0000, Product=00CC (Version 0.0) 156 Serial Number= 156 Product= 156 Manufacturer= 156 Vendor=0000, Product=0004 (Version 0.0) 156 Serial Number= 156 ------------------------------------------------------------------- 172 LogOptions=00000000 00000001 172 ------------------------------------------------------------------- 172 ------ Setting the hooks and direct calls into the simulator ------ 172 --- CONTROLS timer memory location obtained ok 172 --- SIM1 Frictions access gained 172 --- FS Controls Table located ok 172 --- Installed Mouse Macro hooks ok. 172 --- Wind smoothing fix is installed 172 --- SimConnect intercept for texts and menus option is off 172 --- All links okay (except older global weather setting method) 172 ------------------------------------------------------------------- 172 SimConnect_Open succeeded: waiting to check version okay 172 Trying to use SimConnect Prepar3D 172 Opened separate AI Traffic client okay 1547 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.9.18400 (SimConnect: 3.4.0.0) 1547 Initialising SimConnect data requests now 1547 FSUIPC Menu entry added 1594 \\P3D1\Users\P3D\Documents\Prepar3D v3 Files\start.fxml 1594 D:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\JF_De Havilland Dove\DH104.air 9953 Weather Mode now = Global 49375 User Aircraft ID 2 supplied, now being used 50078 System time = 07/02/2017 12:34:22, Simulator time = 14:15:38 (13:15Z) 50094 Aircraft="de Havilland Dove6 Early3" 51078 Starting everything now ... 51250 Advanced Weather Interface Enabled 1370609 ***ERROR C0000005 at 6E2878A8 ExWriteStateData(Offset=0C04, Size=2) 1370609 *** Access violation trying to read address 00000008 1370609 *** EAX 00000000 EBX 00000001 ECX 42B3C048 EDX 00000000 EDI 0F43A5A8 ESI 227AEDF8 Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2017 Report Share Posted February 7, 2017 I can't do much with the others, but the last, the FSUIPC4 Log is useful. Your program or driver is evidently in error and trying to write to somewhere it shouldn't. Enable ipc Write logging in FSUIPC's Logging tab, which will show what you/it is trying to do. Pete Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Thank You Peter, I will. Its gonna be a couple off days probably, i am away for work. Best regards, Remco Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Hello Pete, I just did a small test and got a long list, this is the last part where it went wrong: 2096094 WRITEex 0378, 2 bytes: 01 00 .. 2096094 WRITEex 0BDC, 4 bytes: 20 00 00 00 ... 2096140 WRITEex 3BAC, 2 bytes: 93 FF .. 2096187 WRITEex 0C4E, 2 bytes: 96 00 .. 2096187 WRITEex 3BAC, 2 bytes: 26 FF &. 2096187 WRITEex 0BDC, 4 bytes: 40 00 00 00 @... 2096250 WRITEex 0378, 2 bytes: 01 00 .. ******** FSUIPC4, Version 4.96 (26th January 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.4.22.19868 Reading options from "D:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=62380000 User Name= User Addr= FSUIPC4 Key is provided WideFS7 Key is provided 47 System time = 07/02/2017 14:34:55 62 FLT UNC path = "\\P3D1\Users\P3D\Documents\Prepar3D v3 Files\" 62 ------ Module Version Check ------ 62 acontain.dll: 3.4.22.19868 62 api.dll: 3.4.22.19868 62 controls.dll: 3.4.22.19868 62 fs-traffic.dll: 3.4.22.19868 62 G3D.dll: 3.4.22.19868 62 language.dll: 3.4.22.19868 62 sim1.dll: 3.4.22.19868 62 visualfx.dll: 3.4.22.19868 62 weather.dll: 3.4.22.19868 62 window.dll: 3.4.22.19868 62 ---------------------------------- 62 Trying D:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 62 Found it: trying to connect 62 FS UNC path = "D:\Lockheed Martin\Prepar3D v3\" 156 ---------------------- Joystick Device Scan ----------------------- 156 Product= Pro Flight Cessna Trim Wheel 156 Manufacturer= Saitek 156 Vendor=06A3, Product=0BD4 (Version 1.6) 156 Serial Number= RD001533 156 Product= USBAXES-PLUS 156 Manufacturer= Opencockpits 156 Vendor=0000, Product=00CC (Version 0.0) 156 Serial Number= 156 Product= 156 Manufacturer= 156 Vendor=0000, Product=0004 (Version 0.0) 156 Serial Number= 156 ------------------------------------------------------------------- 187 LogOptions=00000000 00000001 187 ------------------------------------------------------------------- 187 ------ Setting the hooks and direct calls into the simulator ------ 187 --- CONTROLS timer memory location obtained ok 187 --- SIM1 Frictions access gained 187 --- FS Controls Table located ok 187 --- Installed Mouse Macro hooks ok. 187 --- Wind smoothing fix is installed 187 --- SimConnect intercept for texts and menus option is off 187 --- All links okay (except older global weather setting method) 187 ------------------------------------------------------------------- 187 SimConnect_Open succeeded: waiting to check version okay 187 Trying to use SimConnect Prepar3D 187 Opened separate AI Traffic client okay 1328 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0) 1328 Initialising SimConnect data requests now 1328 FSUIPC Menu entry added 1375 \\P3D1\Users\P3D\Documents\Prepar3D v3 Files\start.fxml 1375 D:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\JF_De Havilland Dove\DH104.air 8640 Weather Mode now = Global 48906 User Aircraft ID 1 supplied, now being used 49640 System time = 07/02/2017 14:35:44, Simulator time = 14:15:38 (13:15Z) 49640 Aircraft="de Havilland Dove6 Early3" 50640 Starting everything now ... 50812 Advanced Weather Interface Enabled 69484 Exception 20 "DATA_ERROR", Ref 2844, Index param 1 on write SetData for "ADF SOUND" 193000 Sim stopped: average frame rate for last 144 secs = 59.6 fps 193000 Max AI traffic was 11 aircraft (Deleted 0) 900140 Sim stopped: average frame rate for last 689 secs = 59.5 fps 900140 Max AI traffic was 14 aircraft (Deleted 0) Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 For some reason i cannot see the rudder trim as rudder trim.. i.e. 3BC2 : Rudder trim The only thing i see is rudder: 3BAC 2 Rudder in the whole list... that would imply that the rudder trim , eventough it is configured in fsuipc as ruddertrim axis is rudder ????? Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 FSUIPC4.log Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 FSUIPC4.ini Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2017 Report Share Posted February 7, 2017 17 minutes ago, remcosol said: I just did a small test and got a long list, this is the last part where it went wrong: 2096094 WRITEex 0378, 2 bytes: 01 00 .. 2096094 WRITEex 0BDC, 4 bytes: 20 00 00 00 ... 2096140 WRITEex 3BAC, 2 bytes: 93 FF .. 2096187 WRITEex 0C4E, 2 bytes: 96 00 .. 2096187 WRITEex 3BAC, 2 bytes: 26 FF &. 2096187 WRITEex 0BDC, 4 bytes: 40 00 00 00 @... 2096250 WRITEex 0378, 2 bytes: 01 00 Was there an error report immediately after, like the previous one, i.e like this? 1370609 ***ERROR C0000005 at 6E2878A8 ExWriteStateData(Offset=0C04, Size=2) 1370609 *** Access violation trying to read address 00000008 1370609 *** EAX 00000000 EBX 00000001 ECX 42B3C048 EDX 00000000 EDI 0F43A5A8 ESI 227AEDF8 If not, was that last WRITEex the last line in the log? Not sure of the point of the partial log you also appended? Pete Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 This Is my ini file: [JoyNames] AutoAssignLetters=No 2=Saitek Pro Flight Cessna Trim Wheel 2.GUID={CFC64FF0-6E1F-11E5-8005-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,R1,D,30,0,0,0 -{ DIRECT: CowlFlaps2 }- 1=0Y,R1,D,29,0,0,0 -{ DIRECT: CowlFlaps1 }- 2=0Z,R1,D,28,0,0,0 -{ DIRECT: Rudder Trim }- 3=2X,R1,D,21,0,0,0 -{ DIRECT: ElevatorTrim }- 4=16X,R2,D,1,0,0,0,R3 -{ DIRECT: Aileron }- 5=16Y,R2,D,2,0,0,0,R4 -{ DIRECT: Elevator }- 6=16R,R1,D,3,0,0,0,R3 -{ DIRECT: Rudder }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=P0,2,C65955,1 -{FUEL_SELECTOR_OFF}- 2=P0,3,C65958,1 -{FUEL_SELECTOR_RIGHT}- 3=P0,4,C65957,1 -{FUEL_SELECTOR_LEFT}- 4=P0,22,C66518,1 -{FUEL_SELECTOR_2_LEFT}- 5=P0,23,C66519,1 -{FUEL_SELECTOR_2_RIGHT}- 6=P0,21,C66516,1 -{FUEL_SELECTOR_2_OFF}- 7=P1,7,C65842,1 -{RADIO_VOR1_IDENT_TOGGLE}- 8=U1,7,C65842,0 -{RADIO_VOR1_IDENT_TOGGLE}- 9=P1,6,C65843,1 -{RADIO_VOR2_IDENT_TOGGLE}- 10=U1,6,C65843,0 -{RADIO_VOR2_IDENT_TOGGLE}- 11=P1,5,C65846,1 -{RADIO_ADF_IDENT_TOGGLE}- 12=U1,5,C65846,0 -{RADIO_ADF_IDENT_TOGGLE}- 13=P1,0,C66463,1 -{COM1_TRANSMIT_SELECT}- 14=U1,0,C66463,0 -{COM1_TRANSMIT_SELECT}- 15=P1,2,C1124,1 -{com1/2 tx switch}- 16=U1,2,C1124,0 -{com1/2 tx switch}- 17=P1,3,C66477,1 -{MARKER_SOUND_TOGGLE}- 18=U1,3,C66477,0 -{MARKER_SOUND_TOGGLE}- Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Hi Pete , i added the whole log ? the last part was 2096094 WRITEex 0378, 2 bytes: 01 00 .. 2096094 WRITEex 0BDC, 4 bytes: 20 00 00 00 ... 2096140 WRITEex 3BAC, 2 bytes: 93 FF .. 2096187 WRITEex 0C4E, 2 bytes: 96 00 .. 2096187 WRITEex 3BAC, 2 bytes: 26 FF &. 2096187 WRITEex 0BDC, 4 bytes: 40 00 00 00 @... 2096250 WRITEex 0378, 2 bytes: 01 00 .. This was all there is, as said i have scanned through it all but did not com across a rudder trim set offset.... eventhough it should be configured correctly..., Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 I am just wondering, do all the trim offsets (elevator etc) end up in the control offset , i.e 3BC2 13 Rudder trim into 3BAC 2 Rudder , or are they "real " offsets on their own? Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 And the last question is: Do i set the settings of the axis in fsuipc to: direct to fsuipc calibration or send to fs as normal axis, and what is the difference? Thank you for your help! Best regards, Remco Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2017 Report Share Posted February 7, 2017 24 minutes ago, remcosol said: For some reason i cannot see the rudder trim as rudder trim.. i.e. 3BC2 : Rudder trim The only thing i see is rudder: 3BAC 2 Rudder in the whole list... that would imply that the rudder trim , eventough it is configured in fsuipc as ruddertrim axis is rudder ????? 3BAC is one of the "free" offsets which can be assigned to whatever you like inside FSUIPC's axis assignments. The allocations shown in that list are just those automatically assigned for the PFC driver when my PFCFSX.DLL is loaded. Otherwise you can use any of the 15 available for any axis, but they need assigning in FSUIPC or they will do nothing at all. I don't know why whatever it is you are using is writing to 3BAC. But if it's assigned to rudder trim, it will be rudder trim. These are your only assignments to the PFC axes offsets: 4=16X,R2,D,1,0,0,0,R3 -{ DIRECT: Aileron }-5=16Y,R2,D,2,0,0,0,R4 -{ DIRECT: Elevator }-6=16R,R1,D,3,0,0,0,R3 -{ DIRECT: Rudder }- So you have assigned 3BAC to the rudder, NOT the trim. Your rudder trim, like your elevator trim, is assigned to a normal joystick device: 2=0Z,R1,D,28,0,0,0 -{ DIRECT: Rudder Trim }-3=2X,R1,D,21,0,0,0 -{ DIRECT: ElevatorTrim }- Your joystick devices are very few indeed: [JoyNames]AutoAssignLetters=No2=Saitek Pro Flight Cessna Trim Wheel2.GUID={CFC64FF0-6E1F-11E5-8005-444553540000} So the rudder trim is on your Cessna trim wheel. Your other buttons and axes are assigned to devices 0 and 1, which don't appear to be connected according to the list!!! However: 20 minutes ago, remcosol said: Hi Pete , i added the whole log ? the last part was Not in the message I responded to -- it was a later message which i've only just seen. In that log there are three devices listed: 156 ---------------------- Joystick Device Scan ----------------------- 156 Product= Pro Flight Cessna Trim Wheel 156 Manufacturer= Saitek 156 Vendor=06A3, Product=0BD4 (Version 1.6) 156 Serial Number= RD001533 156 Product= USBAXES-PLUS 156 Manufacturer= Opencockpits 156 Vendor=0000, Product=00CC (Version 0.0) 156 Serial Number= 156 Product= 156 Manufacturer= 156 Vendor=0000, Product=0004 (Version 0.0) 156 Serial Number= so why only one in the INI? Is that an out of date INI? 19 minutes ago, remcosol said: I am just wondering, do all the trim offsets (elevator etc) end up in the control offset , i.e 3BC2 13 Rudder trim into 3BAC 2 Rudder , or are they "real " offsets on their own? Er, you are assigning to FS controls. They are not offsets. In the offsets which can be READ to see the state of the controls you would be able to read those. Check the offsets list. The 3BAC area are just inputs, not outputs. You are just using control offsets, the ex-PFC ones, for the main three flight controls. I don't know why. The two trims and the cowflps controls are sent to FSUIPC calibration as normal controls, just as if you'd assigned in other ways, even in FS. Anyway, the log with the IPC write enabled is no use because it doesn't have the ERROR trap. The last few entries are innocuous. I don't think it is FSUIPC crashing FS. But whatever software you are running which is writing to FSUIPC offsets it putting quite a load on your system, with up to 30 or so writes every second. I just hope they are batched an in one transfer, not all separate calls. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2017 Report Share Posted February 7, 2017 13 minutes ago, remcosol said: Do i set the settings of the axis in fsuipc to: direct to fsuipc calibration or send to fs as normal axis, and what is the difference? Your choice. If you are going to calibrate then Direct is more efficient. The other way involves sending the control to FS first, then FSUIPC intercepts it for calibration just before it is applied. So for every change the first is one message to FS, the second involves two messages to and one message back. However, some add-on aircraft (notably Aerosoft Airbus and PMDG aircraft) don't like some axes being sent direct because they intercept them in the same way as FSUIPC does. Pete Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Thank you Pete, For me fsuipc runs my whole simulator , withe real instruments ( some from real world sims, others from real aircraft) . And also the flightcontrols and buttons lights etc. For this i use: Flightillusion for most buttons and lights and elevator , rudder, aileron, throttles and prop speed. Open cockpits SIOC for all the instruments And the siatek elevator trim for the elevator trim, USB AXIS for the rudder trim, cowlflaps and some buttons, The other card is for buttons alone. It runs great and faultless, unless i use the rudder trim for some reason..... I'll do some more digging Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Just to give you a small impression Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 Is it in theorie possible that both the rudder and rudder trim use 3ABC? I have not assigned anything to that as far as i know..... Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 The reason why i am saying this is because the elevator trim does show up , the rudder trim doesnt.. 439922 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -960 (0xfffffc40) AXIS_ELEV_TRIM_SET 439953 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1280 (0xfffffb00) AXIS_ELEVATOR_SET 439968 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -864 (0xfffffca0) AXIS_ELEV_TRIM_SET 440000 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -832 (0xfffffcc0) AXIS_ELEV_TRIM_SET 440015 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -768 (0xfffffd00) AXIS_ELEV_TRIM_SET 440047 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -736 (0xfffffd20) AXIS_ELEV_TRIM_SET 440062 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -672 (0xfffffd60) AXIS_ELEV_TRIM_SET 440078 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -640 (0xfffffd80) AXIS_ELEV_TRIM_SET 440078 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -875 (0xfffffc95) AXIS_ELEVATOR_SET 440093 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -576 (0xfffffdc0) AXIS_ELEV_TRIM_SET 440359 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -544 (0xfffffde0) AXIS_ELEV_TRIM_SET 440375 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -512 (0xfffffe00) AXIS_ELEV_TRIM_SET 440453 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -448 (0xfffffe40) AXIS_ELEV_TRIM_SET 440468 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -352 (0xfffffea0) AXIS_ELEV_TRIM_SET 440500 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -320 (0xfffffec0) AXIS_ELEV_TRIM_SET 440609 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 111 (0x0000006f) AXIS_RUDDER_SET 440672 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 222 (0x000000de) AXIS_RUDDER_SET 440859 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -352 (0xfffffea0) AXIS_ELEV_TRIM_SET 440906 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -384 (0xfffffe80) AXIS_ELEV_TRIM_SET 440922 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -416 (0xfffffe60) AXIS_ELEV_TRIM_SET 441109 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -448 (0xfffffe40) AXIS_ELEV_TRIM_SET 441140 *** AXIS: Cntrl= 65766 (0x000100e6), Param= -512 (0xfffffe00) AXIS_ELEV_TRIM_SET 441625 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 225 (0x000000e1) FLAPS_SET 441625 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 193 (0x000000c1) FLAPS_SET 441984 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 256 (0x00000100) AXIS_AILERONS_SET 442297 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1145 (0xfffffb87) AXIS_ELEVATOR_SET 442406 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1429 (0xfffffa6b) AXIS_ELEVATOR_SET 442453 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1699 (0xfffff95d) AXIS_ELEVATOR_SET 442547 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1969 (0xfffff84f) AXIS_ELEVATOR_SET 442593 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2253 (0xfffff733) AXIS_ELEVATOR_SET 442656 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2793 (0xfffff517) AXIS_ELEVATOR_SET 442828 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 225 (0x000000e1) FLAPS_SET 442875 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 193 (0x000000c1) FLAPS_SET 443078 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2658 (0xfffff59e) AXIS_ELEVATOR_SET 443187 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 225 (0x000000e1) FLAPS_SET 443234 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 193 (0x000000c1) FLAPS_SET 443390 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2388 (0xfffff6ac) AXIS_ELEVATOR_SET Link to comment Share on other sites More sharing options...
remcosol Posted February 7, 2017 Author Report Share Posted February 7, 2017 it only shows up as axis rudder set Link to comment Share on other sites More sharing options...
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