I have two laptops, one a high end gaming laptop (no problems) and another running Windows 10, Intel Core i3, Intel graphics with 8GB ram (the laptop with the slowness issue).
On the core i3 laptop, the player moves like they are stuck in molasses compared to normal movement. Compared to my gaming laptop, the player walking moves at about the same speed as crouching on the high-end pc. Running on the lower end laptop is about at the speed of walking on the high-end laptop. I play with my son on LAN multiplayer and I noticed when we were both running I would easily outpace him. So I picked up his laptop and was like "Why is your player moving so slowly, even when running?"
On the core i3, I get an average of 50fps, and have all the graphics settings set to minimum resources. Head turning and everything else functions at normal speeds. No network lag (the problem exists even on single player). I did an experiment by creating two towers of blocks with 3 empty space blocks in between the towers. On my gaming laptop, I can make the jump. On the i3, I cannot make the jump, period.
I did some googling, I tried F8 and it made no difference. I tried uninstalling completely, shut down, restart, and reinstalling but the problem still persists on the core i3.
Any advice or info? We've just recently gotten into doing pvp online but whoever is using the core i3 laptop has no chance because of the slower movement compared to other players.
Bump. Still having the same issue. This problem is rendering any type of multiplayer as useless.
EDIT: I fixed the problem by COMPLETELY removing all traces of Minecraft from my PC. Meaning, I did an uninstall. Shut down. Reboot. Delete the entire .minecraft folder from appdata (which surprisingly goes untouched after the uninstall). Then manually removing all remaining traces of Minecraft from Windows. Shut down again, restart. Reinstall. Now it works as it should, and both players on both PC's walk and run at the same speed as they should. I still have no clue what was causing the problem.
Hello, newbie to the forum!
I have two laptops, one a high end gaming laptop (no problems) and another running Windows 10, Intel Core i3, Intel graphics with 8GB ram (the laptop with the slowness issue).
On the core i3 laptop, the player moves like they are stuck in molasses compared to normal movement. Compared to my gaming laptop, the player walking moves at about the same speed as crouching on the high-end pc. Running on the lower end laptop is about at the speed of walking on the high-end laptop. I play with my son on LAN multiplayer and I noticed when we were both running I would easily outpace him. So I picked up his laptop and was like "Why is your player moving so slowly, even when running?"
On the core i3, I get an average of 50fps, and have all the graphics settings set to minimum resources. Head turning and everything else functions at normal speeds. No network lag (the problem exists even on single player). I did an experiment by creating two towers of blocks with 3 empty space blocks in between the towers. On my gaming laptop, I can make the jump. On the i3, I cannot make the jump, period.
I did some googling, I tried F8 and it made no difference. I tried uninstalling completely, shut down, restart, and reinstalling but the problem still persists on the core i3.
Any advice or info? We've just recently gotten into doing pvp online but whoever is using the core i3 laptop has no chance because of the slower movement compared to other players.
Bump. Still having the same issue. This problem is rendering any type of multiplayer as useless.
EDIT: I fixed the problem by COMPLETELY removing all traces of Minecraft from my PC. Meaning, I did an uninstall. Shut down. Reboot. Delete the entire .minecraft folder from appdata (which surprisingly goes untouched after the uninstall). Then manually removing all remaining traces of Minecraft from Windows. Shut down again, restart. Reinstall. Now it works as it should, and both players on both PC's walk and run at the same speed as they should. I still have no clue what was causing the problem.