Presentation Video Link:

Introduction:

Install Introduction:

Github:

Unity 2019.4.28:

Unity hub:

Blender:

How to use:

1. Download the latest Github zip file. Download and install the corresponding Unity version and the latest Blender.

2. Export the zip file to your folder. It is recommended to confirm that the path name of the target folder is all in English before exporting, otherwise it may cause an error during import.

3. Use unity hub to add the folder, then you can open the project. Before opening, please make sure that your unity version number is 2019.4.28, it will be displayed to the right of your project name.

4. When you open it for the first time, Unity will take some time to install the library. This may take a few minutes, no need to worry.

5. After opening the project, the default will enable "CameraRigs.UnityXR" and disable "CameraRigs.SpatialSimulator". If you want to use a computer to simulate the operation of the software, you need to disable "CameraRigs.UnityXR" and enable "CameraRigs.SpatialSimulator". If you use a VR headset, such as Quest1, then you don't need to change these.

6. In the building setting, please make sure that your platform is Android, so that you can export the updated apk and deploy it to your VR device.

Citation:

Self Model:

*Physics and collision

Most of the physics and collisions are used for interaction, such as grabbing. The trick face and meat need to be dropped to the ground, so physics and collisions are also increased.

FPS:

The above is an FPS screenshot of when I used the sword to attack the monster. Under normal circumstances, the FPS in the scene will remain at a high level. Such as ordinary actions, simply taking various things or throwing things.

However, in more complex collision situations, the number of frames may be reduced. For example, when fighting, or when triggering traps to generate a large number of touchable trick faces. When these newly generated objects collide with players, ground, monsters, tables, swords and other objects, a large number of calculations may be generated at the same time, resulting in stuttering and dropped frames. And this has nothing to do with the complexity of the model. Even a simple model may cause frame drop.

Discussion:

The experience of the simulator and using the VR headset is completely different. When using the emulator to play games, our eyes are always staring at the screen, which is no different from playing other games. With a VR helmet, the game scene will rotate as we turn the angle of view. Therefore, in terms of the immersion of the picture, the VR helmet is much better than the simulator.

However, although the immersion of the simulator is not as good as the VR headset, the image effect of the simulator is more stable. I wear glasses myself, so when using a VR helmet, it doesn't always fit well with the helmet. At this time, the picture in the VR headset will become very blurry for me, and I cannot see the content on the screen clearly. And because the VR helmet is not always connected to the computer, the GPU integrated in the helmet will not be too good, which leads to limitations on the screen resolution and refresh rate of the VR helmet. With the emulator, I can use a very good monitor, and use a powerful graphics card to output a large number of frames. The fluency and clarity of the whole world will be better than VR headsets.

At the interactive level, the overall performance of the simulator is much worse than that of the VR headset. The simulator will use WASD to move, the mouse to rotate the angle of view, then Q teleport, E to operate the switch, 23 to adjust the left and right controllers, 1 to return. Most functional simulators can be simulated, but the actual performance of the simulator is not ideal.

Let me talk about adjusting the left and right controllers first. In a VR helmet, the helmet automatically tracks the state of the controller, so it can be said that the state of the controller is basically the same as what we want. In the simulator, if we want to adjust the right controller, we need to press 3 to enter the adjustment. Then, use WASD to control the position, and use the mouse to control the rotation. But the speed of this control cannot be adjusted, so it becomes difficult to control. For example, I want to extend the controller slightly forward, but I may lightly tap the W key, which will increase the distance of the controller a lot; similarly, the adjustment of the rotating controller is also very troublesome and requires specialization. Stop to adjust. Even if the adjustment of the simulator becomes very proficient, these steps cannot be omitted, so the simulator cannot be the same as the VR helmet, so that the state of the controller is consistent with what we want at any time.

In addition, the interaction of the simulator is not exactly the same as in the VR headset. For example, WASD mobile is mainly used in the simulator, and Q teleport is rarely used. The VR helmet is limited by the actual space, and Q teleport will be used more often. In VR headsets, if we want to grab things, throw things, or wave things, this will be closer to our actual habits in life. In the simulator, if I want to swing a sword, I will use the mouse to rotate the screen continuously; throwing things is also by rotating the screen to create "force". These operations in the VR headset are like shaking their heads all the time, and they cannot simulate the actual interaction logic very well.