Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mario Kart DS multiple black lines on screen on Wario Stadium track(Special cup). #234

Closed
ghost opened this issue Mar 18, 2018 · 5 comments
Closed

Comments

@ghost
Copy link

@ghost ghost commented Mar 18, 2018

Tested in MelonDS 0.6b
1
2

@Arisotura
Copy link
Owner

@Arisotura Arisotura commented Jun 14, 2018

Similar glitches happen everywhere (albeit less visible). I suspect they come from the faux-antialiasing code.

@scottbeebiwan
Copy link

@scottbeebiwan scottbeebiwan commented Aug 21, 2018

i assume fixing this would be part of the lcd blending mentioned in readme.md? @StapleButter

@Arisotura
Copy link
Owner

@Arisotura Arisotura commented Nov 4, 2018

nope

LCD blending would cover different effects and not this kind of glitch (which is the emulator's fault)

@Arisotura
Copy link
Owner

@Arisotura Arisotura commented Nov 4, 2018

quick notes on this:

  • not caused by antialiasing
  • not fog
  • not translucent polygons
Arisotura added a commit that referenced this issue Nov 4, 2018
…ven very flat X-major edge slopes.

this, by a fucking shitshow of butterfly effect, ends up fixing #234. technically, the rasterizer was going out of bounds, which, under certain circumstances, caused interpolation to shit itself and generate Z values that were out of range (but still ended up in the zbuffer). sometimes those values ended up negative, which caused these glitches when polygons had to be drawn over those.

about fucking time.
@Arisotura
Copy link
Owner

@Arisotura Arisotura commented Nov 4, 2018

this is now fixed but Github didn't get the memo apparently

@Arisotura Arisotura closed this Nov 4, 2018
m4tsa pushed a commit to m4tsa/melonDS that referenced this issue Jul 26, 2019
…ven very flat X-major edge slopes.

this, by a fucking shitshow of butterfly effect, ends up fixing Arisotura#234. technically, the rasterizer was going out of bounds, which, under certain circumstances, caused interpolation to shit itself and generate Z values that were out of range (but still ended up in the zbuffer). sometimes those values ended up negative, which caused these glitches when polygons had to be drawn over those.

about fucking time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants