[WIP] New example : core/vr_simulator

[Hultan]

[WIP] - Do not merge yet

I am starting to believe that the new VR functions (#429) are not correctly implemented. I cannot get the sample core/vr_simulator to work, and I have looked over the code again and again and cannot find any differences.

Since the VR functions were added earlier today, I figured that they have never been tested. Can someone try this example out on their computer and see if it works there?

All I get is a blank screen (with a FPS counter).

[JupiterRider]

Your example is correct. The bug is in the raylib (c version) itself. The example doesn't seem to work in versions > 5.0 anymore.

If you want, you can open an issue here: https://github.com/raysan5/raylib/issues

[Hultan]

Hmmm...is my problem then that I am developing these examples against the dev version of raylib-go instead of the latest stable version? Is version 5.0.0 recommended to use now?

I have several examples that have mysterious bugs that I cannot find, that might suffer from similar problems like the VR example:

core/automation_events 
// code compiles now, thanks to #431, but it still does not work correctly. Might be a problem with PlayAutomationEvent?

shapes/splines_drawing 
// everything work except bezier, problem with DrawSplineBezierCubic?

shapes/top_down_lights 
// mysterious drawing issues, that I can't seem to fix

[Hultan]

I have completely messed up my fork, and local repository, of raylib-go. I will make a new PR when I have gotten the example to work.