Skip to main content

Browse GamesGame JamsUpload GameDeveloper LogsCommunity
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
LutzGrosshennig1 year ago(+1)

I asked someone to test it with an AMD GPU and he confirmed that this happens in the Windows build while being in the secondary reality near the (optional) mini boss.

The funny thing is, only in the native windows build but NOT in the WebGL build. I'll guess it could be shader related but I'll have to debug thins on an AMD system.

Reply
SmokeSomeFrogs1 year ago(+1)

Really weird - in one of my games I also had problems only with my AMD GPU and only with newer drivers, Intel integrated and NVidia worked fine, dunno what is the problem there. Thankfully it didn't crash and was still completable, so that's certainly a plus :)

Reply
Kordanor1 year ago

Hey there! That also happens with NVidia GPUs, using a GTX 1700 here.

Reply
LutzGrosshennig1 year ago

Hmm that is weird, thanks for reporting. 

Does it also happen in the WebGL build? And I assume you are in the second reality when it happens?

Nvidia 30x0  series seem to be fine. I wonder if this is some undefined behavior inside a shader. Have to investigate this on a affected system.


Thanks for investigating it.

Reply
LutzGrosshennig1 year ago (1 edit)

There seems to be something funky going on with the mini boss in the 2nd reality but only in the native windows release build. 

He is optional after all but he does give +100 rift and a nice damage boost.

Reply
AboutFAQBlogContact us
Copyright © 2025 itch corp · Directory · Terms · Privacy · Cookies