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

Jurassic Park: transparency gitch on the first stage #1718

Open
vanfanel opened this issue Mar 13, 2024 · 4 comments
Open

Jurassic Park: transparency gitch on the first stage #1718

vanfanel opened this issue Mar 13, 2024 · 4 comments

Comments

@vanfanel
Copy link

Hello there,

Running latest FBNeo GIT code here.
I've noticed a transparency glitch on the first stage of Jurassic Park, where brown-ish transparent bands move up and down with the cursor.
I recorded a video of it:

jpark_glitch.mp4

Seems like a Sega System 32 emulation bug.

@dinkc64
Copy link
Collaborator

dinkc64 commented Mar 14, 2024

Hi vanfanel,
Here's how it's supposed to look:
https://youtu.be/Mx0fHZOThlo?si=pflfqBvwG1VW1Y6R&t=153

I'll try to figure it out, but I can't promise anything, the Sega System 32 is kinda complex!

best regards,

  • dink

@mahoneyt944
Copy link

mahoneyt944 commented Jun 13, 2024

I believe it's related to row scroll. I managed to get it working for player 2 but not player 1 in mame2003+. Player 1 might just be a priority issue though as its not shown at all but I never got any further with it. Maybe this will help here though.

https://github.com/libretro/mame2003-plus-libretro/blob/3206819c48567e759f993134ac27491b11b3dd80/src/vidhrdw/system32_vidhrdw.c#L1327-L1331
jpark-240613-021406

@dinkc64
Copy link
Collaborator

dinkc64 commented Jun 13, 2024

Hi mahoneyt944, thanks for the tip!
I'll see if this can be improved upon,

best regards,

  • dink

@mahoneyt944
Copy link

@dinkc64 I went down the rabbit hole a little by porting newer segas32 video code over to mame2003+.... I get the same issue noted here. Curiously it's not broken for player 2 in any code base, so I'm hopeful that it's a minor adjustment needed for player 1. This issue has been present since the beginning of this video code (around mame 97u2), so it's unlikely my previous comment will help here. Player 2's render might point us in the right direction though.

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