Some LAS files are not rendered

[SoftwareMechanic]

Some LAS files are not rendered, but in some cases there are no errors when model is loaded and the AABB is calculated correctly. in other cases I receive an error -> "this._state.flagsBuf is null"

Here I attach one las file which is giving no errors and is not rendered: WeTransfer link

Here I attach another las file which is giving an error when loading: WeTransfer link

Both links will last one week, I will resend you new links if needed.

In order to verify if these files are valid I tried open both this '.las' files on lidarview.com and I can see them.

• OS: Windows 10
• Browser: chrome, firefox

Please let me know if you need more Info about this issue.

[xeolabs]

Thanks - what version are these las files?

On Tue, Jan 30, 2024, 17:00 SoftwareMechanic @.***> wrote:

Some LAS files are not rendered, but in some cases there are no errors when model is loaded and the AABB is calculated correctly. in other cases I receive an error -> "this._state.flagsBuf is null"

Here I attach one las file which is giving no errors and is not rendered: WeTransfer link https://we.tl/t-LKfdJBmLdl

Here I attach another las file which is giving an error when loading: WeTransfer link https://we.tl/t-GUgX8Zvs0A

Both links will last one week, I will resend you new links if needed.

In order to verify if these files are valid I tried open both this '.las' files on lidarview.com and I can see them. Screenshots If applicable, add screenshots to help explain your problem.

• OS: Windows 10
• Browser: chrome, firefox

Please let me know if you need more Info about this issue.

— Reply to this email directly, view it on GitHub https://github.com/xeokit/xeokit-sdk/issues/1358, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAUJHERB65AW6EW3ZYFI2TYREKKNAVCNFSM6AAAAABCRQG2XSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYDQMRRGM4TSNQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[SoftwareMechanic]

The first one should be 1.2, the second one I am not sure honestly. I will ask to my coworker

the second one (Segmentation3D) is 1.2, my coworker found on the software 'lasview' that Segmentation3D has a projection, maybe it is related to the issue

[paireks]

Just for the record I could open both files using "las_IndoorScan" example without any errors:

The only thing I had to change was setting the camera at the end to be in a proper position, cause these scans can appear in totally different locations: sceneModel.on("loaded", () => { viewer.cameraFlight.jumpTo(sceneModel); });

Tested on chrome and Windows 10.

[xeolabs]

Also, LASLoaderPlugin and convert2xkt oonly supports LAS/LAZ files up to LAS v1.3. They do not support LAS v1.4 files.

[SoftwareMechanic]

Thank you for these clarifications, I am still having the same issue, but in the coming days I will retry also using the example provided. Thank you!

[SoftwareMechanic]

Hello! I tested with example as you suggested me and yes, it works within the example. So I tried to upload the package.

But still, I have some las files which are visible and these which are loaded correctly but not rendered.

I tried using this code:

sceneModel.on("loaded", () => {
       console.log("Model loaded")
      
       this.viewer.cameraFlight.jumpTo(sceneModel); 

      this.modelsLoaded.push({id: sceneModel.id, sceneModel: sceneModel})
      //const aabb = this.viewer.scene.aabb         
      //this.viewer.cameraFlight.flyTo(aabb);
})

the event is called correctly (it works also with other las files and all other file formats that xeokit can read). the las loader settings are the same and also the viewer.scene.pointsMaterial options are the same. (copied from the example you suggested)

maybe the issue could be related to the fact I am using Next.js?

it's very weird that with other files I don't have this problem...

EDIT:

I created a method which shows the bouning box of the model, this is what I see after I load those files that are not visible to me:

[xeolabs]

Hi, do you represent one of our commercial users? If so then we could possibly help you with Next.js integrations via our Asana issue tracker.