Engine Core Architecture
Rerpess Studio's proprietary engine is built for maximum efficiency across modern hardware stacks. Explore the modular subsystems that power our interactive experiences.
Physics Engine
- Deterministic rigid body simulation
- Optimized for mobile SoC constraints
- Sub-millisecond collision detection
- Unity-compatible serialization
Renderer
- Vulkan/Metal cross-platform backend
- Built-in occlusion culling
- Deferred lighting pipeline
- Asset streaming over WebSocket
Audio Subsystem
- Real-time spatialization
- Adaptive music layering
- Lossless compression codec
- Sub-10ms latency on iOS
Mobile Optimization
- Thermal throttling detection
- Dynamic resolution scaling
- Memory footprint tracking
- Battery-efficient rendering
Candle Gazer & Night Trader: Flicker Engine
Our proprietary lighting system simulates organic candle flicker and nocturnal market volatility patterns. Originally developed for a horror adventure title, the algorithm now powers dynamic environmental storytelling across our entire portfolio.
- Physically-based light decay modeling
- Market sentiment correlation engine
- Procedural noise generation
Rerpess Studio Field Guide
Core Concept: Engine Modularity
Rerpess Studio builds every project on a modular architecture where physics, rendering, and audio operate independently. This isolation allows our team to push updates to the physics subsystem without destabilizing the renderer, crucial when deploying cross-platform titles to mobile devices.
When you join a development sprint, you'll work within this modular framework. Each module exposes a strict API contract, preventing spaghetti code and ensuring that your physics implementation doesn't accidentally trigger audio events.
Decision Criteria
- →Mobile Performance: If your feature consumes >15ms per frame on a Snapdragon 888, it must be refactored.
- →Cross-Platform Stability: Code must compile for Android, iOS, and WebGL without conditional compilation hell.
- →Asset Size: Total package must stay under 50MB for initial download. Use streaming for larger assets.
Myth vs. Fact
Myth: "Custom engines are always slower than Unity."
Fact: Our engine's physics module outperforms Unity's built-in system by 18% on mobile targets due to our lightweight collision detection and lack of legacy overhead.
Myth: "Modular systems introduce latency."
Fact: IPC (inter-process communication) overhead is negligible on modern devices, and our strict API contracts actually reduce overall system latency.
Key Terms
- Deterministic Physics: Simulation that produces identical results given identical inputs, crucial for multiplayer sync.
- Thermal Budget: Maximum sustained compute cycles before device throttling occurs.
- Asset Streaming: Loading game assets in real-time over network rather than bundling them in the initial download.
- Render Pass: A distinct phase of rendering (e.g., geometry, lighting, post-processing) that groups draw calls.
Common Mistakes
- Over-coupling physics with rendering updates (breaks mobile performance).
- Ignoring audio latency budgets (causes sync issues in rhythm games).
- Shipping unstripped binaries (doubles package size unnecessarily).
- Hardcoding platform-specific input handling (creates maintenance nightmares).
- Skipping thermal testing on mid-range devices (leads to throttling in production).
Engine Inquiries & Partnerships
Interested in licensing our modular engine architecture for your next project? We provide technical documentation, SDK access, and direct integration support for qualified studios. Reach out with your project scope and we'll schedule a technical deep-dive with our core engineering team.
Contact Information
- Address:
- Merrion Square 140, Limerick
- Phone:
- +353 87 7539243
- Email:
- info@rerpess.com
- Hours:
- Mon-Fri: 9:00-18:00
Dublin Night Operations
Development center active since 2011
Signals of Trust & Quality
Measured across 50+ device profiles during thermal stress testing.
Engine maintains sub-50MB footprint for 2D project baseline.
Shipped across iOS, Android, and Web platforms since 2011.
Scenario-Based Feedback
"The modular architecture saved us three weeks on our last mobile port. We could update the physics without touching audio code, which meant fewer regressions."
"The thermal throttling detection actually works. Our QA team noticed the engine scaling resolution automatically on older test devices, preventing crashes."