| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Apple Boy
Gallente Dirty Deeds Corp. Axiom Empire
|
Posted - 2008.09.19 19:23:00 -
[1]
just had my first 400+ local fleet battle and from what I can gather the mac client doesn't handle fleet battles the way the windows client does. Whenever I warped onto grid I loaded everything almost immediately (awesome) and when I hit approach or mwd it would activate and approach instantly, and if I activated guns they would fire one round and say they missed and then it would just sit there.
It seems that the mac client sends the commands to the server, executes them client side, and then waits for the server to catch up. It also doesn't update overview with what's currently going on. I would see ships explode, wrecks and pods in space, but overview would still show the ship there and say invulnerable if I tried to lock them.
Has anyone else used the mac client in a fleet battle lately? if so, how did your system handle the usual lag?
|

Real Poison
Minmatar Stormlord Battleforce Vanguard.
|
Posted - 2008.09.20 07:37:00 -
[2]
Edited by: Real Poison on 20/09/2008 07:38:39 been a while since i've been in a really large battle but the last times my mac client was always way ahead of everyone else.
do you remember that large dread battle together with cva, paxton, vanguard, iac and some more?
i was in the support fleet trying to get there. while slowly going through the totally lagged out systems i always jumped and ended up on the next gate 5 minutes before anyone else, some poor windows users ;) even had to wait 10-15 minutes until they loaded grid while i already killed the gate rats at the next gate.
so yes, the mac client seems to handle lags and large fleets alot better :)
maybe it's just the ram that is handled better by OSX compared to XP which wouldn't even fully utilize the 4gigs i have.
|

Good Things
Basement Innovations
|
Posted - 2008.09.20 09:38:00 -
[3]
I would have to say that I also noticed that the Mac client does handle fleet battles a tad better. I wouldn't say that for my MacBook Air but on an iMac it runs pretty good.
|

Apple Boy
Gallente Dirty Deeds Corp. Axiom Empire
|
Posted - 2008.09.20 13:41:00 -
[4]
I do agree some of the ways the mac client works in lag is awesome (If I hit warp, I actually warped almost instantly, and would load grid within 20 seconds of landing) but trying to activate modules didn't seem to work right. It would activate them client side so you think they were running even if it hadn't gotten confirmation from the server that the module was activated.
Example, I was approaching a wreck, had hit the mwd, and was rapidly approaching it from 60km, but once I got there it kept saying I was too far away from the wreck when I tried to open it without telling me how far away I really was from the wreck. Just had to wait 
|

Nate D
Caldari Provisions
|
Posted - 2008.09.22 17:40:00 -
[5]
Edited by: Nate D on 22/09/2008 17:44:28
Originally by: Apple Boy It seems that the mac client sends the commands to the server, executes them client side, and then waits for the server to catch up.
Nope, the Mac client is the same client that's running on windows. It is repackaged in a Cedar bundle and compiled to run on Mac. The windows client is a dumb client meaning that all commands are executed on the server.
Edit: I actually think this "realization" that the Mac client, in some way, handles fleet battles better is really all in your head. I just find it hard to believe that the same client that windows users run natively can be emulated to run faster or handle lag better on a Mac. The ONLY way I see this as a possibility is if CCP chose to cut some corners after the initial client was found to be a bit too slow. Though I'm sure this is not the case.
|

Juliette Leblanc
Gallente Federal Navy Academy
|
Posted - 2008.09.22 20:46:00 -
[6]
Originally by: Nate D I just find it hard to believe that the same client that windows users run natively can be emulated to run faster or handle lag better on a Mac.
Cider is not an hardware emulator. It's a simplified implementation of the Windows APIs that maps onto the Mac/Linux native APIs.
I do not know the specifics of the EvE client, therefore I have no idea what exactly is better and what is worse when run under Cider with respect to the native environment. But I know there may be a lot of things that can be worse as well as a lot of things that can be better. I have seen many windows executables that are actually much more performing when run under Linux (with WINE and other layers that are similar to Cedega). Specifically for Mac I expect any Direct-X specific routines to be slower, some video driver related routines to be slower. All the rest may be slower or faster. Network access, disk and cache access, execution of the graphics shaders, task switching, memory allocation/deallocation and many other common stuff may well be much faster than in the native case.
|

Soldara
The Graduates Morsus Mihi
|
Posted - 2008.09.22 21:57:00 -
[7]
I've been in a number of large fleet battles over the past 7 months... including a 400 man POS bash in 15W over the weekend. from what I can tell the Mac client handles lag the same as the Windows client... badly. 
|

Captain Ziltoid
|
Posted - 2008.09.24 15:11:00 -
[8]
Originally by: Nate D Edited by: Nate D on 22/09/2008 17:44:28
Originally by: Apple Boy It seems that the mac client sends the commands to the server, executes them client side, and then waits for the server to catch up.
Nope, the Mac client is the same client that's running on windows. It is repackaged in a Cedar bundle and compiled to run on Mac. The windows client is a dumb client meaning that all commands are executed on the server.
Edit: I actually think this "realization" that the Mac client, in some way, handles fleet battles better is really all in your head. I just find it hard to believe that the same client that windows users run natively can be emulated to run faster or handle lag better on a Mac. The ONLY way I see this as a possibility is if CCP chose to cut some corners after the initial client was found to be a bit too slow. Though I'm sure this is not the case.
Tell that to my Linux partition that runs Neverwinter Nights not only faster, but with the correct textures. My frame rates are at least double that of my Windows install.
However, I relate that more to nVidia and its drivers and NWN being a more outdated game.
And yes, I use Mac, Windows, and Linux. I want it all.
|

Fayne Victormas
|
Posted - 2008.10.01 01:39:00 -
[9]
The network stack in OSX and most other UNIXs is better than the one in Windows. Lower latency and much less overhead to the overall OS. The crossover API is written to be Windows compatible on the application side (eve), but uses the native network stack (OSX).
I find this to be the case for many programs that share ports across windows and osx.
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |