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

Potential Display Bug - non-original game codebase #8

Open
b-mag opened this issue Aug 29, 2022 · 4 comments
Open

Potential Display Bug - non-original game codebase #8

b-mag opened this issue Aug 29, 2022 · 4 comments

Comments

@b-mag
Copy link

b-mag commented Aug 29, 2022

COTYLEDON.zip

Hello, I'm coding some vectrex components to be used with an upcoming game. I'm using this core in retroarch as an extra layer of testing.

I noticed on hardware and debugger the cursor character has a collision box that pops up near the center of the line when crossing it.

However using vecx this collision box does not display.
potential_bug

@b-mag
Copy link
Author

b-mag commented Aug 29, 2022

By the way I have never used retroarch/vecx... wow very nice all around! I remember the days when running emulators was a painful experience! So great work on this.

@gtoal
Copy link

gtoal commented Aug 29, 2022

Brandon, try running that bin of yours under Vectrexy - it issues lots of warnings about stray writes and stack corruption. Unless those are deliberate, make sure your program isn't corrupting itself before looking too hard at the emulators... I think for example that Vide doesn't protect the virtual 'rom' addresses from being overwritten.

@b-mag
Copy link
Author

b-mag commented Aug 29, 2022

Thank you I will check it out. Did you see something that makes it seem like I'm corrupting something? By the way I just set a 1 byte collision variable with a 1 and in my draw routine if it is 1 I also draw a simple rectangle at player x/y. Strange that would be the piece it is upset with.

@b-mag
Copy link
Author

b-mag commented Aug 30, 2022

Both current builds of Vectrexy crash on my windows 7 upon initial execution.

However I tested it with ParaJVE just now (never used any of these emulators before ) and it works great. Output matches hardware and VIDE's emulator so I am happy now.

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

2 participants