totaljourney.blogg.se

I don't know whether this is related, but I don't think I ever had this error until I installed the recent (October 2015) Xbox One update that changed up the home screen. Since none of this works, I now get a guaranteed crash every time try to set up a covert op, among other things, making the game totally unplayable. hard power off (disconnect power) for 1 minute That information is interesting, but in the end, useless to console players.

There's a lot of chatter about this bug from PC players who are saying its related to anti-virus settings on the folder where XCOM 2 stores photos. Apparently, when the game has trouble retrieving soldier photos, it sometimes catches the error and displays the "img:" placeholder instead, but in other places, such as the covert op screen, it doesn't catch the error, and crashes instead. On my latest playthrough, I get it at the first covert op. I would give up on that playthrough and start another one, but I would see the "img:" bug and start getting crashes even sooner. Once it did, I could never proceed past the crash no matter what I did. Once I started seeing this "img:" I knew the game would crash soon. A few of the many places this would appear was at the squad screen when a soldier was kiled, in the Memorial, and in the Photobooth (making it utterly useless). Overall, the game runs like a dream despite the hefty mod list.For the past few days, I've been getting a crash in WOTC that has gotten worse and has now made the game unplayable.Ībout two playthroughs ago, I noticed that some of the photos of the soldiers and VIPs weren't being displayed, but a placeholder with the text "img:" against a tri-color background would appear in their place.

Granted, most of it is cosmetic or VPs, though I doubt it's an overflow issue as I ran into them before and resolved them by just decreasing the number of cosmetics.Īnyone have any ideas how which mods to look at first? For now, I might just console command it, but it'd be nice to know a possible solution and possible future issues. I'm fairly sure it's a mod issue, but might need help narrowing it down due to it being a hefty list. Edit 2:fixed the geoscape CTD doing some load order stuff,but yeah,still CTD when loading the first mission now.Unbelievable. The Reaper/Skirmisher mission, haven missions, etc. I noticed the download on nexus,the first mission load like the breaching mode,and workshopsteam download,load the skyranger mode,that crash when load the map.I suspect some archive may be corrupted,nexus or steamworkshop. Same thing happened before each crash where apparently it couldn't find the getdifficultyfromsettings function and decided to crash? Every mission before worked. I've already tried validating the files which didn't work and tried the mission again which also didn't work. It loads for a bit, starts to stutter, and then crash. Here's the crash log for anyone curious: and to be specific, it's during the screen before it loads the Firehawk interior and directly after you finish the mission.