Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

I love this. All I've been doing is sitting on my ideas and short stories. Having the first steps be made for me is great. It's like bouncing ideas off someone else, but it's just me from a day/week-o-ago. THANKS, MATE.


***it stop opening up after the third time i close

I'm glad you're making use of this! I didn't personally realise there is interest in this, but it's great you're having a blast with it.

I cannot reproduce this issue, however. Can you confirm the following:

  • Is Story Creator being launched into the background by Windows?
    • If so, close all instances of Story Creator and try again.
  • Did the .NET Framework get removed or updated by Windows recently?

For the Story Creator being launched into the background by Windows. I am not sure if it's not shown up in task manager...

.NET Framework might have been updated from I'm reading the blogs I read.

(1 edit)

If you can, try and re-install .NET Framework 4.7.2 from here, uninstalling any previous versions. Please let me know if this works. Make sure to restart your computer before trying again.

thanks, I'll report back after work.

Sorry, even when I go back to a version of the .NET Framework, It’s still not opening the program anywhere.

I restarted twice for every version I could go back to. SOBBING

(1 edit)

I will investigate what could cause this issue. I am unsure of any alternative solutions at present or what could cause this. I know other applications written in any other language can have similar issues, and it may be isolated to certain Windows related setups. Can you go into your Event Log and see if there are any issues there that Windows may have reported?

Also see if reinstalling Story Creator helps. It may be that a configuration file got corrupted the last time the app exited.

Will do, I'll be back if i found something.  Fine warning I'm not brightest clown. Might be glazing over something very simple.

Application: StoryDev.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at System.IO.__Error.WinIOError(Int32, System.String) at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean) at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, Int32, System.IO.FileOptions, System.String, Boolean, Boolean, Boolean) at System.IO.StreamReader..ctor(System.String, System.Text.Encoding, Boolean, Int32, Boolean) at System.IO.File.InternalReadAllText(System.String, System.Text.Encoding, Boolean) at StoryDev.Globals.GlobalInit() at StoryDev.Program.Main()</Data>

  </EventData>

  </Event>

In Windows Explorer, if you navigate to the following:

%LocalAppData%/StoryDev/

And tell me if,

  1. The directory exists, and if it does,
  2. The file "settings.json" exists.

The likelihood is that "settings.json" cannot be found, based on the supplied error.

If it does exist, please open the file properties and add full access permissions to the file and try re-opening Story Creator.

Let me know how you get on.

There is nothing inside??

And as soon as I delete it and try again open the application Story Creator once more IT OPEN?!?!?

(+1)

Ah, the code is poorly written for it's time. So, what was happening was Story Creator was detecting if the folder existed or if the file existed, but if the folder existed and the settings file didn't exist, it would still attempt to read the settings.json file, hence the error.

I don't think this is a major issue, however, as the only code pertaining to this file is literally one global setting to determine if word-wrapping should be enabled in the dialogue editor.

However, I realise this has caused an inconvenience for you and this shouldn't be the case. If it happens again, simply delete the folder as you have done and start up the application again.