Dataset_Synthesizer
Dataset_Synthesizer copied to clipboard
NVIDIA
bounding box gives wrong value
I tried to use the tool and draw a bounding box (yellow line) over it using bounding_box data in json file. So far, it seems so good. But sometimes the value I take from NDDS seems to be not normal. Any idea why this happens?
How does NDDS calculate a bounding box?
I am also facing a similar issue, some bounding boxes seem to be correct however others are wrong. Unsure what is causing this?
I faced this issue a few months ago. My solution was to re-create my static mesh and re-import it into Unreal Engine.
See: https://github.com/NVIDIA/Dataset_Synthesizer/issues/18#issuecomment-533237904
This might not fix the underlying bug but it might be a quick fix.
Hmm interesting. I've just clicked the 'Use Explicit Camera Intrinsic' option under SceneCapturer_Simple and now all the bounding boxes align perfectly. I'm assuming the issue is something to do with the latency between the camera changing its FOV and the calculation of the bounding boxes of the meshes in the image? Did you have this option turned on or off?
I solved this issue from the 3D cad modeling part itself. While i made my static mesh , i followed same dimensions. The even when i imported it in Blender. I scaled dimension to match my objects real world dimension in centimeters cm.
UE4 unit values are in cm. So kindly requesting you all to follow in cms.
Then the problem will be solved.
I solved this issue from the 3D cad modeling part itself. While i made my static mesh , i followed same dimensions. The even when i imported it in Blender. I scaled dimension to match my objects real world dimension in centimeters cm.
UE4 unit values are in cm. So kindly requesting you all to follow in cms.
Then the problem will be solved.
When you imported into UE4, did you keep the scaling at 1.0?
Yes. Inorder to keep the scaling in 1.0 in UE4; initially from the blender itself you have to keep the dimensions and units in cm.
Did you alter the cameras FoV from 90deg?
Yes. Its upto you whic camera you are using for detection and pose estimation
Hi guys, would it be possible for you to send this repository to me through dropbox or google drive? Now the github lfs of this repository no longer work, I cannot git clone the files anymore....
Did you alter the cameras FoV from 90deg?
Yes. Its upto you whic camera you are using for detection and pose estimation
I tried this morning using a FoV range from 90 to 120 and just place a basic cone StaticMeshActor. Again, I get the wrong bounding box value. If I'm using a mesh inbuilt to Unreal, the issue cannot be with importing meshes with different units?
