[Oleksandr Kramer]

You can restore a database using MySQL Workbench

To restore a database from an SQL file backup using MySQL Workbench, you can follow these steps:

1. Launch MySQL Workbench and connect to your MySQL server.
2. On the home screen, click on the “Server” menu and select “Data Import”.
3. In the Data Import/Restore window, choose the “Import from Self-Contained File” option.
4. Click on the folder icon next to the “Import from Self-Contained File” field and browse to the location where your SQL file backup is stored. Select the file and click “Open”.
5. Once you have selected the SQL file, you will be back at the Data Import/Restore window. Ensure that the “Default Target Schema” is selected or choose a specific schema from the dropdown if you want to restore the database to a different schema.
6. Review the other import options such as Import Options, Object Creation Options, etc., based on your requirements. You can modify these options as needed.
7. Click on the “Start Import” button to begin the restoration process.
8. MySQL Workbench will execute the SQL statements from the backup file and restore the database. You can monitor the progress in the “Output” tab.
9. Once the restoration process is complete, you will see a summary of the import process. Review the summary to ensure the restoration was successful.
10. You can now close the Data Import/Restore window and verify that your database has been restored by checking the schema and tables in MySQL Workbench.

Please note that the steps mentioned above are based on MySQL Workbench version 8.0. The user interface and options may vary slightly depending on the version you are using, but the overall process should be similar.

[Oleksandr Kramer]

Unfortunately, currently this option doesn’t present. Moving in most cases will break links from other scenes/material libraries. So copy option is safer.

[Oleksandr Kramer]

This issue is fixed in version 3.21.04
You can download the latest version from the dashboard.
Auto-updater will be triggered in a few days if there’s no critical issue found.
Thanks for your feedback.

[Oleksandr Kramer]

You can save to formats as early as 3 versions prior to the current version. This is a 3Ds Max limitation

[Oleksandr Kramer]

Hello

1. Check if the pivot of SceneDummy is located at the bottom
2. Try to override the pivot for models in the render settings

[Oleksandr Kramer]

No – all work as always. Just remember that scenematerial is a read-only material library.
You mess scenematerials and material library files





 

[Resolved]

[Oleksandr Kramer]

This a logical 3ds max restriction for all versions – of course, you can’t add new materials directly to the scene materials, because it doesn’t material library file.
To add a new material to the scene, you should assign it to the object.
You should use the material library file to add new materials from the SME

[Oleksandr Kramer]

Thank you!

[Oleksandr Kramer]

You can’t add new materials to scene materials in this way.

You should use the material library file to add new materials from the SME

[Oleksandr Kramer]

In case a file has the status #Found, the tool will use a link that found by 3ds Max system

[Oleksandr Kramer]

It asks only in case the files are different

[Oleksandr Kramer]

This issue is fixed in version 3.20.25
You can download the latest version from the dashboard.
Auto-updater will be triggered in a few days if there’s no critical issue found.
Thanks for your feedback.

[Oleksandr Kramer]

You right . This work as expected for models, but relink materials not to the nearest location.
Thanks for your feedback

[Oleksandr Kramer]

Image size uses settings from these options

[Oleksandr Kramer]

Hello
Please attach here or send to email your template material
You can find it by this path %localappdata%\Kstudio\data\