Skip to content

Commit 6f81bfc

Browse files
authored
Merge pull request #89253 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
2 parents 58cc4ec + 4bc569b commit 6f81bfc

File tree

3 files changed

+36
-3
lines changed

3 files changed

+36
-3
lines changed

articles/azure-functions/durable/durable-functions-http-features.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -200,9 +200,9 @@ The built-in support for calling HTTP APIs is a convenience feature and is not a
200200
If any of these limitations may impact your use-case, consider instead using activity functions and language-specific HTTP client libraries to make outbound HTTP calls.
201201

202202
> [!NOTE]
203-
> If you are a .NET developer, you might be wondering why this feature uses `DurableHttpRequest` and `DurableHttpResponse` types instead of the built-in .NET `HttpRequestMessage` and `HttpResponseMessage`. This design choice was intentional. The primary reason is that a custom types help ensure that users don't make incorrect assumptions about the supported behaviors of the internal HTTP client. Durable-specific types also make it possible to simplify the API design and more easily light up special features, such as [managed identity integration](#managed-identities) and the [polling consumer pattern](#http-202-handling).
203+
> If you are a .NET developer, you might be wondering why this feature uses `DurableHttpRequest` and `DurableHttpResponse` types instead of the built-in .NET `HttpRequestMessage` and `HttpResponseMessage`. This design choice was intentional. The primary reason is that custom types help ensure that users don't make incorrect assumptions about the supported behaviors of the internal HTTP client. Durable-specific types also make it possible to simplify the API design and more easily light up special features, such as [managed identity integration](#managed-identities) and the [polling consumer pattern](#http-202-handling).
204204
205205
## Next steps
206206

207207
> [!div class="nextstepaction"]
208-
> [Learn about durable entities](durable-functions-entities.md)
208+
> [Learn about durable entities](durable-functions-entities.md)

articles/kinect-dk/body-sdk-download.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ keywords: azure, kinect, sdk, download update, latest, available, install, body,
1111

1212
# Download Azure Kinect Body Tracking SDK
1313

14-
This document provides links to install each version of the Azure Kinect Body Tracking SDK.
14+
This document provides links to install each version of the Azure Kinect Body Tracking SDK.
1515

1616
## Azure Kinect Body Tracking SDK contents
1717

@@ -23,6 +23,7 @@ This document provides links to install each version of the Azure Kinect Body Tr
2323

2424
Version | Download
2525
--------------|----------
26+
0.9.3 | [msi](https://www.microsoft.com/en-us/download/details.aspx?id=100307) [nuget](https://www.nuget.org/packages/Microsoft.Azure.Kinect.BodyTracking/0.9.3)
2627
0.9.2 | [msi](https://www.microsoft.com/en-us/download/details.aspx?id=100128) [nuget](https://www.nuget.org/packages/Microsoft.Azure.Kinect.BodyTracking/0.9.2)
2728
0.9.1 | [msi](https://www.microsoft.com/en-us/download/details.aspx?id=100063) [nuget](https://www.nuget.org/packages/Microsoft.Azure.Kinect.BodyTracking/0.9.1)
2829
0.9.0 | [msi](https://www.microsoft.com/en-us/download/details.aspx?id=58402) [nuget](https://www.nuget.org/packages/Microsoft.Azure.Kinect.BodyTracking/0.9.0)
@@ -47,6 +48,13 @@ If the command succeeds, the SDK is ready for use.
4748
4849
## Change log
4950

51+
### v0.9.3
52+
* [Feature] Publish a new DNN model dnn_model_2_0.onnx, which largely improves the robustness of the body tracking.
53+
* [Feature] Disable the temporal smoothing by default. The tracked joints will be more responsive.
54+
* [Feature] Improve the accuracy of the body index map.
55+
* [Bug Fix] Fix bug that the sensor orientation setting is not effective.
56+
* [Bug Fix] Change the body_index_map type from K4A_IMAGE_FORMAT_CUSTOM to K4A_IMAGE_FORMAT_CUSTOM8.
57+
5058
### v0.9.2
5159
* [Breaking Change] Update to depend on the latest Azure Kinect Sensor SDK 1.2.0.
5260
* [API Change] `k4abt_tracker_create` function will start to take a `k4abt_tracker_configuration_t` input.

articles/kinect-dk/troubleshooting.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,31 @@ For more information, see below clip from header file:
5656
*/
5757
```
5858

59+
Logging for the Body Tracking SDK K4ABT.dll is similar except that users should modify a different set of environment variable names:
60+
61+
```console
62+
/**
63+
* environment variables
64+
* K4ABT_ENABLE_LOG_TO_A_FILE =
65+
* 0 - completely disable logging to a file
66+
* log\custom.log - log all messages to the path and file specified - must end in '.log' to
67+
* be considered a valid entry
68+
* ** When enabled this takes precedence over the value of K4A_ENABLE_LOG_TO_STDOUT
69+
*
70+
* K4ABT_ENABLE_LOG_TO_STDOUT =
71+
* 0 - disable logging to stdout
72+
* all else - log all messages to stdout
73+
*
74+
* K4ABT_LOG_LEVEL =
75+
* 'c' - log all messages of level 'critical' criticality
76+
* 'e' - log all messages of level 'error' or higher criticality
77+
* 'w' - log all messages of level 'warning' or higher criticality
78+
* 'i' - log all messages of level 'info' or higher criticality
79+
* 't' - log all messages of level 'trace' or higher criticality
80+
* DEFAULT - log all message of level 'error' or higher criticality
81+
*/
82+
```
83+
5984
## Device doesn't enumerate in device manager
6085

6186
- Check the status LED behind the device, if it's blinking amber you have USB connectivity issue and it doesn't get enough power. The power supply cable should be plugged into the

0 commit comments

Comments
 (0)