Releases: LumKitty/VRnyan
Release list
v2.3-rc5
Stopped calling reflection every frame and instead grab a reference to FollowCam's transform once during init. Should be a lot more performant, and reduce stutter (requires FollowCam 0.5-beta5 or higher)
Bumped straight to RC5 so that it lines up with FollowCam beta release numbers, since these are being developed in tandem.
If all you need is the ActiveOnStart fix, and are not using followcam these RCs should all be identical, and not worth upgrading past RC1
2.3-rc2
2.3-rc1
v2.2 - The GUI update
v2.2-beta2 was released as 2.2 with no changes other than a version bump
This update adds a simple GUI that allows you to fine tune its settings at runtime. This is especially useful for tuning the Dynamic Clip Plane settings when used with OnAirTap.
The only settings that need to be set in the .json file are "ActiveOnStart" and "LinuxRootDriveLetter" as these are required to be set before startup.
v2.2-beta2
More GUI improvements.
Added the ability to select which bone should be tracked for Dynamic Clip Plane adjustment in OnAirTap
v2.2-beta1
v2.2-beta1
Added a basic GUI!
Is it pretty? no Does it work? Probably. Please beta test!
v2.1
Support for writing to Linux shared memory directly - bridge DLL is not required. If you have changed the Wine default root drive letter from Z: then change the LinuxRootDriveLetter setting to mates.
Removed last remaining references to LIV outside of the LIV plugin itself
If you are using OnAirTap, please upgrade to OnAirTap 1.1 at the same time
If you are using LIV, please remove LIV-Vnyan.dll from your CameraBehaviors folder and replace it with VRnyan-LIV.dll from this release
If you were running 2.1-RC1 you do not need to upgrade. I literally just renamed this release to 2.1 after successful testing
v2.1-alpha1
Attempt to support Linux shared memory directly
Further rebranding to VRnyan
v2.0
Rebrand to VRnyan, full support for OnAirTap (see release notes for 1.3a1 & 1.3a2 for details)
After upgrading, please delete VNyan_Liv.dll as you shouldn't run both versions at once. This remains backwards-compatible with the LIV camera plugin
V2.0-RC1 is now 2.0 final with no changes. If you installed RC1 there is no need to upgrade
Changes:
Added support for sending a bone position to OnAirTap, to use for dynamically adjusting the clip plane at runtime
New config settings:
"BoneClip": "Hips" - Name of the bone to use. See the Unity docs for valid values. This is case sensitive
"BoneClipDistanceAdjust": "-0.15" - This adds additional distance from the camera to the bone position, e.g. to allow for body size when tracking hip bone. Negative numbers = closer to camera
"BoneClipDistanceAdjust2DOnly": "True" - Probably enable if OnAirTap is using a vertical clip plane. Ignores the Y axis when calculating distance
New trigger:
_lum_vr_setbone - Allows setting BoneClip & Distance Adjust
Text1 - Name of bone to set - See the Unity docs for valid values. This is case sensitive
Text2 - Distance to the bone position to add
Previous _lum_liv_xxx triggers are now _lum_vr_xxx however the legacy liv variants will still work
v1.3a2
Added support for sending a bone position to OnAirTap, to use for dynamically adjusting the clip plane at runtime
New config settings:
"BoneClip": "Hips" - Name of the bone to use. See the Unity docs for valid values. This is case sensitive
"BoneClipDistanceAdjust": "-0.15" - This adds additional distance from the camera to the bone position, e.g. to allow for body size when tracking hip bone. Negative numbers = closer to camera
"BoneClipDistanceAdjust2DOnly": "True" - Probably enable if OnAirTap is using a vertical clip plane. Ignores the Y axis when calculating distance
New trigger:
_lum_liv_setbone - Allows setting BoneClip & Distance Adjust
Text1 - Name of bone to set - See the Unity docs for valid values. This is case sensitive
Text2 - Distance to the bone position to add