Merge pull request #214561 from FlorianBorn71/NewPointCloudFormatsLASandLAZ

Added LAS and LAZ as new point cloud formats

Author: prmerger-automator[bot]

articles/remote-rendering/how-tos/conversion/configure-model-conversion.md

@@ -91,7 +91,7 @@ The schema is identical for converting triangular meshes and point clouds. Howev
 
 ## Settings for triangular meshes
 
-For converting a triangular mesh, for instance from an .fbx file, all parameters from the schema above do affect the outcome. The parameters are explained in detail now:
+When converting a triangular mesh, for instance from an .fbx file, all parameters from the schema above do affect the outcome. The parameters are explained in detail now:
 
 ### Geometry parameters
 
@@ -127,7 +127,7 @@ If a model is defined using gamma space, then these options should be set to tru
 * `gammaToLinearVertex` - Convert :::no-loc text="vertex"::: colors from gamma space to linear space
 
 > [!NOTE]
-> For FBX, E57, PLY and XYZ files these settings are set to `true` by default. For all other file types, the default is `false`.
+> For FBX, E57, PLY, LAS, LAZ and XYZ files these settings are set to `true` by default. For all other file types, the default is `false`.
 
 ### Scene parameters
 
@@ -252,7 +252,7 @@ The properties that do have an effect on point cloud conversion are:
 * `scaling` - same meaning as for triangular meshes.
 * `recenterToOrigin` - same meaning as for triangular meshes.
 * `axis` - same meaning as for triangular meshes. Default values are `["+x", "+y", "+z"]`, however most point cloud data will be rotated compared to renderer's own coordinate system. To compensate, in most cases `["+x", "+z", "-y"]` fixes the rotation.
-* `gammaToLinearVertex` - similar to triangular meshes, this flag indicates whether point colors should be converted from gamma space to linear space. Default value for point cloud formats (E57, PLY and XYZ) is true.
+* `gammaToLinearVertex` - similar to triangular meshes, this flag indicates whether point colors should be converted from gamma space to linear space. Default value for point cloud formats (E57, PLY, LAS, LAZ and XYZ) is true.
 
 * `generateCollisionMesh` - similar to triangular meshes, this flag needs to be enabled to support [spatial queries](../../overview/features/spatial-queries.md). But unlike for triangular meshes, this flag doesn't incurs longer conversion times, larger output file sizes, or longer runtime loading times. So disabling this flag can't be considered an optimization.
 
@@ -277,7 +277,7 @@ A simple way to test whether instancing information gets preserved during conver
 
 #### Example: Instancing setup in 3ds Max
 
-[Autodesk 3ds Max](https://www.autodesk.de/products/3ds-max) has distinct object cloning modes called **`Copy`**, **`Instance`**, and **`Reference`** that behave differently with regard to instancing in the exported `.fbx` file.
+[Autodesk 3ds Max](https://www.autodesk.de/products/3ds-max) has distinct object cloning modes called **`Copy`**, **`Instance`**, and **`Reference`** that behave differently regarding instancing in the exported `.fbx` file.
 
 ![Cloning in 3ds Max](./media/3dsmax-clone-object.png)
 
@@ -329,7 +329,7 @@ Because lighting is already baked into the textures, no dynamic lighting is need
 
 ### Use case: Visualization of compact machines, etc.
 
-In these use cases, the models often have very high detail within a small volume. The renderer is heavily optimized to handle such cases well. However, most of the optimizations mentioned in the previous use case don't apply here:
+In these use cases, the models often have high detail within a small volume. The renderer is heavily optimized to handle such cases well. However, most of the optimizations mentioned in the previous use case don't apply here:
 
 * Individual parts should be selectable and movable, so the `sceneGraphMode` must be left to `dynamic`.
 * Ray casts are typically an integral part of the application, so collision meshes must be generated.

articles/remote-rendering/how-tos/conversion/model-conversion.md

@@ -9,7 +9,7 @@ ms.topic: how-to
 
 # Convert models
 
-Azure Remote Rendering allows you to render very complex models. To achieve maximum performance, the data must be preprocessed to be in an optimal format. Depending on the amount of data, this step might take a while. It would be impractical, if this time was spent during model loading. Also, it would be wasteful to repeat this process for multiple sessions.
+Azure Remote Rendering allows you to render complex models. To achieve maximum performance, the data must be preprocessed to be in an optimal format. Depending on the amount of data, this step might take a while. It would be impractical, if this time was spent during model loading. Also, it would be wasteful to repeat this process for multiple sessions.
 For these reasons, ARR service provides a dedicated *conversion service*, which you can run ahead of time.
 Once converted, a model can be loaded from an Azure Storage Account.
 
@@ -22,7 +22,7 @@ The conversion service supports these formats:
 * **FBX**  (version 2011 to version 2020)
 * **GLTF**/**GLB** (version 2.x)
 
-There are minor differences between the formats with regard to material property conversion, as listed in chapter [material mapping for model formats](../../reference/material-mapping.md).
+There are minor differences between the formats regarding material property conversion, as listed in chapter [material mapping for model formats](../../reference/material-mapping.md).
 
 ### Point clouds
 
@@ -35,6 +35,7 @@ There are minor differences between the formats with regard to material property
 
   In case any other properties exist, they're ignored during ingestion.
 * **E57** : E57 contains two types of data: `data3d` and `image2d`. The conversion service only loads the `data3d` part of the file, while the `image2d` part of the file is being ignored.
+* **LAS**, **LAZ** : In case color data isn't present, the intensity attribute is used as color.
 
 ## The conversion process