News Liste Ready Or Not

Vol. 73 - Ready or Not Development Briefing
Ready Or Not
10.05.24 18:30 Community Announcements

Attention Officers,



Thank you for joining us for the 73rd edition of our Ready or Not development briefing, May 10th, 2024!

This week we’ll be showing some work on new AI target detection systems that make engagements feel more fair in situations where the player is partially obscured from Suspect/Civilian AI line of sight.

We have two new specific types of target detection checks under development that are meant to meet this goal of improved fairness: “dynamic visibility blockers” that make thick CS gas clouds obscure your location from AI, and “AI detection cone checks” that make you less likely to be detected between small cracks or when mostly-obscured by cover at longer distances.

We also want to highlight that this is Mental Health Awareness month and contextualize the new videos on the topic that are releasing on our YouTube channel. In this newsletter you’ll find some additional development philosophy regarding the inception of our existing SWAT AI mental health system in-game for Commander Mode.

These development briefings serve to keep you in the loop about parts of our ongoing support for Ready or Not, however the briefings do not encompass everything that we’re working on at a given moment. Please keep in mind that everything in this development briefing is work in progress and subject to change.

Vol. 73 Development Briefing Summary Points:
(not a changelog)

  • AI Target Detection Changes [list]
  • New dynamic visibility blockers that cause thick CS gas clouds to block effective AI target acquisition
  • [list]
  • AI fires at target’s last known position
[*] AI accuracy is now reduced per meter of CS gas thickness [/list]
  • New target detection “cone” checks help prevent AI from acquiring targets through unintended tiny cracks, small gaps from a distance, and acquiring peaking players from a distance or at difficult corner angles
[/list]
  • May is Mental Health Awareness Month
  • [list]
  • New thematically relevant videos releasing on the VOID YouTube channel to help bring awareness to mental health concepts present in the game[list]
  • First video is titled “PTSD”
[/list]
  • Game design insights for the inception of the SWAT AI mental health feature in Commander Mode; simply surviving is not always enough.
[/list]


AI Target Detection Changes



Both “dynamic visibility blockers” and “target detection cone checks” are WIP mechanics intended to make it more difficult for the AI to acquire the player as a target in certain challenging circumstances.

These mechanics supplement our existing static visibility blocking volumes already manually placed in maps by the Level Design team. You can can learn more about those visibility blocking volumes in our Vol. 61 Development Briefing.

The “dynamic visibility blockers” for CS gas build upon the concept of static visibility blockers, making a new form that can emerge and dissipate during active gameplay. These new dynamic visibility blockers can also penalize AI accuracy corresponding to each meter of CS gas thickness.

Meanwhile, “target detection cone checks” help static visibility blockers by preventing edge-case issues where enemies might see through tiny cracks in things like door hinges, small gaps from a distance, or odd corners.


Clouded Vision


CS Gas Dynamic Visibility Blockers

Suspect AI will no longer be able to easily see the player through a CS gas cloud once it has spread to be thick enough. This takes advantage of our gradual CS gas propagation system which requires time for gas to reach full potential area coverage.

In our current testing this means that Suspect AI will only recognize your last known position once CS gas has reached its full intensity. If they continue to engage the player they fire upon their last known position through the gas with reduced accuracy instead of actively tracking them.

In the video below you can see the green boxes indicate the gradual propagation of the gas. The yellow line between the player and suspect shows the line of sight between the two. Once the volume of gas becomes thick enough the suspect’s target detection ability becomes blocked by it, represented by the yellow line between the two turning blue.

(Video below: The blue line shows that the thick CS gas cloud is now blocking the AI’s vision)
[previewyoutube=fszWA9H1TC4;full][/previewyoutube]
(Video below: AI accuracy is reduced for every meter of CS gas that exists between them and their target)
[previewyoutube=vOxc8A53_qE;full][/previewyoutube]

Peek-a-Boo


Target Detection Cone Checks

Our system for target detection uses 4 trace locations on different parts of the players body that draw invisible lines to each AI on a given map. These 4 trace locations are: the top of the player’s head, the bottom of the player’s head, the lower left arm, and the lower right arm.

(Image below: 4 red lines on the debug interface indicate failed target detection traces to each of the 4 possible trace locations on a player. [Note: this image uses the new "cone" based system explained later])

These traces connect to every AI in the level. If both traces of a pair make it directly to an AI’s 'eyes' within its field of vision without hitting map geometry, or any manually placed visibility blocking volumes, then that AI is able to acquire the player as a target.


Old "Parallel" System:

In the previous target detection system, a pair of parallel traces ran from each trace location with a small offset between them. The fact that these two lines were simply parallel, with no angle deviation between them, ultimately caused issues.

The old system worked well in conjunction with visibility blocking volumes manually placed throughout the level; these static volumes prevented AI from seeing through things like tiny fence gaps or thick foliage.

Unfortunately, this system had a few key downsides in edge-cases.

Firstly, players could be acquired through small gaps in map geometry that would feel fair and logical if the AI was standing right nearby the gap, but unfair if the AI was standing a further distance away where this gap would make up a much smaller fraction of their field of view.

Secondly, there were sometimes issues where the offsets between traces could collapse to miniscule values, resulting in effectively only a single trace being required for an AI to detect a player. This meant that the AI could sometimes see through tiny gaps where visibility blocking volumes were missing, or where only a sliver of the player was visible.


New "Cone" System:

Our new system elegantly solves these problems by implementing several pairs of diverging traces that begin with an increased offset. Each pair of traces run to one of the four trace locations on the player's character, forming the edges of horizontal 2D "cones." Both lines of a cone from a given trace location must be successfully completed for an AI to consider a player visible.

(Image below: The player is not acquired as a target; only one line of the cone from the bottom head trace location is successfully completed. [Note: The debug overlay does not show both trace lines of a pair unless one was successful])


Therefore, this “cone” solution prevents enemies from being able to acquire the player through unintended tiny gaps, small gaps from a distance, and harder to acquire when peaking corners (especially at distance or at odd angles).

(Images below: A simplified debug interface view showing only the player’s top of head trace location line pair forming its 2d horizontal cone. At close range the player can be acquired as a target through a gap this size, but at long range the player is not detected as a target.)


(GIF below: The Suspect AI acquires the player as a target once a pair of trace lines from player has succesfully connected to the Suspect AI’s field of view. [Note: The AI has further delays or inaccuracies for when it actually begins engaging, and it may decide not to engage at all.])





May is Mental Health Awareness Month



Over the next few weeks, we’re bringing attention to Mental Health Awareness month by uploading videos which explore various concepts of mental health related to the themes present in Ready or Not.

(Video below: The first of these videos, titled “PTSD”)
[previewyoutube=HIFg98i3MWw;full][/previewyoutube]
Mental health is an aspect of the game that we wanted included in some way for a while, eventually finding its place in Commander Mode for SWAT AI. Our intention was to highlight the traumatic events that occur within the world of Ready or Not and the toll that these sorts of scenarios take not only physically, but also mentally. In the process it is meant to help make your team members feel more human.

From a dedicated game design perspective, the goal was to explore a meta game loop that reinforced the rules of Ready or Not in a way that wasn’t overly restrictive, while also reflecting the gravity with which we wanted players to think of these scenarios.

As this SWAT team you are meant to apprehend suspects, rescue civilians, preserve lives, and ultimately defuse the situation. The scenarios presented are already traumatic enough, but if on top of that if you aren’t fulfilling those goals... your team’s purpose becomes distorted and twisted. Neglecting to care for the mental wellbeing of those involved or otherwise fulfilling your mission to properly defuse situations would eventually cause enough dissonance that valuable members would leave your squad.

Simply surviving is not always enough.


Conclusion



We are continuing to tweak the WIP AI target detection changes mentioned in this newsletter and hope to be able to expand their concepts to even more areas of the game. Each variable can be fine-tuned in order to help us find the best balance to integrate with our existing game systems.

The improvements to CS gas via dynamic visibility blockers should make your engagements feel more fair and make less lethal options more attractive to control situations and sight lines, particularly on maps with open spaces.

Target detection cone checks will supplement the visibility blockers already placed in levels to help ensure engagements occur in ways that feel fair to the player. On missions that have large amounts of props combined with vast sight lines, like Greased Palms, it should help make situations where you are shot at feel more understandable without requiring map-specific tweaks or overly neutering AI combat abilities.

Lastly, we hope you are all taking good care of yourselves and each other. Mental Health Awareness month is an appropriate reminder to learn more about yourself, others, and how to best address the challenges in your own life. Don't be afraid to call on support.

This concludes our 73rd development briefing, thank you again for joining us. Be sure to fall in next time for more development news!



Follow Ready or Not on Steam here.
Our other links: Discord, X, YouTube, Instagram, Facebook.

Stack up and clear out.
VOID Interactive

Logo for Ready Or Not
Release:13.12.2023 Genre: Actionspiel Entwickler: VOID Interactive Vertrieb: Team 17 Engine:keine Infos Kopierschutz:keine Infos Franchise:keine Infos
Einzelspieler Mehrspieler Koop

