My render has some weird shadow/reflection going on.
Not sure if it’s a material or ground plane or lighting issue.
Here is what it looks like in the viewport
Here is what it looks like when I print the viewport as Rhino PDF
1.pdf (435.8 KB)
My render has some weird shadow/reflection going on.
Not sure if it’s a material or ground plane or lighting issue.
Here is what it looks like in the viewport
Here is what it looks like when I print the viewport as Rhino PDF
1.pdf (435.8 KB)
will you please open rhino and run the systeminfo command and paste the report here?
does it do the same thing if you use the adobe pdf?
Rhino 8 SR12 2024-10-8 (Rhino 8, 8.12.24282.07002, Git hash:master @ 2f42167325d83e0da0f3fe08e796c2b26e602bc5)
License type: Commercial, build 2024-10-08
License details: Cloud Zoo
Apple macOS Version 14.7.1 (Build 23H222) (Physical RAM: 32GB)
Mac Model Identifier: MacBookPro18,2
Language: en-US (MacOS default)
.NET 7.0.0
Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M1 Max
Color LCD (1728 x 1117 @ 120.00Hz)
DELL SE2719H (1920 x 1080 @ 60.00Hz)
GPU Vendor: Apple
USB devices
None
Bluetooth devices
None
Third party kernel extensions
None
Third party plugins
/usr/lib/swift/libswiftCore.dylib
/usr/lib/swift/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftCoreImage.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftMetal.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftQuartzCore.dylib
/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswift_Concurrency.dylib
/usr/lib/swift/libswiftos.dylib
/usr/lib/swift/libswiftsimd.dylib
/usr/lib/swift/libswift_StringProcessing.dylib
/usr/lib/swift/libswift_RegexParser.dylib
/usr/lib/swift/libswiftCryptoTokenKit.dylib
/usr/lib/usd/libusd_ms.dylib
/usr/lib/swift/libswiftCoreAudio.dylib
/usr/lib/swift/libswiftCoreLocation.dylib
/usr/lib/swift/libswiftCoreMedia.dylib
/usr/lib/swift/libswiftCompression.dylib
/usr/lib/swift/libswiftCoreMIDI.dylib
/usr/lib/swift/libswiftAVFoundation.dylib
/usr/lib/swift/libswiftCoreML.dylib
/usr/lib/swift/libswiftFileProvider.dylib
/usr/lib/swift/libswiftIntents.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftGLKit.dylib
/usr/lib/swift/libswiftGameplayKit.dylib
/usr/lib/swift/libswiftMetalKit.dylib
/usr/lib/swift/libswiftModelIO.dylib
/usr/lib/swift/libswiftSceneKit.dylib
/usr/lib/swift/libswiftSpriteKit.dylib
/usr/lib/swift/libswiftVision.dylib
/usr/lib/swift/libswiftRegexBuilder.dylib
/usr/lib/swift/libswiftDemangle.dylib
/usr/lib/swift/libswiftShazamKit.dylib
/usr/lib/swift/libswiftObservation.dylib
/usr/lib/swift/libswiftVideoToolbox.dylib
/usr/lib/swift/libswiftWebKit.dylib
/usr/lib/swift/libswiftNaturalLanguage.dylib
/usr/lib/swift/libswiftSystem.dylib
/usr/lib/swift/libswiftMapKit.dylib
/usr/lib/log/liblog_network.dylib
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
/Applications/Rhino 8.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 8.12.24282.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 8.12.24282.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/MeshCommands.rhp “MeshCommands” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_PDF.rhp “PDF Export” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rhino Render” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/PlugIns/SectionTools.rhp “SectionTools” 8.12.24282.1002
/Applications/Rhino 8.app/Contents/PlugIns/RhinoRender.rhp “Legacy Rhino Render” 8.12.24282.1002
/Applications/Rhino 8.app/Contents/PlugIns/Displacement.rhp “Displacement” 8.12.24282.1002
/Applications/Rhino 8.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 8.12.24282.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 8.12.24282.7002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCodePlugin.rhp “RhinoCodePlugin” 8.12.24282.7002
ok, I have an almost identical machine here.
to clarify, are you rendering by hitting the render button, or is this rendered viewport mode?
if it’s rendered viewport mode, can you please reset your rendered mode to default?
also does this also misbehave with the adobe pdf driver?
I do “rendered viewport”, then “file - print”
Destination “Rhino PDF”, then hit “print”, and save as PDF
Somehow the issue goes away when I lower the resolution from 300 to 200 dpi.
I will try to reset my rendered mode.
2.pdf (454.3 KB)
still there after the rendered mode reset.
This is also after I reset Rhino to factory setting.
1.pdf (698.8 KB)
It’s a weird 4 viewport thing going on
Hi James -
Is there any reason for not updating to macOS Sequoia?
Does anything change if you disconnect the external monitor?
-wim
though it works, i believe its not fully supported yet, having some bugs registered due to the new system (none which i know off directly)
Hello Wim,
“Your Mac is running the latest software update allowed by your organization”
The render still has the issue after disconnecting the external monitor.
this tiling issue has been bugging Rhino for several years if i remember well, wonder why its so difficult to be fixed
Hi James -
I see that this issue was fixed in Rhino 8.13:
-wim
Hello Wim,
Yes. The issue is gone after updating to the latest version of Rhino.
Thank you for your help!