Game visually hangs, usually in inventory screen. Game continues to run but nothing renders.

[Wil-dTrick]

Modpack

FTB Evolution

Modpack version

1.5 - 1.9

Launcher

ATLauncher

Has the pack been modified

No

Log Files

This console log was cleared after game load but before opening the world. So it's just this once instance of the error. https://paste.atlauncher.com/view/048a920c-ef56-4e93-980e-6d6b62160e57

This is all the records for the same timeframe from rocket-client.log
https://pastebin.com/EbN7yubQ

Nothing else appears to have any useful additional information. I think there's a set of log files elsewhere I saw when trying to troubleshoot it but I don't know how useful those are.

Describe the bug

I've tested this on all version from 1.5 - 1.9 - Java JDK 21 installed from jdk-21_windows-x64_bin.exe

Game will play for a random amount of time. FPS 40 - 50 (Significantly lower while recording due to my computer not liking me recording while I play). No unusual lag or anything else. Sometimes it doesn't happen for hours, sometimes it happens immediately.

Usually I will open the inventory and the graphics of the game will hang. The game continues to play in the background. I can always close the game just by knowing or guessing where the "Save and Exit" and "Quit" buttons are. That is the only consistent issue.

In addition to the issue above, sometimes I notice other things that may or may not be connected. But they don't happen every time. And if they happen, they don't reliably cause this hang to happen.

Occasionally I also notice:
Screen glitches in the inventory screen especially. Looks like it's trying to render something triangular. If my laptop didn't play literally every other modpack, and Control and Satisfactory, without issue, I'd think my video card was bugging. I have no issues in other modpacks or games.

Sometimes the text will get colored dots all around it or pieces of the text will go missing. I thought this was potentially related and have tried it with and without any font related settings/mods removed.

