Unity Plugin:

• Updated plugin to work with new app. Plugin no longer cycles trackers when screen tapped.
• Plugin now responds to tracker selection commands from the server.

Android App:

• Fixed feedback and help items not actually going anywhere. (Help no longer says "No Help For You!" in a toast message).
• Fixed servers not searching without tap and drag action in the server browser.

Fixed bug where calibration UI would be hidden in immersive mode due to android bug.

• Added menu when back button pressed while streaming.
• Added menu item to explicitly disconnect from server.
• Added menu item to recalibrate ARCore in the "back menu".
• Added menu item to select tracked object in the "back menu".

Mod Installer:

• Now checks added games against list of known modded games, if the names are the same, it will use the known configs for that game. This was done for Oculus users who have to locate their games manually.
• Added support for the following games;
• Mindshow
• Budget Cuts
• Removed support for Beat Saber at their request.

Because of how quickly the implementation of position tracking was made, it has an awful user interface. We're kinda relying on developers to create a good one for us.

To use the tracker tracked experience, select the externally tracked option in the app.
When you connect to a modded game, tapping on the screen will cycle through the different trackers.

If the game has SteamVR set as its tracking system in the configs, you'll have 16 different tracked objects to choose from, always. the first 3 are usually the headset, and controllers, then you'll have your tracked non-controller objects.

If the game has UnityXR set as its tracking system in the configs, you'll have 6 + (number of base stations) + (number of trackers) objects to choose from. Each tap will set you to a different tracked object, you'll cycle between headset, 3 untracked objects that are meant to be left, right and "center" eye, the 2 controllers, the base stations, then get to your trackers.

You want to ensure that the tracker offsets are set correctly in the viewrcamera.cfg file as well. You can find out by experimenting with the numbers.

Find out about how we attached trackers here.

Recording.... is an awful hack at this stage, but it lets us capture footage in the most basic sense. It will be much more heavily optimized before we announce it as an actual feature.

Warning, using this feature bug has a very good chance of crashing your game... but we're going to tell you how to do it anyway.

To start off, you'll need:

• An android device that has ViewR installed.
• If the aforementioned device doesn't have ARCore, a tracker for your VR setup
• VR ready computer
• The pc we used had a GTX 1080, 6th gen Intel i7, and the game installed on an SSD.
• We tried it on a laptop with an external 1080, and it was quite laggy, even with an SSD.
• ReNumber
• ffmpeg

First off, you want to enable the setting in viewrcamera.cfg. Open up that file in the game you wish to record and set allowrecording to true. You can see our lovely warning in the file as well.

Don't forget to also match the tracker offsets and field of view in viewrcamera.cfg as well.


Now you want to boot up your game and connect ViewR.

Once you have calibration setup, be it with ARCore or with SteamVR tracking. Pressing E on your keyboard will start recording. You can tell if it's started recording by checking the game folder for a new folder with something like the current unix epoch time in millis.


