3D model converted in nxz can't be seen in 3DHop

[virgilejarrige]

Hi there,

I hope you are doing ok!

We're having two issues with a 3D model from a researcher:

• Once it is converted into .nxz, it isn't displayed in 3DHop. https://seafile.unistra.fr/d/37acf603b37c428fb3a2/
• When geolocalisation is embedded, meshlab doesn't display it correctly (and same result with .nxz/3DHop) https://seafile.unistra.fr/d/7cd1e963226f43018af0/

Could you have a look at them?

Many thanks in advance.

Take care,

Virgile

[alemuntoni]

@ponchio could you take a look at this? Thanks!

[virgilejarrige]

Hi there! Any news on my issue?

[ponchio]

Hi Virgile, sorry I lost track of this issue...

I had a look at the model, and I got no problem using 3dhop (wrong path in 3dhop configuration?), if you can either send me a public link or a folder with yours 3dhop folder I can detect the issue.

The problem with geolocalization is that UTM coords are in the millions (4000000), nexus, meshlab and most importantly the graphic cards use 32 bit floating point to store coords. Floating point shave 24 bit for mantissa which means the the precision you reach in the 4 millions range is about half a meter.

Nexus detects this issue and allows you to move the model in the vicinity of the origin (0, 0), rendering is then correct.

If you want to render this object in some georeferenced system, it should be possible to define the origin of the model in geographic coordinates and display the object in the correct location (Nexus writes an xml files containing the translation info).

If instead you want to render multiple georeference datasets in 3dhop, just apply the same translations to all the objects (and their relative position will be ok).

[virgilejarrige]

No worries! Thank you for your precise answer.

I finally caught the researcher and we found how to move the origin point. It opens correctly in Meshlab, but we still don't see it in our 3DHop.

Here is the link to the model, using 3DHop : https://pount-pprd.app.unistra.fr/p/items/31700c81-88ad-49b4-952b-75c7859b629b you can download the nxz from this page.

Take care

[ponchio]

There is a problem with the nxz model: the one of the textures has 0 byte size, and the code fails to retrieve a zero length range request (you can't really specify a 0-byte range request).

I suspect the problem is in the nxsbuilder process. Would you send me the .ply (or .obj) that i can investigate the issue?

Thanks.