Here it is
Looks clean, but it also looks like you haven't cleaned your cache in awhile. I'd delete it.
G
Here it is
Looks clean, but it also looks like you haven't cleaned your cache in awhile. I'd delete it.
G
I don't quite understand. I deleted the Cache folder before installing this new beta and have played one game since.
I don't know what I did wrong:
Spoiler :![]()
I cleared my cache and I deleted LUA folders in CP and CBP.
I had that as well, i closed down all tabs and kept going, and it solved itself.
Started a new game and indeed it happened again:
![]()
Clicking on Accept makes him decline and clicking on any items does nothing.
Attached is the Autosave from 1 or 2 turns before and the Logs folder.
HTH!
I get that user-error is a very common thing, but this is the 4th person to report that.
Perhaps you can clarify for me, I don't understand the phrase "delete LUA folders as needed" from the OP. How do I need which LUA folders I need to delete?Yep, and the fact that the beta has lua folders in the CP/CBP (which the auto-installer lacks) means that some users forget.
G
Perhaps you can clarify for me, I don't understand the phrase "delete LUA folders as needed" from the OP. How do I need which LUA folders I need to delete?![]()
Actually, there aren't, from what I can see in the CP folder.There are readme or install text files in the archives you are unpacking.
Perhaps you can clarify for me, I don't understand the phrase "delete LUA folders as needed" from the OP. How do I need which LUA folders I need to delete?![]()
The way the boxes are all misaligned makes me think that you did not delete LUA files from the CP/CBP, and/or some other installation issue.
G
This time I made sure I installed correctly; I deleted all old CP and EUI files, deleted the Cache and the Moduserdata folder, let Steam check file integrity. Copied the new beta files into the Mods folder, deleted LUA folders from CP and CBP, and copied EUI into the DLC folder.
I don't think it was a bad installation. I'm positive I installed correctly and I repeatedly had that bug as well.
The good news is it will go away on its own after a few turns, and I haven't had it happen so far in the (12/10) version.