4dads Posted 2 hours ago Report Posted 2 hours ago Good Evening, Been trying to get my Jetmax Sim to play ball with the thrust reversers on the PMDG 737-800. Have found this evening that there is apparently an input from the Avionics PC to the Sim PC. Narrowed it down to Wideclient. Is there any way to tell FSUIPC to ignore commands from networked PCs? Only need the data to be outputting not coming back the other way.
John Dowson Posted 2 hours ago Report Posted 2 hours ago You can try setting ButtonScanInterval=0 From the WideFS User guide: Quote With a user-registered FSUIPC3 or 4 all Windows, EPIC and GoFlight buttons will be recognised on Client PCs and transmitted to FSUIPC for programming unless this action is explicitly turned off in the Client. This action is automatic. You need do nothing to enable it—except, for GoFlight only, installing the Gfdev.dll as mentioned in the WideClient installation instructions earlier. For WideClient there is only one controlling parameter: ButtonScanInterval=20 This parameter, in the [Config] section of the WideClient.ini file, controls the rate at which WideClient scans EPIC and Windows joystick buttons. GoFlight buttons are not scanned by WideClient—those are dealt with by the Gfdev.dll. However the parameter is still relevant since if you set this to 0 (zero), it switches the whole facility off.
4dads Posted 49 minutes ago Author Report Posted 49 minutes ago Has been done, still the same issue, repeating within the log when the Avionics PC is sending data is. 250953 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET 250953 *** EVENT: Cntrl= 66488 (0x000103b8), Param= 1 (0x00000001) ANTI_ICE_SET_ENG1 250953 *** EVENT: Cntrl= 66489 (0x000103b9), Param= 1 (0x00000001) ANTI_ICE_SET_ENG2 250953 *** EVENT: Cntrl= 66337 (0x00010321), Param= 0 (0x00000000) TOGGLE_STRUCTURAL_DEICE 250953 *** EVENT: Cntrl= 66040 (0x000101f8), Param1= 16211 (0x00003f53), Param2= 0 (0x00000000) KOHLSMAN_SET From my understanding the KOHLSMAN_SET is linked to Baro.
4dads Posted 44 minutes ago Author Report Posted 44 minutes ago Last thing before going to bed, would a IgnoreDevice work on those?
John Dowson Posted 5 minutes ago Report Posted 5 minutes ago 34 minutes ago, 4dads said: Has been done, still the same issue, repeating within the log when the Avionics PC is sending data is. 250953 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET 250953 *** EVENT: Cntrl= 66488 (0x000103b8), Param= 1 (0x00000001) ANTI_ICE_SET_ENG1 250953 *** EVENT: Cntrl= 66489 (0x000103b9), Param= 1 (0x00000001) ANTI_ICE_SET_ENG2 250953 *** EVENT: Cntrl= 66337 (0x00010321), Param= 0 (0x00000000) TOGGLE_STRUCTURAL_DEICE 250953 *** EVENT: Cntrl= 66040 (0x000101f8), Param1= 16211 (0x00003f53), Param2= 0 (0x00000000) KOHLSMAN_SET Those are just events that are being logged....FSUIPC logs ALL events applied to the FS. Why do you think that those are coming from FSUIPC or WideClient? If you have no assignments in FSUIPC / WideFS, they won't be coming from there... Try setting logging for Buttons & Switches - that will log any button press that is triggering an assignment. If those events are being sent from your device and you don't want them to be sent, remove whatever you are using that is sending them. Note that many aircraft in MSFS continually emit certain events, and these event are different for each aircraft. These events are just noise really, and you can prevent them being logged using the DontLogThese ini parameter. 35 minutes ago, 4dads said: Last thing before going to bed, would a IgnoreDevice work on those? No, as they are most probably not coming from FSUIPC or WideFS. FSUIPC is just logging them, not sending them.
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