HomeGamesUpdatesPricingMethodology
Steam News29 March 20263mo ago

Game Updated to Version 1.1.2r

A couple players have encountered a strange bug that I am unable to reproduce. In dungeons you can access the map with "m" and if you want to place a custom map marker, you can press "space" to do so.

In this update2

Full notes

Full Cyclopean: The Great Abyss update

Read the full published notes in a cleaner layout. The original post stays linked below.

What changed

0 fixes0 additions6 changes0 removals
  • Maps
  • Compatibility
  • Gameplay
changedIn dungeons you can access the map with "m" and if you want to place a custom map marker, you can press "space" to do so. Occasionally, it seems to produce a wall object that will get the player stuck on that grid space, unable to escape.
changedLinux Related?The most recent report comes from a person playing on Linux, so I am wondering if that might be part of the problem. I cannot remember what the previous player was using. If anyone has seen this bug, please report in the comments and let me know which platform was being used.
changedFlying BlindSo I am trying to troubleshoot the bug without being able to reproduce it on my system for now. I moved the custom map marker so it will appear slightly above the player's head now. It is a passable entity, so the player should never get stuck on it, but it seems like that is just what is happening. So moving it up slightly might prevent these collisions from taking place.
changedFlying BlindAnother thing, I adjusted the name of the map marker model file. Previously, it had a longer name, so I shortened it, in case there was some issue with the length of the model name. It is a shot in the dark, I know.
changedFlying BlindFinally the model itself was altered. Previously it used free floating vertices to draw the lines on the map. Now I have added some polygons, so it forms a proper 3D shape in the model file. It should still only show lines on the map, but I am wondering if Linux might have trouble with a model file that has no actual 3D geometry.
changedFlying BlindThese are all just guesswork at this point. It works exactly the same as previously on my computer, so most players will not notice any difference.

Cyclopean: The Great Abyss changes

changedIn dungeons you can access the map with "m" and if you want to place a custom map marker, you can press "space" to do so. Occasionally, it seems to produce a wall object that will get the player stuck on that grid space, unable to escape.
changedThe most recent report comes from a person playing on Linux, so I am wondering if that might be part of the problem. I cannot remember what the previous player was using. If anyone has seen this bug, please report in the comments and let me know which platform was being used.
changedSo I am trying to troubleshoot the bug without being able to reproduce it on my system for now. I moved the custom map marker so it will appear slightly above the player's head now. It is a passable entity, so the player should never get stuck on it, but it seems like that is just what is happening. So moving it up slightly might prevent these collisions from taking place.
changedAnother thing, I adjusted the name of the map marker model file. Previously, it had a longer name, so I shortened it, in case there was some issue with the length of the model name. It is a shot in the dark, I know.
changedFinally the model itself was altered. Previously it used free floating vertices to draw the lines on the map. Now I have added some polygons, so it forms a proper 3D shape in the model file. It should still only show lines on the map, but I am wondering if Linux might have trouble with a model file that has no actual 3D geometry.

A couple players have encountered a strange bug that I am unable to reproduce.

In dungeons you can access the map with "m" and if you want to place a custom map marker, you can press "space" to do so. Occasionally, it seems to produce a wall object that will get the player stuck on that grid space, unable to escape.

So far, no matter what I have tried, I cannot seem to get this error to occur.

The most recent report comes from a person playing on Linux, so I am wondering if that might be part of the problem. I cannot remember what the previous player was using. If anyone has seen this bug, please report in the comments and let me know which platform was being used.

Flying Blind

So I am trying to troubleshoot the bug without being able to reproduce it on my system for now. I moved the custom map marker so it will appear slightly above the player's head now. It is a passable entity, so the player should never get stuck on it, but it seems like that is just what is happening. So moving it up slightly might prevent these collisions from taking place.

Another thing, I adjusted the name of the map marker model file. Previously, it had a longer name, so I shortened it, in case there was some issue with the length of the model name. It is a shot in the dark, I know.

Finally the model itself was altered. Previously it used free floating vertices to draw the lines on the map. Now I have added some polygons, so it forms a proper 3D shape in the model file. It should still only show lines on the map, but I am wondering if Linux might have trouble with a model file that has no actual 3D geometry.

These are all just guesswork at this point. It works exactly the same as previously on my computer, so most players will not notice any difference.

Source

Steam News / 29 March 2026

Open original post

Changelog.gg summarizes and formats this update. How we read updates.