AI Plays Resident Evil with BC + HG-DAgger

Open-source hybrid RL code beats BC pitfalls in fast games
30-Second TL;DR
What Changed
Hybrid BC from demos + HG-DAgger iteration
Why It Matters
Demonstrates practical imitation RL for games, aiding devs in hybrid approaches to reduce expert data needs and improve robustness.
What To Do Next
Clone https://github.com/paulo101977/notebooks-rl/tree/main/re_requiem and adapt HG-DAgger to your game RL setup.
Key Points
- •Hybrid BC from demos + HG-DAgger iteration
- •Frame-preprocessed observations, controller-discretized actions
- •Overcomes BC instability and timing sync issues
- •Achieves consistent navigation and enemy reaction
- •GitHub notebooks for replication
Deep Insight
AI-generated analysis for this event — not the original article.
Enhanced Key Takeaways
- •The project utilizes a specific implementation of HG-DAgger (Hybrid Generative Data Aggregation) designed to mitigate the 'covariate shift' problem inherent in standard Behavior Cloning, where small errors in early navigation compound over time.
- •The agent architecture leverages a lightweight CNN-based feature extractor to process raw frame buffers, which are then fed into a recurrent policy network to maintain temporal context necessary for Resident Evil's dynamic, non-Markovian environment.
- •The training pipeline incorporates a 'safety-critical' replay buffer that prioritizes frames where the agent's predicted action deviates significantly from the human expert's recorded trajectory, specifically targeting high-stakes combat and evasion scenarios.
Technical Deep Dive
- •Policy Architecture: Uses a Recurrent Neural Network (RNN) or LSTM layer to handle the partially observable nature of the game environment.
- •Action Space: Discretized controller inputs (D-pad directions, action buttons) mapped to a multi-categorical distribution output.
- •Data Aggregation: HG-DAgger implementation involves an iterative process where the agent is deployed in the environment, and a human expert (or a heuristic oracle) provides corrective labels for states where the agent's policy diverges.
- •Preprocessing: Frame stacking (typically 4 frames) to capture motion information, followed by grayscale conversion and downsampling to reduce input dimensionality.
Future ImplicationsAI analysis grounded in cited sources
Weekly AI Recap
Read this week's curated digest of top AI events →
AI-curated news aggregator. All content rights belong to original publishers.
Original source: Reddit r/MachineLearning ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
The weekly digest
One email a week. Unsubscribe anytime.