11.07 Stadium effects not calculated

[GSpencer]

Whenever I go to edit stadiums, I find myself having to automatically calculate the effects for each stadium. For example, without entering any changes to the stadiums, clicking the calculate effects button can reduce allowed home runs by 20! How are home runs, batting averages, etc. calculated, and why do they change manually but not automatically?

[HoustonGM]

Well, you said that clicking the button does not change the numbers, correct? That means that it is automatically calculating the numbers..

[GSpencer]

No, I mean that it does NOT calculate the numbers. One would have to manually press the button for each stadium to get the proper calculations.

[HoustonGM]

No, I mean that it does NOT calculate the numbers. One would have to manually press the button for each stadium to get the proper calculations.
I'm not following you...

[GSpencer]

Under "Stadium Editor" and "Stadium Effects", it tells how many HR's are to be allowed, how batting average would be affected by the park, etc. When I open up the dialog, there are already set values in the window. However, clicking "Calculate Effects" changes these values, presumably to the correct values based upon foul territory, fence dimensions, etc. My question is, why aren't these automatically set to the correct value?

[HoustonGM]

Under "Stadium Editor" and "Stadium Effects", it tells how many HR's are to be allowed, how batting average would be affected by the park, etc. When I open up the dialog, there are already set values in the window. However, clicking "Calculate Effects" changes these values, presumably to the correct values based upon foul territory, fence dimensions, etc. My question is, why aren't these automatically set to the correct value?
Are you using a usermade roster?

The game allows users to input their own stadium effects for the stadiums, "overwriting" the ones the game would calculate normally.

[GSpencer]

Nope, I usually start a game from scratch using the rosters from the game, so the stadium attributes are not altered by me at all, which is why I don't understand why they all aren't automatically calculated.

[Grig]

I always just assumed that the original stadium effects are based on real life park factors (i.e. even though the fences might be far, home runs still fly out consistently) and that when you calculate the effects, it bases it solely on the dimensions (a direct relationship between the size and the factors.)

Does that make sense? Basically, the first #'s are meant to mimic reality, while the second calculated #'s disregard factors that BM doesn't take into account (altitude, wind, being able to see the ball on the outfield wall, etc.)

Granted, this might be incorrect, but that's what I've always assumed.

[HoustonGM]

Baseball Mogul DOES take into account altitude, etc. All the things variables shown in the stadium editor are used in calculating the stadium effects.

[jonnymo]

When I open up the dialog, there are already set values in the window. However, clicking "Calculate Effects" changes these values, presumably to the correct values based upon foul territory, fence dimensions, etc. My question is, why aren't these automatically set to the correct value?
Spence is correct, and this is really easy to reproduce. I started a new game in 10.24 using default settings. Before I did anything else, I turned on Commissioner Mode and opened League > Stadium Editor... (see first screenshot). Then I clicked "Calculate Effects" (see second screenshot). Obviously, the stadium effects have changed. I repeated this w/ other teams and other years. Either:

the dialog is not showing the correct effects beforehand, or
the dialog is not showing the correct effects afterwards, or
the default effects are supposed to be different from the calculated effects, due to park anomalies.

If the answer is (1) or (2), this is a bug. If it's (3), then no problem. But, I would like to know for sure. Clay? Ian?

[GSpencer]

Spence is correct, and this is really easy to reproduce.

Usually, the recalculations are much more drastic than yours have shown. For instance, the first attached picture is before calculations, the second attached picture is after.

[HoustonGM]

I'm guessing this is not a bug. The stadium effects get loaded in from the stadium file, and that allows you to edit the effects out of the game so they load in how you want. I'm moving this to General Discussion.

[ohms_law]

I don't want to actually override ya HGM, but I've left it in Bug reports for the last 9 months for one reason. jonnymo is exactly correct:

If the answer is (1) or (2), this is a bug. If it's (3), then no problem. But, I would like to know for sure. Clay? Ian?

I don't know Clay's intent for sure, and the code isn't clear about it either (from what I've seen), so...
*shrug*

[HoustonGM]

Well, I just figured it pretty much had to be #3 to allow for easier editting of the stadium files. Makes sense, although I suppose you're right that only Clay can confirm it.

[ohms_law]

It most likely is... but unless it's blindingly obvious, I try to leave it to Clay (or Ian) to say so. Usually he'll mark the thread title with "[Not a bug]" and either leave it or move it himself, and will occasionally say something in a post to clarify things, but like I said unless it's obvious (either from the report, past experience, public and/or private comments from Clay or Ian, or at least in my case code and/or code comments) then I try to leave it to him.

In cases like this it could easily be that this just hasn't been a priority, in which case leaving the thread here is extremely helpful.

[Jeff Olsen]

Either:

the dialog is not showing the correct effects beforehand, or
the dialog is not showing the correct effects afterwards, or
the default effects are supposed to be different from the calculated effects, due to park anomalies.
When I used 2K4 to compile the first stadium database, I entered the dimensions and hit Calculate Effects whenever the size of the field changed. If nothing has been changed in the database, then it's possible that the calculation process changed somewhere along the way.

[kayelbe]

This still happens in 2k9....