20 replies to this topic

[Bishop Steiner]

just dropped in my HBK-4G(F) and was moving like in frozen molasses.

Dropped back to mechlab, checked accel... my Crab showed 29 kph/s accel... my Hunchback? 0.29 kph/s. Kanajashi reports the same in his RVN-3L(C) .36 kph/s

My JR7-F(F) 0.29 kph/s, CPLT-C1(F) 0.2 kph/s and my AS7-D(F) is 0.12 kph/s

I think we missed a few decimals.

*JR-IIC(O), CDA-X5, VND-SIB, CTF-3L(L), BLR-2C, GRH-5H(C) are also off by 2 decimal spaces

Edited by Bishop Steiner, 01 March 2017 - 11:14 PM.

[SnafuSnafu]

Bishop Steiner, on 01 March 2017 - 10:51 PM, said:

just dropped in my HBK-4G(F) and was moving like in frozen molasses.

Dropped back to mechlab, checked accel... my Crab showed 29 kph/s accel... my Hunchback? .29 kph/s. Kanajashi reports the same in his RVN-3L(C) .36 kph/s

My JR7-F(F) .29 kph/s, CPLT-C1(F) .2 kph/s and my AS7-D(F) is .12 kph/s

I think we missed a few decimals.

JR-IIC(O), CDA-X5, VND-SIB, CTF-3L(L), are also off by 2 decimal spaces

Yes there are bugged values, BLR-2C is also one of them

[Bishop Steiner]

SnafuSnafu, on 01 March 2017 - 10:54 PM, said:

Yes there are bugged values, BLR-2C is also one of them

if you find any more, feel free to add them, those were just the ones on my IS account I had. Checking my clan acct now.

[Mcgral18]

Bishop Steiner, on 01 March 2017 - 10:51 PM, said:

just dropped in my HBK-4G(F) and was moving like in frozen molasses.

Dropped back to mechlab, checked accel... my Crab showed 29 kph/s accel... my Hunchback? .29 kph/s. Kanajashi reports the same in his RVN-3L(C) .36 kph/s

My JR7-F(F) .29 kph/s, CPLT-C1(F) .2 kph/s and my AS7-D(F) is .12 kph/s

I think we missed a few decimals.

JR-IIC(O), CDA-X5, VND-SIB, CTF-3L(L), are also off by 2 decimal spaces

QUESTION:


Do you actually see decimal values in the Mechlab? Or just the graph?
They're not terribly friendly to read.


Can confirm, some have their live values, and without modifiers (presumably from the engine) they be SLOW


Others (like the Viper) are just naturally slow...which is upsetting.


And photo evidence, because why not


If its posted many times, it will be seen eventually

Edited by Mcgral18, 01 March 2017 - 11:00 PM.

[Bishop Steiner]

Mcgral18, on 01 March 2017 - 11:00 PM, said:

QUESTION:


Do you actually see decimal values in the Mechlab? Or just the graph?
They're not terribly friendly to read.


Can confirm, some have their live values, and without modifiers (presumably from the engine) they be SLOW


Others (like the Viper) are just naturally slow...which is upsetting.


And photo evidence, because why not


If its posted many times, it will be seen eventually

Here ya go, screenies of the BLR-2C and the BLR-2C(C)




Now call me crazy...but one is 20.02kph/s ...the other? 0.19 kph/s

[Mcgral18]

Oh, you HOVER over
That's much easier to read

Yeah, it's a fairly common issue, actually
Onion currently has the wrong quirks (2C, O variant)
Catapult for the longest time had one variant with a missing module slots, IIRC
1500% weapon cooldowns


All you can do is report them, which is good.

[Wintersdark]

oh hilarious, that's just awesome. Patching now; had no internets last night because Reasons.

Gotta love some mechs having 1/100th the acceleration of others of the same weight class!

[GrimRiver]

Same for Sparky.

+1KPH per every 20 seconds.

