SDK C Samples (9.0.3) not displaying any images from cameras

[Alexis_G]

Greetings,

I don't know if you can help me to understand what is happening with those samples, the OpenCV windows are not showing any data coming from the cameras, they are just creating the Mat objects full of zeros.  I also can see the pointers of both distorted_frame_*, but somehow is not "pulling" the data from that memory location. So far, I am able to get Pose, camera parameters and so on...

 

To verify the hardware, I already built the Unity samples and its working fine.

 

Thanks in advance.

 

 

 

@Daniel_Y @Jad

[Alexis_G]

[Update]

I've been exploring the content of the pointers using the main_CameraControl.cpp file (after the calling for Vive_SR_GetModuleData), so far, I just can retrieve values for poses, timestamps, sequences, but all related to camera values (lux, color temperature, etc) remains empty.

 

@Daniel_Y @zzy @Andy.YC_Wang @Sean_Su

[Alexis_G]

[Update]

 

I've been playing with the debugger a little bit yesterday at night and it shows that the GetModuleData method does not returns the data for the given pointers (data: '/0'). Please reply, using the Unity version really reduces my flexibility using the SDK resources.

 

Thanks in advance.

[Daniel_Y]

What device you are using? 

[Daniel_Y]

Could you provide the logs existing in this folder, $(drive)\Users\$(name)\AppData\LocalLow\HTC Corporation\SR_Logs

[Alexis_G]

Thanks for replaying, HTC VIVE PRO, here are the logs...

Please be aware of the following references:

- 2/19/2020 10:50 AM (Unity) ~1.5 min -> SUCCESSFUL TEST

- 2/19/2020 10:53 AM (C SDK  9.0.3, Camera Control) ~1.5min -> FAILED TEST

Hopefully these can give you a good hint to solve this problem.

 

Thanks in advance!!!

HTC_LOGS.zip

[wenjiec_shen]

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.

[ayumu_naga]

The solution mentioned above works nicely but contains typos, 

Correct is 

ViveSR_SetParameterBool( ID_SEETHROUGH, ViveSR::SeeThrough::Param::DISTORT_GPU_TO_CPU_ENABLE, true);

after 

ViveSR_InitialModule(ID_SEETHROUGH);

 

[Arto]

On 2/25/2020 at 8:20 AM, wenjiec_shen said:

We are going to fix this issue in next version.

The aforementioned workaround fixed this for me as well.

@wenjiec_shen When are you guys planning to release the next version? It's been three months since you posted the workaround. For new customers--such as myself--this bug makes it seem that the SRWorks SDK is broken altogether (the example programs don't show any camera input at all).

[Tony PH Lin]

@Arto, @ayumu_naga, @Alexis_G,

The latest SRWorks 0.9.3.0 has been uploaded to website.

Please check it out and let us know if you still have the issues on this topic, thanks.

https://developer.vive.com/resources/2020/05/26/vive-srworks-sdk-updated-0-9-3-0/