Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.20
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2070 (NVidia) Memory: 8GB, Driver date: 4-11-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 552.22
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port 0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 4-11-2024
Driver Version: 31.0.15.5222
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\SimLab\Plugins\SimLab 3D PDF From Rhino 6\plugins\SimLabPDFExporter.rhp “SimLab PDF Exporter”
hi @Charles thanks for sending the files.
there is still some mix-up happing with rui and xml files, and so far I haven’t been able to pinpoint how it happens.
When you closed the toolbar, did you have any other instances of Rhino open?
yes, but I get the same result in Windows.
For some reason Rhino doesn’t clean the xml files it generates.
I bet you get a good toolbar once you find the similarly named xml file in your Scheme_Default folder
(%appdata%/mcneel/rhinoceros/8.0/settings)
I didn’t expect that, but still needed to make sure
I’ve been hunting this problem for a while, but unfortunately cannot reproduce it on my end. Here the xml always gets erased correctly when I save the rui and close Rhino.
I’d expect the xml is killed right after the rui is saved.
And not when Rhino shuts down.
If Rhino should crash or somehow forgets what to do, killing the xml wouldn’t happen.
Yep, that is my experience too. @stevebaer shut off the automatic saving of .rui files awhile back because there were too many bugs when that happened… A number if them have now been fixed. I don’t know when it should be turned back on…
Dunno, I recently made a toolbar with 18 buttons in one go, and it still works fine.
However, that being said, I no longer make new toolbar buttons in the classic way. I first make all the macros that will go in the LMB/RMB via the Macros dialog, including macro name, commands, tooltips image etc. Then I make all the buttons, choosing the macros from the library.
@charles, I tried following your process to recreate the toolbars the way you did in the video, and it just worked well for the most part. I agree that deleting the xml right on save should be better, but I’m afraid it is not going to work very well with multiple instances open. But @stevebaer will be able to judge this better.
I will ask what the current status is regarding the xml files for custom RUI files. As mentioned before, the ultimate goal is to get rid of them completely for custom RUI files.
The multiple instances ‘problem’ is still the same.
Perhaps a warning like 'Multiple instances detected. The last closed Rhino will win writing the settings.'
could be helpful.