March 17, 2018 at 7:19 PM #20170
I’ve been playing with this for a while now, and I’ve noticed that this firmware has really significantly reduced compatibility for the NES and SNES with my TV. I’m not sure what it’s doing to process the consoles differently, but both no longer work in 5x mode and in the other modes experience intermittent screen blanking. I used to have that problem on an older official firmware, but ever since 0.78 the vanilla firmware has handled both consoles perfectly. So, not sure what is going on with this firmware that would reduce compatibility. I know both consoles have somewhat odd timing, but I would assume this only introduces an overlay over the official firmware.
Definitely worth looking into before merging this into 0.81, because at this point it looks like I’ll be stuck with 0.80 vanilla if I want my systems to work correctly. Which is a shame, because when this firmware works it looks so much better than the old scanlines.March 18, 2018 at 1:01 PM #20180paulb_nlParticipant
@Fnnrqwin Did your NES/SNES work properly with the firmware that had glitches in lineX5 mode? If you normally use the non-audio firmware then you should set TX mode to DVI because its set to HDMI by default on the audio firmware.
Here are firmware builds from the latest code of Marqs. Please try it out.
https://drive.google.com/file/d/18FladboTv64w5KxXwlphjwypVmZur-a9/view?usp=sharingMarch 20, 2018 at 1:25 AM #20227
@paulb_nl I flashed the OSSC with the new firmware you linked. It is definitely more compatible with the NES and SNES. I already had TX mode set to DVI, and I’m not sure what has changed under the hood, if anything. 4x mode is still the highest mode both consoles support, although the vanilla firmware still supports 5x for those on my TV, so something is still going on there. However, 4x mode is no longer resulting in any screen blanking.March 20, 2018 at 11:38 AM #20234paulb_nlParticipant
Did you get 5x working with the firmware that had glitches? Have you tried to set Allow H-PLL2x to off?March 21, 2018 at 8:40 PM #20288
– 4x still actually lost image, just not as frequently as before.
– Everything’s working now, but I had to bypass going through my receiver, which originally was compatible with every resolution configuration I threw at it. I’m not sure why that would stop working with this custom firmware, but connecting straight to the TV works.
– Honestly, it’s probably not worth trying to further work on this compatibility issue since we haven’t heard from anybody else losing compatibility. It works directly with my TV, so that’s good enough.
– H-PLL2x makes no difference whatsoever. Same with upsample 2x. I’ve actually never noticed a difference with either of those enabled or disabled, so I can’t speak to the effectiveness of that piece of advice.
So long story short, my receiver used to work with all these, but now doesn’t. I’m not sure what in the firmware changed that, but it doesn’t really matter since connecting to the TV works fine and I’ve not seen any other complaints about this from anybody else.
I guess just carry on and if anybody else chimes in with incompatibilities on previously fully compatible setups, then it’s worth looking at? But for now I seem to have had a one-off problem I’m able to bypass.April 17, 2018 at 8:05 AM #20863mdd45Participant
So any update on final 0.81 release and hybrid scanlines?May 4, 2018 at 8:07 PM #21348rgdelatoParticipant
I just wanted to say a huge thanks to all of you in the thread who made this happen! The hybrid scanlines really do look great. 😀May 10, 2018 at 2:32 AM #21489PRCParticipant
So how does the new hybrid and multiplication compare to the scanlines on a pvm/bvm?? or are this options meant to be more like a consumer CRT??
- You must be logged in to reply to this topic.