Search results

  • 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
  1. B

    Problem Lag on Localhost DW20 1.7

    Well, I hate to admit defeat, but I did try opening my single player game to LAN and that worked much better. I wish I understood why; but for now, this is what I'll use. Thanks for the help!
  2. B

    Problem Lag on Localhost DW20 1.7

    Well, I was skeptical but hopeful, so I tried turning off Vsync. Unfortunately, it did nothing for the input lag. Boy, is it hard to code in Computercraft with laggy inputs. I'm really surprised there can be lag when I'm connecting to a server on my local computer. Does anybody know why this...
  3. B

    Problem Lag on Localhost DW20 1.7

    Well, that's the thing. It's running on the same computer. So it doesn't even have to go through my LAN. (The other computer does have to go through the LAN, so that's probably a 100 gigabit connection or the like. It's still got <1ms ping.) So I can't figure out how it would lag at all.
  4. B

    Problem Lag on Localhost DW20 1.7

    I installed Fastcraft, and it does seem to have helped. Specifically, I no longer have massive dirt block repop when I shovel. Thanks! I'm still getting some significant lag that I notice in combat, though. I'll swing, and it won't respond for a second or two, then both I and the mob get...
  5. B

    Problem Lag on Localhost DW20 1.7

    The window reports about 600MB with 25% free, but in Task Manager it shows about 1.2GB for java.exe. No, I hadn't heard of it- maybe I'll try it. My previous computer (i.e., a generation lower performance) ran a two-player DW20 1.5 server without much incident, so I hadn't thought performance...
  6. B

    Problem Lag on Localhost DW20 1.7

    About 65%, as reported by Task Manager.
  7. B

    Problem Lag on Localhost DW20 1.7

    I'm getting very consistent lag on a server I run on my own computer. About 50% of the time you break a block, it reappears. There are only two connections: mine, on the local host (going through 127.0.0.1) and another computer on the LAN, going through 192.168.1.x. The server memory usage is...