bstone icon indicating copy to clipboard operation
bstone copied to clipboard

[1.2.1.1] BStone crashes on launch

Open StroggVorbis opened this issue 3 years ago • 9 comments

The 32-Bit version of BStone crashes after the Apogee logo with with a "CRITICAL: [GL_ERR] GL_INVALID_ENUM (0x0500) error. The 64-Bit version crashes instantly with the same error. I tried both AoG and PS and all the various renderers, even software. No difference.

My Specs: Windows 10 64-Bit i7-4790k GTX 970 16GB DDR3 RAM @ 1600MHz

Thx in advance

EDIT: The 32-Bit version actually runs fine as long as I don't press the left mouse button. I can wait out the intro screens or skip them with spacebar or Escape and even get in game, but as soon as I hit left mouse, the game crashes with the above error.

EDIT 2: Upon further investigation, going to the options menu and changing the renderer from there to anything other than 3.2 Core makes it run fine. Upon trying to change back to 3.2 Core however, the window says it runs in software mode.

EDIT 3: It seems like changing the renderer from command line doesn't work for me, the game will always try to boot up with 3.2 Core. Editing the bstone_config.txt manually however seems to work. Now even the 64-Bit version boots up without problems. So it seems like something is wrong with either the renderer, my system, or both.

StroggVorbis avatar Apr 02 '21 05:04 StroggVorbis

Please email or attach logs when you switch renderers and when the game crashes.

bibendovsky avatar Apr 02 '21 07:04 bibendovsky

bstone_log - crash midgame.txt bstone_log - crash on launch.txt

I've attached two logs. The first is the crash I get when trying to switch to 3.2 in game. The second is trying to immediately launch with 3.2.

StroggVorbis avatar Apr 02 '21 17:04 StroggVorbis

bstone_bin_win7_32_v1_2_12-20210815-b4828e9-msvc-19_29_30133_0.zip bstone_bin_win7_64_v1_2_12-20210815-b4828e9-msvc-19_29_30133_0.zip

Made errors more detailed for renderer-related components. Please attach the log.

bibendovsky avatar Aug 15 '21 17:08 bibendovsky

@StroggVorbis Does the latest release still affected by the issue?

bibendovsky avatar Sep 18 '22 10:09 bibendovsky

Not sure if this is related, but I get an immediate crash in all OpenGL modes on the latest build(s). On start up, presumably auto-detect is selecting OpenGL and game immediately crashes. Likewise when I force software render mode, the game starts up fine, but crashes when I select any OpenGL mode and hit apply. This still occurs on the most recent build. I reverted back to 1.2.0 and the OpenGL modes seem to work fine there.

[CRITICAL] [VIDEO] VL_Startup [VIDEO] vid_check_vsync [HW_VIDEO] present [REN_3D_GL] present [GL_ERROR] ensure {GL_ERROR] GL_INVALID_OPERATION (0x0502)

Side note. RE: OPs EDIT2, in v1.2.0 at least, the Window does initially display software render mode in the banner, regardless of which mode I am truly in. This seems to resolve itself once I switch modes.

I will attempt to run versions between 1.2.0 and 1.2.12 to find the point at which this OpenGL crash was introduced.

[Update] 1.2.11 seems fine!

Thank you for an amazing port. As a fellow software developer, I appreciate the effort involved.

johnsant65 avatar Oct 29 '22 20:10 johnsant65

Not sure if this is related, but I get an immediate crash in all OpenGL modes on the latest build(s). On start up, presumably auto-detect is selecting OpenGL and game immediately crashes. Likewise when I force software render mode, the game starts up fine, but crashes when I select any OpenGL mode and hit apply. This still occurs on the most recent build. I reverted back to 1.2.0 and the OpenGL modes seem to work fine there.

[CRITICAL] [VIDEO] VL_Startup [VIDEO] vid_check_vsync [HW_VIDEO] present [REN_3D_GL] present [GL_ERROR] ensure {GL_ERROR] GL_INVALID_OPERATION (0x0502)

Side note. RE: OPs EDIT2, in v1.2.0 at least, the Window does initially display software render mode in the banner, regardless of which mode I am truly in. This seems to resolve itself once I switch modes.

I will attempt to run versions between 1.2.0 and 1.2.12 to find the point at which this OpenGL crash was introduced.

[Update] 1.2.11 seems fine!

Thank you for an amazing port. As a fellow software developer, I appreciate the effort involved.

Fixed, see #435 for new binaries.

bibendovsky avatar Mar 08 '24 10:03 bibendovsky

@StroggVorbis Could you test those new binaries in #435 too? Does the game still crashes?

bibendovsky avatar Mar 08 '24 10:03 bibendovsky

Just tried with Planet Strike. Seems to work :D

Edit: It does crash when I have Bandicam open in the background (which I use to limit FPS), if the 'Show FPS Overlay' option is enabled. I can still limit FPS without the display, so it's not that bad. image image

StroggVorbis avatar Mar 08 '24 15:03 StroggVorbis

Just tried with Planet Strike. Seems to work :D

Edit: It does crash when I have Bandicam open in the background (which I use to limit FPS), if the 'Show FPS Overlay' option is enabled. I can still limit FPS without the display, so it's not that bad. image image

Unfortunately it's not reproduceable for me.

Try binaries and command-line option from here to get more specific location of an error.

bibendovsky avatar Mar 15 '24 21:03 bibendovsky