Is that updating it on Steam you're having trouble with?

Thanks for the report Squirmo, i'll pass it through for the code team to take a look at and see if there's anything odd about the output log to cause the lagging.

Hi Webbernever1,

It sounds like your map's meta data some how got corrupted which is stopping the game from recognizing it properly. Whilst that is pretty inconvenient, if the map file still exists on your PC, the meta data can usually be repaired.

If I remember correctly, the location of the maps should be something like:

C:\Program Files (x86)\Steam\steamapps\common\War For The Overworld\GameData\Maps

Can you take a look and see if you can find the map file (and the similarly named meta data file)

If you manage to find them, attach them to a reply here and i'll ask Nano to try and repair the meta data for you.

Closed after 2 weeks due to inactivity / non-response from OP.

Any further tickets about this issue will be declined as there is nothing the core members of dev team can do to fix the issue. But you are welcome to contact me privately should you wish to attempt my possible solution.

Updated the status for you Nano.

Theory: By the looks of it, his 16gb ram is actually 4 smaller (4gb) blocks working together/in tandem, perhaps WFTO is only recognising / using one of them and maxing that one out (due to only being 4gb), but ignoring the others?

Looks like something got missed there, thanks for the heads up

By the looks of it, the extra weird looking highlights are probably the VFX (and the flat planes they appear on)

Well usually the QA Team follow up on the issue on the reporter's behalf, but in this particular case it's a very specialised case that only Nano would be able to resolve even if we could reproduce it, which obviously we can't reproduce because it only exists on your machine, and despite our best efforts we haven't been able to talk you through the process of finding your missing in one of the other folders so it presumably isn't there either.

Luckily for you, I think i've found a solution to the problem and can restore your map back from the dead. That assumes of course you'd like to acknowledge my existence, not ignore my response and actually try my solution.

I noticed 2 strange things in the output log:

• "AddComponent with MonoBehaviour is not allowed. Create a class that derives from MonoBehaviour and add it instead."
• "HighlightingSystem : Framebuffer depth data is not available and can't be used to occlude highlighting."

The Highlighting thing was repeated many many times during the log.

Sending through for code team to review.