BZ 1715: The ball will not disappear

[Curtis]

I manage all of my games, and it took me exactly two batters to discover that I was right when I assumed that crowd noise and ball movement would be annoying distractions. The crowd noise is now gone, and the ball isn't MOVING, but it is still APPEARING.

On every play that damn ball makes an appearance, and it's nowhere near where the play-by-play tells me it should be. On foul pops it appears on top of the second baseman. On infield singles it appears in deep centerfield. The frigging thing is driving me crazy.

[Nutlaw]

Are you using the default stadium displays that came with the game?

[StyxNCa]

Originally Posted by Nutlaw

Are you using the default stadium displays that came with the game?

What defaults are these? I have the same problem and have tried setting everything under the sun to get rid of it and it's still there.

[Curtis]

Originally Posted by Nutlaw

Are you using the default stadium displays that came with the game?

Yes. I see that there was a thread in the General section of the forum that tried to explain how to eliminate the ball, but I couldn't follow the explanation. It had to do with giving very large coordinates to… something. I couldn't even understand the first step.

I'll try to dig up a reference to that thread.

http://www.ootpdevelopments.com/boar...gured-out.html

[Tycobbler]

On your team home page/ options and ballpark/ edit ball park/ ball locations is where you'll find where you can set the coordinates extremely high 2000 i think they sugested, to eliminate the BALL

....just remember to hit enter when you're done

[Curtis]

Okay, I just went and looked in my game. There are about, oh, manymany sets of coordinates, and they all have to be set to 2000? And hit enter after each one? And then do that for all 104 parks?

Thank you for explaining,Tycobbler, but if the workaround is that involved, I'd rather just call it busted.

Edit: Too bad there's no 'mass select' option for this game. If there was you could just select all coordinates, then enter once for each park. 104 I could do. 104 times what, eighty? No way.

[Tycobbler]

For those who want to eliminate the ball flight completely (where the ball graphic no longer shows on the field) here is a workaround...

Open any team's stadium editor. Next, go to the ball flight coordinates screen. Then, give all the x coordinates a ridiculously large number like 2000. That'll do it. No more ball graphic on the field at all, just like it was in previous versions of ootp. Next, you can 1) edit each parks ball locations by hand, or 2) click the 'action' button and then 'assign coordinates and ball locations to all parks.' If you go with the second option you'll most likely have to edit your player coordinates (easy as drag and drop) to match you parks. Also, remember to disable ball flight in the pre-game screen.

Folks who use full screen with different screen resolutions, like I do, might be interested in this. I love the ball flight idea, but perhaps in the future a way will be added so that we can easily use the ball coordinates outside the default screen resolution.

There ya go. Easier than ya thought

[Curtis]

Easier than I thought? Well, sort of…

It took over half an hour to input the 348 (not eighty) coordinates. For those of you keeping track, that's 2368 keystrokes*. Of course, that IS easier than entering all of that 104 times, but still one has to wonder whether that sort of effort should really be necessary in a released game.

On a positive note, I found you can do the same thing with the fielder and baserunner coordinates, so now I have all of them copied across, too. This should resolve one of my previous tech support threads (already closed).

Thank you for sticking with me through this, Tycobbler. Mission is apparantly accomplished.

*=six strokes each for the first 132 coordinates, including selecting and hitting return on each {= 792} + seven strokes each for the next 156, including the above and having to page down for each one {= 1092} + eight strokes each for the last sixty, including having to page down twice for each one {= 480} + four missed strokes {so sue me, I was getting punchy} = 2368

[Nutlaw]

So are you all set on this one, Curtis?

[Curtis]

My particular problem has gone away. The point I was trying to get across with the ridiculously elaborate counting of keystrokes was that such effort should not be neccessary. If 20% of the players of this game each have to enter 2364 keystrokes to fix their own problem, my guess is it would be easier for Marcus to make whatever correction would be neccessary to make no ball appear when ball animation is turned off.

So, I guess you should consider this to be a feature request, rather than a bug report (though it certainly feels like a bug to me).

Edit: This is especially true due to the ball not appearing where the play-by-play says it went. Distracting.

[Nutlaw]

Bz 1715

[Nutlaw]

... and ten seconds later, this was marked as fixed. Guess it was already taken care of.