I've been looking for solutions everywhere, but to no avail. My Minecraft has 1 fps all of the time, and the only time it increases is after I change a setting like "Mipmap Level". When I change the aforementioned setting from 1 to 0, I get ~10 seconds of beautiful 60 fps, but it them drops back to 1 fps. Specs are as follows:
Intel Core i5-5200 CPU @ 2.20GHz
8.00 GB of RAM
Nvidia Geforce 940M
64x System, 64x based processor - Windows 10
All other games like CS:GO, Fallout 4, etc. run perfectly fine, it's just Minecraft. I've already tried to allocate more RAM in the launcher, and using a .bat, I can only install the 64-bit version of Java; If I try to install 32-bit, the program stops after "Downloading Installer". Thanks in advance!
I think there's a thread here somewhere where someone said this behavior was related to having a Windows 10 install via upgrade. Clean install didn't have the problem. You should search for that thread.
I've been looking for solutions everywhere, but to no avail. My Minecraft has 1 fps all of the time, and the only time it increases is after I change a setting like "Mipmap Level". When I change the aforementioned setting from 1 to 0, I get ~10 seconds of beautiful 60 fps, but it them drops back to 1 fps. Specs are as follows:
Intel Core i5-5200 CPU @ 2.20GHz
8.00 GB of RAM
Nvidia Geforce 940M
64x System, 64x based processor - Windows 10
All other games like CS:GO, Fallout 4, etc. run perfectly fine, it's just Minecraft. I've already tried to allocate more RAM in the launcher, and using a .bat, I can only install the 64-bit version of Java; If I try to install 32-bit, the program stops after "Downloading Installer". Thanks in advance!
Try the OPTIFINE.
Try deleting unwanted programs, processes, and games running background. I think this could help solve the issue.
Already have Optifine; The disk space and CPU are fine, nothing except skype is running.
UPDATE: Turns out the lag only affects 1.9 and MODDED 1.7.10 . Still need help.
I think there's a thread here somewhere where someone said this behavior was related to having a Windows 10 install via upgrade. Clean install didn't have the problem. You should search for that thread.