Thank you for installing 3ds Max 2025. Use Autodesk Access (formerly Autodesk Desktop App) to download and install automatically, or access the download from your Autodesk Account.

3ds Max 2025 system requirements

3ds Max 2025 installation and licensing

To learn about the new features and updated workflows, see What's New in 3ds Max 2025. The rest of these release notes describe known limitations and fixes included in this release.

• What's Fixed
• Known Issues and workarounds

What's Fixed

Note that 3ds Max 2025 also includes fixes delivered in 3ds Max 2024.1 and 2024.2. Check out the following links for more information.

• 3ds Max 2024 Update 1 Release Notes

• 3ds Max 2024 Update 2 Release Notes

• 3ds Max 2024 Update 2.1 Release Notes

Back to top

Back to top

Back to top

Back to top

Back to top

Back to top

Back to top

Back to top

Back to top

Back to top

Known Issues and workarounds

With the introduction of Qt's new Rendering Hardware Interface (RHI), the render surface management of the underlying Qt windows has changed.

Developers need to take extra care when embedding/parenting a QWidget that uses RHI for rendering like QWebEngineView or QQuickWidget into the 3dsMax application QMainWindow. The parenting process on the Qt side is now taking the render surface type into account and when a QWidget gets parented it will compare both surface types and convert the parent's top level window surface to match the surface type of the new RHI based child widget. Unfortunately it always does this by destroying and recreating the underlying native platform window, which can be our 3ds Max application window. This will end up in crashing 3ds Max due to its mixed UI frameworks (Win32, .Net, and Qt) which rely on a persistent application HWND for parenting.

Refer also to this Qt bug report for more information.

In case of 3ds Max, the initial surface type of the application's QMainWindow is QSurface::RasterSurface, whereas for example a QWebEngineView could be on QSurface::OpenGLSurface or QSurface::Direct3DSurface. So by parenting the QWebEngineView into the application window, for instance using a QDockWidget, the 3ds Max surface type will be changed to OpenGLSurface/Direct3DSurface, which causes the deletion of 3ds Max native platform window.

Workaround: There are ways to workaround this issue. The child needs to have its own QWindow in the background, separated from the QWindow of the top level parent widget where the child is supposed to get embedded. By keeping the QWindow for the child, it will still render in its own surface and not in the parent one, thus no conversion of the top level window's surface type will happen.

In practice this can be achieved by using QWindow based Qt UI components, as far as available, and embed them via the QWidget container created by the QWidget::createWindowContainer() method into the parent UI.

For QML you can use the QQuickView instead of the QQuickWidget. QQuickView is QWindow based.

auto quickView = new QQuickView();
quickView->setResizeMode(QQuickView::SizeRootObjectToView);
quickView->setSource(QUrl::fromLocalFile("Panel.qml"));
// Create a container widget so that the child's QWindow can be properly embedded into the top level parents QWindow.
QWidget* container = QWidget::createWindowContainer(quickView);
auto dockWidget = new QDockWidget("QQuickView Dock Window", mainWindow);
dockWidget->setAllowedAreas(Qt::AllDockWidgetAreas);
mainWindow->addDockWidget(Qt::LeftDockWidgetArea, dockWidget);
// Add quickView container widget, which refers to the QWindow we created for the quickView.
dockWidget->setWidget(container);

You can also embed QWidget-based UI like the QWebEngineView into a parent widget hierarchy without changing the top level window's surface type. You just need to force the creation of the actual QWindow for the child widget and then create a second container widget around its QWindow which you then use for the parenting.

auto webView = new QWebEngineView();
webView->load(QUrl("https://qt-project.org/"));
// Force the creation of the QWindow, since QWebEngineView is QWidget based
webView->winId();
// Create a container widget so that the child's QWindow can be properly embedded into the top level parents QWindow.
QWidget* container = QWidget::createWindowContainer(webView->windowHandle());
// Create dock widget for hosting a web view
auto dockWidget = new QDockWidget("WebView DockWidget", mainWindow);
dockWidget->setAllowedAreas(Qt::AllDockWidgetAreas);
mainWindow->addDockWidget(Qt::LeftDockWidgetArea, dockWidget);
dockWidget->setFloating(true);
// Add webView container widget, which refers to the QWindow we created for the webView.
dockWidget->setWidget(container);

Back to top