Closed originalfoo closed 5 years ago
@aubergine10 Have you manually moved over your steamapps folder without using Steam's Library function?
I only ask this because I previously moved my game to the D:\ drive once upon a time and I developed like that; never had an issue with TMPE.log not having permission to be written to.
EDIT: My apologies, I had missed the discussion link. Looking more into it, it appears he has moved windows by... literally moving and dragging the folders over. Nobody should ever do that, ever. If he wanted to install on a different drive, he should have changed the drive while he was installing Windows. En quote, "I got many problems with administrator rights with steam games." Clearly this is not the only time he's had an issue like this.
Your solution of reinstalling the game using the Steam Library function PROPERLY should have fixed it, HOWEVER that being said it is likely it wont due to folder permissions being screwed up due to him... moving... windows... manually. Don't do that. Don't ever do that. It's stupid.
I run everything on Drive C: (1TB SSD). The error report above was from a user on Steam (discussion link in OP).
@aubergine10 My apologies. The issue for this is not a TM:PE issue and is in fact a user-error issue. I'm closing this issue until I can find some reason this is caused by TM:PE and not him moving everything manually. I have repsponded to his discussion and hopefully he'll be able to get it resolved.
If user moves their
steamapps
folder to another drive (or their entire C: drive for that matter) something in the game isn't getting updated properly and exceptions occur:https://steamcommunity.com/app/255710/discussions/0/1678063648163403458/