I use these JVM arguments:Gg found my new favorite texture pack, Faithful 32x32 Is my absolute new favorite texturepack. I don't know why I didn't try this out sooner =\
Edit: Something that I am confused on, I get better FPS with 32x32 than with 16x16, can anyone explain at all or?
Also something that could help with FPS even more is maybe some JVM arguements, anyone got any?
System Specs: 2 GTX 580 classifieds 16 gb of ram and this processor:
I use these JVM arguments:
http://forum.feed-the-beast.com/thr...ava-arguments-been-updated.48285/#post-709599
I dont personally see much fps improvement with them, but that could be because I am playing beyond the point of "system grinding into a halt due to massive density of tech built". Might help on memory garbage collection etc. or something.
Another thing that I tend to do and I seem to notice a bit of an effect from, is setting Affinity for the javaw.exe. Running an quadcore i7 with hyperthreading (like you do I think) and since MC don't have multicore support I think you would benefit from only allowing the java process to use the "true" cores(not the hyperthreading threads. You only gain from deviding a core up into 2 threads if the process supports multithreading). So I go to the taskmanager and set Affinity of the main javaw.exe to cpu 0,2,4,6 only. Seems to stabilize fps a bit and remove some spikes.
NO DON'T DO THAT. Never realtime. Never.Oh my god. I totally forgot about doing that. I used to do that and well... I'm an idiot
If I do that now it will definitely help, I shall also set its priority to realtime as that should help too.
Dont set it to real time, that will be cause some pretty bad things I think. Set it to high if you want to.Oh my god. I totally forgot about doing that. I used to do that and well... I'm an idiot
If I do that now it will definitely help, I shall also set its priority to realtime as that should help too.
From what I remember from my Regulation and Control courses, real time computing is something you use when your processes are time sensitive. For example if you want to do measurements on something happening and log it depending on when it happens. Now if you just run this as a normal process you cant be guaranteed that your "measure data and log them" actually occurs at the right moment due to the processor might already being tied up doing something else(checking for updates for flash, looking for virus etc). By setting a process to real time, you are basically tell the processor to only run this process and let nothing else interfere.Are you sure? I set it to real time and it seemed to stop most spikes in framerate when loading chunks and I have seen no negative effects. Everything is acting as it should
Lolnope never mind it just crashed. Never go real time again