SUModelSaveToFile doesn't create file on Release build with msvc

Developers SketchUp SDK
1

So on msvc2022 when I compile the x64 Release build with latest SDK - so on Debug x64 it’s slower but at the end it creates a file in the project directory, but with the release one I don’t see the output model.

I use:

SUModelSaveToFile(model, “new_model.skp”),
//SUModelRelease(&model),
SUTerminate(),
system(“PAUSE”);

To terminate. Thanks in advance.

Forget the memory part - it’s unrelated - but I consistently get the above problem.

2

Hi,

Just a quick guess: maybe when you debug you are running the app as administrator. Try running the release app as administrator. It can be a directory or file access rights issue.

Attila

3

I agree. All the file operations for all SketchUp APIs will operate on the current working directory unless you use a full absolute path.

If not using absolute paths, save the working directory before using a file function, set it to your target path and reset if after.

4

Take note of the Memory Management in the SketchUp C API section of the API main page:

https://extensions.sketchup.com/developers/sketchup_c_api/sketchup/index.html

1 Like
5

Yeah I save it under my project folder - I run both Debug And Release from Visual Studio and they both operate on the same directory - don’t know how one could have different permission.

Oh you are saying the Release build may have different current directory - but also I had the same issue running outside Visual Studio and the Release build doesn’t save in the current directory.

It’s a simple cmd app - I don’t change my working directory.

6

This has nothing to do with VS. It is all about where the model file is saved at runtime of your app.

But what is it? Any other app could change the WD at any time.
It is always safer to use absolute file paths.

Ie … your sample code was only a .skp file name without a path.

7

Ok I understand - will try an absolute directory next time - hopefully it works this way thanks.

8

To this day still issue fix your library please

9

I don’t care what whatever refers to whatever every other APIs work your doesn’t please

10

You are mistaken. I do not work for Trimble. I cannot fix the API nor your code.
Since you’ve decided to be churlish with downvotes, I’ll no longer offer you any opinions.

1 Like
11

So bad for me

12

Never mind is because the code is in assertion oh well

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.