These video's just keep getting better.
Wednesday, April 22, 2009
Friday, March 27, 2009
EVE Racial DPS: Tier 1 Battleships
There are endless discussions all over the web about which race in EVE is the best for PVP. These discussions are invariably colored with people's individual tastes and dislikes. I'll not delve into dark discussions of tactics and corner-case weaknesses or strengths of the given races, but I would like to provide some much needed factual information on the topic.
I've run various ships through EFT to try to put solid numbers on the actual DPS of a variety of ships. I'll be the first to admit that there's more to combat in EVE than raw damage output and the ability to absorb raw damage output but let's be honest. If you can't put out damage at least similar to your opponent you will almost never win a 1 vs 1.
There's a lot of ground to cover here so I'll make this post focus specifically on the DPS of tier 1 battleships. I'll profile the DPS of each of these ships using the following criteria:
- EFT 2.9.1 will be used
-All fitting and final numbers will be based on the default "All Level V" character in EFT thereby removing pilot skill from the equation.
-All dps will be based on the biggest/best tech 2 guns/launchers, tech 2 ammo (high dmg, not range), tech 2 drones (all gallente), tech 2 everything
-No rigs will be used
-No fleet bonuses will be considered
-If weapon upgrades are used, they will be used equally. Notes will be made in any situations where the use of these rigs is not feasibly sustainable.
-Fittings will only be as specific as they need to be. e.g. I'll usually put an armor repper on armor tanking boats to verify that the ship has the powergrid to sustain both the repper and the guns I'm fitting but I will leave all slots empty that don't affect DPS directly (rate of fire bonus, dmg bonus) or indirectly (powergrid/CPU shortage) . I will not bother telling you that the ship has a repper fitted as this does not affect the DPS.
So, off we go...
Tier 1 Battleships
Amarr: Armageddon:
7x Mega Pulse II (conflag ammo)
5x Ogre II's
DPS: 842
Caldari: Scorpion
4x Siege Missile Launcher II (mjolnir rage)
2x Neutron Blaster II (void)
5x Hammerhead II (cannot fit 5 large drones)
DPS: 609
Gallente: Dominix
3x Ion Blaster II (void ammo)
3x Electron Blaster II (void ammo)
5x Ogre II's
DPS: 921
Minmatar: Typhoon
4x Siege Missile Launcher II (mjolnir rage torp)
4x 800mm repeating artillery II (hail)
5x Ogre II
DPS: 1012
I've run various ships through EFT to try to put solid numbers on the actual DPS of a variety of ships. I'll be the first to admit that there's more to combat in EVE than raw damage output and the ability to absorb raw damage output but let's be honest. If you can't put out damage at least similar to your opponent you will almost never win a 1 vs 1.
There's a lot of ground to cover here so I'll make this post focus specifically on the DPS of tier 1 battleships. I'll profile the DPS of each of these ships using the following criteria:
- EFT 2.9.1 will be used
-All fitting and final numbers will be based on the default "All Level V" character in EFT thereby removing pilot skill from the equation.
-All dps will be based on the biggest/best tech 2 guns/launchers, tech 2 ammo (high dmg, not range), tech 2 drones (all gallente), tech 2 everything
-No rigs will be used
-No fleet bonuses will be considered
-If weapon upgrades are used, they will be used equally. Notes will be made in any situations where the use of these rigs is not feasibly sustainable.
-Fittings will only be as specific as they need to be. e.g. I'll usually put an armor repper on armor tanking boats to verify that the ship has the powergrid to sustain both the repper and the guns I'm fitting but I will leave all slots empty that don't affect DPS directly (rate of fire bonus, dmg bonus) or indirectly (powergrid/CPU shortage) . I will not bother telling you that the ship has a repper fitted as this does not affect the DPS.
So, off we go...
Tier 1 Battleships
Amarr: Armageddon:
7x Mega Pulse II (conflag ammo)
5x Ogre II's
DPS: 842
Caldari: Scorpion
4x Siege Missile Launcher II (mjolnir rage)
2x Neutron Blaster II (void)
5x Hammerhead II (cannot fit 5 large drones)
DPS: 609
Gallente: Dominix
3x Ion Blaster II (void ammo)
3x Electron Blaster II (void ammo)
5x Ogre II's
DPS: 921
Minmatar: Typhoon
4x Siege Missile Launcher II (mjolnir rage torp)
4x 800mm repeating artillery II (hail)
5x Ogre II
DPS: 1012
Saturday, February 28, 2009
EVE Wine Linux two clients
Ok, so CCP has decided to discontinue support of the Linux EVE client.
Here's how to run EVE on a dual monitor setup using wine.
First, get the latest version of wine.
If you're using Ubuntu/Mint, you can just add this line to your /etc/apt/sources.list file:
deb http://wine.budgetdedicated.com/apt hardy main
Add this key: http://wine.budgetdedicated.com/apt/Scott%20Ritchie.gpg
To your apt keyring by saving the file to disk and then:
sudo apt-key add /path/to/the/key.gpg
And then:
sudo apt-get update
sudo apt-get install wine
If you're not a debian derivative user, just get the source.
You're looking for wine version 1.1.15 (or later)
Verify you have the right version:
wine --version
Download the premium EVE windows client here: http://www.eveonline.com/download/windows.asp
And install:
wine /path/to/file/EVE_Premium_Setup_75883.exe
Fix the ever present font issues by obtaining the mstcorefonts pkg:
sudo apt-get install mstcorefonts
Copy the arial.ttf file into your wine installation:
cp /usr/share/fonts/truetype/msttcorefonts/arial.ttf ~/.wine/drive_c/windows/Fonts/
That path may be linuxmint-centric. Doesn't really matter. You can even download this file from most any windows installation. Point is, the EULA won't display properly if this file isn't in the location listed above, and if you can't click thru the EULA, you can't play
At this point, a single client should be working perfectly. Two clients, not so much.
Two get that second client working, create a second copy of your .wine directory. I prefer to do this:
mv .wine .wine1
cp -ra .wine1 .wine2
So what was the point of that, right? Now you have wasted twice as much space as you need to storing ever file twice. Answer: Whatever CCP says in their docs, they are not storing session, or client, or some sort of data properly and you will get file collisions if you try to run two clients out of the same file tree. I've messed with two client setups extensively in Cedega and Wine and the common thread, regardless of emulation engine, is that you're going to save yourself some major headaches by just running them out of their own source directories. The problem is with the EVE client, not wWne.
Now all that's left to do is to create yourself two snazzy launch icons or scripts that run these commands:
env WINEPREFIX="/home/username/.wine1" wine "C:\Program Files\CCP\EVE\eve.exe"
env WINEPREFIX="/home/username/.wine2" wine "C:\Program Files\CCP\EVE\eve.exe"
And you should be set.
Some additional notes:
I originally messed around a bit with having wine emulate a virtual desktop. This seemed to help with the focus change crash issues, but now that I'm running two separate .wine* directories that problem seems to have gone away. If you still experience the focus change crash, open up the wine configuration dialog by running winecfg and turn on this virtual desktop emulation. BE CAREFUL, the focus change crash sounds like its a sound issue because you'll hear a sound hiccup and then your screen will freeze. It's not sound, trust me.
Also, most linux desktops are running ALSA and/or pulseaudio nowadays. You should ensure that your wine install is set to output sound to the ALSA subsystem. Again you'll want to use winecfg to set this.
EDIT:
Wine 1.1.15 == EVIL!!!!
Or at least it's evil with two clients.
Lost a Hac yesterday due to the frequent freezing.
Rolled back to 1.0.0 and it has been solid since then.
1.1.16 was just released.
Release notes mention addressing some freezing issues, but since I don't know the cause of the freezing I was seeing, it's hard to know if the 1.1.16 release addresses this issue or not.
FINAL EDIT:
Ok, after much pain and suffering I finally found this thread:
http://bugs.winehq.org/show_bug.cgi?id=17437
I ended up having to upgrade to wine 1.1.16 via src patched using the patches included in the winehq thread above. GL.
Here's how to run EVE on a dual monitor setup using wine.
First, get the latest version of wine.
If you're using Ubuntu/Mint, you can just add this line to your /etc/apt/sources.list file:
deb http://wine.budgetdedicated.com/apt hardy main
Add this key: http://wine.budgetdedicated.com/apt/Scott%20Ritchie.gpg
To your apt keyring by saving the file to disk and then:
sudo apt-key add /path/to/the/key.gpg
And then:
sudo apt-get update
sudo apt-get install wine
If you're not a debian derivative user, just get the source.
You're looking for wine version 1.1.15 (or later)
Verify you have the right version:
wine --version
Download the premium EVE windows client here: http://www.eveonline.com/download/windows.asp
And install:
wine /path/to/file/EVE_Premium_Setup_75883.exe
Fix the ever present font issues by obtaining the mstcorefonts pkg:
sudo apt-get install mstcorefonts
Copy the arial.ttf file into your wine installation:
cp /usr/share/fonts/truetype/msttcorefonts/arial.ttf ~/.wine/drive_c/windows/Fonts/
That path may be linuxmint-centric. Doesn't really matter. You can even download this file from most any windows installation. Point is, the EULA won't display properly if this file isn't in the location listed above, and if you can't click thru the EULA, you can't play
At this point, a single client should be working perfectly. Two clients, not so much.
Two get that second client working, create a second copy of your .wine directory. I prefer to do this:
mv .wine .wine1
cp -ra .wine1 .wine2
So what was the point of that, right? Now you have wasted twice as much space as you need to storing ever file twice. Answer: Whatever CCP says in their docs, they are not storing session, or client, or some sort of data properly and you will get file collisions if you try to run two clients out of the same file tree. I've messed with two client setups extensively in Cedega and Wine and the common thread, regardless of emulation engine, is that you're going to save yourself some major headaches by just running them out of their own source directories. The problem is with the EVE client, not wWne.
Now all that's left to do is to create yourself two snazzy launch icons or scripts that run these commands:
env WINEPREFIX="/home/username/.wine1" wine "C:\Program Files\CCP\EVE\eve.exe"
env WINEPREFIX="/home/username/.wine2" wine "C:\Program Files\CCP\EVE\eve.exe"
And you should be set.
Some additional notes:
I originally messed around a bit with having wine emulate a virtual desktop. This seemed to help with the focus change crash issues, but now that I'm running two separate .wine* directories that problem seems to have gone away. If you still experience the focus change crash, open up the wine configuration dialog by running winecfg and turn on this virtual desktop emulation. BE CAREFUL, the focus change crash sounds like its a sound issue because you'll hear a sound hiccup and then your screen will freeze. It's not sound, trust me.
Also, most linux desktops are running ALSA and/or pulseaudio nowadays. You should ensure that your wine install is set to output sound to the ALSA subsystem. Again you'll want to use winecfg to set this.
EDIT:
Wine 1.1.15 == EVIL!!!!
Or at least it's evil with two clients.
Lost a Hac yesterday due to the frequent freezing.
Rolled back to 1.0.0 and it has been solid since then.
1.1.16 was just released.
Release notes mention addressing some freezing issues, but since I don't know the cause of the freezing I was seeing, it's hard to know if the 1.1.16 release addresses this issue or not.
FINAL EDIT:
Ok, after much pain and suffering I finally found this thread:
http://bugs.winehq.org/show_bug.cgi?id=17437
I ended up having to upgrade to wine 1.1.16 via src patched using the patches included in the winehq thread above. GL.
Tuesday, February 24, 2009
apocrypha teaser
http://www.eveonline.com/apocrypha/index.html
Be sure to click the features after you've viewed the trailer.
worm holes.
nummy.
Be sure to click the features after you've viewed the trailer.
worm holes.
nummy.
Thursday, February 19, 2009
The suck
In the interest of fairness, and the off chance that someone from CCP might actually tune into this blog, here are some of the issues with EVE that bug me.
1. 1850, meet the future:
I can't transmit coordinates and it makes me want to end myself. Short story of EVE is that every point in a solar system exists on an x/y/x coordinate plane/grid. If you set a book mark at any place in space, you can actually pull that bookmark open and see those x/y/z values. Which is cool. What you can't do is you can't transmit this information to anyone else. This means that if you want to get another person to a place you have found and bookmarked, you have two options. You can
1. Form a fleet with them, fly to the location yourself and have them warp to you. Or 2. you can fly to that location, set a bookmark, (and this is where it gets really odd) you can pull that coordinate physically out of your bookmark window and it becomes an object that you can store in your cargo hold. You can then actually trade it over to someone else and they can put it into their bookmark folder. If that's not 1850 I don't know what is.
Basically it amounts to writing the location down on a piece of paper, docking up to another ship or meeting in station and handing the location off. DUMB.
But wait, you're probably thinking "Hey didn't you say you could see the x/y/z coords? Why not just tell someone what the coordiates are and let them use those to get to the location?" First I salute you for thinking this. It's a reasonable thought and very definitely should work. The only reason it doesn't work is that CCP has not provided any way to travel to a given coordinate. Meaning that there's no way for me to type a coordinate in and say "warp to". Just doesn't exist. Again I say: DUMB.
To be fair, I think I know why they do this. It makes it a lot harder for a turn-coat to disclose the location of her/his fleet to enemies in a game that doesn't allow for coordinate transmission. But I still say they should have done it. There's already so many ways a turn-coat can hut you (please see the BoB is no more post). What's the point in removing this one method for treachery when the existing of coordinate transmission would ease so many other aspects of the game. e.g. "Hey guys I just set up a new production tower in system blah-blah-blah. Here let me transmit the coordinates to it to you so you don't have to plan a special time to fly out there with me and/or so I don't have to create 15 bookmarks and hand them all out to you individually."
Enough for now.
I shall rant further later.
1. 1850, meet the future:
I can't transmit coordinates and it makes me want to end myself. Short story of EVE is that every point in a solar system exists on an x/y/x coordinate plane/grid. If you set a book mark at any place in space, you can actually pull that bookmark open and see those x/y/z values. Which is cool. What you can't do is you can't transmit this information to anyone else. This means that if you want to get another person to a place you have found and bookmarked, you have two options. You can
1. Form a fleet with them, fly to the location yourself and have them warp to you. Or 2. you can fly to that location, set a bookmark, (and this is where it gets really odd) you can pull that coordinate physically out of your bookmark window and it becomes an object that you can store in your cargo hold. You can then actually trade it over to someone else and they can put it into their bookmark folder. If that's not 1850 I don't know what is.
Basically it amounts to writing the location down on a piece of paper, docking up to another ship or meeting in station and handing the location off. DUMB.
But wait, you're probably thinking "Hey didn't you say you could see the x/y/z coords? Why not just tell someone what the coordiates are and let them use those to get to the location?" First I salute you for thinking this. It's a reasonable thought and very definitely should work. The only reason it doesn't work is that CCP has not provided any way to travel to a given coordinate. Meaning that there's no way for me to type a coordinate in and say "warp to". Just doesn't exist. Again I say: DUMB.
To be fair, I think I know why they do this. It makes it a lot harder for a turn-coat to disclose the location of her/his fleet to enemies in a game that doesn't allow for coordinate transmission. But I still say they should have done it. There's already so many ways a turn-coat can hut you (please see the BoB is no more post). What's the point in removing this one method for treachery when the existing of coordinate transmission would ease so many other aspects of the game. e.g. "Hey guys I just set up a new production tower in system blah-blah-blah. Here let me transmit the coordinates to it to you so you don't have to plan a special time to fly out there with me and/or so I don't have to create 15 bookmarks and hand them all out to you individually."
Enough for now.
I shall rant further later.
Sunday, February 15, 2009
Alliance Tournament VI finals
Watch it.
Just.....watch it.
There's nothing else out there remotely close to this level of cool.
Just.....watch it.
There's nothing else out there remotely close to this level of cool.
Subscribe to:
Posts (Atom)