Jellico73

If he's using a skin, he should be fine removing the skin out of the folder to like the desktop, deleting the preferences and cache folder out of App data, start the game in the base skin, shut it down then put the skin he was using back in and restarting the game again. And you should only have 1 skin in the skins folder. That's been my experience anyways. Jellico

Are you using a skin?

Yeah, I ran into the same issue again when I reloaded after changing a skin. Try @EdLcommand line fix, it worked for me.

@EdL I ran into the same issue after my previous attempt at a fix, and the added intruction worked for me. I am using a Radeon 5700XT Thanks, Jellico

Deletes your preferences and cache folders out of AppData/Sports Interactive. Start the game, it will load very slowly. When it finally loads, close it, then restart and it should be OK. If you are using a custom skin the first time you try advancing the game might crash to desktop, but after a restart it will work fine. If I had to guess its an issue with the update having conflicts with the prexisting preferences and cache, and it has to go to the process of rebuilding them. That seems to have worked for me so far...

Not enough info there, so let me add onto it for you: You are a Boston United fan, you grew up following them after you moved away, and now have the opportunity to be a regular starter for them. Harrogate wants you to be a fringe player, and like all players, you want a long career, and regular playing time. So, 500 a week with a game every week, or 1500 a month with possible no games over the course of a season. Why are you choosing Harrowgate?

To be fair, there's a distinction. I recently had elbow surgery. My arm mobility and strength is nowhere near what it was before I hurt it. Can I use it? Sure. Is it 100%, no. But it's not fallen off at the shoulder and flopping around the floor by itself either.

Thats a of zero's....somewhere planck is smiling

This strike me as as a situation where the graphics engine can't properly display what the goal keeper is doing. Which happens at quite a few other positions as well. It's annoying on many levels, and one of the primary reasons I go back to 2d

- Hey, your welcome to your opinions, no matter how wrong they are.

I think some of @Ferocious289points are valid. I've my concerns about the game as well, I've submitted bug reports and I'm not starting a new save until the loan economy is fixed. And this isn't the only game I play on a regular basis that is still in Beta, hell I play Tarkov when FM frustrates me and I want to blow stuff up and that game had been in Beta for years now... But, having participated on those games forums and this one as well, and having a couple decades experience in some pretty complex project management positions (Sure you can build a pipeline faster, just dig up the dirt, put the pipe in, cover it up, easy, right? Literally a comment I heard at a meeting one time), the one thing that is apparent is that while of people a lot of people posting their concerns and solutions mean well, they have no concept or idea of real world project management workflow and refuse to accept the fact that some things are different even though they may look the same, and no matter how soon you or I or SI want them to be done and no matter how much money or people you throw at the issues, some things take time. Could they take less time? Possibly but that's a different conversation. The PC/Touch ME conversation is a prime example of this. But to put it another way, putting nine women in a room isn't going to get you a baby in a month, no matter how many other women you add or how much money you dedicate to the process. I am happy to buy unfinished games if I know they are a Beta, which this one was (unlike say, Cyberpunk 2077). Having played FM for awhile now, though not as long as others, I am also familiar with SI's product cycle and how they choose to push updates and what they choose to push them for. Past versions have also taught me that when the game left Beta there would still be issues, and they would push a patch if something was game breaking, and thats SI's definition of game breaking, not the players. And I know from previous experience that SI's chooses not too push a bunch of small patches that could potentially cause more problems (will updating a countries competition rules break a save game? I don't know), they prefer to do one big patch. So If I know this, and assuming you you know this, and assuming most everyone else who has plays the game the past few years knows this, and we all bought the game, why should we expect their dev cycle to be different this year? Jellico

So what part of Neils post are you taking issue with in this response?

Jordan Smith would be the 1st Choice keeper for Forrest if they hadn't brought Henderson in on loan from United...he's probably not a 3M pound player, but there in lies the problem: Value is subjective. You and I can look at the same player and come up with what we believe is a respectable value for that player with the reasons why, and we could both be wrong. Or right. What I read from the OP was that he has a young keeper who is not a full time starter who has 25 clean sheets in 2 years across different levels of competitions. I would need a lot more info than that to make a judgement calls (Shots stopped, rating, clean sheets per season, team defensive stats, etc), but IMO assuming he's automatically worth X because he's on a Premier League team is what causes a lot of valuation errors in the 1st place.

They stage they are on is that they are working on it.. At the end of the day, do you want the patch done right? Or do you want the patch done right now?

And the number of "Why fix Touch first when PC is a bigger platform..." variety of threads would also go up...

I think you have to wait for the initial trail to expire, then offer them a new one. 2 weeks is the minimum you need to find out everything about the player though. ! week will get you some information but not all of it.

Teams winning games but not keeping clean sheets with a 44 YO keeper who is clearly on the downside of his career isn't realistic?

Wow, OK, that is very odd, IMO such crashes don't start occurring until well in the save and with larger dbases. The only other thing I can think of off the top of my head is that if you didn't have this ussue back in FM22, roll your video card driver back a few versions, and if it works keep updating the driver until it doesn't. Good luck!

How far into the save?

What sort of save are you running? How many leagues/players loaded etc?

I suspect the feed is just generated off a bunch of possibilities, one of which is not a lookup to a historical table of such events...now that I think about it that would be one heck of a table...

Usually within the panel is a code or widget name or some other piece of information. I use a program called astrogrep, lets you search files in a directory and shows the results. So say as an example you are looking for say, id="CnaG", you put that in the search and it returns all the files that have id=CnaG in it. When i started getting XML like the ones abopve, one of them was related to a font, was able to search for the font and find out it wasn't even in the skin I was using, which helped me track down why I was getting the XML error.

The economics side of the loan system has issues, SI is working on them

I discovered this because one of my errors was referencing a font that wasn't even used in the Musterman skin, but was in another skin I had within the FM23 folder structure. Move that to my desktop, no more font error.

Take every skin out of your skins folder. If you have a skin anywhere else in your FM23 directory, take it out, put it on its own folder, like on the desktop. Go to C:\Users\YOURUSER\AppData\Local\Sports Interactive\Football Manager 2023 and delete the Caches, preferences and temp folder. Restart the game, it will default to the FM skin. Bring in the skin you want to use, switch to that skin. If you make any changes to that skin like adding a panel/widget from a different skin, change to the base skin, make the changes, and then change back. When you start FM, one of the things it does is create an skc file in the caches folder. For some reason, when looking for skins, the game is not limiting itself to just looking at the skins folder, it is examining the entire FM23 directory and building the skc file off of that, and as a result is creating some pathing/error issues where the game is trying to do something it's not supposed to, hence all the errors. I moved my Other FM skins folder to the desktop, deleted my cache, restarted the gamew, and there was a 60000kb difference in the Mustermann Numerical 1440.skc file size.. It's the only solution I have found that works. Jellico