Posted December 13, 2023
This game befuddles me. It's almost like the computer is a living thing rather than a calculator that should always get the same answer.
But starting this game every day is the same routine. I will double click the icon (No Galaxy, never had it, never will), the initial logo screen will come up and the intro video. At this point it matters not whether I let the intro video play or interrupt it by hitting escape, the loading screen comes up with a "loading line" that fills up left to right (we see these types of loading screens in many games and when the line "fills up" the loading is done and the game or new section of the game displays.
But in this case, the "loading line" usually moves rapidly to halfway, then a pause, then completes. But with this game, every morning, and so far it's been four days in a row now, but every morning that loading line gets to the exact halfway point, and the game crashes back to desktop.
I then start the game again, and sometimes a third or even fourth time, but eventually it gets to that halfway point, and instead of crashing it finishes loading and I can continue. Now the strange thing is that after that initial hiccup, I can then quit and start the game multiple times and it loads and runs fine. Until I go to sleep and wake up and start again, and then it goes through this routine again.
WTF? It's almost like the computer is "tired" when it first wakes, then it's like... "oh, okay, I guess we have to run this program now" and off it goes. But that shouldn't happen, right? I mean double clicking the same icon should result in the exact same instructions resulting in the exact same results (1 plus 1 should ALWAYS equal 2, yes?) every time. Yet it's almost like this computer has to go through that first failure or two and then runs. It's like a "brute force" method where dammit if you keep running those same instructions and calculations (the code) over and over again you will get different results (sometimes it crashes, sometimes it doesn't) I have never understood how this is possible. I'm used to when software has a problem, it remains a problem until something changes (a patch changing the code, new drivers for hardware, etc) but this is like "meh, sometimes when I run that same set of instructions and calculations using this same hardware I'll give you different results depending on how I feel at the moment." How is that possible?
And, of course, the bigger question is, is there a "fix" for this problem that is sometimes a problem but sometimes isn't????
But starting this game every day is the same routine. I will double click the icon (No Galaxy, never had it, never will), the initial logo screen will come up and the intro video. At this point it matters not whether I let the intro video play or interrupt it by hitting escape, the loading screen comes up with a "loading line" that fills up left to right (we see these types of loading screens in many games and when the line "fills up" the loading is done and the game or new section of the game displays.
But in this case, the "loading line" usually moves rapidly to halfway, then a pause, then completes. But with this game, every morning, and so far it's been four days in a row now, but every morning that loading line gets to the exact halfway point, and the game crashes back to desktop.
I then start the game again, and sometimes a third or even fourth time, but eventually it gets to that halfway point, and instead of crashing it finishes loading and I can continue. Now the strange thing is that after that initial hiccup, I can then quit and start the game multiple times and it loads and runs fine. Until I go to sleep and wake up and start again, and then it goes through this routine again.
WTF? It's almost like the computer is "tired" when it first wakes, then it's like... "oh, okay, I guess we have to run this program now" and off it goes. But that shouldn't happen, right? I mean double clicking the same icon should result in the exact same instructions resulting in the exact same results (1 plus 1 should ALWAYS equal 2, yes?) every time. Yet it's almost like this computer has to go through that first failure or two and then runs. It's like a "brute force" method where dammit if you keep running those same instructions and calculations (the code) over and over again you will get different results (sometimes it crashes, sometimes it doesn't) I have never understood how this is possible. I'm used to when software has a problem, it remains a problem until something changes (a patch changing the code, new drivers for hardware, etc) but this is like "meh, sometimes when I run that same set of instructions and calculations using this same hardware I'll give you different results depending on how I feel at the moment." How is that possible?
And, of course, the bigger question is, is there a "fix" for this problem that is sometimes a problem but sometimes isn't????