SevTech: Ages of the Sky

SevTech: Ages of the Sky

Modpacks
1M Downloads

Constant White Screen

ShomanOfficial opened this issue ยท 1 comments

commented

Bug Description

Hey, I have been having a white screen issue in Sevtech Ages for about a week now. It was just after I went to Jupiter in Galactacraft. Ever since, my ram usage for the game starts slowly climbing with white screens happening every so often (like every 4 minutes). I have allocated around 24gb of ram which has not fixed the issue. I also notice when I am getting the white screen lag my CPU is reaching full capacity. After 20 minutes I hit full ram usage and the pack is unplayable, I get white screened every minute. I'm addicted to the pack, and would love to keep playing so if anybody knows what's going on that would be greatly appreciated. Thanks.

PC Specs;

Processor: Intel Core i7-7700

CPU: 3.60ghz

Installed Ram: 32gb

64bit Operating System

Did this behavior use to work in the previous version?

I didn't have this problem on my previous playthrough of the modpack, I played it on the same PC.

Steps to Reproduce (for bugs)

  1. This happens constantly, at this point if I play I will eventually be forced to restart
  2. I have looked up multiple videos online to no avail
  3. I have looked up solutions online to no avail

Logs

  • Client/Server Log: They are attached
  • Crash Log: They are attached

Client Information

  • Modpack Version: 3.1.7
  • Java Version: 8 update 291
  • Launcher Used: Curse Forge Launcher
  • Memory Allocated: Around 23gb
  • Server/LAN/Single Player: Single Player
  • Optifine Installed: No
  • Shaders Enabled: No

World Information

commented

So I figured it out, I was sure that the cause was Galacticraft. So I took the Galacticraft's folder out from Sevtech's folder and loaded Sevtech up. Then a new folder should be created in your Sevtech folder. I then went into the chunkloading note and set LoadOnLogin to false, so it should say B:LoadOnLogin=false. This WILL delete your planet files so do this at your own risk, but this fixed it for me. Thanks to everyone for trying to help :), take care.