-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quick recommendation for performance (not an issue) #6
Comments
When you're playing singleplayer just stand still for a minute and wait for all the chunks to load. This already has many FPS fixes from eaglercraft. It has the GPU memory leak fix, 1.5.2's font renderer, texture mipmapping from beta 1.3, updated texture management from b1.3 and 1.5.2, the service pack fixes from 1.5.2, and some other additional optimizations like limited chunk updates, optifine's fast math and optifine's smooth entity updates. |
The main reason for the lag is because beta 1.7.3 is single-threaded while newer versions of eaglercraft use web workers for chunk loading and everything else |
Btw this newer update should get more FPS but it's a little broken atm |
the performance is sh-- on my school chromebook (2-5fps) it ran at like 40 before, with stutters. |
Might be the chunk compression I'm not sure, I'll make an option to turn it off in the next update. |
I have a new school Chromebook now, it runs a little worse than eaglercraft 1.8.8 which runs at 50-60 fps, and I'm getting 30-40 fps on your 1.7.3 beta web port. this chromebook has 4gb of ddr4 (same as my old Chromebook) and a intel n100 (idk the CPU of my old Chromebook) but I also found a bug with the textures, when I first load into a world after opening the url, the textures don't load and all I see is black. but when I go to textures and mods on the main menu and click default, then load back into my world, all the textures work. |
the game stutters pretty bad on my school but I think I would be nice to implement the lag fix used in modern eaglercraft, or add a fps limiter
The text was updated successfully, but these errors were encountered: