How to determine what's wrong with a file when UVtools cannot open it with crash

[Megidd]

I try to open this faulty CBDDLP file. The UVtools crashes and cannot open it. Is there any tool to figure out why UVtools crashes, i.e. to find out what's wrong with the file?

teapot_2021-06-09 (3).zip

The crash happens at random times:

• When loading thumbnails
• When loading layers
• ...

Some screenshots right before the crash:

[sn4k3]

Are you on a Linux OS?

1. Go to UVtools -> Help -> Open settings folder
2. Open the "errors.log"

EDIT: Ok i found the problem. That file is very old, is from Version: 1 of the format which UVtools do not fully known. It's only ready to deal with v2 and v3. That file must have years... Even PhotonFileValidator can't read it. Somehow is corrupted. You can try run on printer without vat to see if it runs.

[sn4k3]

well your preview data was incomplete/bad and layer exposure was set to a very high value. Other than that everything else look ok.
You also have this in Go: https://github.com/ezrec/uv3dp Much more modern, complete and support much more files.
Also you can use UVtools Core to generate files if you want but only with C# or powershell: https://github.com/sn4k3/UVtools/tree/master/UVtools.Powershell

UVtools GUI also allow you to import a collection of PNGs to replace a layer colection and upload previews

[Megidd]

I installed VS 2019 Community Edition and the tools here 😃 Opening the solution, there are two sub-projects marked as incompatible. Not sure why! 3 out of 5 sub-projects are built fine 😄

[Megidd]

Also, when running build\CompileWindows.bat, an error is thrown:

MSBUILD : error MSB1009: Project file does not exist.
Switch: UVtools.sln

[Megidd]

When I try to use the debugger, this error is shown 😕 I'm not sure how to resolve it:

[sn4k3]

I installed VS 2019 Community Edition and the tools here 😃 Opening the solution, there are two sub-projects marked as incompatible. Not sure why! 3 out of 5 sub-projects are built fine 😄

Ignore them, they are the MSI installer, not required, you can also unload them.

Also, when running build\CompileWindows.bat, an error is thrown:

Strange, it works for me:

UVtools.sln Compile
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe"
Microsoft (R) Build Engine version 16.10.1+2fd48ab73 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
Build started 10/06/2021 14:30:16.
Project "D:\Tiago\Dropbox\Programming\C#\UVtools\UVtools.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Release|Any CPU".
ValidateProjects:
  The project "UVtools.InstallerMM" is not selected for building in solution configuration "Release|Any CPU".
  The project "UVtools.Installer" is not selected for building in solution configuration "Release|Any CPU".
Project "D:\Tiago\Dropbox\Programming\C#\UVtools\UVtools.sln" (1) is building "D:\Tiago\Dropbox\Programming\C#\UVtools\
UVtools.Core\UVtools.Core.csproj" (2) on node 1 (default targets).
CoreGenerateAssemblyInfo:
Skipping target "CoreGenerateAssemblyInfo" because all output files are up-to-date with respect to the input files.
CoreCompile:

When I try to use the debugger, this error is shown 😕 I'm not sure how to resolve it:

You are trying to debug a library (UVtools.Core), you need to switch for UVtools.WPF.
Right click on UVtools.WPF on right panel, and set it as default project.
OR click on the list where says UVtools.Core near the green debug button and switch to UVtools.WPF