Replies: 8 comments 11 replies
-
|
The 3DTiles in error were created from CityGML using FME. |
Beta Was this translation helpful? Give feedback.
-
|
@belom88 It may be that 3D tiles depends to literally on luma.gl v8 accessors. Any chance your team could do a quick test on the tileset in question? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Failure and normal examples have been uploaded. Version 9.0.14 3DTitles assets
Error messages Version 8.9.35 |
Beta Was this translation helpful? Give feedback.
-
|
Source code is here. |
Beta Was this translation helpful? Give feedback.
-
|
I encounter a very similar error, it seems related to incorrect byte alignment for uint8 (in my case) vertex attribute not aligned to 16bit boundaries see WebGPU data memory layout: See code in @luma.gl\core\dist\adapter\type-utils\vertex-format-from-attribute.js line 62: /** Get the vertex format for an attribute with TypedArray and size */
export function getVertexFormatFromAttribute(typedArray, size, normalized) {
if (!size || size > 4) {
throw new Error(`size ${size}`);
}
const components = size;
let dataType = getDataTypeFromTypedArray(typedArray);
if (dataType === 'uint8' || dataType === 'sint8') {
if (components === 1 || components === 3) {
// WebGPU 8 bit formats must be aligned to 16 bit boundaries');
throw new Error(`size: ${size}`);
}
if (normalized) {
dataType = dataType.replace('int', 'norm');
}
return `${dataType}x${components}`;
}
... |
Beta Was this translation helpful? Give feedback.
-
|
Following the luma.gl v8 to v9 breaking change guide it shows that the WebGL2 API (and support) is exchanged for WebGPU, |
Beta Was this translation helpful? Give feedback.
-
|
Load option: 3d-tiles.decodeQuantizedPositions in https://loaders.gl/docs/modules/3d-tiles/api-reference/tiles-3d-loader seemed to be what I needed, however no succes: this.tile3DLayer = new Tile3DLayer({
id: 'tile-3d-layer',
data: url,
pickable: true,
loadOptions: {
'3d-tiles': { decodeQuantizedPositions: true }
},
... |
Beta Was this translation helpful? Give feedback.
-
|
Following the backend notes for luma.gl: It states that: And that: |
Beta Was this translation helpful? Give feedback.
-
|
Correct. The part that is perhaps missing is that the luma v9 API is a "WebGPU first design" that is optimized for WebGPU with added portability to WebGL. This means that it intentionally removes explicit support for options that are WebGL only, to ensure that apps remain portable. I can't say for sure that this is the cause of the failure, but once I get time to look into this, this limitation around 1 byte attribute support could be one of the first "clues" to what is going on. |
Beta Was this translation helpful? Give feedback.
-
|
@ibgreen Thanks for your response and clarification! |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I will keep an eye for new developments, thanks! On another note, I hope that our issues have enough common ground and added to instead of hijacked your discussion @hig-bit. |
Beta Was this translation helpful? Give feedback.
-
|
Apologies, I suppose my chit-chat is just a way of stalling for time until someone is actually able to look at this. Figured it would be better than radio silence... |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, Is there a workaround or solution for this issue, or is downgrading to version 8 the only option? Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
No know workaround other than the observation that not all models are affected - i.e. someone might be able to control how models are generated. I've tried to relax the restriction in the function listed above, let's see if it is an easy fix. Fix published in luma.gl@9.0.25 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the restriction relaxation! The variable "normalized" is undefined in my scenario unfortunately: I do think that this relaxation is an improvement. |
Beta Was this translation helpful? Give feedback.
-
An error will occur with the 3D tiles downloaded from the following page.
https://www.geospatial.jp/ckan/dataset/plateau-13103-minato-ku-2023/resource/5f661701-f928-431a-9120-1ab46045bbf5
No error will occur with the 3D tiles downloaded from the following page. It will be drawn properly.
https://github.com/CesiumGS/3d-tiles-samples/tree/main/1.0/TilesetWithDiscreteLOD
The contents of the error are as follows.
Source code
It may be a problem with the 3D Tiles file format, but is there a way to draw correctly even in v9?
Beta Was this translation helpful? Give feedback.
All reactions