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

iCarly - Groovy Foodie! (USA)graphic glitches #375

Closed
benderscruffy opened this issue Feb 3, 2019 · 6 comments

Comments

Projects
None yet
2 participants
@benderscruffy
Copy link

commented Feb 3, 2019

using 0.7.3
on the title screen there is green glitchy lines and during game play there are glitchy red lines in the completed bar in the top screen
icarly
icarly1

@Arisotura

This comment has been minimized.

Copy link
Owner

commented Mar 26, 2019

3D renderer accuracy issue, I guess. interesting

@Arisotura

This comment has been minimized.

Copy link
Owner

commented Jun 9, 2019

ok, quick testing shows that both DeSmuME and NO$GBA also have this bug

guess this is going to be interesting

unless it also occurs on hardware?

@Arisotura

This comment has been minimized.

Copy link
Owner

commented Jun 9, 2019

confirmed to not occur on hardware

so, sit down and fasten your belt, this is going to be a fun ride

@Arisotura Arisotura removed the 3D accuracy label Jun 9, 2019

@Arisotura

This comment has been minimized.

Copy link
Owner

commented Jun 9, 2019

first of all we can take down the 3D label as that has nothing to do with it

the titlescreen logo is made with sprites; it seems to be doing something weird like changing them midframe

we're probably in for a timing issue, or unknown hardware behavior

(tbh this kind of game is the last place where I'd expect to see clever tricks like that)

@Arisotura

This comment has been minimized.

Copy link
Owner

commented Jun 9, 2019

well yeah it's updating the OAM midframe. welp

trying to figure out why that's shitting itself, tho

@Arisotura

This comment has been minimized.

Copy link
Owner

commented Jun 9, 2019

for example: it updates OAM right before scanline 30 (during the hblank period of scanline 29), but the changes aren't supposed to apply till scanline 31

I think it's because the hardware renders sprites one scanline in advance or something like that, but I need to do hardware tests

@Arisotura Arisotura closed this in d280356 Jun 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.