Page 4 of 4

Re: Another runetime error

Posted: Sun Jun 14, 2015 2:54 am
by Mark
Yes it is the same issue. I played waterloo file for a day and a half. Then it crashed to desktop after I hosted a multiplayer game. It has not been able to run since. I have uninstalled, deleted registry SOW files, I have redownloaded, I have system restored back to when it was working. In short I have done everything and I still cannot run the game.

Re: Another runetime error

Posted: Sun Jun 14, 2015 3:05 am
by Pawsy_bear
no expert but did you delete the SoW file in documents as well where I think it keeps its settings?

Re: Another runetime error

Posted: Sun Jun 14, 2015 3:23 am
by Mark
yep. even deleted the registry files... no trace left

Re: Another runetime error

Posted: Sun Jun 14, 2015 5:34 am
by norb
Have you tried disabling any antivirus software. That's what this sounds like. Matrix is working on a signed version of the app, hopefully in the next patch. That might help. But since it ran fine, then stopped, it's like antivirus picked it up and shut it down. I do not know of anything else that would do that to a program.

Re: Another runetime error

Posted: Sun Jun 14, 2015 7:44 am
by Mark
I only run Microsoft security; I never downloaded an anti-virus. Additionally I restored to the point where I could previously run it and it did not work.

No idea what else I should do.

Re: Another runetime error

Posted: Sun Jun 14, 2015 8:05 am
by Mark
I FIXED IT. no Idea how

Re: Another runetime error

Posted: Sun Jun 14, 2015 8:37 pm
by Jim
Thanks Mark, every bit of information helps.

-Jim

Re: Another runetime error

Posted: Sun Jun 14, 2015 11:29 pm
by norb
Well I was certainly wrong! It's my bug and will be fixed tonight or tomorrow in a beta patch. Thank you everyone for sending your files. That is what helped track this down.

I put in a quick fix at the end to check for UTF8 files. MyGUI uses them and our language files needed them. There were instances where the game had to load the files for MyGUI and it was a last minute thing. Problem is that my check was pretty weak and some of our files that we write as data files were getting marked as UTF8. Dumb mistake, sorry about that. Your files are fine. It's the loading of them that is crashing the game. Compressed files, header reporting that there are 4 billion files in there, allocation crash. All cause of the UTF8 check.

This did come up in testing, but we thought it was something else and wiping out the temp files fixed the issue, so we didn't look hard enough.