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

L.A. MACHINEGUNS: screen garbage #219

Open
Garagefreek opened this issue Nov 11, 2024 · 6 comments
Open

L.A. MACHINEGUNS: screen garbage #219

Garagefreek opened this issue Nov 11, 2024 · 6 comments

Comments

@Garagefreek
Copy link

Garagefreek commented Nov 11, 2024

The screen should transition to black for a quick second before the game begins after selecting the stage but on the emulator we get this? screen shot below, is it fixable? Actual pcb footage https://youtu.be/IpKb5x-Ynds?feature=shared&t=68
Screenshot 2024-11-11 011958

@Garagefreek Garagefreek changed the title L.A . MACHINEGUNS: screen garbage L.A. MACHINEGUNS: screen garbage Nov 12, 2024
@Garagefreek
Copy link
Author

So any luck with this issue?

@ghost
Copy link

ghost commented Dec 15, 2024

try dropping the ppc frequency

@ghost
Copy link

ghost commented Dec 15, 2024

On my win 11 Intel laptop, it seems to poduce garbage at -ppc-frequency=75.
Try a value lower than that.

@dukeeeey
Copy link
Collaborator

These games aren't designed to run at those low clock frequencies, such garbage is expected

@ghost
Copy link

ghost commented Dec 15, 2024

For me it's the opposite.
Letting Supermodel run at speeds now defined by the 'step' seems to cause the garbage.
Switching back to a lower frequency seems to fix it.
I never changed my launch scripts from ppc 66, so seeing this garbage was news to me and only achieved by letting Supermodel run 'out of the box'.

La guns seems tricky though. It feels a bit intense/laggy as if it needs more cycles, as you suggest. But too many cycles seems to throw off the rendering or timing?

@gm-matthew
Copy link
Contributor

I think this might be similar to Scud Japan in that the tilegen glitches if it is updated too fast. I really ought to implement tilegen wait states to fix both of these issues; I've had a rough solution for quite a while that needs a bit of polishing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants