VR Survival Shooter

VR Survival Shooter is the first-person shooter in Virtual Reality: kill the zombies and save your life with full immersion in the game! Feel the power of Unity FPS VR Shooter. 

Unity FPS Package contains a demo with Google VR SDK.

Unity Asset Store | Download Button

Advantages of Unity VR Shooter

Bring the enchanting Power of Virtual Reality into your amazing Game or App:

  • Feel the effect of presence.
  • Full immersion in the game!
  • Greater coverage of devices with Google Cardboard.

Dependencies

All auxiliary Unity Assets are available for free:

Features of VR Survival Shooter

Changes are made regarding the original project by Unity Technologies.

All modules are designed independently to keep this asset extendable & easy to understand.

VR FPS

  • Google VR SDK (Customized Back Button),
  • “Iron Throne” with Player Damage Zone,
  • VR Object Detector with GvrReticlePointer (changes a material for the zombie that the player points at),
  • Complete Scene for VR.

Common

  • Menu Scene in VR,
  • Start Tutorial in Game Scene,
  • Colored Particles for Zombies.

Optimizations (Mobile, UI, etc)

  • Object Pool with separate Enemy Manager for each Zombie prefab;
  • Caching of all Components & Animation Parameters for Enemy Prefabs;
  • TextMesh PRO for Texts (Score Text is updated when it really needs),
  • UI is noticeable on Mobile in VR now (new cool design of Health UI with blinking when damaging),
  • Load Screen Control,
  • Mobile Shaders for enemies,
  • Public Unity Events for more flexibility,
  • And more…

Testing

You can test the project in the Unity Editor holding alt (option) key with Google VR SDK.

Tested With

  • iOS on iPhone 6 (by myself),
  • Android (by my clients).

Tutorial

Getting Started with VR Survival Shooter

Important: This is the docs for 2.0 version of the asset.
For the previous version use the local tutorial in the package folder.

For legal reasons, I can’t include some assets in the package, but you can get them for free separately.

If you have any issues with the first launch then just email me with Invoice Number and I will send you complete project.

I used Unity 2018.1.0f2 for this tutorial.

  • Download and import VR Survival Shooter into Unity;
  • Download and import Google VR SDK into Unity (Tested with v1.150.0);
  • Download and import Survival Shooter Tutorial with API Updating:
    • Don’t import:
      • Readme.asset;
      • Folders:
        • ProjectSettings,
        • TutorialInfo;
  • Reopen Unity VR project;
  • Test in the Unity Editor or build for mobile.

Related Shooter Game

AR Survival Shooter (docs).

Changelog

2.2:

  • Google VR SDK v1.150.0 support.

2.1:

  • Unity 2018.2 version;
  • TextMesh Pro texts for Menu Scene.

Read more about TextMesh Pro for Unity 2018.2.

2.0 (New Architecture — Object Pools):

EnemyManagersXRControl initializes each zombie type (EnemyManagerXR with Object Pool) now (more performance). There are 3 object pools in total: ZomBunny, ZomBear, Hellephant.

  • Unity 2018.1 version;
  • Object Pool with separate Enemy Manager for each Zombie prefab;
  • Caching of all Components & Animation Parameters for Enemy Prefabs;
  • Start Tutorial in Game Scene.

Optimizations:

  • Merge EnemyMovementXR.cs with EnemyHealthXR.cs;
  • InvokeRepeating () => Coroutine in EnemyManagerXR.cs;
  • Set “navMeshAgent.enabled = false;” once after Death;
  • Enemies are disappearing right after death now.

1.1 (More Complete Project as a Separate Game):

  • Shoot Animation,
  • VR Menu Scene,
  • Load Screen Control,
  • Colored Particles for Zombies,
  • Mobile Shaders for enemies,
  • Public Unity Events for more flexibility,
  • And more…
Support for Unity Assets
I am Andrew Sirota, Founder at Makaka Games and full-time Publisher on Unity Asset Store. First of all, read the latest docs online. If it didn’t help, get the support.
Related Articles
Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button

Spelling error report

The following text will be sent to our editors: