With 0.6.0 can and should we delete the direct to rift

Just tested this quickly with empty scene and oculus camera (Unity 5.0.1f1). Not other settings. Built it and normal exe just runs the app in my monitor. DirectToRift runs it in Rift. So perhaps it is still needed.

Yea I noticed that to. Its strange that the new features say "Eliminated the need for the DirectToRift.exe in Unity 4.6.3p2 and later." but it works the same as before.

I noticed that if I ran the main file it did go direct to the rift. However if other people are finding this not to be the case I'll continue to include the direct to rift exe.

I guess with the Rift not being released until the first quarter of 2016 there is plenty of time to fix these issues :)

I noticed Unity 4.6.5f1 does not create the *_DirectToRift.exe, but Unity 5.0.2f1 creates it.
There might be a problem on version detection.

Probably this is it. :)

OVRUnityVersion.cs called from OVRShimLoader.cs

	public static bool hasPreInitSupport
	{
		get
		{
			return (version.major == 4 && version >= "4.6.3p2");
		}
	}

How are you starting your game on the Rift without DirectToRift?

Im not sure how to run a game anymore. I just downloaded Unity 5 and it won't create a Direct to Rift file. The regular exe does not open in the Rift.

@kevingulling: The latest versions of Unity 5 (starting at 5.1.1) have included VR support with the engine. There is no "DirectToRift" anymore. You just select "Virtual Reality Supported" in the player settings and use the normal exe file. You also can't use the Unity integration anymore (this is for Unity 4) but can use the Oculus Utilities.