Trimmed Image Re-proportions

This bug should have been fixed in 7.4 or 7.5… In any case I am not seeing it here in 7.6 RC with your original image posted at the top after trimming.

Yes, it’s fixed in Rhino 7. Unfortunately I can’t get VisualArq to behave in Rhino 7.

I don’t think it’s going to be retroactively fixed in V6. It should not automatically shrink in V6 after trimming (that was one bug that was fixed), but if you shrink the trimmed surface in V6 (the second bug), the image will distort. Fixed in V7.


It is only partially fixed in Rhino 7, actually. Invoking the Cycles Renderer causes trimmed bitmaps in the the project to become disproportinately resized images instead.

This issue has returned today for me.

Bitmap images I inserted into layout space - hand drawings requiring cad revision - were scanned and meticulously cropped and reassembled in layout space yesterday.

Today reopening the project the entire image fills each cropped version, stretched to fit, just as happened back in February.

Rhino 7 SR9 (7.9.21222.15001, 2021-08-10)

I find that cropping images continues to be unreliable due to this frequent bug. I avoid cropping whenever I can.
I am using Rhino 7’s latest release on a new windows 11 computer but, just as on last year’s windows 10 computer, a cropped image will often reproportion its entire extents into the cropped boundaries. Today I had two very similair images side-by-side on a layout, cropped with the same rectangle. On reopening the project, one was distorted, the other wasn’t.

These problems recurr. Please see the below video:

Hi Folks:

Just to draw attention, we have above a claim from spring of last year that this bug has been fixed, and my example above from this month showing that it still happens in the latest version of Rhino 7. A response would be appreciated. Referrring to or including bitmaps in a drawing is a common requirement in my workflow, and not being able to edit them in Rhino is a significant shortcoming.

Can you post the file that shows this behavior, as I cannot reproduce the issue on 7.24 and don’t recall it to have happend for quite some time either. I often insert pictures and trim them.

I’ve been avoiding using any trimmed pictures, because it remains unreliable. Today it happens immediately on trimming. Usually the corruption doesn’t happen until a file is reopened. So I’m uploading a file and a gif showing what’s happening.

hi @djhg I tried to reproduce this, but I cannot, and I highly suspect this is display driver related.
Pls. run _SystemInfo in Rhino and post back the results, thanks.

Rhino 7 SR34 2023-9-24 (Rhino 7, 7.34.23267.11001, Git hash:master @ a37d83041828484840f2448d5b3e3770e46694f9)
License type: Commercial, build 2023-09-24
License details: Cloud Zoo

Windows 11 (10.0.22621 SR0.0) or greater (Physical RAM: 64Gb)

Computer platform: LAPTOP - Plugged in [96% battery remaining]

Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics (Intel) Memory: 1GB, Driver date: 3-16-2023 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA RTX A5000 Laptop GPU (NVidia) Memory: 16GB, Driver date: 10-18-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.70
> Integrated accelerated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port

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: 10-18-2023
Driver Version:
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 16 GB

Rhino plugins that do not ship with Rhino
C:\Users\djhg\AppData\Local\Programs\Enscape\Bin64\Enscape.Rhino7.Plugin.dll “Enscape.Rhino7.Plugin” 0.0.22283.1642
C:\Program Files\Rhino 7\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Rhino 7\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
C:\Users\djhg\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SubstanceImporter\2.0.3\Substance.Win.rhp “SubstanceImporter”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino 7\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\BlockEdit.rhp “BlockEdit” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”

Can you, as a test, disable all plugins that don’t ship with Rhino, and see if the problem persists?