tell me, have you tried selecting window mode in the settings, and playing with a lower resolution?
yes i did. i wasn't sure wat really the problem istell me, have you tried selecting window mode in the settings, and playing with a lower resolution?
disable all unnecessary programs during the game.
Then do something elseyes i did. i wasn't sure wat really the problem is![]()
32-bit Windows. You need to change to a 64-bit OS.yes i did. i wasn't sure wat really the problem is![]()
Because it's impossible on a 32-bit OS to utilise a full 4GB of RAM, let alone your 8GB of RAM.i also try to play the game with just 4gb ram but still the same.
If that is the case - which means the engine is really crappy - why even bother building a 32 bit version of the game? And besides, what in a game like this could justify a minimum of several gigs of RAM in order for it not to crash? As far as I can see, it's mostly showing some static images with a text overlay, and then an occasional video clip.You mentioned 32-bit Windows 7, but having 8GB RAM... Your machine cannot utilise more than around 3.47GB of RAM because you're using a 32-bit OS. Ten minutes later, however much RAM (out of around 3.47GB) isn't being used by your system has been gobbled up by the game and it crashes.
It isn't engine related, because no one else reported crashes on their 32bit systems. More likely that it is an issue on players end.If that is the case - which means the engine is really crappy - why even bother building a 32 bit version of the game? And besides, what in a game like this could justify a minimum of several gigs of RAM in order for it not to crash? As far as I can see, it's mostly showing some static images with a text overlay, and then an occasional video clip.
It's derived from Unity, and IIRC it's specifically tailored for creating Visual Novels.If that is the case - which means the engine is really crappy -
It's not about needing several gigs for it not to crash. It's about having an OS capable of fully utilising the available RAM. Huge difference.And besides, what in a game like this could justify a minimum of several gigs of RAM in order for it not to crash? As far as I can see, it's mostly showing some static images with a text overlay, and then an occasional video clip.
My point exactly. Advising someone to re-install their OS based on something like this is just bad. Worst case someone wipes their machine only to realize that their dual core CPU is a 32 bit chip.It isn't engine related, because no one else reported crashes on their 32bit systems. More likely that it is an issue on players end.
Window 7 32 bit is perfectly capable of utilizing available RAM, given it's limitations. Software does not crash like that unless they are poorly written. Sure, you could get a performance hit due to excessive use of the page file, but it shouldn't crash.It's derived from Unity, and IIRC it's specifically tailored for creating Visual Novels.
It's not about needing several gigs for it not to crash. It's about having an OS capable of fully utilising the available RAM. Huge difference.
This game can be run perfectly fine on a 64-bit OS with only 4GB RAM.
His machine's using an i3 processor. That's not a 32-bit chip, not even the first generation of them.My point exactly. Advising someone to re-install their OS based on something like this is just bad. Worst case someone wipes their machine only to realize that their dual core CPU is a 32 bit chip.
First of all, how much RAM he has in the machine doesn't matter, the OS won't address more than what the 32 bit address space allows. Secondly, ever considered someone else might read our advice?His machine's using an i3 processor. That's not a 32-bit chip, not even the first generation of them.
He's also running 8GB RAM, with 32-bit Windows 7... Maybe next time try reading all the relevant information.
He has 8GB RAM with a 32-bit OS = Pointless as it's only capable of utilising, at best around 3.5GB.First of all, how much RAM he has in the machine doesn't matter, the OS won't address more than what the 32 bit address space allows.
Yes, (though the majority of users never seem to actually use the Search function let alone bother to read even a couple of the most recent pages of a thread) and I'm sure that they'll notice you didn't bother to check provided information before saying something silly, even to the point of implying that the problem is the engine, the second time after being told that this can't be related to the engine because there's been no other instance reported.Secondly, ever considered someone else might read our advice?
No, I never said that he had a 32 bit CPU. And pointless or not, that is not your concern. What you should focus on is not giving incorrect advice. The fact that the program crashes has nothing to do with a 32 bit OS, low memory or whatnot. The problem lies elsewhere and if you want to help, your focus should be on figuring out what that might be, not telling people that reinstalling Windows is the way to go.He has 8GB RAM with a 32-bit OS = Pointless as it's only capable of utilising, at best around 3.5GB.
You erroneously speculated on the possibility that his machine's CPU is 32-bit, not bothering to actually see what it was he was using.
Yes, but no. What I said was that if your statement was true, then the engine would be crap. And since you're wrong, and that had been my opinion since the very beginning, I hardly considered problems with the engine.... even to the point of implying that the problem is the engine, the second time after being told that this can't be related to the engine because there's been no other instance reported.
First of all save location is posted on OP, second the game has no auto-save function.need help where are the saves and how i find them im tryna not start over since the game does auto saves so im using saves from thread
Thank you for that I thought I was stupid or something since I couldn't find the dl linkIt's chapter two of this game, not a sequel.
Thank you !! It workedcold_arctus , trenini2
It doesn't matter where he downloaded the game or which one.
There was already a case with a password requirement, I even saw a screenshot in person. This bug came from a very early version of Timestamps, when the game required a password. It is treated by cleaning the local folder.
I haven't actually given incorrect advice, unless it's incorrect to say that he should have a 64-bit OS to utilise the remaining 4.5GB of his 8GB RAM. That absolutely will provide more than enough of a performance boost that should eliminate his issue of the game crashing after 10 minutes of game play.What you should focus on is not giving incorrect advice.
You're still failing to give any advice, instead focusing solely on me... I'm flattered you're apparently obsessed with me, but it's boring now.Secondly, ever considered someone else might read our advice?