Page 1 of 1
Local Config Editor version does not match VMS version
Posted: 26 Feb 2018, 14:54
by u-double-u
Hi,
I can't get Ventuz to run in VR, and i get the above warning in Config editor.
I guess this might be the reason?
I do want to keep version 5 installed.
cheers
Re: Local Config Editor version does not match VMS version
Posted: 27 Feb 2018, 18:13
by u-double-u
I figured it out by disabling th "older" VMS in the services-control panel,
Now VR is running. And it looks really good!
Re: Local Config Editor version does not match VMS version
Posted: 28 Feb 2018, 07:14
by Agalar Ragimov
u-double-u wrote:I figured it out by disabling th "older" VMS in the services-control panel,
Now VR is running. And it looks really good!
Did you face any problems with controllers? Left and right controllers are working well, aren't they?
Btw, what device are you using? HTC Vive or Oculus?
Re: Local Config Editor version does not match VMS version
Posted: 28 Feb 2018, 11:50
by u-double-u
HTC Vive. The Controllers are working.
In Vetuz 6 and 5 (after the fix)
Although I do have the "feeling", they behave differently since the beginning of this year. Whenever I teleport to a location, that location gets centered at the center of my playing area (which I have set to be visible), not to where I am standing. Maybe this has to do with the recent bug that was disabling controllers for ventuz 5.
Re: Local Config Editor version does not match VMS version
Posted: 28 Feb 2018, 12:06
by Dennis
Hey,
it was always the same since the beginning, the teleporation location will be the center of the chaperone/room set in the SteamConfiguration.
Sorry,
but we will try to improve that behavior, that it feels and works more like with "the lab demo"... where you could exactly "see the target by footstep indicators.. and you will be positioned there..."
all the best and
reg
Arts
Dee
Re: Local Config Editor version does not match VMS version
Posted: 28 Feb 2018, 16:42
by u-double-u
cool.