![]() |
This game is optimized really poorly, and loads whenever it likes. An SSD seems to perform better, as you might expect. If we were to count times with and without loads (specifically when the mace spins in the bottom-right) everyone's time would improve, and the gaps between times would decrease as well. Of course, this is Garshasp we're talking about. It's not that important in the grand scheme of things. |
StackyMcBearsStackyMcBears likes this. |
|
1) I'll have you know that garshasp is a really good game We have four runs on the board with minutes between them; once discrepancies in loading times become the discerning factor between runs, maybe it will be worth it. Even then, though, loading times (other than game start) aren't very high in variance or even that frequent, right? It seems like more clerical work to track this without much gain. Which loading zones are you concerned about? Here are the ones that come to mind: |
![]() |
![]() |
It would definitely level the playing field. However, like Stacky said, the runs are minutes apart, not seconds, and the loading times, though varying, largely seem to stay somewhat consistent. Right now, it would be more work than it's worth to track loading times. I'm not totally against it, but it doesn't seem necessary yet. |
StackyMcBearsStackyMcBears and ![]() |