Shouldn't UseSSE autodetect the latest version your CPU supports?
Wow, y'all... and people wonder why we Windows developers hate Java so much.
Many thanks for giving me parameters I can paste into my game though!
Oh, I understand the cross-platform benefits and all. Its just that when a person has developed in .net for enough years, some of the stuff Java does seems more than a little insane. Especially when it comes to intuitive interface development.
Well, I can try it again. I know it was horrible how long it took to load when I did that before. The biggest problem is that I was actually logged in for about 30 seconds BEFORE the game came up. That means my character was on the server, frozen, until my client decided to give me control. Typically the most frustrating way this went down is that I would be out caving or wandering around at night, and get in a fight with some mobs, then the game would crash. If I logged back on, the mobs would kick my ass for 30 seconds likely killing me BEFORE I could even respond. So then, all my valuable items get spilled on the ground in the middle of nowhere and I have 5 minutes to try and recover them before they despawn. What a pain in the ass that was to go through many times. I even got in the habit of setting an alarm to go off 10 minutes after the crash so I could log back on in daytime and not get attacked when trying to load.
Hopefully it won't do that this time. Plus with the new JVM stuff I'm using the game seems MUCH more stable now. I've been playing it for hours without a single crash, and I got Sphax textures plus about 110 mods running just fine.
While ramdisk helps somewhat on client-side, I find that the effect is more pronounced on the serverside, when there is heavy io load (e.g., imagine 10 players with gravichest armors flying with boost in 10 different directions on a server running on SSD vs Ramdisk).
Wow, y'all... and people wonder why we Windows developers hate Java so much.
From my personal experience, running out of permgen space due to class loading is indeed the issue and modpacks indeed crash directly on startup. There generally are no memory leaks in stable mod versions. In fact, I can't recall a single one since switching to 1.5.x. Your mileage may vary, of course, since you might play different mods/modpacks.
Also, using JRockit doesn't improve performance because of permgen memory management, but because JRockit is significantly more responsive and lower latency in actually processing stuff.
All those options should not even have to be specified. Heck, people just add crap they found on stackoverflow to their options without even knowing what the problem is.
There are simply two reasons Java can run out of permgen space:
- The application really uses more classes than the default space can contain (unlikely)
- There is a memoryleak because some part of the software does funky classloading shit.
It's easy enough to see which of the two is the case:
- Does your application crash during startup or soon after: you don't have enough permgen space.
- Does it crash after a while: you have a memory leak.
Unfortunately FTB is just adding more and more mods without any regards of the quality of the code. With more mods, especially ones added by java amateurs, the chances of mistakes increase. And because a lot of them think "Garbage collection means I don't have to worry about disposing my crap" the chances of bugs are high.
I also find it rather funny people are messing with garbage collector options when there are memory leaks. The whole problem with memory leaks is that the memory is not being marked as 'free'. No matter how many threads you assign to the GC (4, really?), the GC will never ever touch that memory simply because it's not free.
Also trying to use JRockit instead of the default VM doesn't do anything. Just because JRockit doesn't have a separate permgen space it doesn't mean you won't get an out of memory error. It will just complain it runs out of heap space instead of permgen space.
apparently you dont know how java memory allocation works. you can't "dispose of your crap" manually in java. java doesnt allow you to allocate memory space like you must do in Cpp/# or other compiled languages, therefore there is no way to "dispose" of it. this is the SOLE PURPOSE of the GC.
using jrocket is moot. as of java7/8, jrockit and hotspot are slowly being merged into a single JVM.
Having worked as a professional Java dev for 15 years I can say I know damn well what you do and do not need to do. It's very possible to create memory leaks in Java, especially when low level stuff is involved.
I never refuted the ability to create memory leaks. i refuted that, with most things in java, you cant just dispose of what you create. once an object is created, the programer has no real control over when it gets unloaded. java does this. so if you've been a java programer for 15 years, why would you even come down on a modder (even amateur) for thinking "i don't have to dispose of my crap," when that is one of the fundamental aspects of how java works.