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

Strange lighting? error with curved tracks and bogeys #6633

Closed
ReRouteGaming opened this issue Jun 27, 2024 · 5 comments
Closed

Strange lighting? error with curved tracks and bogeys #6633

ReRouteGaming opened this issue Jun 27, 2024 · 5 comments
Labels
type: bug Issue where something isn't working

Comments

@ReRouteGaming
Copy link

Describe the Bug

When placing down track that is curved, they appear solid black.
Minecraft-06-26-2024 19-06-17-635
Upon placing more curved track nearby the glitched track, the new track will become effected, and the old track will become unaffected.

Also, when assembling a train that has more than 1 bogey and multiple carriages, the same issue shows up on the last bogies of the train.
Minecraft-06-26-2024 19-08-16-922

Reproduction Steps

  1. Place down curved track

  2. Assemble a train with multiple bogeys

Expected Result

Tracks/bogeys will appear as normal.

Screenshots and Videos

Minecraft-06-26-2024 19-06-17-635
Minecraft-06-26-2024 19-08-16-922

Crash Report or Log

No response

Operating System

Windows 11

Mod Version

0.5.1f

Minecraft Version

1.20.1

Forge Version

47.2.0

Other Mods

No response

Additional Context

No response

@ReRouteGaming ReRouteGaming added the type: bug Issue where something isn't working label Jun 27, 2024
@IThundxr
Copy link
Member

/flywheel backend batching

@IThundxr IThundxr closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2024
@MarioSMB
Copy link
Contributor

Why was this closed? This is a pretty severe bug, and switching to the batching backend can result in a massive performance loss.

@IThundxr
Copy link
Member

Why was this closed? This is a pretty severe bug, and switching to the batching backend can result in a massive performance loss.

It's caused by something that's changed in the AMD driver and it's fixed with flywheel 1.0 anyway

@PepperCode1
Copy link
Member

This is also a duplicate of Engine-Room/Flywheel#226.

@MarioSMB
Copy link
Contributor

I see - thanks for referencing the issue, this one is easier to find via Google currently so that should help with redirecting people with the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Issue where something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants