Add project writeups
This commit is contained in:
parent
b20139cb60
commit
e5a219499e
17 changed files with 743 additions and 0 deletions
25
src/content/posts/city-simulation-unity-traffic.md
Normal file
25
src/content/posts/city-simulation-unity-traffic.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
title: A Unity City Simulation for a Cybersecurity Challenge
|
||||
description: A client-server Unity simulation where REST-controlled traffic lights made mistakes immediately visible through crashes.
|
||||
date: 2026-05-01
|
||||
projectPeriod: 'July-August 2018'
|
||||
thumbnail:
|
||||
src: ./_assets/city-simulation.jpg
|
||||
alt: Screenshot of a Unity traffic simulation.
|
||||
tags: ['simulation', 'systems']
|
||||
role: Simulation author
|
||||
stack: ['Unity', 'C#', 'REST API', 'Blender']
|
||||
outcome: A visual context for a PLC-focused cybersecurity challenge
|
||||
audience: technical
|
||||
links: []
|
||||
---
|
||||
|
||||
I simulated a city where car crashes were more frequent than usual.
|
||||
|
||||
The state of the traffic lights could be changed through a REST API. Drivers followed the instructions of those lights, so if a mistake was made, collisions appeared in the simulation. There was also support for displaying tweets on a HUD.
|
||||
|
||||
The project was the context for a cybersecurity challenge about PLCs. Contestants could see the effect of their work immediately, as crashes.
|
||||
|
||||
The architecture was server-client. Every decision of the agents was calculated server-side, and the real challenge was broadcasting those decisions in a fault-tolerant way on minimal bandwidth.
|
||||
|
||||
It was built in Unity with C# as the scripting language. I also made the models and animations in Blender.
|
||||
Loading…
Add table
Add a link
Reference in a new issue