[Initial State]


We thank our sister project, 'STYGIAN ABYSS' for the temporary hosting. This is our present list of knowns, unknowns, and fixes that are yet to be deployed to the 'MK-II MISSION DATA RECREATION PROJECT', more informally known as 'EVENT ZERO'. You may expect these changes to be deployed to the next version of the project, which will be announced in the 'Devlogs' here.

  • Added
    • Data-Drop near the big filtration gate in Zone -1. Data contains information on the high risk of SAVIOR destruction as well as information on how to bypass it.
    • Battery recharge stations at key points throughout EZ-0
    • Configuration setting for mouse sensitivity (no other options other than audio options will function for the moment)
  • Fixed
    • [Out-of-bounds] Zone 4
    • [Out-of-bounds] Zone 5
  • Features in Evaluation
    • Automated hull repair tool to the laboratory
    • Savepoints/Unlockable hulls
    • Better pursuit/capture simulation for SCP-30023 // ITEM-4.
  • Known Issues
    • Longwave sonar no longer functions throughout most of the map (temporary)
    • The intro audio log auto-plays and there's no 'skip' feature for it (this'll live in the Data menu before too long and be one of your first environment pick-ups)
    • Audio logs do not respect the authority of the pause screen; this results in both audio playing irrespective of pause and subtitle de-synchronization. A fix for this is in the works and should dramatically lessen the amount of time it takes to make subs for the audio logs -- but may also take a little bit of development time to make.
    • Shortwave sonar has a very limited range. This can make Gate-code transmission a bit difficult as you must proceed to be very close to the gates in order for them to receive the key (this can sometimes present as 'BAD KEY')
    • Underwater vents make no noise when not actively firing.

Files

SaviorTB_002.zip 83 MB
Jul 08, 2023

Get Unfathomed: Event Zero

Comments

Log in with itch.io to leave a comment.

(1 edit) (+1)

I really love the concept, but would it be possible to add an option to make the lidar spraying more dense? It feels like it takes too long to get a decent picture of your surroundings at the moment.


It's cool if it's not possible, just a suggestion. :)

(3 edits)

By 'spraying' you mean increasing how quickly LMB  fires off LiDAR points?

Either way, it is certainly possible. The system I'm using can support millions of points without much FPS loss; I'm just keeping the amount low because it 'makes more sense' versus the setting of 1990s for it to be capped to (presently) 65535 points of data. (ed: That said, I am actively listening to player feedback and it's not something I would mind adjusting if there's calls for it)

I am considering on the backburner things like discoverable upgrades that expand the amount you can have scanned, scan speed, scan fade distance, scan density, and battery maximums and charge speed. Would those be things you'd be interested in exploring the exclusion zone to find?

(+1)

Hi! Yeah, I mean how quickly the LiDAR fires off points.

The upgrades sound cool. I'd still prefer a higher density for the base LiDAR if possible though. Please note that this is just my opinion (so please do ignore it if it doesn't fit in with your design plan) and I'm looking at it from a rather selfish perspective that I'd like to cover it on a YT video, but it won't make a very entertaining video if viewers can't see anything. :)

(+1)

Also, just increasing the size of the LiDAR points might help. :)

(1 edit)

Cool, I'll bear that in mind and fiddle with it some. No worries about the design plan; it's rather loose on the particulars. I'm going for a 'vibe' but there's a number of directions I can approach it from. This sort of feedback's what the open testing is all about.

That said, I do apologize for anyone who tries to stream or capture the game as some of the noise involved with this game is going to be just devastating to bitrates for modern CODECs.  That said, I suppose it does lend opportunity for whoever's capturing to try and describe what they see/saw haha

Let me know if you do some capturing and if the noise causes the quality to drop too much. I might build an accessibility feature for something more CODEC-friendly for streamers if it's too harsh/makes it difficult for viewers to see the gameplay (same with the LiDAR dots themselves in terms of shape/color/size).

Thanks for your feedback thus far, Researcher ABG. Do feel free to record/post video footage of the game wherever you'd like to as well. (Of course we'd love a link as seeing folks engage with the MK-II gives a tremendous amount of data for us to analyze and consider)