shorthauler Posted October 1 Report Posted October 1 After a reinstall I some of the buttons in my homebuilt cockpit (Mobiflight, FDUIPC buttons) are triggering an outside view of the aircraft as only the key "S" would do. Can you help me find out what is going on? Best regards, Shorthauler
John Dowson Posted October 2 Report Posted October 2 You can try using FSUIPC's logging - set logging for Events and Button & Keys and take a look at the FSUIPC7.log file when this switch occurs and see if you can see the event that does this - if it comes from FSUIPC you should also see the assignment as well.
shorthauler Posted October 2 Author Report Posted October 2 Thank you for replying. I am still on FSX and, consequently, on FSUIPC4. I have attached the log file. I have deleted my personal information. Best, shorthauler FSUIPC4.zip
John Dowson Posted October 3 Report Posted October 3 The log file you attached is a continuation log - please only provide full log files, i.e. do not start a new log. You also have logging for IPC Reads and Writes activated for some reason, and no logging for Events or Buttons & Switches. And I cannot see when this change of view is occurring - only you. So try again, but only with the suggested logging activated, and keep the logging console window open. Then look to see what is logged when the unwanted view switch occurs. This may then tell you where this is coming from, if its from an FSUIPC assignment. Do you have anything assigned to witch to the external view? If you attach your FSUIPC4.ini file I can check. John
shorthauler Posted October 5 Author Report Posted October 5 I was able to isolate this, but I cannot figure out what triggers the event contrls 66416 and 65567. It happens as soon as I open mobiflight, Or is it this? 1008172 Button changed: bRef=0, Joy=3, Btn=2, Pressed 1008110 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 71231 (0x0001163f) ROTOR_BRAKE 1008110 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 71232 (0x00011640) ROTOR_BRAKE 1008110 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 71217 (0x00011631) ROTOR_BRAKE 1008110 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 71218 (0x00011632) ROTOR_BRAKE 1008157 *** EVENT: Cntrl= 66818 (0x00010502), Param= -79 (0xffffffb1) STEERING_SET 1008172 Button changed: bRef=0, Joy=3, Btn=2, Pressed 1008172 [Buttons.FSLabs A320X CFM - Austrian Airlines (OE-LBS)] 28=P3,2,CL6:V,20 1008172 Button changed: bRef=0, Joy=3, Btn=8, Pressed 1008172 [Buttons.FSLabs A320X CFM - Austrian Airlines (OE-LBS)] 32=P3,8,CL7:V,0 1008172 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 1008172 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 1008391 FS Control Sent: Ctrl=66587, Param=71021 1008391 FS Control Sent: Ctrl=66587, Param=71024 1008391 *** EVENT: Cntrl= 66818 (0x00010502), Param= -79 (0xffffffb1) STEERING_SET
John Dowson Posted October 5 Report Posted October 5 1 hour ago, shorthauler said: 1008172 [Buttons.FSLabs A320X CFM - Austrian Airlines (OE-LBS)] 32=P3,8,CL7:V,0 1008172 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 1008172 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE Would be helpful if you attached your FSUIPC4.ini file, but it looks like its coming from an assignment (index 32, to button 8 on device 3) to a lua file, the one with index number 7.
shorthauler Posted October 6 Author Report Posted October 6 Yes, this is the way it should be. Button 8 on device 3 should veed the value "0" into the Lua file. I am attaching the FSUIPC.INI, the FSUIPC4.log and the Lua file and its log. I can't wrap my head around how this triggers 66416 and 65567.
John Dowson Posted October 6 Report Posted October 6 1 hour ago, shorthauler said: I am attaching the FSUIPC.INI, the FSUIPC4.log and the Lua file and its log. No files attached,,,!
John Dowson Posted October 7 Report Posted October 7 On 10/6/2024 at 11:42 AM, shorthauler said: I can't wrap my head around how this triggers 66416 and 65567. It doesn't/can't.... Can you show me/attach the A320 Mode.lua script - it may come from this assignment: Quote 1008172 Button changed: bRef=0, Joy=3, Btn=2, Pressed 1008172 [Buttons.FSLabs A320X CFM - Austrian Airlines (OE-LBS)] 28=P3,2,CL6:V,20 1008172 Button changed: bRef=0, Joy=3, Btn=8, Pressed 1008172 [Buttons.FSLabs A320X CFM - Austrian Airlines (OE-LBS)] 32=P3,8,CL7:V,0 1008172 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 1008172 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE
John Dowson Posted October 8 Report Posted October 8 Well, its not coming from there either...can you show me / attach your FSUIPC4.ini file. Do you have controls disabled in FSUIPC4? If not, also check any assignments there. This assignment/control isn't coming from FSUIPC
shorthauler Posted October 8 Author Report Posted October 8 Thank you, problem solved. The out-of-the-box controls in FSX were *not* disabled (options/settings/controls/enable controllers) so they were interfering. My CMOS battery was empty and I had to start the PC without it a few times before the new battery came in. I don't know if it was this or something else, but something must have erased my FSX.cfg (I take this from the fact that all of a sudden the startup music was back on). And so the controllers were enabled and interfered. Apologies for taking your time with something that I could have figured myself. My punishment are a lot of nights without flight simming.
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