Skip to main content

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

hello!

1. This game rules!

2. I'm having a small issue (and it's probably my fault). The rom works great on my Everdrive N8, but it's not working on my Everdrive N8-Pro. Let me clarify: The rom loads on both fine, but the zapper doesn't work with the N8-Pro for some reason.

Like I said, it's probably something I'm doing wrong, but any help would be appreciated. Thanks!

Interesting.
I have an Everdrive N8 I use for testing, but I don't have an N8-Pro, so I'm not familiar with N8-Pro specific features. I don't suppose there are some settings in the N8-Pro that could be a factor. Would I be correct in presuming that your Zapper is plugged into controller slot 2?

Also, regarding the Zapper not working. Are you getting any response when you pull the trigger? If so, does it flicker the screen to black when their are targets on the screen (either in the 2-choice menus or when enemies are on screen)? 

Last aspect to check, what type of device are you playing the Everdrive on? Is it a stock NES or a third-party machine like a Retron? Is the device plugged in directly to a CRT TV or does it go through another device along the way?

Sorry for the volley of questions. These are just what came up as I started thinking about what might be going on.

Hello!

Yes, zapper is in port 2.

Zero response at all from multiple zappers I tried.

Tried it on both an original NES and a top loader directly into my CRT. Both same results. 

I also tested out some other zapper games on the N8-Pro and they worked fine. Like I said, it works GREAT on the N8.

Just wanted to give you the heads up. 

Thanks!

Thank you!
I definitely appreciate the heads-up.

Hi Joe,

I just picked up an Everdrive N8-Pro and the Zapper seems to be working on mine. Do you know which version of the OS you're running? You can check it by hitting SELECT at the Everdrive menu and selecting Device Info.

hello! OS Version 2.14 is what i'm seeing. 

When I was testing, I was using OS Version 2.15. Could that be it?
Once I'm done with the convention this weekend, I'll try changing my OS version and see if that reproduces the bug.