Baki

Myrten, could you please explain demonjaxs findings exaclty? why is there only "attack + recovery mod"? i thought our earlier tests had shown that these are different things affecting different stats.

@Myrten: no, only Reload Time and Dex affect Reload Time.

Yeah, me and him. BTW Could you put a link to the spreadsheet into your first post? somehow i cant edit the first post.

you mean you and hugin? I've done nothing in the ciphers part

OK, I did this change, formula is monstrous now gj. thanks! i think it would be better to show dps values in the big damage table. i'm more interested in dps values vs certain DRs than pure dmg values. the one cell with avg dps is just not enough :/

probably, yes. we don't know for sure yet. it might be even lower because some minor parts of the animation might not be affected by dex at all.

20 WeaponDmg vs 40 WeaponDmg 10DR 0 Dmg Mods 0 Accuracy Mods Old Way: 20 Base -> 3.5 Dmg 40 Base -> 17 Dmg Comparision 17/3.5=4.85 <- The Weapon with 40 Damage is 4.85 times better. New Way: 20 Base -> 5 Dmg 40 Base -> 18.5 Dmg Comparision 18.5/5=3.7 <- The Weapon with 40 Damage is 3.7 times better. 4.85/3.7= 1.31 -> the old calculation favors the higher weapon damage by 31% -> 31% inaccurate. thats nearly 1/3. clearly significant imo. this would get worse if we had a situation with high dmg mods and critchance.

but you use total dmg mod? what we currently do is: BaseDmg*TotalDmgMod-DR and we should do ChanceGraze*BaseDmg*TotalDmgModGraze-DR + ChanceHit*BaseDmg*TotalDmgModHit-DR + ChanceCrit*BaseDmg*TotalDmgModCrit-DR Let me do it with numbers: 10 Weapon Base Dmg, no Dmg Mod (Dmg Mod=1), No Accuracy Mod, DR 3 currently we calculate the total dmg mod first. 0.35*0.5+0.5*1=0.675 Then we calculate the Dmg: 10*0.675-3=3.75 But what we should do is: 0.35*(10*(1-0.5)-3) + 0.5*(10*(1+0)-3) = 4.2

i think we should change how we handle accuracy in the sheet lets say we have these stats: Avg base weapon damage: 10 Dmg Mod from might etc: 100% DR of the target 10 5% Miss 35% Graze 50% Hit 10% Crit then the avg dmg would be 0.35*10*(1+1-0.5)-10 +0.5*10*(1+1)-10 +0.1*10*(1+1+0.5)-10 We cant just calculate an accuracy mod of 0.685 and use that as a factor like we currently do.

im not so sure about that. but its the closest we have so far. this is so frustrating. i will never understand why devs do not reveal this stuff.

next time please come up with a theory that works for all cases before declaring it valid

Can we really be so sure that MaximKat's formula is correct? -Does not work for Attack Speed: 52/1.24=42 and not 44 as expected -Does not work for Reload Speed: 98/1.24= 79 and not 81 as expected

57.65 is too far from 60 imo. ~2.35/14=16.8% deviation Edit: oh, 74/1.24 is actually 59.68 GJ MaximCat! also, you are welcome to do the data cleanup yourself fraps and virtualdub are everything you need. Another edit: i added MaximKat's attack speed findings in the sheet. Also edited Melee Fast and Arbalest Dmg (Patch)

okay, this time with locked framerate Base AT 52 REC 74 REL 98 Only Chant (Rec x1.2, REL x2) AT 52 REC 60 -> 74*(1-0.2)=59.2 REL 51 = 98*(1-0.5)=49 Only Armor (Rec -50%) AT 52 Rec 112 -> 74*(1+0.5)=111 Rel 98 Only Dex (AT, REC, REL 24%) AT 44 -> 52*(1-0.24)=39.52 <- wrong REC 60 <- 74*(1-0.24)=56.24 <- wrong REL 81 <- 98*(1-0.24)=74.48 <- wrong Only Pen Shot (Rec -20%) AT 52 REC 89 -> 74*(1+0.2)=88.8 REL 98 ALL AT 44 -> 52*(1-0.24)=39.52 <- wrong REC 90 -> 74*(1-0.24+0.2+0.5-0.2)=93.24 <- wrong REL 43 -> 98*(1-0.5-0.24)=25.48 <- wrong, maybe multiplicative stacking? Any suggestions?

do you have the "lock frame rate while recording" option on ? because if your game runs at say 45 and you record at 30 it will be highly inaccurate so either lock it in fraps or in drivers yep EDIT: wait.. i had the videop capture settings on 30 fps but the framerate was not locked.. okay, all again :D @kmbogd: nope, ill try to figure out the ranged stuff first