3 or 3.1 alpha 4?

Joe.F · April 7, 2016, 3:04am

Recently, i want to test the jMonkeyVr in jme3, but i dont know whether 3 or 3.1 I should use.
because i have moved a project to 3.1 alpha 1 from 3, but it made lots of errors. So anyone could help me?

nehon · April 7, 2016, 5:17am

Lats time I checked MonkeyVr use his own of JME3 that is synced to the official repo from time to time.
I also remember it being clearly specified in the MonkeyVr readme.md file.

github.com

phr00t/jMonkeyVR/blob/master/README.md

<b>Commercial games on Steam using jMonkeyVR: <a href="http://store.steampowered.com/app/414510/">5089</a> *
<a href="http://store.steampowered.com/app/363460">Spermination</a> * <a href="http://store.steampowered.com/app/329770/">4089</a></b>

Phr00t's jMonkeyEngine build is required: https://github.com/phr00t/jmonkeyengine (the main jME3 build might work, but VR-specific changes will be made first on Phr00t's build) -- you can just use the JAR/libs under the dist/ and lib/ folders

SteamVR is required. You can download & install it free with the Steam client (under Tools).

See <a href="https://github.com/phr00t/jMonkeyVR/blob/master/test/jmevr/TestjMonkeyVR.java">TestOpenVR.java</a> to see a full example of how to set up an application to use VR hardware & jME3.

<b>OSVR Support is a work-in-progress!</b>

<b>Adding OpenVR support to your application:</b>

(0) Use jme3-lwjgl3 in your project, not jme3-lwjgl (needs GLFW in LWJGL 3).

(1) Add the latest jna-x.x.x & JMonkeyVR.jar to the project.

(2) Instead of extending SimpleApplication/BaseApplication for your Main class, extend VRApplication. This class will handle starting your application in VR mode if VR hardware is detected, or normal mode otherwise. If you want to configure a few things, use the preconfigureVRApp function as follows.

```

This file has been truncated. show original

Here is @phr00t’s JME build GitHub - phr00t/jmonkeyengine: jMonkeyEngine is a 3D game engine for adventurous Java developers. It’s open source, cross platform and cutting edge. And it is all beautifully documented. This is Phr00t's version of that library; better performance, bleeding-edge commits, support for Virtual Reality & multithreading.

Joe.F · April 7, 2016, 6:21am

Thank you！

Ogli · April 7, 2016, 3:03pm

Hey,

will need to know my “VR with jME” options soon. Having a Oculus DK 2 and a Google cardboard (but willing to get other things too).
Somehow I don’t like the idea that I will need to use a fork, but if it’s the only or superior way, I will use it.
An overview on the available VR options for jME would be cool. Maybe a wiki page?
Shall I open another topic for this, once I’m ready for action? Or should we use a topic already existing (like this one)?

Thanks,

phr00t · April 7, 2016, 3:16pm

1 & 3) I’m not sure if @rickard is still maintaining his fork, which I believe at least originally was trying to fit into the main jME3 branch (to address #2).

Yeah, I understand it isn’t ideal. Too many competing interests… it could be done, but I think it’d slow both of our progress if we were trying to keep things aligned. I strive to keep my branch as closely to the main jME3 branch as possible, but with changes required for VR simplicity & performance.
I prefer new topics over old… better organization.

rickard · April 7, 2016, 4:36pm

Yeah, definitely new topic. But a wiki page sounds good.

Joe.F · April 8, 2016, 2:05am

Sorry, I’ve nevered heared that its have two branch. Uh… a wiki page or a overview topic must be cool, I’m looking forword it.

Joe.F · April 8, 2016, 2:06am

I’m looking forward to it too.