Version 0.8 does not start

Teawan

Back to the roots?
This error (see picture) was gone months ago and returns with the latest version
I am on 0.8.0.3c5a (17,14,2)

It depends not on what I like to start same result for any tested map so far. (Yes aleo the ones coming with the 0.8)
Yes my installation is clean in a brand new directory.
My graphic card driver is up to date.

Looks like I have to stay on the 0.7. for while.

Shatojon

Uh oh..

Have you tried a fresh reinstall where you uninstall, then manually delete your Castle Story folder before reinstalling? Make sure to backup your saves.

If you have, give me an hour or two, I'm not at the studio yet but once I get there I'll get you an answer, someone else had that issue in house and we resolved it pretty easily.

Shatojon

Hey Teawan,

Turns out this is a settings messup. Try these things, in order.

1- Just restart the game. Sounds silly but, gotta start with the basics.
2- In the launcher, change the resolution to the smallest available one. Launch the game, close it, then launch it again in the proper resolution.
3- If all fails, try this; https://sauropodstudio.zendesk.com/hc/en-us/articles/218389798-How-to-do-a-fresh-reinstall-of-Castle-Story-Crashes-Crash-

Please let me know how it goes!

Teawan

Hi Shatojon,

OK, I am back to my PC.

1- Same error (and meanwhile I also started the PC)
2- 640x480 is the smallest I have - same error
3- I installed into a new empty directory (I'm not using steam, so I don't care about that step). To make sure the download was not corrupted somehow I just loaded it again. - works

But I had I Trojan warning for the file castlestories.exe
See attaches picture (sorry text is in German)
Line 1: McAfeeautomatically quarantained a file
Line 2: Found: Artemis!9BE06C54320E
Line 3: Isolated from: Path

I'm relatively confident that this is a false positive - just to let you know.

Cheers
Teawan

Shatojon

Thanks for the heads up, definitely a false positive.

Thank you Teawan.

Teawan

And after some research I found the reason for that behavior: Some files had been write protected. I have no clue why. After removing the write protection the game was running without any error messages.
Perhaps this helps someone.