Hi,
I’m not sure if this is a bug or a feature.
Using my Honeycomp Yoke with the default profile in fs2020 I can see in the event log of FSUIPC that permanently a number of events are fired.
Like Avionics_Master1_on and all Light commands. If I clean the key binding for e.g.the Avionic Master Switch, the event is gone. Compared to my Saitek X52 this is a strange behavior. The onliest idea for me is that FS2020 during Startup has no idea in which position the pushbutton is and therefore always firing this event. I’m little bit worried about performance, tons of events. This makes it hard to monitor other events. I’m still waiting for all the G1000 commands still missing, turning G1000 Group and Page knob is a nightmare with the mouse.
May be someone has p3d or fsx running and can tell me if this identical. Google did not help on this.
Thx
My understanding is this has been a “feature” of some control systems since way back when FSX first launched. Honeycomb do indeed send constant event type to the sim and this currently causes issues which show up as the headings bug where it will only change in 10 degree intervals and also altimeter issues.
Unfortunately, there is nothing that can be done unless the feature is worked out of the core sim which may not be possible given how long its been there. I also have a class echo flight control screen which the developer has used SPADNEXT to create a profile to change those events to simple on / off events instead and this seems to fix the problem so maybe something similar would help you.
Looking at a post earlier today regarding the Bravo throttle, this shows the same behaviours so I think it will be a case of creating profiles for that as well when people start receiving them.
Hello, thanks a lot, this makes it clearer now. I have to read a bit more about Spadnext, whether it could help me. First I’ll do is delete the keybindings, all this buttons are not so often in use.
Check it this link for a workaround. I has the save issue with broken knob increments. The below provides a temporary solution.
Many aircraft fire different events, but this shouldn’t be related to your hardware, unless these are events assigned to your hardware buttons/conttrols, and the buttons are firing (or you have your assignments on repeat and a button is identified as “pressed” but not “released”).
FSUIPC has an ini parameter DontLogThese which you can add to ignore such events. Currently only possible to add this in the [General] section of your ini, but it will also be possible to use this ini parameter in profiles in the next FSUIPC7 release, so that you can specify this individually for different profiles.
John / FSUIPC
Hello John, thank you for your tips. Without FSUIPC I wouldn’t be able to see this problem. In this case it’s really the honeycomb yoke. Main problem seems to be the ignition switch, causing a heading bug. Also Honeycomp states in Facebook that they are working on this issue with Asobo. I removed keybindings for the moment. I’ll keep the hint with the ini file in mind.
Yes, I have heard there are various problems with the Honeycomb yoke. I should have one here soon (+ the new Bravo quadrant) to do some further testing with these…
John
I’ve had the Honeycomb yoke quite a while and have not had any switch problems. I use all the magneto switch positions to pre-flight test the magnetos, and start aircraft with the start switch.
I move the heading bug ten degrees with the mouse wheel and one degree with mouse clicks- works great.
Why all the problems and fuss for so many alpha users?
Hi, I did not really have a problem with this Honeycomb yoke. My intention was to understand why all this events are created. I had to learn that other user have a problem with the yoke and a heading bug. Yes of course there is a way to overcome this bug, but real simmers expect working software.
I assume . Honeycomb is also working on this issue.
Before we blame Honeycomb, is anyone with “switches in a home cockpit” having these problems with the 10 degrees jump?