Calamity 1.1 Map appears with no shaders and purely gray color after I put my game to low settings(Possibly me turning off bloom)

Would be nice to see screenshot, settings and most importantly infolog.txt

I think there are two options to submit your infolog.

In any case. Run Zero-K, find the huge "Help" button on the left side of the screen, then either:

• press "Report a bug", fill in the fields and Submit. The game will open a browser window/tab with the link to your bug report. Post this link here.
• click Links, then select "Game Data". This should open you a folder where your game is. The infolog.txt should be there. So, host Calamity 1.1 map in skirmish, make sure graphical bug is there, exit the game, locate infolog, post it somewhere and post the link here.

This infolog is crazy long and has a lot of noise. Looking for the word error immediately yielded more than 1000 occurrences, even my browser started become unresponsive.

Can you do the following:

• Exit the game lobby
• Locate infolog.txt and delete it. Don't worry it's safe.
• Launch lobby
• Start single player --> skirmish game. Choose inactive AI as opponent (make sure to remove default AI). Change map to Calamity 1.1. Start the game.
• Observe the visual glitch
• Exit from the game, then immediately from the lobby.
• Upload infolog.txt

Also does your visual artifact appear on any other map? Look for big ones in particular.

This hang detector should be leashed somehow, it causes so many false positives...
This is most likely one of them.

It doesn't appear on any map, only this one

ivand https://privatebin.net/?a8304126d4ead68b#7UM7WSSHhItmbnELfkBd/oUydCp/9f/91kmWQKJYW5Q=

TheMooseIsLoose thanks for that, I found it on the second info log as well

@_Shaman EDIT: I followed the instructions you sent to me in ZK Lobby and apparently the map loads normally for a second before suddenly turning back into the broken version of the map.

I did ivand's instructions again after applying the Atihacks and HangTimeout then posting it here:

https://privatebin.net/?172d9f800f290a7d#gFQTQ5v2twxi0tHBL5ezMr5poNuJyzfdAhJxyH27gYs=

[f=-000001] Input grabbing is enabled! <- this line looks suspicious to me but welp IDK much how all these things work anyways so not sure

UPDATE:
Putting settings back to defaults no longer fixes the problem

I'm a bit lost.

CUS errors shouldn't affect map rendering and generally shouldn't throw errors like this.
I guess you will need to do the following:
1. Go to the last working graphical preset. Reload Zero-K lobby. Make sure Calamity looks well.
2. Screenshot or right down the individual graphical setting on a) Last working graphical preset b) Preset where you have visual glitches.
3. Now go to the last working graphical preset and change setting one by one for those that are different between presets. Load Calamity and observe if changing some the individual setting break things.

Might sound like a lot of work. Yeah it's. But this way I found one particular setting due to which my FPS was dropping from 80 to 1 on older GPU.


EDIT: Actually there is one extra idea. Assuming you are are in skirmish, when in game on this map and see the bug, type into the chat:
/cheat
/luarules disable
/luaui disable
/advmapshading 0
/advmodelshading 0

See if any of last 4 have any effect.

Can you go to some other map with the current settings and post infolog?

Also the error traces keep telling something is wrong with your driver stack. I guess you have tried already switching to latest stable or alternatively latest beta version of AMD driver?

Glad you sorted that out. A bit bad we likely won't know what was causing it.