In game, the user may experience a performance hit. This is caused by us writing a huge amount of data to the hard drive. This problem is sometimes remedied by moving the game to an SSD (we'll fix this before actual release). To finish recording, press E again, this is the part which may or may not crash your game. Once we're done, your folder will be filled with jpegs.


Now, click and drag the folder over ReNumber.exe. Windows will pop up with a warning, accept the warning to run the app. If you don't trust us, you can download the source, read it, and compile it yourself. ReNumber will generate a text file in your folder called input.txt.

If you haven't done so already, download ffmpeg and add it to your computer's path. Google will tell you how to add the ffmpeg folder to path.

Once that's done, you want to open powershell in that folder and run the following command.

ffmpeg -f concat -i input.txt -vf "transpose=2" -vcodec libx264 -crf 15 -pix_fmt yuv420p capture.mp4

The number after transpose specifies which direction to rotate the frames. StackOverflow kindly tells us that:

• 0 =  90CounterCLockwise and Vertical Flip  (default) 
• 1 = 90Clockwise 
• 2 = 90CounterClockwise 
• 3 = 90Clockwise and Vertical Flip

If you've done so correctly, you'll see the matrix scrolling by.

Modding ViewR into games that run Unity is quite simple but takes time. The mod uses Illusion Plugin Architecture to inject code into Unity to run, very similarly to how Beat Saber mods are made.

To start off with, the requirements that we've discovered are:

• Unity must be in 64bit (discovered from Space Pirate Trainer, which is apparently 32bit) 
• The game must be newer than Unity 5.5 (discovered from The Lab which runs 5.4)

Start by installing IPA in the game that you wish to mod. You can do this through the mod installer, or installing all the components manually.

Using the ViewR mod installer

Download the latest mod installer here.

To mod ViewR into a Unity game that we haven't added to our games list yet, click the add button and find your game, and click OK.


You should be able to see your game added to the list.

Then click patch and wait for the matrix to finish loading.

Setting Configs

Once IPA is installed, also download and place PressPToPause in the plugins folder. We'll use this to explore the Unity scene.



Once all the files are in the required places, run the game in --verbose mode.



This should launch the game with a console window (which is helpful but not necessary).



When the game has launched and VR is working, click on the game window and press x on your keyboard to dump the hierarchy to a file.


In the file, locate where the headset is. This is usually marked with <<<Camera.main>>> or the like.


Copy the names of the headset, and the play space GameObjects to the viewrcamera.cfg file. Also, find out which MonoBehaviours to add to the camerabehaviourfilter (this is mostly through trial and error, sometimes incredibly obvious).


Find out if the game uses SteamVR or UnityXR. This can usually be found by checking the attached scripts on the hmd object for scripts starting with SteamVR_*. UnityXR tends to be used for Unity games running unity 2017 and higher, you can find this at the top of the logs that are shown at the top of the --verbose console. Once you've figured that out, fill in the field in viewrplugin.cfg.


Find out if the game initializes VR later than when the game starts. This can usually be told from whether or not there's a VR hmd/play space when the first loaded scene is dumped.

Culling layer settings, regenerate camera, and allow hdr tend to be trial and error.

Once these settings have been set. ViewR should work with the game you've modded. (And ayy, it worked first try).


(I don't know if budget cuts actually got modded correctly, at this point I'm too tired to actually test it properly with a headset. I'll come back and fix this later if you guys tell me it's actually broken.)

ViewRInterface manages incoming and disconnecting devices.

Editor Params

Target
The headset transform, setting this lets users calibrate based on headset location. If both Target and Origin are set, calibration will be based on the ground directly below the headset.

Origin
The play space transform, setting this lets users calibrate based on play space location. If both Target and Origin are set, calibration will be based on the ground directly below the headset.

Data Port
This is the port which ViewR App will communicate through. This port is usually communicated through the server search procedure. But if the server isn't found by by the server list on the app, use the manual connect button on the app and use the port shown here and see if it works.

Device Object
This is the object that will be instantiated on device connection. You can change what gets instantiated by default by setting an object here.

Events

DeviceConnectEvent
Triggered when a client connects to server.

DeviceDisconnectEvent
Triggered when a client disconnected from server.

Getting started with ViewR is quite simple.
 You should also be able to see this in the editor.


If there is someone in VR, the frozen VR head in the middle of the world will follow them, and you'll be able to see them with ViewR. They will also be able to see you

The VR player can also explode blocks into different colours.

Congratulations, ViewR is now working on your computer. Source code for the demo scene is available on our Github.

For our tracked footage, we've used one of three rigs to attach Vive trackers to our cameras/phones/tablets. Which we'll provide information about here. If you have your own 3D printer or if you could find

Phone Clip

Parts

• 5/16 x 1/4in Countersunk bolt
• Phone Bracket
• 3D Printed Printed Part

Suction Cup

• Suction cup

Camera Hot Shoe

Parts

• 5/16 x 1/4in Countersunk bolt
• 3D Printed Printed Part