World Axes Icon visible in raytraced mode but is switched off in settings

Rhino Rhino for Windows
1

I have the world axes icon switched off in the raytraced mode settings yet it is displayed in my renders.

I am using _ViewCaptureToFile to render custom resolution images.

Version 6 SR29
(6.29.20238.11501, 25/08/2020)
Commercial

Exhibit A:

image
image1382×1343 53.8 KB

Exhibit B:

v6_1k_black_ps
v6_1k_black_ps1333×750 89.2 KB

2

You likely have it or cplane axes enabled in the capture dialog, or on the capture command line:

Exhibit A
Exhibit A1140×59 5.25 KB

Exhibit B
Exhibit B405×637 75.9 KB

3

thanks Nathan,

my python script wasn’t explicitly setting DisplayWorldAxes to No

I set it to No and all is well but I am having occasional crashes when rendering. I ignored the offer to tell McNeel because I just wanted to some renders done.

Now I want to send a crash report but the last crash didn’t raise the crash report dialog.

I have a crash dump 3dm file and a rhinodotnetcrash.txt file on my desktop. The 3dm file is 591 Mb in size.

Should I just post a crash msg here and try to upload the files?

Is there something in the Rhino UI that will do the job of the crash report dialog (for all those people who change their minds and decide to send that report after all)?

4

Hello - best would be to reproduce the crash with the report UI. If you cannot, can you export the relevant objects to a new file, verify the problem still happens, and send us that, to tech@mcneel.com? If it only happens with the full file, send us that if you can - please include a link to this topic. If the file is very large, please SaveSmall, Zip and upload to www.rhino3d.com/upload to my attention.

-Pascal

5

I ran the render again and it didn’t crash.

I noticed that a lot of ram was being used (saw it in task manager). I had a fair number of programs open so I closed them and memory usage went down to ~50%. And I got no crash.

Maybe it’s ram related.

I used to have this problem when I only had 16 Gb of ram so upgraded to 32 Gb. But when I only had 16 Gb there were screen drawing issues when a render was running. I don’t see those issues these days with 32 Gb. (There were black rectangles on screen were windows should have been. I think that Windows was running out of memory to buffer window images.)

I’m going to kick off a new batch of renders and see if things fall over then. I will upload the crash report and file if I get a crash.

PS

It would be nice if Rhino saved enough info to be able to upload crash reports at a later date. And a way to launch the reporting dialog by hand.

Is there documentation available that says what’s needed for a crash report? Are there hidden (or not obvious) files? Or is there only the text file and crash file on the desktop?