Crashing when changing scouting accuracy

philthepat · 06-19-2009, 07:22 PM

Since installing the new patch, whenever I try and change the scouting accuracy to 'very high' it immediately gives me the 'OOTP has stopped responding'.

Ive tried it with a league I started before the patch. Ive tried it after starting a new league with the new patch installed. All of the other options are fine, its just the 'very high' selection which crashes it.

Rand · 06-19-2009, 07:38 PM

I can confirm this, if I change scouting accuracy to 'Very High' in an existing league or try to create a new league with scouting at "Very High' the game crashed to desktop when it scouts the players.

Probably not system related as I'm seeing the issue on both my laptop and desktop computers.

All other scouting settings work properly.

jun9901 · 06-20-2009, 06:28 AM

Another confirmation. The game crashed when I make a MLB 2009 new game and changed my scouting accuracy to very high. It is reproducable - means every time I make a new game and change the option, the same problem ocurrs.

For fixer's shake, here is my system :

I downloaded the whole new version install file. I installed it at C:\Games\OOTPX folder, which is not default. I'm using Korean version Windows XP with SP3 but my account name is english. My machine is a notebook with dual-core intel processor T2300(1.66 GHz), 1GB memory, 70 GB hard with 50 GB free space.

And here is error msg and others.

AppName: ootp10.exe AppVer: 2.0.0.0 ModName: ootp10.exe
ModVer: 2.0.0.0 Offset: 00140b72

icecake · 06-20-2009, 12:09 PM

Same thing happened to me. Hope there will be a solution.

Nutlaw · 06-23-2009, 01:59 PM

Version 10.2.16 should have addressed this. Is anyone still having trouble using that version?

Rand · 06-24-2009, 10:38 PM

Quote:

Originally Posted by Nutlaw

Version 10.2.16 should have addressed this. Is anyone still having trouble using that version?

Fixed for me

philthepat · 06-25-2009, 12:43 PM

Quote:

Originally Posted by Nutlaw

Version 10.2.16 should have addressed this. Is anyone still having trouble using that version?

Yep, it works perfectly now.

06-19-2009, 07:22 PM	#1
philthepat Moderator Join Date: Nov 2006 Location: Dover, UK Posts: 279	Crashing when changing scouting accuracy Since installing the new patch, whenever I try and change the scouting accuracy to 'very high' it immediately gives me the 'OOTP has stopped responding'. Ive tried it with a league I started before the patch. Ive tried it after starting a new league with the new patch installed. All of the other options are fine, its just the 'very high' selection which crashes it.

06-20-2009, 06:28 AM	#3
jun9901 Bat Boy Join Date: Jun 2009 Posts: 1	Another confirmation. The game crashed when I make a MLB 2009 new game and changed my scouting accuracy to very high. It is reproducable - means every time I make a new game and change the option, the same problem ocurrs. For fixer's shake, here is my system : I downloaded the whole new version install file. I installed it at C:\Games\OOTPX folder, which is not default. I'm using Korean version Windows XP with SP3 but my account name is english. My machine is a notebook with dual-core intel processor T2300(1.66 GHz), 1GB memory, 70 GB hard with 50 GB free space. And here is error msg and others. AppName: ootp10.exe AppVer: 2.0.0.0 ModName: ootp10.exe ModVer: 2.0.0.0 Offset: 00140b72 Last edited by jun9901; 06-20-2009 at 06:39 AM. Reason: More infos

06-19-2009, 07:38 PM	#2
Rand Minors (Double A) Join Date: Dec 2003 Posts: 124	I can confirm this, if I change scouting accuracy to 'Very High' in an existing league or try to create a new league with scouting at "Very High' the game crashed to desktop when it scouts the players. Probably not system related as I'm seeing the issue on both my laptop and desktop computers. All other scouting settings work properly.

06-20-2009, 12:09 PM	#4
icecake Minors (Rookie Ball) Join Date: Jun 2009 Posts: 24	Same thing happened to me. Hope there will be a solution.

06-23-2009, 01:59 PM	#5
Nutlaw Hall Of Famer Join Date: Apr 2003 Posts: 9,538	Version 10.2.16 should have addressed this. Is anyone still having trouble using that version?