Since the combat (and after combat) are the times it crashes the most, could you add a "pre-combat" autosave, please?

bjg wrote:Since the combat (and after combat) are the times it crashes the most, could you add a "pre-combat" autosave, please?

I could... but, I'd much rather fix the root issue.

I just pushed a patch to 'stable' (r14702) that might fix the crashes you've been experiencing on your Intel laptop. Can you tell me if you're still getting regular crashes, after updating?

It's got the update, but I haven't played long enough yet to tell if it's got better. It hasn't got worse though.

bjg wrote:It's got the update, but I haven't played long enough yet to tell if it's got better. It hasn't got worse though.

Well, that's a start!

It's just crashed. Ran out of system memory.

bjg wrote:It's just crashed. Ran out of system memory.

I've encountered a rumor in a dark corner of the internet that may have some bearing on these crashes. Apparently the intel hd opengl driver has some issues when running 32 bit binaries on 64 bit Windows. So, in theory, switching to a 64 bit build of SiS might fix these crashes.

As of the latest stable build -- there should be an exe called sis64.exe inside Stars in Shadow/. This is still experimental -- but, what testing I've done thus far suggests that crashes are less likely, and total memory use lower, when running sis64.exe on Intel HD Graphics machines.

Could those of you who have been running into crashes on the Intel HD Hardware (and who are also using 64 bit windows), try testing using sis64.exe, and let me whether or not that appears to fix the crashes?

sis64.exe won't start for me. (I'm on 64-bit Windows 10 Home).

"The application was unable to start correctly (0xc000007b)."

Arioch wrote:sis64.exe won't start for me. (I'm on 64-bit Windows 10 Home).

"The application was unable to start correctly (0xc000007b)."

Hrm. It's probably missing a dll or something. I'll see if I can get that fixed after supper.

Arioch wrote:sis64.exe won't start for me. (I'm on 64-bit Windows 10 Home).

"The application was unable to start correctly (0xc000007b)."

Ok, as of r14760, I think this may be fixed. Unfortunately, I don't have a clean test machine to check the dll issues on. Can you let me know if sis64.exe is running on your Windows 10 box?

Edit: As of r14764, the start menu screen should show whether you're running a 32-bit or 64-bit build of the game. (right now, the autoupdater will launch the 32-bit version, even if the update launched from the 64-bit binary -- so, you may end up in a 32 bit build, in moments when you don't expect to.)

sis64 runs and loads the game for me (on Win7), haven't tried to play yet.

Still doesn't run on my Win10 system. No error message, it just never starts, and the explorer window I tried to launch it from becomes unresponsive.

Can't talk to marauders. The error is sent. Switching back to 32 for now.

bjg wrote:Can't talk to marauders. The error is sent. Switching back to 32 for now.

Ok -- I can replicate that. Very strange. Must be some low-level compatibility thing in my regex parser. A fix will need to wait for tomorrow.

Thanks for the testing!

bjg wrote:Can't talk to marauders. The error is sent. Switching back to 32 for now.

Looks like the x64 microsoft c++ compiler has some interesting quirks.

These "Attempt to access an uninitialized boost::match_results<> class" bugs should be fixed in the version of sis64.exe now posted on stable (r14768).

Theodotus wrote:So now that I've had the opportunity to play SIS a bit:

I've been looking over your beta testing logs, and you have indeed logged quite a few hours over the last 3 days! From what I can tell, you're playing on a machine with an Intel HD Graphics 4600 adapter; and you have experienced 3 crashes while running with the 32-bit binary (sis.exe). However, you've also been doing a lot of testing using sis64.exe, and as best as I can tell, it's never crashed for you. Is this correct?

If so, it may be about time to change the updater / installer scripts so any new players on an Intel HD Graphics machine are sent to the 64-binary automatically.

Also -- can I ask how the game has been performing for you? (If you hit ctrl+h in an end-game map, what fps numbers do you typically see?)

Thanks again for all the testing and feedback.