EVE General Discussion

There's a 64 bit client?

Not really an issue with the transfer speed I have on the secondary drive 6.0Gb/s.

64bit client would have the only advantage that it could use more than 4gb ram.
However since the eve client only use about 1gb ram, there is no point to move it to 64bit version.


>Just running into irregular dips in FPS using a 32 Bit client and 4 accounts simultaneously @ max graphics.
Upgrade your graphics card, or reduce the graphics detail level.

They have a moblie section now don't they?
I think making eve playable on smartphones is pretty this decade-dy.

I have no problem with 4 accounts on this computer which is about 3/4 years old and has 4 gigs of ram...but have a 480 GT but have 3 of the accounts turned down.

I could run 3 more accounts on my 3 old PC's if they hadn't done that ****. Still raging.

Use isboxer. It will allow you to resize the windows onto 1 screen, plus dedicate each client to its own core. I run 12 clients w/ 8 gigs ram, ati 4870 capped at 30 fps each client, 1920x1080 resolution on a q9550 cpu. Set for performance graphic settings. It can still lag in ice fields with like 50+ other ships.

Using isboxer you can have the active client set to 30-60 fps, and background clients set to 15-30 fps giving you more flexibility.

If you want each client to use more memory, enable resource cache.

64-bit won't help you. All 64-bit does is allow windows to use a much larger virtual memory space, above the 3 gig barrier. The client uses only about a gigabyte, and half of that tends to be cache memory (as far as I understand). It uses less memory the more clients you run, about half for each client because windows stops assigning memory as cache.

I would set the interval to immediate. This will disable vsync and use the full power of your card instead of capping your fps at 60 which I assume is your monitor refresh rate.

If you are using max graphics even with intveral one, your going beyond your graphic card limitations. Anti-aliasing, HDR, Shaders, and Shadows are big performance hitters.

I7 has between 2 and 6 cores, if it's less than 4, then your running into a cpu bottleneck.

Install Process Lasso and set exefile as game or multimedia process. It will automatically lower process priority of process's that may effect system responsiveness. It's great.

Use gpu-Z to monitor your gpu load. If you see variable fps and your gpu load is 98%+ your video card is the bottleneck and you have no choice but to lower your settings.

I use windows 8. Not only does windows startup in about 15 seconds as oppossed to 1-2 minutes on windows 7, its actually better at responsiveness. It may take some time adjusting because things are done a bit differently. I dual boot it on a laptop w/ 5 gigs of ram and a single core amd v120 2.2ghz. It came preloaded w/ 7 and I had to get a license key from the win7 registry. All I can say is it was a painful experience. Some hate and resist change though.

Also your disk can effect your fps if it's 100% utilized. Superfetch has been notorious for this for several windows versions. Kills my FPS when it decides to do its thing. Turn it off.

Use LatencyMon to check DPC latency. If your processor lowers its clock/memory speeds automatically, it will affect system responsiveness. It's called EIST or Speedstep in the bios. Bad USB, WiFi, Audio, and Video Card Drivers can induce System Lag thereby effecting FPS. Infact Malwarebytes Website Blocking feature actually causes latency problems too, which is the only software that I know of causes DPC latency problems.

The EVE client has also been basically patched for 10 years and is based on stackless python code. Python is an interpreter as opposed to a compiler. A compiler converts the source code into machine code only once. An Interpreter does it everytime its run, which makes it slower. But development speed is greater which is why it is used.

Hope this helps.

-Sabotaged
http://oi44.tinypic.com/2m5xqq0.jpg

also more registers and an extended instruction set.

Not quite - the 3GB limit came from the physical 4GB addressing limitation of the IA32, basically you had to fit the peripheral memory map under 4GB or pretty much every driver on the planet failed.

The /PAE switch was used to address memory above 4GB, and the /3GB switch was used to increase addressable space per process.

Frankly IME enabling /PAE was a last resort as it had all sorts of horrible side effects on other 32 bit programs.

My point is that the whole “32bit = can't use more than 4GB” was never really true other than from a licensing standpoint. It was just that the consumer versions of Win2k and WinXP were limited that way by design, and if you picked a different license, you could make use of (a lot) more.

Of course, as always, many windows programmers never took the time to learn their environment properly and therefore wrote software that broke horribly when it encounter anything other than a default environment (eg. crashes when not running administrator, crashes when not allowed to write to c:\, crashes when not allowed to write to “all users”, crashes when encountering any kind of permission flags… or UAE, and un-neighbourly behaviour in an above-4GB system).