MH Warfare

# MH Warfare 0.4.0 Beta 2

The second public beta release of MH Warfare is now available.

This update focuses on a much more stable long-range FPV experience, the new Chuyka 4.0 passive video-interception system, improved high-speed Remote View streaming, multiplayer fairness, more precise mortar controls, operator-relative spatial audio, bounded explosion and smoke effects, improved own-airframe FPV rendering, updated Baba Yaga and Chuyka models, and a large collection of stability and rendering fixes.

## Highlights

- Added the Chuyka 4.0 passive FPV video detector and interception receiver

- Significantly improved high-speed and long-range Remote View streaming

- Improved multiplayer fairness for multiple active fast drones and Remote View sessions

- Added separate control, video, telemetry, and navigation signal channels

- Added reliable high-speed Molniya-1 swept entity contact

- Added precise 1-degree mortar azimuth adjustment and held-input rotation

- Added operator-relative spatial drone and incoming-mortar audio

- Added bounded explosion debris, terrain-following smoke, hot plumes, LOD, and volumetric airburst clouds

- Improved own-airframe visibility in FPV for supported drones

- Fixed Chuyka camera direction, water/translucent rendering, and player geometry

- Added refreshed Baba Yaga and Chuyka 4.0 models

## Chuyka 4.0

- Added the portable Chuyka 4.0 passive analogue FPV detector

- Added four receiver bands: 1.2 GHz, 3.3 GHz, 5.8 GHz, and 8.6 GHz

- Added a stepped full-band scanning cycle

- Added read-only interception of eligible unencrypted analogue FPV video

- Added live intercepted video to the held Chuyka screen

- Added live service information to the physical status screen

- Added red signal-detected and green no-signal indicators

- Added a local warning chirp for newly detected compatible video signals

- Added Chuyka alert enable/disable and volume controls

- Added an internal battery simulation and external battery packs

- Added a dedicated receiver menu and scanning interface

- Added English, Ukrainian, and Russian localization for the receiver

- Detection remains server-authoritative

- Digital, encrypted, fibre-optic, and satellite traffic is not exposed by the receiver

- Intercepted video is read-only and does not grant flight, payload, or detonation control

- The scan packet does not expose source coordinates, direction, distance, platform name, or owner identity

- Powered receivers can continue scanning while carried in the player inventory

- Manual signal selection survives closing and reopening the receiver interface

- Automatic tuning follows the nearest eligible analogue source when no manual selection is active

- The held screen and GUI reuse the same Remote View stream instead of creating duplicate world sessions

- The player world remains visible normally while the intercepted drone view is rendered into a dedicated offscreen target

- Repeated held/menu transitions no longer unnecessarily tear down and recreate the Remote View session

- Added warm isolated-renderer reuse for faster repeated Chuyka activation

- Fixed the intercepted camera using an unconfigured or stale offscreen camera transform

- Fixed intercepted video pointing in a different direction from the actual drone camera

- Fixed water and translucent terrain becoming stretched, detached, or screen-space aligned

- Fixed player/entity geometry becoming stretched or displaced inside the Chuyka video

- Matched the isolated renderer auxiliary targets to the Chuyka framebuffer size

- Preserved the normal player camera, render target, and sound listener after every offscreen pass

- Updated the Chuyka 4.0 physical model with a wider video screen

- Reduced the top and bottom letterbox area without stretching or cropping the intercepted image

## Signal and Electronic Warfare Foundation

- Split drone links into independent control, video, telemetry, and navigation roles

- Added transport metadata for analogue RF, digital RF, fibre optic, satellite receive, and disconnected links

- Added band, logical-channel, encryption, jamming-resistance, and interception metadata

- Added server-authoritative quality, latency, packet-loss, interference, and link-state snapshots for each channel

- Added role-specific range calculations while preserving existing compatibility paths

- Extended direct and SYCH-1 relay routes to calculate channel state independently

- Added platform signal profiles for SYCH-1, Wild Hornets, Mavic, P1-SUN, Molniya-1, and Baba Yaga

- Separated camera sensor type from video transport

- Added analogue RF video artifacts including noise, scanlines, desaturation, sync tearing, and moving static

- Added digital video degradation including macroblocks, unstable-frame masking, and hard video loss

- Preserved clean video behavior for non-RF transports where applicable

- Added additional signal diagnostics for control, video, and telemetry quality

## Remote View and High-Speed Flight

- Reworked high-speed Remote View scheduling around camera-critical terrain

- Added predictive, camera-critical, and background streaming lanes

- Added bounded world-generation admission instead of repeatedly restarting unresolved generation work

- Added server load-governor and headroom checks for expensive terrain work

- Added bounded stream leases and loading ownership

- Added persistent progressive renderer-liveness recovery

- Avoided synchronous full renderer rebuilds during normal high-speed flight recovery

- Decoupled guaranteed camera coverage from predictive forward lead

- Added a client-ready bootstrap so useful first-flight delivery begins when the isolated renderer is ready

- Improved stream-center stability during fast flight

- Improved stale-packet rejection when the camera window moves

- Improved terrain and light delivery pacing

- Improved Remote View continuity through fresh terrain

- Preserved responsive drone control while background terrain is allowed to fill later

- Improved P1-SUN operation at approximately 300+ km/h without force-loading the full visual window as an entity-ticking area

- Distant background pop-in may still occur at very high speed, but camera-critical terrain and control are prioritized

- Improved recovery from temporary remote-renderer terrain loss

- Preserved the accepted Remote View radius and avoided uncontrolled radius inflation

## Multiplayer and Session Fairness

- Added fair-share physical corridor scheduling for multiple fast drones

- Added rotating/round-robin ordering instead of allowing one active drone to permanently monopolize shared loading work

- Improved shared unresolved-load behavior for simultaneous high-speed aircraft

- Preserved per-viewer Remote View session isolation

- Preserved per-session acknowledgement and readiness handling

- Preserved server-authoritative control ownership and validation

- Improved behavior when multiple Remote View pilots are active at the same time

- Kept expensive shared work bounded to protect server tick time

## Molniya-1

- Added bounded swept entity contact for high-speed Molniya-1 flight

- Reduced the chance of valid entity impacts being skipped between server ticks

- Preserved the existing Molniya-1 flight model, launcher flow, damage, and detonation systems

- Kept collision handling bounded instead of adding an expensive unrestricted sweep

## Mortar Controls

- Added precise 1-degree mortar azimuth adjustment

- Added bounded held-input repeat for smoother continuous rotation

- Replaced coarse azimuth jumps with more controllable aiming behavior

- Preserved existing mortar ballistics, ammunition, firing modes, damage, and Remote View synchronization

## Spatial Audio

- Improved drone audio direction relative to the actual operator/listener context

- Improved incoming mortar whistle direction while using FPV and Remote View

- Restored the correct local sound listener after Chuyka offscreen rendering

- Preserved existing radio and proximity-voice systems

## Explosion and Smoke Visuals

- Added bounded explosion visual budgets

- Added terrain-textured debris without unbounded entity creation

- Added persistent near-surface smoke with controlled lifetime and density

- Added terrain-aware smoke placement using loaded-world information

- Added rising hot-plume behavior

- Added ceiling-aware lateral smoke flow

- Added distance-based LOD and deterministic update staggering

- Reduced the chance of large barrages producing synchronized visual spikes

- Added irregular volumetric airburst smoke for true aerial detonations

- Added multi-lobe airburst shapes instead of flat or uniform clouds

- Kept particle budgets bounded for normal and Remote View rendering

- Preserved gameplay damage independently from visual smoke complexity

## FPV Camera and Airframe Improvements

- Improved own-airframe visibility in FPV for Wild Hornets, P1-SUN, Molniya-1, Mavic, and Baba Yaga

- Kept physically appropriate parts of the drone visible to the operator

- Hid only the camera/gimbal subtree where necessary instead of hiding the entire aircraft

- Preserved SYCH-1's established camera behavior

- Fixed Baba Yaga's camera mount so it follows body yaw, pitch, and roll

- Removed the old yaw-only/world-up camera offset behavior

- Prevented Baba Yaga front geometry from incorrectly entering the FPV lens during body rotation

- Updated the Baba Yaga model and synchronized the camera mount with the new authored geometry

- Updated the Chuyka 4.0 model while preserving functional screen, indicator, antenna, and control bones

## Performance and Stability

- Reduced unnecessary renderer teardown/recreation during repeated Chuyka use

- Reused a quiescent warm renderer shell where safe

- Kept expensive terrain work bounded by server load and per-owner budgets

- Improved fairness between simultaneous high-speed drone workloads

- Reduced the risk of repeated synchronous renderer refreshes during flight

- Preserved packet pacing and stale-session protections

- Preserved registry IDs, UUID workflows, and compatible saved drone data

- Preserved normal player-world rendering while Remote View operates in an isolated client world

- Preserved dedicated-server classloading separation for client-only rendering code

## Fixed

- Fixed high-speed Molniya-1 entity impacts being missed between ticks

- Fixed coarse mortar azimuth stepping

- Fixed repeated Chuyka held/menu transitions causing unnecessary Remote View teardown

- Fixed repeated Chuyka activation paying the full isolated-renderer setup cost every time

- Fixed Chuyka intercepted video using the wrong camera transform

- Fixed the Chuyka image heading disagreeing with the physical drone camera heading

- Fixed broken water/translucent composition inside the Chuyka monitor

- Fixed water appearing as a large screen-space wedge or floating layer

- Fixed local and remote player geometry becoming stretched or displaced in Chuyka video

- Fixed mismatched auxiliary render-target sizes during the Chuyka offscreen pass

- Fixed Baba Yaga FPV camera placement not following full aircraft body rotation

- Fixed several own-airframe FPV visibility inconsistencies

- Fixed several long-range Remote View renderer-liveness and stale-terrain edge cases

- Fixed unfair shared physical loading behavior between multiple fast drones

- Fixed several spatial-audio listener-context inconsistencies during Remote View

## Visual Improvements

- Added improved analogue FPV interference presentation

- Added live video and service displays to the Chuyka 4.0 model

- Added functional Chuyka alert indicators

- Added a refreshed wider Chuyka physical video screen

- Added updated Baba Yaga and Chuyka models

- Added more natural explosion debris and smoke presentation

- Added hot-plume, ceiling-flow, LOD, and volumetric airburst smoke behavior

- Improved the amount of the controlled drone body visible in FPV without blocking the camera

- Preserved English, Ukrainian, and Russian localization parity

## Compatibility

- Preserved dedicated-server support

- Preserved existing registry IDs

- Preserved existing drone UUID and Drone Registry workflows

- Preserved compatible NBT data for existing supported platforms

- Preserved keyboard, mouse, and joystick control systems

- Preserved universal ordnance and mortar compatibility

- Preserved electronic warfare, radio, and native proximity-voice systems

- Preserved Remote View session isolation and server-authoritative control validation

- Install the same MH Warfare build and GeckoLib version on every client and server

## Fibre FPV Scope

Experimental Khizhak-13 fibre-optic FPV development is not included in the player-facing Beta 2 release. The fibre drone, spool, cable-physics, snag, remnant, and related experimental systems remain archived as separate future R&D and are not required by this release.

## Requirements

- Minecraft Java Edition 1.20.1

- Minecraft Forge 47.4.x

- Java 17

- GeckoLib 4.8.4 or newer compatible 4.x version

- Installation on both the client and dedicated server

## Important

MH Warfare remains beta software.

Although this release has received extensive development and runtime testing, edge-case bugs, balance issues, very-high-speed distant terrain pop-in, and mod compatibility problems may still occur.

Back up important worlds before updating. The same MH Warfare and GeckoLib versions must be installed on the client and server.