ML Crash Problem - help?

[9-Ball]

Folks,

I'm experiencing a strange crash issue with PES 2009. My situation is as follows:

I have PES 2009 installed and patched to 1.20

I am using a no-cd patch

I have installed Gaming Access Patch 2.5 and then heavily edited the option file myself, adding in 6 or 7 teams, many classic players, squad edits, strip changes via Kitserver, etc.

I have reached near the end of my second season, where I'm 1
game from winning Div1. The crash happens whenever I actually clinch the D1 title. On the current save, I have a game versus Man Utd. If I win this game, it proceeds to display the cut-scene in the dressing room, then when it tries to progress past this, I presume to return to the main menu, it crashes to desktop without any error message. I don't have Auto-save enabled but it seems to be trying to write to the settings or option file, following the game, for a split second. I should add I have no problem loading into the ML for this game, so I think I can presume the save file isn't corrupt?

If I lose this game, or tie, then it goes back to the ML main menu without issue and I can go to the next game. It's just on winning D1, finally.

My PC far exceeds the recommended specs for the game and I have no other crashes with anything at all.

I'd hugely appreciate any info or advice anyone can offer since I'd hate to go and restart a new ML career, perhaps only to re-encounter the same problem eventually.

I've tried jumping the resolution down to 800x600 but no progress.
I've tried reinstalling on my second drive and no using the no-cd patch, but no use.

regards,
9.

 

[9-Ball]

I figured I'd add to this to say I found a fix, in case anyone else has a similar issue. I managed to get through the game and cut scene and then save again, all by uninstalling kitserver from the gcp.exe file for just the one game. It results in playing the game in all black kits, versus a team in all black kits (a challenge!) but at least it's a workaround.

I haven't reinstalled it yet, nor played the next game in the season, but it seems to highlight the cause of the problem as being related to whatever is written to the save or option file after winning the ML Div1, and thereby at least formally unlocking the hidden players. I'd unlocked them via a hex edit to the relevant .img file and I guess it caused some write/written already issue. Fingers crossed it lets me continue on without further issue but it seems like it should.

I guess if anyone wants more info on this due to similar problems then post up, otherwise any mod can delete this if need be.

9.

 

[9-Ball]

Well, maybe not. It seems that on also winning the D1 Cup I encounter the same issue, I presume related to players the game thinks it should be unlocking after this. I presume also, that the same workaround may fix it but we'll see.

This is becoming a talk-to-self exercise

 

[zlac]

Well, let's break that self-chatting session

I'm not sure that your problem is 100% related to manually unlocked players (you did it by hex-editing unnamed_1163.bin in ga0f.img, right?)

#1 - I'd say that game tries to unlock ML youth players right before the first week in the mid-season transfer window (and does it each and every season, unlocking only a fraction of hidden ML youth database). I haven't noticed any ML youngsters appearing neither during the regular season weeks, nor during the end-of-season transfer window.

#2 - I'd say that all the other Classic/Hidden players appear on the market in one batch, during the mid-season transfer window of the very first season (and since you're about to win D1, you're at least one season beyond that point).


So, if you want to test whether manual unlocking did the harm, try simply to remove unnamed_1163.bin from gakserver\img\ga0f.img, no need to uninstall entire kitserver and watch all blacks on the pitch

Disabling kitserver entirely did help, but you still cannot be sure which part of GDB or img caused the problems. It may have been related to some bad fan celebration gfx in god knows which .bin


One question though - when you hex-edited that 1163.bin, have you accidentaly unlocked ML youth sections too? That might not be such a good idea, since ML youth has a kind of "special treatment". Maybe locking them back could help.