Aktuelle Steam News
Neue Steam News in der ePrison Datenbank

Ready or Not: Home Invasion Bundle is Available Now
Ready Or Not
1 Tag 16:44 Community Announcements
Ready or Not: Official Soundtrack is Available Now
Ready Or Not
09.08.24 17:12 Community Announcements
Home Invasion Patch 2 Changelog
Ready Or Not
02.08.24 19:02 Community Announcements
Vol. 76 - Ready or Not Development Briefing
Ready Or Not
02.08.24 18:01 Community Announcements
Home Invasion Patch 1 Changelog
Ready Or Not
26.07.24 19:01 Community Announcements
Ready or Not: Home Invasion DLC is Now Available!
Ready Or Not
23.07.24 21:23 Community Announcements
Home Invasion Release Changelog
Ready Or Not
23.07.24 21:12 Community Announcements
Ready or Not Community Creations Exhibit
Ready Or Not
19.07.24 18:00 Community Announcements
Ready or Not | Home Invasion Trailer
Ready Or Not
17.07.24 17:02 Community Announcements
Ready or Not - Vol. 75 Development Briefing
Ready Or Not
05.07.24 17:19 Community Announcements
Ready or Not - Vol. 74 Development Briefing
Ready Or Not
07.06.24 18:04 Community Announcements
Vol. 73 - Ready or Not Development Briefing
Ready Or Not
10.05.24 18:30 Community Announcements
Ready or Not 33% off for Steam FPS Fest
Ready Or Not
15.04.24 20:29 Community Announcements
Vol. 72 - Ready or Not Development Briefing
Ready Or Not
12.04.24 19:30 Community Announcements
Vol.71 - Ready or Not Development Briefing
Ready Or Not
29.03.24 19:31 Community Announcements
Vol.70 - Ready or Not Development Briefing
Ready Or Not
15.03.24 19:20 Community Announcements
Ready or Not - Game Update 1.04
Ready Or Not
05.03.24 17:43 Community Announcements
Vol.69 - Ready or Not Development Briefing
Ready Or Not
01.03.24 19:00 Community Announcements
Ready or Not - 1.0: Hotfix #4
Ready Or Not
20.02.24 17:59 Community Announcements
Vol.68 - Ready or Not Development Briefing
Ready Or Not
16.02.24 19:03 Community Announcements
Ready or Not - 1.0: Hotfix #3
Ready Or Not
06.02.24 17:59 Community Announcements
Vol.67 - Ready or Not Development Briefing
Ready Or Not
19.01.24 19:13 Community Announcements
Ready or Not - 1.0: Hotfix #2
Ready Or Not
17.01.24 19:35 Community Announcements
Ready or Not - 1.0: Hotfix #1
Ready Or Not
18.12.23 21:55 Community Announcements
Vol.66 - Ready or Not Development Briefing
Ready Or Not
15.12.23 19:01 Community Announcements
Ready or Not - We're Live at 1.0 Launch
Ready Or Not
13.12.23 18:00 Community Announcements
1.0 Launch Major Feature Changelog, 1.0 Out Now!
Ready Or Not
13.12.23 18:00 Community Announcements
Supporter Edition Purchase Availability Conclusion
Ready Or Not
12.12.23 18:35 Community Announcements
1.0 Launch Tomorrow December 13th, @10am PST!
Ready Or Not
12.12.23 18:00 Community Announcements
Our SWAT AI Dev Vlog is on the VOID YouTube channel!
Ready Or Not
12.12.23 16:28 Community Announcements
Ready or Not Launches on the 13th of December!
Ready Or Not
08.12.23 02:34 Community Announcements
Vol.65 - Ready or Not Development Briefing
Ready Or Not
01.12.23 21:54 Community Announcements
Vol.64 - Ready or Not Development Briefing
Ready Or Not
17.11.23 19:09 Community Announcements
Vol.63 - Ready or Not Development Briefing
Ready Or Not
03.11.23 18:01 Community Announcements
Vol.62 - Ready or Not Development Briefing
Ready Or Not
20.10.23 18:08 Community Announcements
Vol.61 - Ready or Not Development Briefing
Ready Or Not
06.10.23 18:02 Community Announcements
Vol.60 - Ready or Not Development Briefing - Special PSA
Ready Or Not
22.09.23 20:37 Community Announcements
Vol. 59 - Ready or Not Development Update
Ready Or Not
08.09.23 18:00 Community Announcements