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

feature request #14

Open
copilot-lover opened this issue Feb 27, 2024 · 0 comments
Open

feature request #14

copilot-lover opened this issue Feb 27, 2024 · 0 comments

Comments

@copilot-lover
Copy link

When Minecraft is loading, most of the loading process is handled by the rendering thread, as indicated by the game logs:

[Render thread/INFO]: [Spectrum] Starting Common Startup
[Render thread/INFO]: Registered the class blah.blah.blah.............
[Render thread/INFO]: Created: 512x256x1 minecraft:textures/atlas/beds.png-atlas

However, since the rendering thread is responsible for the, well, rendering, this can cause the loading process to appear frozen to the user. Windows may even display a message stating that "Minecraft isn't responding," even though the game is still loading.

To address this issue, one solution would be to move the rendering process to a separate thread. Alternatively, a dedicated loading thread could be created to handle the loading process separately from the rendering thread, resulting in a smoother and more enjoyable loading experience for the user.

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

1 participant