Curve Offset Bug

Hi RMA, maybe @Joshua_Kennedy

Attached you’ll find an example where a curve offset fails depending on the position of the curve.
The red curve is history based, simply move the curve to the right and see…

Thanks,
Jess

Rhino 9 SR0 2026-1-6
curve_offset_bug_jM.3dm (2.5 MB)

Thank you @Jess for your report, and I have logged this issue with our development engineers.

RH-91403 Offset: the record history cannot be maintained

1 Like

Thanks @jessesn !

What makes me wonder is why the file size is 2.5MB?
Even after SaveSmall, but that may be a different problem…

Thanks,
Jess

I’m seeing this issue as well, and I will log this issue with out development engineers. Thank you.

I thought that the ~2mb file size even on virtually empty files is due to the hi-res thumbnail stored in the file?

1 Like

Hmm, exporting to V8 with Save Geometry only gives me 2508 KB for a single line segment. Same thing saved small with V8 is 37 KB. And I don’t see any difference in the thumbnail.

1 Like

no its not, and its infuriating me for years that i have to export a file instead of saving it to save it at a reasonable size, something i have brought to attention already 10 years ago i believe, with no outcome and false explanations from mcneel that caused that myth regarding the thumbnail.

What are your file compression settings between V8 and the WIP?

1 Like

Hi Mitch,
Thanks for the hint. Using Compression in SaveAs in V9 solves that issue.
In V8 I don’t have that setting.
Jess

In V8 it should be here:


(in WIP also)

i am really curious if you are using a mac or a windows here. i have this activated on v8 for mac since forever and just saving one tiny circle without texture, saving small, geometry only and without plugins i still get 3.3 mb.

the only way i get it smaller is using export instead of save, save as.

Hi @encephalon

I’m using V9 on Mac and Windows. After enabling compression in SaveAs dialog on Mac I’ve got a file size of 100KB with a simple circle.

Jess

I have compression turned off as it drastically slows down file saving. I’m not really worried about file size…

Yeah, looks like compression does a good job on the overhead in small files. This may make sense when working on huge assemblies with many small linked files.

I made a test with a 500MB file and compression saves about 20% which may not be worth the delay.

Oh - and it looks like that compression actually is a document setting. Once saved compressed from the SaveAs Dialog it will be compressed later on when saved. Makes sense.

Why don’t make a new variable setting so that the user could set a minimum file size (like 300 MB) above which Rhino will save with no compression, while everything below (less than 300 MB) will use compression? That should provide compression and relatively sorry save time for most files, while the large ones will be saved quickly at the cost of taking extra space on the hard drive.

What about another possible solution, having two “Save” functions (LMB/RMB): one will save with no compression, the other one will use compression.