Hi guys,



Just to share my experience.

Note : I am using Windows 7 - 64bits and bought the game two days ago



I could create a world once two days ago (the tutorial).

However, when wanting to start a new game with a friend, I could not generate a world (but HE could, and I could join his game flawlessly).



The error message is as follows :

"The World Generator has encountered an exception : IOException File exists" (joining screenshot) :





I tried all the solutions mentionned in the various topics, and rolled back on most, I also emptied the local temp cache for Endless Legend (in C:\Users\lcn440\Documents\Endless Legend\Temporary Files\*)

Since it seemed an issue with file access, I tried to tinker with the excellent Sysinternals tools : Procmon, for the WorldGenerator.exe process.



It showed a LOT of : "Name Collision" for files in C:\Users\lcn440\AppData\Local\Temp\tmp****.tmp

I then decided to remove everything in that directory (not only the .tmp files), as there were more than 66000 files.



I restarted the game and tried to create a new world : bingo, this time it worked.



To sum up, what I did :

-- I downloaded the two MANIFEST files (https://www.games2gether.com/endless-legend/forum/13-tech-support/thread/5336-workaround-crash-at-world-generation-identical-world-generation) and put them in their correct directories

-- I also downloaded WorldGenerator.zip and replaced files in X:\Steam\SteamApps\Common\EndlessLegend\Public\WorldGenerator (in the same post right above)

-- I purged the C:\Users\lcn440\AppData\Local\Temp\ directory



I did NOT do the following :

-- stop my Antivirus program (Avast)

-- run the program as Administrator or set any compatibility mode (I did try, but no effect)

-- modify any steam command line

-- re-install any .NET framework (I only have 4.5.2)

-- remove Read-Only attribute from X:\Steam\SteamApps\Common\EndlessLegend\Public\WorldGenerator (I did try, but the attribute was set back right away after game restart)



I hope this may be useful to someone, though it seems that there are a lot of different errors.

To dev/support team, I can forward you the excerpt of my procmon output if needed.