gwentdragoon - Comments

Well the images should be named with stadium id. You can then replace the image in the pack (if one is present) by overwriting the current image. If you want to add a "new" image to a stadium that hasn't got a image them save the image with stadium id in the folder and add a line in the config. If you want the club to change stadium then use the ingame editor FMRTE : https://www.fmrte.com/ (it cost a small amount) and you can change the stadium and the image on the stadium will also change. Or you can change the stadium in the "normal" editor before starting a new game. (Darlington arena id=142535)

Is that in the Steam folder or the Documents folder? It should be in the latter, but users have been known to erroneously place it in the former where it's known to cause issues. I was thinking that might have been the case.

The price of your computer is not really relevant at this point but, as I've explained before, it's unlikely that it's related to your system, even more now that you've indicated that removing the facepack seems to remove the problem.

When exactly was the game crashing? Was it crashing during matches? Was it crashing when clicking on a particular page (player/team/competition)? Was it crashing during processing? Are the player images displaying at any point before crashing? Have you extracted the megapack file download? How many images do you have in there? Any more info you can provide will help us maybe pinpoint the problem. It seems to me that you've somehow installed it incorrectly from the little evidence that I can gather, but remote assistance is rather difficult unless you can provide me with some furthe details.

I'm not sure what your problem with me is here. It's a Sunday evening and I'm trying to help you find a solution to your problem so I don't believe your attitude is warranted tbph.

You still have not told me the exact path the MP's been placed in. Help me help you here.

The pack works fine for me and thousands of others so it's pretty clear there's something wrong at your end. Either you've installed it incorrectly or your PC can't somehow cope with the size of it, but this is imo unlikely.