Importantly, just because the compute boots and idles (or even runs games for hours) without crashing, doesn't mean the ram is running as it should.īackground errors could be accumulating. My RAM is rated for 3000 but I have to run it at 2130 or so - any higher and I get errors. It might be in part or whole the fualt of my mobo not fully supporting it. And I learned the hard way that despite being the same model - they aren't compatible with each other at their rated speed. If it does, it's because you don't have enough ram, and the pagefile isn't big enough to pick up the slack.Did you add 2 sticks to now have 4 total? You can check the game logs to see if the end of the log before a crash mentions memory or ram. Ram related crashes will probably stop being an issue with 16 gb ram at some point during the beta phase once they get around to optimizing the game, but that is wasted effort right now, since the systems they would optimize are bound to change. If you only have 16 gb ram, and the drive your pagefile is on doesn't have loads of free space, I would honestly expect the game to crash a fair bit from high ram usage. I regularly see the game itself using 20 gb ram or more. When I had 16 gb, the ram usage was always pinned at 100%, and my pagefile was on an SSD with about 300+ gb empty.Īfter upgrading to 32 gb ram, the game is running much more smoothly (not much higher framerate, but it stopped stuttering). I'd guess the crashes come from you guys running out of ram. It's just a question of whether they can finish the game before they run out of funding from the playerbase. I'm seeing (slow) progress on core features that will be necessary for the game to properly exist, so I'm not too worried about perpetual alpha. Bugs in an alpha is fine, but perpetual alpha with no progress isn't. If it never leaves alpha, that is not okay. Once the game is feature complete, the game moves on to beta, at which point CIG will focus on fixing bugs instead of adding new features. As long as the game has that label, you should expect bugs, and you should expect that they're going to focus on new features over bug fixing. That's to be expected from alpha releases, though. We're still years away from release, and it definitely has lots of serious bugs. Star Citizen is still an alpha, which means CIG isn't focused on stability and bug fixing yet, only fixing the most severe issues that prevent players and QA from testing the features currently in the game (the part they're focusing on). I generally have play sessions of a few hours, with no severe bugs or crashes.Ĭyberpunk 2077 had way more gamebreaking bugs around launch than this game does at the moment, in my experience. Server crashes are also way more rare than before I took a break. I think I've had a single client crash since I picked the game back up in November of last year, and that was a ninetails event that spawned way too many things, eventually killing the server and every client at once. Saved build info to C:\Users\Elkad\AppData\Local\Star Citizen\Crashes\Ĭopied Game.log to C:\Users\Elkad\AppData\Local\Star Citizen\Crashes\game.logĪll crash related data successfully handed over to crash info collector process Saved cvar dump to C:\Users\Elkad\AppData\Local\Star Citizen\Crashes\cvar.dump Saved screenshot to C:\Users\Elkad\AppData\Local\Star Citizen\Crashes\screenshot.jpg * Size of Uninitialized Data : 0 (diskoh), 0 (memoh) * Size of Headers : 1024 (diskoh), 1024 (memoh) System Memory Status: 16236MB total physical, 1826MB free physical, 34952MB system wide commit limitĬloud Imperium Games public crash handler taking over.ĭetails for StarCitizen.exe (md5=91f4e9a72874d9805fa6534098c30075). Process Memory Status: 9128MB working set size, 22361MB commit size (23044MB peak), 4466MB left to commit
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |