The problem Military Educator solves

The Problem It Solves

1. Bridging the Gap Between Civilians and Defense Tech Most people never get the chance to see heavy military assets (like warships, submarines, or battle tanks) up close. They are restricted, dangerous, or located in specific bases. This app democratizes access, allowing anyone to bring these massive assets into their living room or classroom to explore them safely and in detail.

2. Transforming Passive Learning into Active Exploration Traditional methods of learning about the Indian Army—textbooks, 2D photos, or video clips—are passive. They don't convey the true scale or complexity of the machinery. This AR application solves this by providing immersive, spatial visualization. Users can walk around a tank, inspect a ship from different angles, and understand the scale of the equipment relative to their own environment.

3. Zero-Cost, Risk-Free Training & Education For students, cadets, or defense enthusiasts, examining real equipment is expensive and logistically difficult. This app solves the logistical nightmare of physical field trips. It serves as a safe, portable digital museum, making defense education accessible without the need for physical travel or security clearance.

4. Inspiring the Next Generation By making the Indian Army's assets interactive and "gamified" through Augmented Reality, the app engages younger audiences in a way that static images cannot. It acts as a modern tool for inspiration and recruitment, sparking curiosity about engineering and defense careers among youth.

Challenges we ran into

Challenges I Ran Into

1. The "Grey Screen" Configuration Nightmare One of the biggest hurdles was getting the AR camera to actually render on the device. After building the APK, the app would launch but only show a static "grey skybox" instead of the camera feed.

The Bug: The app was treating the project as a standard 3D game rather than an AR experience.

How I Solved It: I dug into Unity's XR Plug-in Management and realized the "Google ARCore" provider wasn't explicitly enabled. Additionally, I discovered that the Vulkan graphics API was causing crashes on Android. Switching the graphics API to OpenGLES3 and enabling the ARCore plugin instantly fixed the feed.

2. The "Infinite Clones" Logic Error Initially, my TapToPlace script was too simple. Every time I tapped the screen to move the 3D model, it would Instantiate (spawn) a new copy of the tank/ship. Within seconds, my room was filled with overlapping models.

How I Solved It: I refactored the C# script to check if the object already exists (spawnedObject != null). If it does, the code now simply updates the position of the existing object to the new raycast hit point, rather than spawning a new one.

3. The "Invisible Model" (Pivot Point Offset) When I imported my .glb models from Blender, the AR placement felt broken. I would tap the floor, but the tank would spawn 3 meters to the right or behind a wall, making it look like the app wasn't working.

The Bug: The pivot point (origin) of the model in Blender wasn't set to (0,0,0), and the export had a massive transform offset.

How I Solved It: I learned to "freeze transformations" in Blender before exporting. In Unity, I created a parent prefab to zero out the position (0,0,0) and standardized the scale to 0.1 so the heavy machinery fit realistically inside a room without clipping through the ceiling.