ByteG Posted January 11, 2014 Report Posted January 11, 2014 Hi, last week I've purchased Hifi's Active Sky Next which requires at least FSUIPC version 4.926 (my version was 4.920). So, I've upgraded FSUIPC to version 4.927. But with the upgrade I've noticed that the aircraft doors (offset 3367) has stopped working, while everything else was still working fine. I am using LINDA and most of the buttons are handled with ipc.write... After downgrading FSUIPC to the previous version the doors were opening again. Thank you, Dejan
Pete Dowson Posted January 11, 2014 Report Posted January 11, 2014 So, I've upgraded FSUIPC to version 4.927. But with the upgrade I've noticed that the aircraft doors (offset 3367) has stopped working, while everything else was still working fine. I am using LINDA and most of the buttons are handled with ipc.write... The doors work fine here, with 4.927a or 4.927b (the current version), and there's been no change at all anywhere near this area. The doors operated through 3367 use regular FSX controls -- please enable event logging and see if the toggle controls are being used. You could monitor 3367 as type U8 on the right-hand side of the Logging tab to check too. Show me the log (paste here). Pete
ByteG Posted January 11, 2014 Author Report Posted January 11, 2014 The doors work fine here, with 4.927a or 4.927b (the current version), and there's been no change at all anywhere near this area. The doors operated through 3367 use regular FSX controls -- please enable event logging and see if the toggle controls are being used. You could monitor 3367 as type U8 on the right-hand side of the Logging tab to check too. Show me the log (paste here). Pete I've found this interesting: Exception 3 "UNRECOGNIZED_ID", Ref 2457, Index param 4 on TransmitClientEvent, object=0, id=66389 (TOGGLE_AIRCRAFT_EXIT), data=1 VRI com3 <--- DSP0Dor1 [from Lua Plug-in] VRI com3 <--- DSP1Open [from Lua Plug-in] VRI com3 <--- DSP0 [from Lua Plug-in] VRI com3 <--- DSP1 [from Lua Plug-in] WRITE0[5008] 66C0, 2 bytes: 6B 00 k. WRITElua 3367, 1 bytes: 00 . Exception 3 "UNRECOGNIZED_ID", Ref 2467, Index param 4 on TransmitClientEvent, object=0, id=66389 (TOGGLE_AIRCRAFT_EXIT), data=1 VRI com3 <--- DSP0Dor1 [from Lua Plug-in] VRI com3 <--- DSP1Clsd [from Lua Plug-in] VRI com3 <--- DSP0 [from Lua Plug-in] VRI com3 <--- DSP1 [from Lua Plug-in] WRITE0[5008] 66C0, 2 bytes: 6B 00 k. WRITElua 3367, 1 bytes: 01 This is log when I press avionics key: Memory in use: 1688Mb, Avail=2408Mb VRI com3 <--- DSP0 [from Lua Plug-in] VRI com3 <--- DSP1 [from Lua Plug-in] WRITE0[5008] 66C0, 2 bytes: C0 00 .. WRITElua 2E80, 2 bytes: 00 00 .. [C] Control: 66293 - 0 TOGGLE_AVIONICS_MASTER VRI com3 <--- DSP0AVIO [from Lua Plug-in] VRI com3 <--- DSP1Off [from Lua Plug-in] VRI com3 <--- DSP0 [from Lua Plug-in] VRI com3 <--- DSP1 [from Lua Plug-in] .
Pete Dowson Posted January 11, 2014 Report Posted January 11, 2014 I've found this interesting: Exception 3 "UNRECOGNIZED_ID", Ref 2457, Index param 4 on TransmitClientEvent, object=0, id=66389 (TOGGLE_AIRCRAFT_EXIT), data=1 Looks like it could be a corruption someplace in your installation. "TOGGLE_AIRCRAFT_EXIT" is the correct control. It takes a parameter, 1, 2, 3 or 4 defining which doors to toggle. A parameter of 0 is the same as 1 in this case. Try using the keyboard, with the logging still exabled. I think door toggling is Shift+E isn't it? (Check first), then the number you press after becomes the parameter. If that works then FS is okay but there's possibly something up with SimConnect. It might be helpful to get a SimConnect log -- there's a FAQ about that the FAQ subforum. It'll be big though -- maybe ZIP it and send to petedowson@btconnect.com. But first try the latest FSUIPC test version, FSUIPC4927f.zip which may just possibly make a difference as it should fix a small problem related to interception of SimConnect Text requests. Pete
ByteG Posted January 11, 2014 Author Report Posted January 11, 2014 Looks like it could be a corruption someplace in your installation. "TOGGLE_AIRCRAFT_EXIT" is the correct control. It takes a parameter, 1, 2, 3 or 4 defining which doors to toggle. A parameter of 0 is the same as 1 in this case. Try using the keyboard, with the logging still exabled. I think door toggling is Shift+E isn't it? (Check first), then the number you press after becomes the parameter. If that works then FS is okay but there's possibly something up with SimConnect. It might be helpful to get a SimConnect log -- there's a FAQ about that the FAQ subforum. It'll be big though -- maybe ZIP it and send to petedowson@btconnect.com. But first try the latest FSUIPC test version, FSUIPC4927f.zip which may just possibly make a difference as it should fix a small problem related to interception of SimConnect Text requests. Pete Hi Pete, I have installed the latest file but doesn't correct the problem. I have temporary enabled Shift+E to see if it works directly from FSX and it was ok. But I can't seem to get the same error as before. WRITE0[4248] 66C0, 2 bytes: 6B 00 k. WRITElua 3367, 1 bytes: 01 . VRI com3 <--- DSP0Dor1 [from Lua Plug-in] VRI com3 <--- DSP1Open [from Lua Plug-in] VRI com3 <--- DSP0 [from Lua Plug-in] VRI com3 <--- DSP1 [from Lua Plug-in] WRITE0[4248] 66C0, 2 bytes: C0 00 .. WRITElua 2E80, 2 bytes: 01 00 .. [C] Control: 66293 - 0 TOGGLE_AVIONICS_MASTER VRI com3 <--- DSP0AVIO [from Lua Plug-in] VRI com3 <--- DSP1On [from Lua Plug-in] VRI com3 <--- DSP0 [from Lua Plug-in] VRI com3 <--- DSP1 [from Lua Plug-in] This is from FSUIPC4.INI Debug=Please FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 LogWrites=Yes LogEvents=Yes LogExtras=x4 To sum up. 1) It works with fsx controls 2)It works with ipc.write in FSUIPC 4.920 3)It doesn't work with FSUIPC 4.927a-f If something is wrong with SimConnect - why 2 is ok, and 3 is not? I have sent the simconnect.log to your e-mail as well. Dejan
Pete Dowson Posted January 11, 2014 Report Posted January 11, 2014 I have installed the latest file but doesn't correct the problem. Okay. It was a long shot. I've just tested it in my cockpt and have no problem. I have temporary enabled Shift+E to see if it works directly from FSX and it was ok. No FSUIPC log of events to show what was sent? That was the point, really. But I can't seem to get the same error as before. WRITE0[4248] 66C0, 2 bytes: 6B 00 k. WRITElua 3367, 1 bytes: 01 . Unless the write of 01 to 3367 changes its previous value, it won't do anything. You don't seem to be monitoring 3367 as I asked, nor do you show any logs, so I'm really none the wiser. This is from FSUIPC4.INI Debug=Please FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 LogWrites=Yes LogEvents=Yes LogExtras=x4 Those are only from the [General] section. The Monitor part has its own section. To sum up. 1) It works with fsx controls 2)It works with ipc.write in FSUIPC 4.920 3)It doesn't work with FSUIPC 4.927a-f If something is wrong with SimConnect - why 2 is ok, and 3 is not? Sorry, I've no idea. Maybe we need to see identical logs etc from 4.920 ad 4.927f to compare them -- FSUIPC logging/monitoring and SimConnect logs. If there's a difference it should show up. The fact that it works perfectly fine here suggests there's some interaction with something different on your system. Is "NewInterceptTextMenu=No" set in the [General] section of FSUIPC4.INI? If not, try that. So far I've insufficient information. Aren't you using the Monitor as requested? Also the actual logs would be more useful to look at than your extracts -- what are they from? I have sent the simconnect.log to your e-mail as well. Yes, and that proves things were correctly set: > 9.82378 [136, 1887]MapClientEventToSimEvent:EventID=66389, EventName="TOGGLE_AIRCRAFT_EXIT" That's where FSUIPC's definition of its event #66389 is assigned to TOGGLE AIRCRAFT EXIT, and > 174.83120 [136, 2463]TransmitClientEvent:ObjectID=0, EventID=66389, dwData=1, GroupID=3, Flags=0 < 174.83121 [136] >>>>> EXCEPTION=3, SendID=2463, Index=4 <<<<< that's where it said the request was invalid. Why it does that I'm afraid I've no idea. Note that the request was for Exit 1 (dwData = 1). "Index=4" refers possibly to that parameter rather than the control number (ID) itself. Does Shift+E+1 work? (0 is a default if no numbers are given). Pete
ByteG Posted January 11, 2014 Author Report Posted January 11, 2014 Hi again, Pete Dowson, on 11 Jan 2014 - 7:59 PM, said: Is "NewInterceptTextMenu=No" set in the [General] section of FSUIPC4.INI? If not, try that. It was =Yes. Then I've changed it to No and tried again. No difference. I've reset to Yes. Pete Dowson, on 11 Jan 2014 - 7:59 PM, said: Sorry, I've no idea. Maybe we need to see identical logs etc from 4.920 ad 4.927f to compare them -- FSUIPC logging/monitoring and SimConnect logs. If there's a difference it should show up. The fact that it works perfectly fine here suggests there's some interaction with something different on your system. I have sent to you both simconnect logs and both FSUIPC4 logs with FSUIPC.ini as well. Pete Dowson, on 11 Jan 2014 - 7:59 PM, said: Note that the request was for Exit 1 (dwData = 1). "Index=4" refers possibly to that parameter rather than the control number (ID) itself. Does Shift+E+1 work? (0 is a default if no numbers are given). All combinations Shift+E+1, 2, 3 or 4 open only main exit. I actually never knew whether you should press all 3 buttons together or Shift+E first and then 1. I've always used the following lua script for this: function BG_Doors_set(mask, onoff, str) if str == nil then str = "Door" end local val = ipc.readUB(0x3367) if onoff == 0 then mask = 255 - mask val = logic.And(val, mask) ipc.writeUB(0x3367, val) DspShow(str, "Clsd") else val = logic.Or(val, mask) ipc.writeUB(0x3367, val) DspShow(str, "Open") end end function BG_Doors_toggle_masked(mask, str) if BG_Doors_check_closed(mask) then BG_Doors_set(mask,1,str) else BG_Doors_set(mask,0,str) end end function BG_Doors_1_toggle() BG_Doors_toggle_masked(1, "Dor1") end Dejan
Pete Dowson Posted January 12, 2014 Report Posted January 12, 2014 BTW I notice you are using the FSUIPC4 loader. Why? It isn't a good idea, it was just provided on a "use in extreme case of difficulty" basis. Best not to if you don't really need to. Just delete the Loader from the Modules folder and re-run the Installer to fix the DLL.XML file. Pete
Pete Dowson Posted January 12, 2014 Report Posted January 12, 2014 STOP PRESS! The SimConnect logs were most useful. There's one important difference -- the one using 4.92 has yjis line for FSUIPC: > 10.10816 [136, 2342]SetNotificationGroupPriority:GroupID=3, uPriority=10000000 but this is missing in the log for 4.927f. This is interesting because Group 3 includes the TOGGLE AIRCRAFT EXIT event/control (and others). Checking now how this action can be skipped. I am suspecting some timing issues here -- you have a great many SimConnect clients operating simultaneousy. I'm wondering if some calls are timing out. I may need to add further loggingg in FSUIPC to find out. Pete
Pete Dowson Posted January 12, 2014 Report Posted January 12, 2014 Found it! It's related to an option you have set (which is new in recent versions, AFTER 4.92) to stop FSUIPC's facility for associating numeric keypresses with their preceding controls when using add-on aircraft which otherwise interfere with this by continually sending controls to FS. It seems that you have set: TimeForSelect=0 in the INI file. If you remove this I think you'll find the aircraft exits work with 3367. I'll work out some way of effecting the original objective of this option without destroying FSUIPC's ability to send to related controls of its own volition. Look out for 4.928 some time tomorrow, probably. Thanks for your help in this. It's such an obscure relationship between options that I might never have found it without your help! Sorry for all the hassle involved though. Pete
ByteG Posted January 12, 2014 Author Report Posted January 12, 2014 Found it! It's related to an option you have set (which is new in recent versions, AFTER 4.92) to stop FSUIPC's facility for associating numeric keypresses with their preceding controls when using add-on aircraft which otherwise interfere with this by continually sending controls to FS. It seems that you have set: TimeForSelect=0 in the INI file. If you remove this I think you'll find the aircraft exits work with 3367. I'll work out some way of effecting the original objective of this option without destroying FSUIPC's ability to send to related controls of its own volition. Look out for 4.928 some time tomorrow, probably. Thanks for your help in this. It's such an obscure relationship between options that I might never have found it without your help! Sorry for all the hassle involved though. Pete Yes, you are correct. Removing TimeForSelect=0 has fixed the problem. But now I have a problem with another add-on. Actually, I had similar problem with this add-on before but now FSX wants it disabled. Thank you for time. It was no problem for me providing all the logs to fix this. Dejan
Pete Dowson Posted January 12, 2014 Report Posted January 12, 2014 Yes, you are correct. Removing TimeForSelect=0 has fixed the problem. But now I have a problem with another add-on. Actually, I had similar problem with this add-on before but now FSX wants it disabled. Thank you for time. It was no problem for me providing all the logs to fix this. Dejan FSUIPC 4.928 is now available. 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