| Publisher: | MOBOTIX AG |
|---|---|
| Author: | Bernd Wilhelm Thilo Schüller |
| Date: | 2025-12-16 |
| Document: | release-notes_V5.4.10.4_en_v1.1.html |
| Confidentiality: | public |
These Release Notes contain a technical description of the most important changes in the software for the MOBOTIX network cameras.
| Release Version | Creation Date | Publishing Date |
|---|---|---|
| MX-V5.4.10.4 | 2025-11-10 | 2025-12-16 |
| MX-V5.4.9.9-r1 | 2024-10-22 | 2024-10-24 |
| MX-V5.4.9.4-r3 | 2024-06-14 | 2024-06-17 |
| MX-V5.4.9.4-r1 | 2023-10-04 | 2023-10-16 |
| MX-V5.4.9.4 (replaced by MX-V5.4.9-r1) |
2023-06-01 | 2023-06-16 |
| MX-V5.4.8.4-r2 | 2023-02-24 | 2023-03-03 |
| MX-V5.4.8.4 | 2022-12-01 | 2022-12-07 |
| MX-V5.4.7.12 | 2022-08-26 | 2022-09-02 |
| MX-V5.4.6.7 | 2022-01-27 | 2022-02-15 |
| MX-V5.4.6.6 (replaced by MX-V5.4.6.7) |
2022-01-07 | 2022-01-27 |
| MX-V5.4.6.3 | 2021-09-21 | 2021-09-28 |
| MX-V5.4.0.55 | 2021-04-21 | 2021-06-02 |
| MX-V5.4.0.49 | 2020-12-11 | 2020-12-16 |
| MX-V5.4.0.45 | 2020-11-09 | 2020-11-12 |
| MX-V5.4.0.44 | 2020-09-17 | 2020-09-18 |
| MX-V5.2.6.7 | 2020-06-16 | 2020-06-24 |
| MX-V5.2.6.4 | 2020-05-15 | 2020-05-20 |
| MX-V5.2.6.2 | 2020-04-23 | 2020-05-05 |
| MX-V5.2.5.15-r1 | 2020-03-05 | 2020-03-12 |
| MX-V5.2.5.15 (replaced by MX-V5.2.5.15-r1) |
2020-01-28 | 2020-02-14 |
| MX-V5.2.4.15-r2 | 2019-09-25 | 2019-10-01 |
| MX-V5.2.4.15 |
2019-07-26 | 2019-07-31 |
| MX-V5.2.3.30 | 2019-04-11 | 2019-04-15 |
| MX-V5.2.1.4 | 2018-12-20 | 2018-12-20 |
| MX-V5.2.0.61 | 2018-10-30 | 2018-11-02 |
| MX-V5.1.0.99-r4 | 2018-10-24 | 2018-11-06 |
| MX-V5.1.0.99-r3 (replaced by MX-V5.1.0.99-r4) |
2018-07-11 | 2018-07-13 |
| MX-V5.1.0.99 (replaced by MX-V5.1.0.99-r3) |
2018-06-15 | 2018-06-15 |
| MX-V5.0.2.14 | 2018-02-07 | 2018-02-14 |
| MX-V5.0.1.53 | 2017-10-26 | 2017-11-20 |
| MX-V5.0.0.133 | 2017-07-21 | 2017-08-08 |
| MX-V5.0.0.130 | 2017-06-21 | 2017-07-14 |
| MX-V5.0.0.127 | 2017-04-27 | 2017-05-05 |
Creation Date: 2025-11-10
Publishing Date: 2025-12-16
Try the following solutions in order. After each step, restart the VM to test.
If the host machine has no physical display attached (a headless server) or you are connected via RDP, the GPU may not initialize properly, causing the hypervisor to believe 3D support is absent.
evenstream.jpg is abortedevenstream.jpg,
for example by the MxManagementCenter, are now better handled. In this case, a message "hh:mm:ss STREAM eventstream[nnnn] Closing stream to 10.xx.yyy.zzz. Write timeout."
is written to the system messages, which suggests an external interruption of the data stream due to network disturbances or a failure of the eventstream client
as the cause of the problem.
The software contains the
same known limitations as the version MX-V5-4-9-9-r1.
Try the following solutions in order. After each step, restart the VM to test.
If the host machine has no physical display attached (a headless server) or you are connected via RDP, the GPU may not initialize properly, causing the hypervisor to believe 3D support is absent.