Anything is possible, I guess. I'm pretty sure this version is the wboy2 romset in MAME which doesn't have the issue, but I don't know if this is meaningful, or not.
Wonder Boy - minor sprite issue
- Thread starter big10p
- Start date
Wboy2 (I think) was used on multiple boards including the original ones that are not factory upgrades from Up 'n Down (As far as I know). The architecture of the boards are different and the logic is not the same so its possible , shot in the dark though as I am just guessing as such. Dont want you going to far down the rabbit hole Alice ! looking for something thats on all boards (If that makes sense)
Dave.
Dave.
I had a look at the Up n Down schems today, and used it to SLICE around, but didn't find anything obviously faulty. There's also a few ICs underneath the daughter board that I can't access to SLICE.
Looking at the schem, there's a couple of customs used in the sprite circuit, so I can't do much with those.
I did notice that the 4 data lines of one of the sprite RAMs used in the circuit are also piped through a nand gate that connects back to a custom, to a pin labelled OBJEND.
Could this be used to signal when a sprite scan line has ended, or something?
I think this is just going to be a 'bug' I'm going to have to live with, but now I've spotted it, it's really distracting while playing. Lol
Looking at the schem, there's a couple of customs used in the sprite circuit, so I can't do much with those.
I did notice that the 4 data lines of one of the sprite RAMs used in the circuit are also piped through a nand gate that connects back to a custom, to a pin labelled OBJEND.
Could this be used to signal when a sprite scan line has ended, or something?
I think this is just going to be a 'bug' I'm going to have to live with, but now I've spotted it, it's really distracting while playing. Lol
Good idea. I'll give that a try.
Yes, it still does it in cocktail mode. It's just on the other side of the sprite for player 2, as everything is up-side down (if you see what I mean).
It seems to be affecting all 'end pixels' that are followed by a blank/transparent pixel in the scan line. Probably didn't explain that very well. lol. It's weird.
It seems to be affecting all 'end pixels' that are followed by a blank/transparent pixel in the scan line. Probably didn't explain that very well. lol. It's weird.