|
|
| Author |
Thread Statistics | Show CCP posts - 5 post(s) |
|
CCP Navigator
C C P
C C P Alliance
1193
   |
Posted - 2012.04.23 13:48:00 -
[1] - Quote
EVE Online: Escalation to Inferno will be deployed on Tuesday, April 24 during an extended downtime. Downtime will begin at 12:00 UTC and is expected to be completed at 12:00 UTC.
This release paves the way for our Inferno release later in the year and includes features, fixes and changes to the user interface, titan re-balancing, rouge drones and much more.
We have a full list of patch notes available for you here and look forward to hearing your feedback.
CCP Navigator -Community Manager |
|
|
CCP Navigator
C C P
C C P Alliance
1194
|
Posted - 2012.04.23 14:05:00 -
[2] - Quote
The deployment time has been corrected.
CCP Navigator -Community Manager |
|
|
CCP Navigator
C C P
C C P Alliance
1194
|
Posted - 2012.04.23 14:34:00 -
[3] - Quote
Sarmatiko wrote:From patchnotes: Quote:NPC's will always aggress you when you warp into their aggression range. It is unclear how this aggression change works exactly. Does it means there will be full aggro in Worlds Collide last pocket (because you probably warp in ship aggression radius) and similar missions? Clarification needed 
This is in relation to some sites that would prevent NPC aggression if you kept warping in and out. It will not affect Worlds Collide or any other misis9ons which have natural aggression.
This is just a simple bug fix.
CCP Navigator -Community Manager |
|
|
CCP Greyscale
C C P
C C P Alliance
1224
|
Posted - 2012.04.23 16:18:00 -
[4] - Quote
Warrior Xena wrote:This is unclear :
GÇóXL turrets have had their signature resolution set to 2000m.
GÇóCapital Turrets that are fitted to titans now have a new damage-scaling attribute; targets with a signature radius smaller than this size will take reduced damage from these turrets. This does not apply to dreadnaughts.
Right now, dreadnoughts have XL turrets, and those turrets already have a damage-scaling attribute, everything with a sig radius under 1000m ( their current sig resolution ) taking a reduced damage.
Bottom line, will this modification affect the turrets fitted on dreadnoughts or not ?
Sig resolution doesn't affect damage, it only affects tracking. The sig resolution changes will affect dreadnaughts (but there's no difference in siege because of the tracking penalty removal); the damage scaling won't. |
|
|
CCP Greyscale
C C P
C C P Alliance
1225
|
Posted - 2012.04.23 17:25:00 -
[5] - Quote
Teibor wrote:still needs clarification on drone alloys that have already dropped and are in hangars etc.
- after DT, will these still appear in hangars if there already before DT?
- will these still repro into the relevent minerals?
edit: seems it mght be in a blog, off for a look.
Nothing's being done to the alloys, they just won't be dropping any more. We're not deleting anything.
Warrior Xena wrote:CCP Greyscale wrote:Sig resolution doesn't affect damage, it only affects tracking. The sig resolution changes will affect dreadnaughts (but there's no difference in siege because of the tracking penalty removal); the damage scaling won't. Actually, according to this formula, it is an independent parameter http://wiki.eve-id.net/Trackinghttp://wiki.eveonline.com/en/wiki/Turret_damage""Turret Signature Resolution" is a number qualifying the originally intended target size (in meters) of your gun turret. The smaller the number, the better your chance to hit will be. " So how is this formula transformed for siege mode ? Hand-on testing : trying to hit with a dread ( naglfar ) a battleship ( apoc ) orbiting at 20km . After boosting and using the right ammo, the tracking speed of dread's turrets is 0.0063806 rad/sec, while the overview window shows only 0.0058207 rad/sec ( LOWER ) for the target battleship. The optimal range is 56.247 km and accuracy falloff 133.52 km. Out of over 50 shots, NOT EVEN ONE landed on target - all missed. And this before the patch. Obviously the perfect tracking speed boost is nothing to compensate for the signature radius versus signature resolution parameter. And this before the patch.
The sig/sig ratio is multiplied by the transversal/tracking*range ratio. Halving the tracking doubles the size of the second ratio, and doubling the size of the second ratio is the same as doubling the size of the first ratio. Halving tracking speed is the same as doubling sig resolution. Honestly it's completely redundant mathematically to have both terms as they're both static authored values that have the same mechanical effect, but there are benefits for the "readability" of the balance work to having both. |
|
|
|
| |
|