search

microsoft / RoomAliveToolkit

Other
715 stars 191 forks source link

I cannot see the 3D Object #5

Open vigocarpato opened 9 years ago

vigocarpato commented 9 years ago

Hello,

I have been following the steps/instructions to compile and calibrate the demo in which at first everything seems to be working fine, but in “projectionMappingSample” I am having trouble trying to visualize the 3D object in the ProyectionMappingSamples.

The rest seems to work well but when I active the “ThreeDObjectEnabled” option, I cannot see the 3D Object. I only get a black or white screen when I position myself in front of the Kinect that we are using for the tracking.

We get a correct calibration because the wobble effect works correctly.

Once calibrated I am using the Kinect which is connected directly to a PC to track the head. The Flag “liveDepthEnabled” is de-activated.

Do you know what could be the problem and is there any fix?

Thanks a lot for your time!

-Pepe-

thundercarrot commented 9 years ago

A couple of thoughts:

If you set LocalHeadTrackingEnabled to false do you see anything?

You might want to jiggle the translation on ProjectionMappingSample.cs:258. This was tuned for my setup.

I'm wondering if the OBJ file is being read successfully. Do you live in a place where decimal points are commas rather than periods? I've seen some odd things with .ply files for example related to that.

Feel free to zip up the directory containing calibration.xml and pose where I can download; I will take a look.

Andy

DBFBlackbull commented 8 years ago

In case you havent looked at it since May. I had the same issue, and contacted thundercarrot about it, and it was fixed.

The issue was due to localization of numbers. The Load3DObjectFromFile reads a file as a string and converts it to float, but since some regions uses dot (.) for thousand seperator and comma (,) for decimal seperator and vice versa, it would read it wrong. So a number like 0.34561 would be converted to string "0.34561" and into a float "34561", making the number way too big. It has been fixed since roughly 3 months ago.