Sssssssllllllllllloooooooooooowwwwwwwwwwwwww.

:'(

[AngrySpartan]

That is why you do not test Skill tree together with some other major gamechanging mechanics, like...let me think of one...(surprise!!!) decoupling engines from mibility!

[Amsro]

AngrySpartan, on 02 March 2017 - 08:54 AM, said:

That is why you do not test Skill tree together with some other major gamechanging mechanics, like...let me think of one...(surprise!!!) decoupling engines from mibility!

Its an honest mistake to miss a few decimal places on a dozen or so mechs.

We are testing it. On the test server.

[Katpocalypse Meow]

The accel/decel values in the skill tree also appear to be broken. It's especially bad with decel where even with max Hard Brake it takes significantly longer to stop then the same mech does on live WITHOUT hard brake. Might be tied to broken values in the mechs themselves like you mentioned with the engine decoupling or the skill tree values are being applied wrong, i.e Hard Braking values are inverted and decreasing decel instead of increasing decel.

Edited by Katpocalypse Meow, 02 March 2017 - 09:08 AM.

[YourSaviorLegion]

Atlas AS7-D is broken too, it gains a KPH every 2-3 seconds.

Edited by YourSaviorLegion, 02 March 2017 - 09:11 AM.

[AngrySpartan]

Amsro, on 02 March 2017 - 09:04 AM, said:

Its an honest mistake to miss a few decimal places on a dozen or so mechs.
We are testing it. On the test server.

I completely understand that and ok with mistakes, they happen!
Sarcasm was related to PGI's habit to mix oranges (engine decoupling) and rotten fish (skill tree) on the same plate (PTS).

[Wintersdark]

AngrySpartan, on 02 March 2017 - 08:54 AM, said:

That is why you do not test Skill tree together with some other major gamechanging mechanics, like...let me think of one...(surprise!!!) decoupling engines from mibility!

Why not, in this case?

It doesn't matter what things are like now. All you need to do is try a mech without Mobility skills, then add the Mobility skills, and Lo! You can test how the mech feels with and without those skills, and thus objectively judge how the skills impact performance.

The bug is a bug. *shrugs* It's clearly unintentional, and likely just due to poor data entry.

AngrySpartan, on 02 March 2017 - 09:09 AM, said:

I completely understand that and ok with mistakes, they happen!
Sarcasm was related to PGI's habit to mix oranges (engine decoupling) and rotten fish (skill tree) on the same plate (PTS).

But in this case, it's sort of part of the same package. Just doing one or the other wouldn't give relevant results [in this particular case].

[Amsro]

Katpocalypse Meow, on 02 March 2017 - 09:08 AM, said:

The accel/decel values in the skill tree also appear to be broken. It's especially bad with decel where even with max Hard Brake it takes significantly longer to stop then the same mech does on live WITHOUT hard brake. Might be tied to broken values in the mechs themselves like you mentioned with the engine decoupling or the skill tree values are being applied wrong, i.e Hard Braking values are inverted and decreasing decel instead of increasing decel.

Yeah hard brake increases the time to stop. HA! and you HAVE to take it to get to the bottom of the skill tree to use speed tweak.

[Bishop Steiner]

GrimRiver, on 02 March 2017 - 08:48 AM, said:

Same for Sparky.

+1KPH per every 20 seconds.

Sssssssllllllllllloooooooooooowwwwwwwwwwwwww.

:'(

guy in my unit tried testing the Jenner ..... took 10 minutes to get to almost max speed. XD

[Bud Crue]

Reporting as requested:

Add the Quickdraw 4G to the list.

[Alex Morgaine]

oooo this'll be fun

[Elizander]

Can't you see all this info in the store and check there?

Or you know, PGI can just run a script on the file and spot any value below 1 or something. :3

Edited by Elizander, 03 March 2017 - 11:28 PM.

[Alex Morgaine]

awww, it looks fixed.