-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Downloads
Posts posted by wenjiec_shen
-
-
Hi MacBread,
Yes, We intended.
The positions of "Dual Camera" and "Render Camera" are at different time steps for making the experience more real.
Thank you.- 1
-
Hi Eyad,
I am sorry for the inconvenience.In the version 0.9.3.0, the project SRWorks (XR) SDK UE4 Samples doesn't support Unreal Engine 4.24 but the project SRWorks (XR) SDK UE4 Plugin have supported it.Are your project based on SRWorks (XR) SDK UE4 Samples?Thank you. -
On 6/30/2020 at 4:14 PM, cru89 said:
Also, when I try to run the C sample, the following call returns a failure (code -1).
ViveSR_InitialModule(ID_PASSTHROUGH);
All cleanup calls afterwards return error 1021 (INVALID_CHANGE). I am on the latest SRWorks 0.9.3.0 version. My SteamVR version is 1.12.5.
Also the normal system see-through of the HMD is working (i.e. when I double-tab the system button on the controller). The cameras aren't broken - it must be some sort of communication error.
Hi cru89,
Would you please attach your log again after running the C sample?
I cannot fetch a piece of information from the log you attached because everything seems fine.
Thank you -
Hi Jawani,
We are forbidden to use any cloud drive in the office.
Would you please attach your log file via the forum?
Thank you
-
Hi Nitesh,
Yes, you are right.
It is just a filter and you can adjust the variable to effect the cutoff slope in the filter.
The default value is 0.007 and you can multiply or divide the variable by 10 until you notice the effect on the gaze data.
Thank you,
WenJie
-
Hi ayumu_naga,
Thank you.
It has been fixed in latest version.
- 1
-
Hi Alexis,
I am sorry for omitting in sample code.
It should add an instruction for copy data from GPU.
You can resolve this problem by calling
ViveSR_SetParameterBool( ID_PASSTHROUGH, ViveSR::PassThrough::Param::DISTORT_GPU_TO_CPU_ENABLE, true);
after
ViveSR_InitialModule(ID_PASSTHROUGH);
We are going to fix this issue in next version.
Thank you for reporting the issue.
- 2
-
Hi @imarin18,
In order confirm your state, could you please provide more information?
For example, your computer equipment, the meaning of x axis in your chart and how you get the timestamp in source code.
Thank you.
-
On 11/14/2019 at 3:36 AM, marcellotham said:
Thank WenJie,
So if I'm interested in the verbose data from eyedata_v2, I shouldn't be worrying about filtering? Is it safe to just disable it nonetheless.
Thank you
Hi Marcellotham,
Yes, filtering works as previous version.
Thanks,
WenJie
-
Hi Marcellotham,
SetEyeParameter() is still supported in Eyedata_v2 but filtering always only works on gaze rays.
So the versions of data doesn't effect filtering.
Thanks,
WenJie
-
Hi André @AKCH,
Gaze origin and Gaze direction are processed if the GazeRayParameter: sensitive_factor has been adjusted.
Pupil position is the raw data.
BR.
WenJie
- 1
-
Hi Scott,
I recommend you can start with values like 0.001 or 0.0001 and multiply and divide this parameter by 10.
-
This satiation might be that you've put too many colliders into the sense.
There is a method to resolve it.
Actually, you can found out that the method Focus() wraps the unity API Physic.Raycast().Acording to documant of unity 3d user manual, you can ignore colliders with layer mask when casting a ray.
Hence, you can manually create a layer and cast a ray only against the layer and ignore all other colliders.
https://docs.unity3d.com/ScriptReference/Physics.Raycast.html
https://docs.unity3d.com/Manual/Layers.html
Thank you.
Pass-through stopped working
in VIVE SRWorks SDK
Posted
Hi Carsten,
We will try to reproduce the issue in more diverse environments.
The information is critical.
Thank you.