HI guys,

I am facing a problem with my AVS NES and the Everdrive N8.

In some screens, the image have some flickering points when I play a game. This is happening in 99% of the games and I dont know what is the problem.

I am thinking that could be an incompatibility between both but I found nothing about it searching the internet.

I recorded a video with the problem:





I changed my power supply, changed the HDMI Cable, changed the TV as well. 

I already tried several different roms and several Everdrive's OS and all AVS firmware.

Nothing takes effect.

I also tested the everdrive in other console (famicom AV) and the problem does not happen there. Just in the AVS. But running the same game in cartridge in the AVS, the problem does not happen at all.
​
Does anyone already faced something like that before?

Many thanks for any help!

Cheers

Might shoot RetroUSB support an email: [email protected]

They'll definitely want to know about it. AFAIK, no one seems to have that issue yet.

I'm getting the same black bars with Mega Man 3 (USA) via Everdrive N8 (NES version).

It's been around for a while. I'm surprised you say it happens with all firmware, because rolling back to 1.1 always gets rid of them for me. I think some of the early betas might also not have them.

Wow, I found the problem! Many thanks for all help.

The problem was the last Everdrive OS version.

I had install V11, V12 nothing happened.

I tried the nesos-v15 and it worked! I still have the problem with MegaMan3 and others (and castlevania 3 does not work in that version) but the flickering is gone for almost all games.

I would not want to change the last beta AVS firmware because I like the color pallets.

Many thanks for all, with your information I was able to make more precise tests!

 

This issue started in b6. Try using b5 with osv16 on the everdrive and everything should work. I notified retrousb support but they didnt seen very interested in fixing the issue on the avs's side.

I was using nesos-v15 when I first noticed this bug.  There are certain games (powerblade 2 and probably others) where it is noticeable.  While I do like the latest AVS firmware, I am also a fan of playing rom hacks with my everdrive.  The everdrive also lets me save games that don't otherwise have a save feature.

My solution has been just to use AVS firmware 1.10 with the latest Everdrive OS v16.  Then I just sort of adjust the color on my television to try to get it the way I like it.  Not a perfect solution, but I suppose it's good enough for now.

I am curious as to the disadvantages of using AVS firmware 1.10 though.  I play a lot of carts and haven't noticed anything yet.  Is there a detailed list of bug fixes between AVS 1.10 and 1.20?  I'd be very interested in looking through it.  The bugfix list seems kind of vauge.

http://retrousb.com/downloads/AVS...

What was wrong with xexyz?  What was wrong with Gradius 2?  I play Gradius 2 somewhat often.  I did notice in one of the AVS firmware betas it seemed to screw up compatibility with Gradius 2 being played through the everdrive, but it didn't seem to screw up compatibility with my Gradius 2 cart.

Xexyz would freeze up on certain carts (not all of them, though.) I did find that mine (finally!) worked after swapping the pin connector.  

It still locks up on the title screen if I try to do certain button inputs wrong, but the game is now playable.
 

Looks like I'm have the same flicker issue on my NES version Everdrive N8, with Little Samson.
I have read though the previous posts and conclude an older AVS firmware seemed to solve it.
Any new information, or solutions.

I'm currently using AVS firmware 1.2. Everdrive N8 firmware v16.

For a quick test, load the Temple (stage 10), password- ?2FK

--glitch/flicker only happens on AVS with everdrive --everdrive rom Little Samson works perfect on my frontloader --Little Samson on a multicart works perfect on AVS and NES



Thanks

Is there a link to all the AVS firmware's?

Thanks

http://www.retrousb.com/downloads...

Awesome.  Cheers for that.  What's the best one to use with N8 Everdrive?

Edit:  I tried a few firmwares on the AVS and they were all buggy on Everdrive N8 os16.  Why haven't they fixed these bugs?    I haven't seen a good FW update for the AVS since 2016?  This is why more will go Analogue.

 

Bunnyboy's had health issues and had the second run of AVS shipments. They're working on them now.

 

You keep talking abou all these bugs, but not anyone else (what bugs are you having anyway?). I know many other people use everdrive with out problems. Maybe your everdrive is the issue????

Huh? At least two other posters in this topic mentioned having the same issues. I also had artifacts in same games when using OS16 Everdrive N8 on AVS. There is another topic that mentioned that some homebrews didn't work on the latest firmware of the AVS, but worked on some earlier versions of the firmware. 
 

One person fixed the problem by updating the everdrive. The other has a single game with a small problem. 

The person I was reply to has posted a few times about "all kinds of bugs", one or two graphic glitches are not "all kinds".  From what I can recall anyone with issues on everdrive+AVS has been a fault of the everdrive. Either wrong/old firmware or maybe fake Chinese everdrive.

My everdrive was from Stone Age gamer, so it's legit. The person fixed the issue by going to an older version of the AVS firmware. I get the artifacts on the later firmware, but not the earlier ones. BTW, if you read other topics there are non everdrive issues like that one Punch Out style homebrew that works on the earlier betas, but not the latest firmware. There are posts elsewhere in this forum that also mention the firmware is buggy. I'm sure part of the issue is on the ED's end, but posts elsewhere suggest that OS 16 solved the problems for NES hardware.

Mention of bugs

oh ok. I understand, but I was under the impression he was talking about other issues. The games that had black or white flickering dashes for me were Super Mario Bros and other games using the same engine like Vs SMB Home Edition (mostly on green objects), the two Flintstones games (while grabbing platforms on EDOS16), JP TMNT Arcade (very minor on OS16, more noticible on earlier ED OSes), and Nightshade. I did notice less artifacts using OS 16. The issue was more minor with OS16, but still there. The flickering lines issue was also mentioned on the krikzz forums. From what I read on the everdrive forums, the issue also affected some later model NES/AV Famicoms, though I didn't have any flickering lines on any Everdrive OS on my AV Famicom. As other posters mentioned, the issue seems to have started with firmware 1.20b6. 

Mog, as you're obviously one of the "men on the ground" with the AVS, I figure you might be the one to ask about this without tying up the bunnyboy's resources.  If he/they can't track down all the bugs and get the FPGA 100% on all games, all the time, is it possible to have a version of firmware which can implement different fixes based on a menu selection vs re-flashing?  The 1.20 version has issues with certain games, but earlier betas (like 1.20b6, for example) work fine with those but have issues with different games.  If there's room in the FPGA, it would be fantastic to simply be able to select which "version" loads from an in-system menu and then let that roll until going to play one of the games which had issues on that particular fix.

That's an interesting idea, but I suspect the firmware version is so deeply ingrained in the operating system that even if you managed to get it to do that, it would wipe everything back to factory settings at the very least.

 

I keep seeing that the problem is with the everdrive and not the AVS. Help me understand details of what is ment. My particular graphical issue only happens with my AVS. (See my post above for specifics) Same rom, same everdrive works great in my front loaded. No graphical/ image issue.

I will give firmware 1.20b6 a try. Maybe 1.20b6 can also help with my menu screen cropping issue.

Thanks in advance

The Everdrive's firmware could be having an issue with the AVS's FPGA that the AVS firmware adjustments have no way of correcting. Which is why the suggestion is change/update the Everdrive firmware first.
 

Thank you, for a logical, civil response.   I am not particularly tech savvy, so this helps me understand.