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

Mini Golf Hole D and E have incorrect underground boundbox #18423

Open
Gymnasiast opened this issue Oct 23, 2022 · 3 comments
Open

Mini Golf Hole D and E have incorrect underground boundbox #18423

Gymnasiast opened this issue Oct 23, 2022 · 3 comments
Labels
bug Something went wrong. z-fighting

Comments

@Gymnasiast
Copy link
Member

Gymnasiast commented Oct 23, 2022

Operating System

Ubuntu 22.04

OpenRCT2 build

286f010

Describe the issue

Not affected by #18404.

Area(s) with issue?

No response

Steps to reproduce

Build Mini Golf Hole E underground. Is likely to apply to other holes as well.

Attachments

No response

@Gymnasiast Gymnasiast added the bug Something went wrong. label Oct 23, 2022
@Gymnasiast Gymnasiast changed the title Mini Golf Hole E has incorrect underground boundbox Mini Golf Hole D and E have incorrect underground boundbox Oct 23, 2022
@raacker
Copy link
Contributor

raacker commented Oct 23, 2022

@Gymnasiast Thanks for creating another issue ticket. I played around a bit but I think I really couldn't understand BoundingBox Size and offset values. For me, feel like hard coded magic numbers.

switch ((direction << 4) | trackSequence)
{
case 0x01:
case 0x32:
PaintAddImageAsParent(session, imageId, { 0, 0, height }, { 2, 26, 3 }, { 30, 3, height + 4 });
break;
case 0x02:
PaintAddImageAsParent(session, imageId, { 0, 0, height }, { 23, 2, 3 }, { 3, 30, height + 4 });
break;
case 0x10:
PaintAddImageAsParent(session, imageId, { 0, 0, height }, { 2, 24, 3 }, { 30, 3, height + 4 });
break;
case 0x20:
case 0x31:
PaintAddImageAsParent(session, imageId, { 0, 0, height }, { 26, 2, 3 }, { 3, 30, height + 4 });
break;
default:
PaintAddImageAsParent(
session, imageId, { 0, 0, height }, { boundBox.x, boundBox.y, 0 },
{ boundBoxOffset.x, boundBoxOffset.y, height + 24 });
break;

I can tell it definitely has z fighting issue and would be resolved by bounding box values.

@Gymnasiast
Copy link
Member Author

People like @rik-smeets and @karst have done this before, so I expect one of them to look into it.

@Derpercoaster
Copy link

Derpercoaster commented Dec 1, 2022

For me, z-fighting doesn't ruin the game experience. It's just part of the game's endless charm. Whenever I run into it, I never think "oh great, not this again!" but instead think "how can I build this so I don't see the bug?" I design my park around bugs, which makes them feel like part of the game.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something went wrong. z-fighting
Projects
None yet
Development

No branches or pull requests

4 participants