[RESOLVED] Upon opening PinballX the cabinet buttons don't work

[Almodo]

I'm experiencing quite a strange problem: 

When opening PinballX my cabinet buttons don't work! 

As soon as I push the Windows key on my keyboard and the Windows rectangle pops up with the usual options the buttons work. When I push Escape to remove it the buttons don't work again. 

I have no idea what to do. Any suggestions are welcome. Thanks in advance!

[Mike_da_Spike]

2 hours ago, Almodo said:

have no idea what to do. Any suggestions are welcome. Thanks in advance!

To start, please post your log file after producing the issue and also post your PinballX.ini.

[Draco1962]

Whenever soliciting for assistance, please attach copies of your pinballx.ini and log.txt file from right after the issue. This helps us to help you much faster. Thanks!

[Almodo]

Sorry, folks, first for not sticking to protocol, really.

But: It now works again! 

I have two game types running in my cabinet setup (lightgun games on one monitor, pinball on all three) with DisplayFusion managing the two configurations. 

Up to yesterday I had DisplayFusion also autostart PinballX on Windows bootup. I tried something and changed that to the regular Windows autostart function "shell:startup", and now it works again. Don't ask me why because the DisplayFusion autostart way used to work as well. 

Thank you so much for your kind replies. If any problem pops up again I'll get back to you. 

Stay safe, take care and thanks again for this great community!

[Draco1962]

2 hours ago, Almodo said:

I have two game types running in my cabinet setup (lightgun games on one monitor, pinball on all three) with DisplayFusion managing the two configurations. 

Up to yesterday I had DisplayFusion also autostart PinballX on Windows bootup. I tried something and changed that to the regular Windows autostart function "shell:startup", and now it works again. Don't ask me why because the DisplayFusion autostart way used to work as well. 

I wonder if it may have been a recent DisplayFusion or Windows update that created conflict. At any rate, you found the issue and resolved it! Thanks for reporting back with your solution!