Thomas Richter

Hi, make sure you install SP1 and SP2 for FSX with later SimConnect. From FlightSim.com or via Microsoft (only SP2) Thomas

Hi, it depends on what they actually use or how. But another important thing is the timing. As Mobiflight uses FSUIPC it has a cycletime for writing and reading Offsets. If you use Mobiflight on a client you have in addition latency. When I'm writing the Offset direct to FSUIPC, in FSUIPC assigned, the log shows 200ms - 650ms between the value and the setback to 0. That does work with SET_AUTOBRAKE_CONTROL = param 1 sending the control via FSUIPC instead of sending the Offset. But that works as well of course correct by sending the SET_AUTOBRAKE_CONTROL = param 1 direct via SimConnect. That must be something setup wrong within Mobiflight. Thomas

Hi, just to confirm the Offset 0x2F80 (1 Byte) works correct writing the values 1=OFF / 2=LO / 3=MED / 4=MAX. The Tested AC is the stock Asobo_A320_NEO , buttons assigned to Offset 0x2F80 12=97,8,x01002F80,x02 -{Num1: Press=offset byte set, offset 2F80 }- 14=98,8,x01002F80,x03 -{Num2: Press=offset byte set, offset 2F80 }- 16=99,8,x01002F80,x04 -{Num3: Press=offset byte set, offset 2F80 }- 18=96,8,x01002F80,x01 -{Num0: Press=offset byte set, offset 2F80 }- The logged values for Offset 0x2F80 are also as we know in sequence, OFF=1 / LO=2->0 / MED=3->0 / MAX=4->0. @asessa if it does work correct with Mobiflight for you then the problem is somehow on their side but not within FSUIPC. Or I just see you use a different AC with an additional FBW program. Thomas

Hi John, for B747 the max AB value you set with value 6, shows correct in 0x2F80 but I didn't try setting it via 0x2F80. I used SET_AUTOBRAKE_CONTROL. For Cockpit builders yes. But that would be only for Airbus. Thomas

Hi John, to set the AB the SET control should be used, that works also correct for B747 (0 to 6). The Offset 0x2F80 shows as you found the sequence of value set and then back to zero. This is because in Airbus you have Momentary Push Buttons, so the actual PUSH shows the correct value (2, 3, 4) but when released it goes back to zero. That is not wrong for Airbus, it is the correct design. What is missing is SimVar(s) for the indication LO / MED / MAX. For B747 the Offset indicates correct in relation to switch position. Thomas

Hi, just to add in relation to FS9. FS2004 (FS9) runs here with the same framerate and WITHOUT any micro stutters in windowed or Fullscreen (ALT+ENTER) mode, FSUIPC 3.999z9b installed or not, at 100 fps to 120 fps+. On Windows 10, 2004 - 20180.1000. nVidia 457.30 Thomas

Hi, PM sent. Thomas

Hi, FSUIPC7 does not run as part of MSFS as it was in previous FS/P3D versions. The "MSFS with FSUIPC7" icon runs a batch file that starts MSFS and after 2 minutes (120 seconds) when executed it will start FSUIPC7. As your video timing shows you stopped at around one minute, the time-delay to start FSUIPC7 hasn't reached. You can change that time-delay as described in the "Installation and Registration Guide", page 4/5. But the standard timing setting of 120 seconds is well chosen. Thomas

Hi, clearly Yes. FSUIPC6 and earlier versions are DLL types and run within FS/P3D as part of it. FSUIPC7 is a separate application and does not run inside MSFS as part of it. FSUIPC7 is compared to any earlier FSUIPC version an EXE stand alone application that doesn't run inside MSFS and as said it doesn't effect any other installation of FSUIPC. But you cannot run multiple instances of FSUIPC at the same time, it means you cannot run your p3Dv4.x and at the same time FSUIPC7 as that would conflict and automatically not start (whichever starts second). Thomas

Hi, FSUIPC7 doesn't have any effect on any other FS/P3D installation with FSUIPC4/5/6. You can even copy your existing FSUIPC6.ini file over to the FSUIPC7 installation folder and rename it to FSUIPC7.ini, that makes your previous setup the same way work. The only current problem might be, depending on your setup, what is and what isn't working in SimConnect interface of MSFS. Same is true for Linda as it depends as well on what is and isn't working for MSFS. Thomas

Hi, AILERON TRIM LEFT/RIGHT don't work in SimConnect yet, Asobo will have to fix those like many others. But AILERON TRIM SET works and so does RUDDER TRIM SET. Both can be assigned as an controller axis in Axis Assignment tab and calibrated in Joystick Calibration tab (P7). You can as well write to the control 66731 (AIL TRIM) or 66732 (RUD TRIM). When writing to the Controls a value please note that the value has to be within the trimmable aircraft range, most likely -10.0 to +10.0 degree. The value you write has to be the multiple of 10, -10.0 = -100 and +10.0 = 100. Thomas

Hi, the control SET works for TBM930 as well but is immediately set back to zero (0), seems the panel light rotary overwrites that, , light comes ON and goes OFF and opposite as weel when ON and set to 0 it comes ON again. So clearly a Asobo failure in those Aircrafts. Thomas

Hi, without any information it is very tricky to guess. Please send your current FSUIPC7.log file after you closed the session and FSUIPC7 process still stays open. Thomas

Hi, the both (PANEL_LIGHTS_ON and PANEL_LIGHTS_OFF) don't do anything via SimConnect, seems not supported yet by Asobo. But you can use PANEL_LIGHTS_SET instead with value 1 for ON and 0 for OFF, checked with Asobo Baron G58 that has that switch. Thomas