When I first watched the trailer for Island 359 I was excited, the idea of hunting dinosaurs from my own home in VR gave me a big smale then I thought about it and started to worry if my AMD RX-480 was up to it. So I lashed out and got it worst case would be that I would have to run it on low setting right?
To test the experiences and games I have on the HTC Vive I wanted to come up with a way to show you and tell you about my experience in VR. Benchmarks in the usual sense can’t demonstrate what the experience is actually like. I chose six different VR games or experiences that exemplify the broad range of VR titles I have been playing around with. I then deliberately picked a section of the game or experience that I could repeat over and over. In the VR headset there is an option (under Settings > Performance) that allows you to be notified with a pop-up during gameplay when drop frames occur. So I turned that on. First run through: I played through the section. Second run through: I recorded Mirror footage from the desktop as it shows what’s happening in the hud, but please note it will not show dropped frames and is only in the video to give you an idea to what’s going on in the game or experience to match the frame data . Third run through: I recorded the frame timing window using the windows game recorder in Windows 10 (Windows Key + G). I then put the two videos together to show what the system was doing at specific times in the game or experience. So the videos that I have produced to show you what VR is like on this budget PC show two recordings overlayed on top of each other: 1) the game or experience and 2) the frame time data, synchronised with the game footage. This provides me with a true representation of what the performance is like. If you watch the far right of the graph you will see the current frames appearing as they relate to the footage of the game or experience you are viewing.
Understanding frame data
It’s one thing to see numbers or graphs, it’s another thing to see the numbers in action. VR is a different ball game when it comes to benchmarks. We are not looking for 150fps as we only have 3 options: 90fps, 45fps x2 (interleaved reprojection), or when your system cannot do that it drops frames. Interleaved reprojection is put in as a safety net for your GPU. When it cannot handle 90fps it will drop back to 45fps and reuse the last frame’s rendered images and reprojects it to make up a fake 90fps. That then means that when you turn your head during a game/experience you still ‘feel’ like it’s running that 90fps, but this has a negative impact on positional movement and animation. Because it is reproducing 2 frames without calculating the positional movement of the headset it can feel like the image is not in the right place, thereby creating glitches or event the feeling of nausea. This has little effect on games and experiences when you are standing still and shooting at something (like the archery game Longbow) but this type of glitch is very noticeable in games like Holopoint where you are required to dodge incoming projectiles.
HTC Vive now also has asynchronous reprojection if you have an Nvidia GPU but AMD GPUs are not supported in this current version. Asynchronous reprojection is a much-awaited feature, particularly for HTC Vive users. The idea is to maintain smooth motion on head orientation when the framerate drops below 90fps. Valve’s current universally-compatible solution is interleaved reprojection (described above). With asynchronous reprojection, a slight drop in performance will not trigger this halving of framerate, instead picking up the previous frame and displaying it again, shifted to match the updated orientation data. The overall result is a major improvement to smoothness and comfort, as situations where frame rate is fluctuating just below 90fps are very common. So my MSI AMD Radeon RX-480 GPU in my budget PC is currently using interleaved reprojection – asynchronous is still in beta testing.
So taking all that into account I have come up with a VR Video Benchmark. You will get to see what is stressing out the GPU and I get to show you where I had dropped frames and show you the impact it had on my experience.
I have set up a five star ranking system that provides a score on how well each application runs on the Budget PC.
Five stars: The application runs at full settings with no noticeable slow downs or drop frames. Any app with a five star rating will not benefit from a GPU upgrade.
Four stars: The application runs well on the Budget PC system but may not be able to achieve the highest settings, or slight slow downs may be noticeable. The deficit in quality in my opinion doesn’t justify upgrading the GPU.
Three stars: The game plays well on the Budget PC but you would definitely see the benefit of a GPU upgrade.
Two stars: The game may be playable but the sacrifice in quality is very noticeable and might even cause nausea and motion sickness.
One star: The game can’t be played well at all on the Budget PC and will cause nausea and motion sickness.
When I first loaded in it was lag hell with dropped frames all over I went to do a video record of the frame data but noticed the desktop window was in full screen so I knew I could not do a video with the frame data in it. But for me it was not a bad thing.
I did the Island 359 intro and was feeling a bit off not somthing that happens to me in VR I set my pc to take a screenshot every 25 seconds so I could see what was happening with the frame data and dropped frames .
Just a minute or so in and I knew somthing was wrong I was feeling sick so I had a look at the data and this is what I found:
The Reprojection I can handle but the dropped frames got so bad it was flashing me out of the game this is not somthing I have seen in any VR game to date. To try and fix it I did a clean install of the latest Radeon Software 6.11.5 .
After the fresh drivers things did not get better.
This is at the start of the game 1 minute after leaving the camp with everything on low, it was not only hard to see but I was feeling real sick. Just as I was about to get attacked the game would flash of for just the right amount of time for this little guy to hit me.
All up I don’t think I could have played through Island 359 three or four times with the RX-480 even an hour later I am still feeling sick.
I know I might be able to make it a little better by doing a fresh install of Windows 10 and playing around with drivers to find the right ones but I don’t think it will be good enough to get the intended experience. I do hope it gets better in time and this is a Beta game so time will tell but Island 359 gets a 1 star: The game can’t be played well at all on the Budget PC and will cause nausea and motion sickness.