ViewCaptureToFile not working above certain resolution

Above a certain resolution (2000 × 2000 px in my case) ViewCaptureToFile will produce images with the top left quadrant tiled four times.

Rhino 7.6.21117.09002
macOS 10.14.6

Modellname: MacBook Pro
Modell-Identifizierung: MacBookPro11,3
Prozessortyp: Intel Core i7
Prozessorgeschwindigkeit: 2,5 GHz
Anzahl der Prozessoren: 1
Gesamtanzahl der Kerne: 4
L2-Cache (pro Kern): 256 KB
L3-Cache: 6 MB
Hyper-Threading Technologie: Aktiviert
Speicher: 16 GB
Boot-ROM-Version: 431.
SMC-Version (System): 2.19f12
Rhino 7 SR6 2021-4-27 (Rhino 7, 7.6.21117.09002, Git hash:master @ 193c626682846040deeeded3f40216c61632977e)
License type: Educational, build 2021-04-27
License details: Cloud Zoo

Apple Intel 64-bit macOS Version 10.14.6 (Build 18G9028) (Physical RAM: 16Gb)
Mac Model Identifier: MacBookPro11,3
Language: en

NVIDIA GeForce GT 750M OpenGL Engine (OpenGL ver:4.1 NVIDIA-12.0.24 355.

OpenGL Settings
	Safe mode: Off
	Use accelerated hardware modes: On
	Redraw scene when viewports are exposed: On
	Anti-alias mode: 4x
	Mip Map Filtering: Linear
	Anisotropic Filtering Mode: High
	Vendor Name: NVIDIA Corporation
	Render version: 4.1
	Shading Language: 4.10
	Maximum Texture size: 16384 x 16384
	Z-Buffer depth: n/a
	Maximum Viewport size: 16384 x 16384
	Total Video Memory: 2 GB
	Graphics: NVIDIA GeForce GT 750M
	Displays: Color LCD (221dpi 2x)

Graphics processors
	Intel Iris Pro (1536 MB)
	NVIDIA GeForce GT 750M (2 GB)
		Color LCD (1440 x 900)

USB devices
	Apple Inc.: Apple Internal Keyboard / Trackpad
	Apple Inc.: Bluetooth USB Host Controller

Bluetooth devices
	Apple: Audio Sink, AVRCP Controller, AAP Server, Handsfree, AVRCP Target

Third party kernel extensions
	com.paragon-software.kext.VDMounter (1370.2) B5F56D88-1A9D-3ED3-BA4A-AEF9F318AA54
	com.paragon-software.filesystems.ntfs (106.5.15) 4575C073-7080-3B2F-AF62-A365668ACD34
	ch.tripmode.TripModeNKE (2.0.3) B1CBB944-226A-3B59-B4E6-98513271AAD6

Third party plugins

Rhino plugins that do not ship with Rhino
	/Users/Felix/Library/Application Support/McNeel/Rhinoceros/packages/7.0/EleFront/4.2.2/ElefrontProperties.rhp	"ElefrontProperties"

Rhino plugins that ship with Rhino
	/Applications/Rhino	"Snapshots"	7.6.21117.1002
	/Applications/Rhino	"Rhino Bonus Tools"	7.6.21117.1002
	/Applications/Rhino	"PanelingTools"	7.6.21117.1002
	/Applications/Rhino	"AnimationTools"	7.6.21117.1002
	/Applications/Rhino	"Renderer Development Kit"	7.6.21117.1002
	/Applications/Rhino	"Displacement"	7.6.21117.1002
	/Applications/Rhino	"Named Position"	7.6.21117.1002
	/Applications/Rhino	"Legacy Rhino Render"	7.6.21117.1002
	/Applications/Rhino	"Commands"	7.6.21117.9002
	/Applications/Rhino	"Import_OBJ"	7.6.21117.9002
	/Applications/Rhino	"export_xaml"	7.6.21117.9002
	/Applications/Rhino	"QuadRemesh"	7.6.21117.9002
	/Applications/Rhino	"export_OBJ"	7.6.21117.9002
	/Applications/Rhino	"RDK_EtoUI"	7.6.21117.9002
	/Applications/Rhino	"Export SVG"	7.6.21117.9002
	/Applications/Rhino	"MeshCommands"	7.6.21117.9002
	/Applications/Rhino	"Export_DAE"	7.6.21117.9002
	/Applications/Rhino	"PDF Export"	7.6.21117.9002
	/Applications/Rhino	"IGES Export Plug-in"	7.6.21117.9002
	/Applications/Rhino	"Import_SVG"	7.6.21117.9002
	/Applications/Rhino	"BlockEdit"	7.6.21117.9002
	/Applications/Rhino	"Export_AMF"	7.6.21117.9002
	/Applications/Rhino	"Rhino Render"	7.6.21117.9002
	/Applications/Rhino	"Import_DST"	7.6.21117.9002
	/Applications/Rhino	"PLY - Polygon File Format Export"	7.6.21117.9002
	/Applications/Rhino	"Import_AMF"	7.6.21117.9002
	/Applications/Rhino	"RhinoCycles"	7.6.21117.9002
	/Applications/Rhino	"IronPython"	7.6.21117.9002
	/Applications/Rhino	"Grasshopper"	7.6.21117.9002

What are your system details (sysinfo)? How much ram is available?

I updated the original post with my system details. Activity Monitor reports 13 GB of 16 GB RAM used with Rhino taking up 4.25 GB. I see no meaningful jump in RAM usage between working and failing resolutions.

1 Like

Hi @messismore,

Can you also post your Rhino System Information output: Help -> System Information...?

Do you also see this issue with a new, empty scene after adding just a sphere to it?


I updated the post.

Do you also see this issue with a new, empty scene after adding just a sphere to it?


Hi @messismore,

I’m unable to reproduce the problem. Here’s a couple of questions:

  1. Can you take a screen shot of your ViewCaptureToFile dialog so that I can see all of the settings?
  2. Do you know if this used to happen with earlier versions? For example Rhino 7.5 or the original Rhino 7.0?
  3. Is there a reason you’re still on macOS Mojave? In case this is a GPU driver issue, it might be a good idea to try to be on the latest version.


Thanks for looking into this @DavidEranen

Pretty sure this has been happening for quite some time, probably in 7.0 and definitely in 7.5. I’m stuck on Mojave because I still depend on some 32bit applications (mostly CS6…). I hoped I could delay the upgrade until my migration to the Affinity suite has fully shaken out.

I did some more testing and there appears to be a pattern. Settings are the same as in the screenshot above, the only difference are the dimensions, as indicated in the filenames.

Hi @messismore,

Rhino 7.7 is now available as a Service Release Candidate. It contains numerous fixes to ViewCapture/Print functionality. Can you test it to see if your issue has been fixed?

Rhino 7 -> Preferences -> General -> Updates -> Update frequency: Service Release Candidate. Then press Check Now.


Hi @DavidEranen,

The issue persists in 7.7 unfortunately.

Version 7 (7.7.21131.13002, 2021-05-11)

Hi @messismore,

According to @encephalon the problem seems to go away when updating macOS to Catalina or Big Sur. See Bug: Pdf, View Capture, Render - larger Format - #16 by encephalon.


I have started to see the same problem. I know this has worked for me in the past. Now when I try a higher resolution for production I get a tiling.

Hello - can you try a size that is just slightly larger than the viewport - does that cause the problem, or is there some larger number that kicks it off?


For me it’s happening with a width set between 3100 and 3200.
Viewport is 2317.