Thought it may be JEI related but disabling all parts of JEI did not fix the problem. Tried it with and without shades. Tried it with and without just about every video feature. No other modpack has this issue. Game runs just fine. Video card driver is up to date (I am currently in a boxing match during which I have to reinstall the most up to date driver every time Windows updates due to the manufacturer not keeping up- so I know it's the newest one.)

Provided full console log (Cleared after start up, but before loading world). Managed to record a series of 1 minute videos of gameplay and capture the issue. I only included the last minute where it bugs out.

Steps to reproduce

Play for a while.
Open an inventory
Video hangs while game continues to process in the background.
Click around the right areas until the game closes correctly to avoid save corruption.

Note: In the video I was able to sort of force it to happen because I noticed the armor in Column 4, Row 6 blinked out for a second and hovered over it. That doesn't always work. We just got lucky. I was looking for anything buggy to try to get to break. Usually it doesn't require anything to be hovered over or interacted with. It will just freeze.

Expected behaviour

At step 3 I would expect to be able to interact with the inventory and not have to close the game because it won't update.

Screenshots

https://www.youtube.com/watch?v=hBKZRdKZ8y4 -- One minute video showing the error.

watch?v=hBKZRdKZ8y4 -- One minute video showing the error. Same video URL modified in case there's a stripping code in place. I can't upload the video directly so this is as close as you can get to seeing it. Frame rate looks lower than stated due to recording.

Additional information

No response

[Gaz492]

We have seen a few issues with people using ATLauncher to start our modpacks, if you use the FTB App do you still run into the graphical issue?

[Wil-dTrick]

I'm really not interested in downloading another application. There's no reason that there should be a difference between the two launchers assuming they're downloading from the same sources and are being set up the same. Especially since AT launcher has an option to download mods that don't allow automatic downloads. I will download it as a zip file if you want me to test it against another fileset.

If there's routinely differences, they should be easy enough to pinpoint and provide information on how to correct.

Otherwise this feels like a cop out to force me into an isolated platform. I may be just a smidge annoyed by the endless 'advertising' spam I have to sift through when trying to read the console. (See: the first dozens of lines in the log. It is just the same ad a bunch of times. It's so bad I thought it might be a console spam issue briefly.)

[Gaz492]

I only used the FTB App as an example, you can also try the CurseForge app or Prism.
We have seen multiple users run into different issues when they used ATLauncher to run FTB packs which is why as a debugging step, I asked if the issue still happens when using a different launcher

[Wil-dTrick]

I only have the one application. I don't tend to install redundant applications. Sorry.

[MichaelHillcox]

If helping debugging this issue is not something you are willing to do, we are unable to help you. Thank you for reporting the issue, and we'll continue to debug this when someone that is willing to attempt our debugging steps reports the issue again. Many thanks.

[Wil-dTrick]

I said I'd test it out by downloading the pack as a zip and installing whatever version you'd like that way. I just don't want to be installing applications I'm unfamiliar with and using them to log into an account I have. I don't think it's unreasonable to not log into applications I haven't vetted.

Alternative to giving me a different debugging route, any information on why different launchers would have different packs given they should be using the same form structures, mod sources, etc could weigh into my decision to take the time to examine a new application.

[MichaelHillcox]

We're unable to provide support when we can not recommend reasonable debugging steps. As we have seen reports of this issue specific with ATLauncher, the only thing we can recommend is attempting to use a different launcher; if this continues to show the same issue, we can safely assume ATLauncher is not the issue.

If you are unwilling to use a different, open source, launcher (Like Prism, FTB App, etc), the only thing I can recommend is that you manually put together a modded instance inside the vanilla launcher. This is a process of seeking the correct Forge / Neoforge version, getting their installer, installing, then coping the pack's contents into the instance the installer creates for you. This is less than ideal and can be easily messed up, but this is unfortunately the only resolve I can offer you.

[Wil-dTrick]

I'm willing to consider it if there's any reason the launcher would provide different results. They're using the same basse program, mod source including (for example) forge, and file structures.

[Wil-dTrick]

I'm not entirely unwilling but it's a big ask for me go vet a new application because I do actually take the time to check what they are up to before giving them my information. So you'd have to wait. I assume that hurts you not-at-all.

[MichaelHillcox]

Please feel free to take as much time as you require. I can personally confirm that launchers like Prism are easily auditable, well-supported and truly open source, just like ATLauncher is. Please update us when you have more info 👍

[Wil-dTrick]

It happens just the same on Prism launcher. Tried latest version FTB evolution.

[MichaelHillcox]

Very interesting! Thanks for the update :D @Gaz492

[Wil-dTrick]

No problem. :)

[Wil-dTrick]

I noticed that, even though I am closing the game through 'save and quit' and 'exit' by guessing where the buttons are- My save is having weird biome issues, with discontinuity between biomes. Coastlines and other shapes are unaffected. I'm not too fussed but it is interesting.

[MichaelHillcox]

A couple more debugging steps as this sounds like it's getting stranger and stranger...

1. Could you maybe supply a short video of the biomes & a short video showing how the game is hanging? It may help track it down.
2. Could you also let us know what CPU & GPU you have, and how much ram you have allocated to the pack?
3. Could you also confirm if you have fully up-to-date graphics drivers
4. Could you try disabling shaders fully (Even if they don't look like they're on, you have to manually go to the shaders menu and click disable to fully disable them) (You can also try removing the Iris mod which will make sure shaders are not enabled)
5. Does this continue to happen even on a new world? (The game hanging?)

[Wil-dTrick]

I included a video of the error in the original post. It doesn't happen with a reliable cadence so recording it is difficult. It can happen after one minute or a couple hours. But only with this modpack.

No other game has this issue. I've played the ABOE pack just fine, No problem with Prominence II: Hasturian Era. Both are large modpacks. I play games like Control and Satisfactory on with no problems.

The CPU is a 10th gen intel i7 and it's using the IRIS graphics it came with. It's from 2019 but I don't know the number off the top of my head. I won't be at my laptop for a bit.

I'll restate some of this from the opening post since I provided most of it already...

It happens on multiple versions of that modpack (tried 1.5.0 - 1.9.0) and multiple worlds. With and without shaders. I've tried every kind of load changing settings including seeing if it still happens at minimum render and simulation distances. It seems to be unrelated to any video or performance settings.

The video driver is up to date. I have to stay on top of it since Windows keeps downgrading it because of an issue with Lenovo that causes Windows Update to downgrade the video card if it runs.

I allocate 8gb memory to Minecraft and have 20 GB total. The issue isn't caused by a memory spike. Or by heat. I tried keeping an eye on it with speedfan and there's no issue.

At this point I've cycled through multiple versions of Java and that doesn't seem to be the issue.