Spiral Knights - Optimizing on a Mac

Optimizing on a Mac

4 replies [Last post]

Mon, 10/24/2011 - 11:57

Speetz

I haven't found anything to help me.

i7 Proc
4 GB RAM
GeForce 330m 512 MB
Mac OSX Snow

What can I do to really get lag down, like dealing with Java etc.? Can someone just give me the basics, like making Java a priority etc. Anything. I chug when there is Fire or Spikes to the point its insane. I believe I have a model with a bad HDD but even still, when completely cooled (that's the only problem that causes is heat) the game will chug. Other's don't; I ran WoW just fine and I have great ping.

Or does the Mac client just blow? (No offense OOO)

Mon, 10/24/2011 - 14:32

Redtoymaker

mac

same here
2.53 GHz Intel Core 2 Duo
4 GB ram
NVIDIA GeForce 9400M 512 MB
Mac OS X 10.6.8

for the most part fire makes me lag makes FCS a pain
btw i run from steam if that helps

Mon, 10/24/2011 - 18:03

Starlinvf

The game clients are all

The game clients are all identical, and all work the same except for a small segment of code that talks to the drivers (those have to be native to the OS). With the release of Lion, it became pretty clear that java on the the older OSX versions doesn't behave like they should.

For non-steam users, you can try using -Xmx 512M to force a larger heap size using the system java settings (don't know the process off hand). But it does have a side effect if you use java heavy websites, since each java instance will start chewing up memory if left running too long.

Mon, 10/24/2011 - 20:29

Speetz

Anything else? Any way or

Anything else? Any way or reason anyone has figured out that Lion runs Java correctly or to simulate on Snow?

And also I am a steam user. Any info in that department? I am desperate.

Mon, 10/24/2011 - 22:19

Starlinvf

No one here understands why

No one here understands why either.... in fact, it was a pleasant surprise when someone upgraded to Lion and confirmed that all the problems with crashing in PvP (which plagued the Mac users) simply vanished. The only reasoning we have is that the Devs were doing Mac testing on an early copy of Lion, which is why it slipped past QA without a hitch. As for technical reasons.... its pretty unclear. The latest Java on Lion and Snow Leopard are both based on JRE 1.6_26, yet its a lot less buggy on Lion. It could simply had been Apple doing a full rebuild of Java for Lion... but I don't follow Mac development.

And the tips should actually work with Steam since both the standard and steam copies end up using the same Java install anyway. I'm tired, give me a break. :P

Search

Optimizing on a Mac