Skip to content

Commit 4e5988f

Browse files
committed
Bumping Acrolinx a bit
1 parent 57155f6 commit 4e5988f

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ The schema is identical for converting triangular meshes and point clouds. Howev
9191

9292
## Settings for triangular meshes
9393

94-
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:
94+
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:
9595

9696
### Geometry parameters
9797

@@ -277,7 +277,7 @@ A simple way to test whether instancing information gets preserved during conver
277277

278278
#### Example: Instancing setup in 3ds Max
279279

280-
[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.
280+
[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.
281281

282282
![Cloning in 3ds Max](./media/3dsmax-clone-object.png)
283283

@@ -329,7 +329,7 @@ Because lighting is already baked into the textures, no dynamic lighting is need
329329

330330
### Use case: Visualization of compact machines, etc.
331331

332-
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:
332+
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:
333333

334334
* Individual parts should be selectable and movable, so the `sceneGraphMode` must be left to `dynamic`.
335335
* 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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
99

1010
# Convert models
1111

12-
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.
12+
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.
1313
For these reasons, ARR service provides a dedicated *conversion service*, which you can run ahead of time.
1414
Once converted, a model can be loaded from an Azure Storage Account.
1515

@@ -22,7 +22,7 @@ The conversion service supports these formats:
2222
* **FBX** (version 2011 to version 2020)
2323
* **GLTF**/**GLB** (version 2.x)
2424

25-
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).
25+
There are minor differences between the formats regarding material property conversion, as listed in chapter [material mapping for model formats](../../reference/material-mapping.md).
2626

2727
### Point clouds
2828

@@ -35,7 +35,7 @@ There are minor differences between the formats with regard to material property
3535

3636
In case any other properties exist, they're ignored during ingestion.
3737
* **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.
38-
* **LAS**, **LAZ** : In case color data is not present, the intensity attribute is used as color.
38+
* **LAS**, **LAZ** : In case color data isn't present, the intensity attribute is used as color.
3939

4040
## The conversion process
4141

0 commit comments

Comments
 (0)