SLG % career total average is calculating wrong

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

SLG % career total average is calculating wrong

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Current Games From Matrix.] >> [Sports] >> PureSim Baseball >> Tech Support >> SLG % career total average is calculating wrong

Page: [1]

Message

<< Older Topic Newer Topic >>

SLG % career total average is calculating wrong - 7/22/2006 11:05:38 PM

verizon32

Posts: 168
Joined: 5/23/2006
Status: offline

Patch 1.22

HTML Almanac browser calculation bug for SLG% career total average.

SLG % career total average is calculating wrong in the html almanac browser when viewing player card in there.

So this is also causing the OPS % career average to be wrong too in the html almanac browser when viewing player card in there.

SLG%+OBP%=OPS%

< Message edited by verizon32 -- 7/22/2006 11:15:42 PM >

Post #: 1

RE: SLG % career total average is calculating wrong - 7/24/2006 5:32:45 AM

verizon32

Posts: 168
Joined: 5/23/2006
Status: offline

same problem in beta 1.24 too

(in reply to verizon32)

Post #: 2

RE: SLG % career total average is calculating wrong - 7/26/2006 4:15:38 AM

Nomo Ootp

Posts: 68
Joined: 6/27/2006
Status: offline

It is the slugging pct that throws this off.... It appears that the slugging pct is set to include 2b, 3b, and HR an extra time in the calc instead of the standard (H + 2B + (2*3B) + (3*HR))/AB

(in reply to verizon32)

Post #: 3

RE: SLG % career total average is calculating wrong - 7/26/2006 4:20:04 AM

verizon32

Posts: 168
Joined: 5/23/2006
Status: offline

bump

This slg% calculation problem is in the html almanac browser only.

(in reply to Nomo Ootp)

Post #: 4

RE: SLG % career total average is calculating wrong - 7/29/2006 10:12:07 AM

verizon32

Posts: 168
Joined: 5/23/2006
Status: offline

Same bug in patch 1.25beta.

Hopefully it will get fix this weekend.