Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi, thanks for responding! I'm using the latest release (22.09) which uses 2.07k. Feel free to ping me over email at ptsochantaris at gmail and I'll be happy to try and debug, I'm just not very familiar with Next basic or I would have given it a go myself. I'm using an N-Go board for what it's worth, and the mouse is connected to the port via USB -> PS2 converter -> Mouse/keyboard splitter -> N-Go. Hope this helps!

(1 edit)

Ah, like l-o-l,  the main thing I see here is that you're both running N-Go boards.  Wonder if the mouse driver is not talking with the N-Go port in the same way.

For starting the game, I read the actual port directly so obviously that works.  The mouse driver just was a faster and more efficient way to work with the mouse. 

Thanks for the feedback.  I will go pester some Next nerds and see if anybody else has run into this...  😁

As I just posted to l-o-l, a good test to see if its a driver thing is to load the basic demo for the mouse.  Its under the /demos/mouse folder