Direwolf20: Severe lag in Nether with version 1.6.1

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
B

Benie76

New Member
Jul 29, 2019
141
0
0
Title Direwolf20: Severe studdering in Nether with version 1.6.1

Launcher Type FTB Launcher

Modpack FTB Presents Direwolf20 (1.10)

Modpack version 1.6.1 (using 1.6.0 currently)

Have you modified the pack? No

Link to log file Not a crash, no log needed?

Details of the issue I've updated from 1.5.1 to 1.6.1 of the latest Direwolf20 pack (1.10.2). I'm using RFTools to teleport into and out of the Nether.
Soon as I got in, I was suffering from severe, unplayable studdering (usually it studders upon load in for a bit (to load in chunks) then goes away, but this was much worse). Chunks wouldn't load properly, and it was impossible to fight Blazes and Ghasts. It froze up my game three times, though thankfully it didn't take my save with it (as in corrupt it).

Downgraded to 1.6.0 (can't go back to 1.5.1 as a lot of blocks have been changed), and the severe studdering is gone. This needs to be looked at, which is why I'm filling out this report.
What I have in the Nether (that's player-placed) is a Matter Receiver(with a Capacitor Bank under it), and a RangedPump with a Ender Tank for lava. But that's what I have in 1.6.0, and they're working fine.

The latest FTBLauncher release could also be responsible for the studdering in 1.6.1, yet it's fine in 1.6.0 (didn't test it with 1.5.1, though).

Specs;
OS: Windows 7 SP1
CPU: AMD FX 4350
GPU: NVIDIA GTX 750 Ti
RAM: 16GB
 
Last edited:
B

Benie76

New Member
Jul 29, 2019
141
0
0
It's not a crash, so a log wouldn't be needed. This is a studdering issue with this version of the pack.
Please re-read the OP. Again, not a crash.
Even people have reported similar issues in here (but with the FTB Launcher) didn't post logs.
 
grandrolf

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
A log contains information about your system.

I did read your post, and I also asked for a log - I didn't say that you crashed, that's not a needed scenario for getting a log.

Most people are asked to provide a log, and even if they don't - does that matter?

You posted asking for help and I'm willing to help you out, but I need more information.

Is there any reason for not wanting to post a log?
 
You must log in or register to reply here.
Top Bottom