If you send us a file that you think takes too long to open in Rhino, we can review it and see if there are any optimizations that could be made.
Hi,
Will do, its big, what method do I use ?
Cheers
Steve
Hi
uploading to link I received, have had to find the three objās and their assoc files. then zipped the entire lot as only one file allowed !
1Gb.
layers with objās on are prefixed ##.
One has rulers in the image, subject of another problem with V8 that HID THEM !.
V5 showed them, this is the v5 file that I have been on ever since it solved that problem.
I normally work on the lowest of the three layers ##.
but sometimes the RULERS one as some textures are clearer.
I initially IMPORTED the rulers one, as no one ever told me otherwise. then scaled and oriented it level in all planes.
then imported the more complete one, (thats is currently turned on) (ita diemed from many more photos) and matched it as exact as was poss.
then another.
I need max detail, so all this crap about decimation, NO NO NO !!! its bad enough as it is with what is like working on objects covered in scrunched up cooking foil then unravlleed and glued all over. Trying to get the true faces off surfaces. sections all wriggly.
Come the day there is a prog that decimates ONLY smooth areas and keeps polys as fine as poss in the detail areas, all will be good.
so dont even suggest decimation, as I need detail detail detail, .decimation is for things to look good and not be used for reverse engineering.
I in fact need far more polys but Agisoft standard doesnt do such, and rhino would cease to work if so.
Its already a complex file and I havent even got into my stride yet ! I tidy up as I go along, saving as V2 then v3 etc,
Its confidential.
It has I see a clipping plane ON. ā¦ClippingPlane view brake assyā¦so turn that layer off to see the full mesh !
Just how can I insert the obj (all 3 of 'em) and have its true high res texture show each time, (and in V8 get the ghosted ruler to show) something V5 does by default, and get in exact same location and size, and speed things up.
Steve
If you want to see how much Rhino should be improved to work with meshes, open the same model in both, Rhino and BalancerNPro. The latter performs about 100-1000 times better on my 2014 PC and handles models with millions of polygons with ease, while Rhino often freezes or crashes with the same models.
Note that Rhino is especially weak when it comes to moving, scaling or rotating a 3d mesh in the viewport. I wrote in numerous topics that Rhinoās undo stack causes issues with memory leakage, so after 2-5 translations of a mesh model with more than 2-3 million polygons, my Rhino 7 simply crashes. I have 16 GB or RAM, and itās eaten by the undo stack in seconds.
That issue multiplies by a lot when you deal with a scene consisting hundreds or thousands of tiny meshes instead of a single mesh. 3d scan data often consists separate meshes that are a huge burden to Rhino. BalancerNPro does not have that issue, itās super smooth even on an old PC.
A few years ago I have been working on some complex models with 10 million polygons on another PC in a company that had 64 GB of RAM. Even that amount of RAM was filled after a couple of minutes and Rhino crashed. My recommendation is to work on a PC with at least 64 GB or 96 GB of RAM if possible. Forget to use a PC with 32 GB or less if you deal with models consisting more than 5-10 millions of polygons. Video RAM may also be an issue, so make sure to use a newer model with at least 12-16 GB of VRAM. Sadly, Rhino is not optimized to handle dense mesh models.
While BalancerNPro could be used to reduce the polygon count with a minor sacrifice of quality at 20% (5 times less polygons), I have no idea whether the modified model will preserve the texture coordinates. Most likely not.
Iāve put that on the list here: RH-88567 Display: Reported Performance Issue
-wim
Hi, need URGENTLY to know as askedā¦
However maybe import is bad practice.
So I need to use Insert and browse to the obj instead. Is that so ?
I had used import obj and browsed to the obj, then V8 allocates the raster image to it, whilst V5 one had to browse to the image.
If i were to try insert for the exact same obj, would it locate to the same position as the existing.
It took me ages to orient it and scale it, as I have three of them that must match, being the same object, one with rulers in the result from Agisoft. matched to have the same spider shit, the same rust spot exact same place.
I canāt redo it all again.
whats the best way of getting them all to match position using insert ?
and my system specs:-
OS Name Microsoft Windows 10 Pro
System Model B550 Pro4
Processor AMD Ryzen 7 5700X 8-Core Processor, 3401 Mhz, 8 Core(s), 16 Logical Processor(s)
Total Physical Memory 63.9 GB
Available Physical Memory 51.7 GB
Name NVIDIA GeForce RTX 3070
FPU has 8GB of GDDR6 memory
AND ASKINGā¦
whats the best way of getting them all to match position using insert ?
Cheers
Steve
Hi Steve -
Itās not clear to me why you would need to do that.
I guess Martin will need to provide background for that statement.
If the only aim is to keep individual files small, then, yes.
Rhino doesnāt auto-align different files that are imported / inserted, so youād have to do that over again if you were to insert the .obj files as linked blocks.
-wim
I like to be able to update a file and keep the file size low so in most situations I use insert.
Hi,
Having uploaded my file with the meshes,
Carla says
Thank you, Iām able to reproduce the problem.
and mentions Wim. RH88567
Iāll wait for our developers to take a look and get back to you.
so maybe wait, as using Insert and redoing all the meshes will be hell.
and Wim , you doubt if Insert is needed.
Steve
I regularly use meshes with around 10 million faces without difficulty. I just did a test with a textured mesh with almost 10 million faces. The mesh was created in Metashape and exported as an .obj file. Open double precision polygon mesh: 5007065 vertices, 9379648 faces with normals.
Importing the mesh took about 40 seconds. Rhino reports it is using 4858 MB of memory.
I imported three additional meshes with a total of over 12 million faces.
With all four meshes displayed, about 22 million faces in total, I can pan and spin the viewport with no obvious lag in rendered, shaded and wireframe modes.
Intel(R) Coreā¢ i7-10700KF CPU @ 3.80GHz, 3801 Mhz, 8 Core(s), 16 Logical Processor(s)
NVIDIA GeForce RTX 2080 Ti 11GB
Resolution 3840 x 2160 x 59 hertz
Rhino 9 SR0 2025-7-15 (Rhino WIP, 9.0.25196.12305, Git hash:master @ 9639bf30c8f88fa73b762adfb15a9b170cd9bfae)
License type: Commercial, build 2025-07-15
License details: Cloud Zoo
Expires on: 2025-08-29
Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 64GB)
.NET 9.0.7
Computer platform: DESKTOP
Standard graphics configuration using OpenGL
Primary display: NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 3-14-2025 (M-D-Y). OpenGL(4.6.0 NVIDIA 572.83)
> 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
GPU Tessellation is: 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: 3-14-2025
Driver Version: 32.0.15.7283
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB
OpenBLAS: OpenBLAS 0.3.29 DYNAMIC_ARCH NO_AFFINITY Haswell MAX_THREADS=64.
Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp āUpdatesAndStatisticsā 9.0.25196.12305
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp āCommandsā 9.0.25196.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp āRenderer Development Kitā
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp āRhino Renderā 9.0.25196.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp āRDK_EtoUIā 9.0.25196.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp āSnapshotsā
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp āMeshCommandsā 9.0.25196.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp āRhinoCyclesā 9.0.25196.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\Toolbars\Toolbars.rhp āToolbarsā 9.0.25196.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxrhino.rhp ā3Dconnexion 3D Mouseā
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp āDisplacementā
C:\Program Files\Rhino 9 WIP\Plug-ins\Calc.rhp āCalcā
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp āSectionToolsā
C:\Program Files\Rhino 9 WIP\Plug-ins\import_OBJ.rhp āImport_OBJā 9.0.25196.12305
Hi David,
Do you have an obj or three, as I have also imported three of the very same object from Agisoft, with subtle differences, existing light, flashgun and ruler.
Closed double precision polygon mesh: 6,513,424 vertices, 11,771,544 polygons I work on most of the time.
Open double precision polygon mesh: 584,494 vertices, 1,131,257 polygons was with rulers for establishihg true size.
Open double precision polygon mesh: 3,654,147 vertices, 7,162,530 polygons another slight variation in lighting.
To then follow a set of tests you say to do, time each one. and compare performance.
Itching to see how my V8 and 3070 with 8Gb ram and system 64Gb DDR4 corsair vengeance pro with all SSD drives performs. compared to same tests you would give results for.
They could be
- import time,
- scale time.
- rotate time.
- project line to time.
- go from perspective to 4 view time.
- frim 4 view to front view time
- others you devise.
In fact others could do same tests, let us compare.
This would form a real world test of our systems. as Holomark is for a non real world test.
Good feedback to the developers who are now with a āseen problemā.
Its clear others say meshes and Rhino are not a happy marriage., so lets get some tests done.
Steve
@Steve1
Import - 10 million face mesh - about 40 seconds.
Scale - 4 meshes with total of 22 million faces - about 10 seconds
Rotate - 4 meshes with total of 22 million faces - a couple of seconds to 8 or 9 seconds
Single perspective viewport to 4 viewports - less than a second
4 viewports to front viewport - less than a second
Project a line onto a mesh with 10 million faces; result is a polyline with 458 points - about 40 seconds.
Hi,
so now to test my V8 with such a mesh, but can I/we have that mesh to try with.
as asked have you a mesh to share for testing ?
or would my 11 million poly mesh be suitable ?
Steve
Hi Steve -
I imported your 3 .obj files into Rhino and saved that as .3dm. There are 3 mesh objects and PolygonCount says there are 0 quadrilateral polygons and 11ļ¾ 236ļ¾ 673 triangular polygons in this selection
Import that .3dm into a new Rhino file - 44 seconds
Scale - 12 seconds
Rotate - 10 seconds
Single perspective viewport to 4 viewports - instant
4 viewports to front viewport - instant
Project a line to all 3 meshes - 25 seconds, 22 curves created with 15 548 points
Move all 3 meshes - 11 seconds
-wim
BalancerNPro does preserve the texture.
Hi,
My V5 with the three meshes and some more solids made, 6 nuts, 6 collars, 6 cylinders, an imported brake drum and hub, and wheel rim, from another file, has gone SLOOOOOW.
rotating in perspective isnt even smooth but a time lag and VERY jerky,
unusable !
save file. 1Gb in size now. said usb SSD drive full, so saved to internal after moving out files to usb.
what size Wim is your file with my meshes ?
I wonder if 6 nuts, studs etc not being āthingysā of a master (cant remember name as hate it) is an issue, However I dont do āthingyā as its hell on earth, or has been, canāt change colours, cant do this and that, and V8 rotates smoothly so its not those anyway.
open that file in V8 and its not jerky.
so back to v8 now. and poor lines, so perhaps now V9 as it adopts V8 v22.
ye gods.
Rhino has a mesh issue . or V5 does.
Hi David
@davidcockey
Is there a mesh I can test with ?
Steve
Hang onā¦
In your June 8 reopening of this old thread, you say this is a Rhino 8 issue. Is that not the case??
-wim
Hi,
V5 and V8 are SLOW, V5 also slow on saving, 2 mins almost, though V8 quicker, as can turn off compression option.
Its over 1Gb in V5, so hate to think of what it is with no compression. !
McNeel have the file as V8, and can replicate the slowness.
since sending to Mcneel V5 has gone jittery in perspective mode, turn off mesh and slick as ice.
3 meshes 11.2million polys.
I have given my system specs,
is there anything wrong with them ?
I am all SSD. the entire tower was remade to be for mesh use in Rhino, this is very upsetting.
how will anyone cope when with Rhino and meshes ?
Agisoft in decimation has no protection of detailed areas.
I have need of ACCURATE sections and especially though nuts, bolts etc, yet I see flat areas with minute triangles, which could be with far less. However I cannot afford to lose one pixel of my jpg.
so just what prog to intelligently re-do the polys after the obj is made in Agisoft ?
One I can afford ?
$1,900 repeated payment. OMG.
balancerNpro does in seconds what Rhino takes minutes at, That says everything.
I am sure Rhino has a fundamental problem with meshes. I am with everything slow, its impractical. I am open to any suggestions to speed things up, but look at what Bobi says.
Its like taking a ford escort to the garage again and again, they remove the bodywork and seats to get more speed from it, then I buy a mazda fastback and no need to ever go to garage again.
Steve
Hi Steve -
As both David and I have reported, 3 meshes totaling 11 million faces is perhaps somewhat slow but not to the point that it becomes impossible to work with.
Based on your report, I only checked performance by importing your three .obj files into a new file. That saves to 684 MB, by the way.
One of your more recent threads made me look at the 1 GB 3dm file that was included in your zip file that you sent to support.
Apart from the 3 meshes, there are 115 412 curves, 4 clipping planes, 906 points, 1 picture surface, 2 surfaces, 3 polysurfaces, 18 extrusions, 1 Leader, 6 angular dimensions, 82 linear dimensions, 57 radius dimensions, and 49 text objects in that file.
Having lots of curves in a scene is known to slow down the display.
Using SelDup, you can delete 65 457 of those curves.
After doing that, SelShortCrv set to 0.01 inches selects 29 888 curves.
Many of those are duplicate segments of longer polylines.
Getting rid of redundant geometry is step 1. After that, you need to manage the scene by hiding anything that is not strictly required for any given task that you need to perform.
-wim
Hi,
it may be a wonky mesh obj make by Metashape 2.2.0
see thisā¦
a discovery, I have the 1st mesh, the one I normally use, withput the ghost rulers, near bott of layer palette, and another rarely used but gives better detail in some areas, as Agisoft is flawed, creating blurred areas, yet my dSLR pics are TOP NOTCH.
Project a lineā¦
the 1st mesh, made with Metashape 2.2.0,.creates bits as well as a continual line.
the 2nd mesh made with Metashape 2.1.1, creates just a single line.
(in layer names)
The 2nd IS QUICKER.
1st mesh project time 26.1 secs
2nd mesh project time 14.25secsā¦ twice as quick.
(exact same line and area)
1st mesh 19 secs top view to 4 view.
2nd mesh 16 secs top view to 4 view.
perspective rotate
1st mesh slow and jerky jittery
2nd mesh smooth and normal, a joy to work with by comparison. ! 
Clearly the 1st mesh, that has gone slow rotate this last 2 days, has an issue.
What can I look for to see whats going on ?
McNeel have this file as well already.
@stevebaer
@wim
@carla.sologuren
This is also now mentioned in the thread on how to remove bits og line from a project line to mesh,
I am using the 2nd mesh to make sections now, saves all those bits.
though it is a fraction out on location, so I get differing sections on a fore/aft position, yet I was mega careful to place both to match and be at same scale etc.
so is metashape 2.2.0 at fault ?
seems so.
Steve