It appears that Redshift Version 2026.1.0 resolves the crash issue.
Is there more specific info as to the "known rendering artifacts when running on Intel CPU + AMD GPU systems on macOS Tahoe"?

https://redshift.maxon.net/topic/53698/version-2026.1.0-is-now-available-2025.10
"Version 2026.1.0 is now available [2025.10] ... On Apple hardware, Redshift requires macOS Sonoma 14 or higher. In general, we strongly recommend using the latest available version of macOS officially supported by Redshift (including dot releases). Currently, this is macOS Tahoe 26.0.1. "

Does this mean that we can now re-install Redshift on MacOS Tahoe 2026.1.0/Intel systems without crashing Cinema 4D?
Is there more specific info as to the "known rendering artifacts when running on Intel CPU + AMD GPU systems on macOS Tahoe"?

Some are just slightly annoying, others more-so, some I gave up re-filing ...

Ticket #714872 Text Height Incorrect … 2025 … persists in 2026 ... text objects are not created at the specified height

Ticket #681014, #277651, #215525 Auto Take <-> User Data Issue … CONFIRMED BUG S24 … persists in 2024 … persists in 2025 … persists in 2026 ... I use a lot of custom camera rigs that are controlled by User Data sliders. IF, while in AUTO TAKE mode ... you change the position in a Child Take using the USER DATA SLIDER, the Parent Take’s value gets changed also

Ticket #681007 + 681012, #277652, #215526 Watermark Large Text … CONFIRMED BUG ON MAC S24 … persists in 2024 … persists in 2025 … persists in 2026 ... Using large type sizes (>72) in Watermarks produces text that is cut off on the bottom.

Ticket #290379 Take Render Warnings … CONFIRMED BUG S26 … PERSISTS IN 2023.2.0 … Take Render Warnings appear even though all assets are accounted for in the Project Asset Inspector. Maxon Support claims it seems related to placing textures on Dropbox. The "Take Render Warnings" will appear when the following two conditions are met ... 1. Filenames are "localized" AND 2. The required textures are in subfolders of the "tex" folder, as is common in organizing scenes with many textures.

Ticket #277653, #194847 Photoshop Adjustment Layers Inside Groups Do Not Render … CONFIRMED BUG S24 … persists in 2023.2.0 … persists in 2026 ... Textures using Photoshop files with groups containing adjustment layers DO NOT render correctly IF THE GROUP IS SELECTED IN THE LAYERSET … the adjustment layers are ignored.

Sigh ... Ticket SOLVED, Ticket CLOSED ... it makes no difference as there is a long pattern - I charitably assume due to engineering understaffing - in which features and functions are put into the application with incomplete or incorrect or scene-damaging functionality and then are allowed to languish literally FOR YEARS - through annual ticket refreshes - in a buggy state with little hope of repair unless enough "customers are affected". Adding new features is great - and I applaud Maxon for the great features it regularly rolls out to us - but fixing the features that are already in the application is also great.

I have two approaches ... if the model's only purpose is for visual impact I sometimes model at an exaggerated size IF I find I can get the scene to look better, BUT if the model's purpose is to show how the thing will look when actually built (such as scenic in a TV studio) OR if the model will be sent to others who have to work from it in the real world (such as a fabricator or lighting designer) then I work at 1:1 actual scale. Hope this perspective helps.

WARNING: Redshift 2025/2026 with MacOS 2026 Tahoe on Intel will crash Cinema 4D on launch.
At present, Maxon reports that Cinema 4D will crash on Intel CPUs under MacOS 2026 Tahoe. Maxon: "It is a known issue as of yesterday that our development team is still researching." Further testing suggests that Redshift itself is the cause. Removing Redshift allows Cinema 4D to launch.