c4d thumbnail doesn't show on MacOS on a MBP

[Tisi]

Update: no change here on my side with 2026.0.0

[Dr. Sassi]

Yes, I know, Tisi, not fun.

Please add to your Tech Support ticket – if I can at all ask for that extra work. I know patience is not endless.
My influence is not inside Apple, where I suspect the main problem is.

Again, sorry, and yes, it isn't very pleasant.

My report for the file preview for 2026.0 is submitted.

My best wishes

[Tisi]

@Dr-Sassi Thank you for your continuing support, it sure is appreciated.

[ericsiegel]

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.

[Dr. Sassi]

Hi Tisi,

Thank you! I hope it is soon history. Fingers crossed.

Cheers

[Dr. Sassi]

Hi ericsiegel,

I have submitted this problem now three times, and yes, it is not OK that it takes that long.
Apple has EOL'd the way it was done before. It wasn't just the code line that was screwed up.

As you report your experience, I can only say, you should not have to face this pattern, and I'm truly sorry.

A pattern means to me at least three of those Solved-Closed, while there are no result cycles. Please share the ticket numbers, so I can ask the Tech Support Manager how that was possible.

Rest assured, as far as I can tell, we have the largest team of developers and tech Support ever, and based on our last Global Summit Meeting, there is a great energy and mood within each team. So, surely no shortage of talent.

All the best

[ericsiegel]

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.

[Dr. Sassi]

Thank you very much, ericsiegel.

I count eleven tickets that are not solved within a version cycle. This is annoying, no argument here at all.

Did I miss it? There is no Preview ticket, correct?

No idea if that is of any interest, but perhaps it saves some time to have that source:
https://support.maxon.net/hc/en-us/articles/8658038724124-Cinema-4D-2026-0-September-10-2025

I will share the ticket numbers along with the question, focusing on pattern detection.

Thanks again.

My best wishes

[Dr. Sassi]

Hi Eric Siegel,

I went through all eleven reports/tickets. As far as I could, I have tried to recreate the setups; some had files redacted (an NDA was mentioned), so I couldn't.
.

Two things stand out: your reports are clear and fair, and the tech support replies mirror that. Thank you for staying so professional. With your long-time expertise in this field, it might be second nature for you anyway to work on that high level. Nevertheless, thank you.
.

The common message I found was that the Tech Support team did everything they could to move it forward to the developers and shared as much information as they were able to.
.

The common ground here is that both sides understand what is needed, wanted, or possible (which doesn't mean they agree or consider it favorable), but some things are not moving forward.
.

That bugs me that more tickets get the attention is a common practice, but keeping something for too long is not cool, I get that.
.

OFFTOPIC (Regarding File Preview)
.

With anything below, I might mention things that you already know, and you might roll your eyes at me for even bringing it up. I have seen your website, and I have no derogatory thoughts on my mind here; if that comes across as such, I apologize, as that was not my intention.
.

As I mentioned, I went through some of the steps, but I was unable to reproduce the user Data/take problem; it worked fine. [2026.0/Mac]
.

The Height in the Text parameter does not match the Coordinates Size numbers manager; there, I found an answer that could have cleared the situation. My perspective is that one shows the object's dimensions, the other the type height.
.

The Watermark is annoying, and nope, this is not OK.
.

The Text in the lower part is cut; I miss the files, sorry, no idea.
.

Photoshop Files with adjustment layers; here, I would suggest something different than a decade ago. Color management-based. Whatever you adjust here might not look the same in another colorspace. Wild geusss here here - as I have no examples from the report/ticket. I have been using OpenEXR for over a decade, and if possible, I already work in the final Color Space.
Besides, when I merge layers in Photoshop, they often produce weird things – in Photoshop itself, and that has been the case for a very long time. I've been using Photoshop for in my forth decade now, and I love it, but it has its limits. I wouldn't expect any third-party app using PS files to process large setups better than PS itself—my two cents.
.

I haven't found any File Preview mentioned in the Ticket Numbers, but you made your point clearly; some things are delayed for too long.
.

I hope that you can see that we care, and my exploration today has shown me that the File-Preview feature has received more attention internally than others. I hope that we find something that will work across platforms and, as much as possible, be backward compatible.
.

Thank you very much for your tremendous effort with the ticket numbers.

My best wishes

[bike-disaster]

hello again! is there any update about the Quick Look issue in newest MacOs.

I ask this in google AI

is the Quick Look for .c4d files work in Tahoe?

No, the standard Quick Look functionality for .c4d files does not work in macOS Tahoe (macOS 16).
The native Quick Look generator plugin included with Cinema 4D uses an older file format (.qlgenerator) that is incompatible with recent macOS changes introduced in Sequoia and continued in Tahoe.
Current Status on macOS Tahoe
Quick Look (Space Bar Preview): Pressing the space bar on a .c4d file will likely only show a large generic icon or no preview, rather than a render of the 3D scene.
Icon Previews (Thumbnails): Similarly, Finder thumbnail previews are generally broken, and you will see a default application icon instead of a preview of the file's content.

Potential Solutions
Maxon is aware of these compatibility issues with newer macOS versions and is expected to release an updated Quick Look extension (using the modern App Extension format required by Apple) in a future software update.

Until Maxon releases an official fix:
Ensure "Show icon preview" is enabled: Check Finder View Options for the folder to ensure thumbnail generation is requested by the OS.
Keep Cinema 4D updated: Ensure you have the latest version of Cinema 4D installed via the Maxon App, as a fix will come through an update.
Check System Settings: You can look in System Settings > Privacy & Security > Extensions > Quick Look to see if any Maxon options appear, but they are unlikely to function correctly if they are using the old format.

[Dr. Sassi]

Hi bike-disaster,

Thanks for pushing. If I see more options to support this, I will do so, of course.

I surely feel it as well, and it is not fun when searching through thousands of C4D files that I got since this problem occurred, especially when most people do not share with simple naming convention.

The problem is clear, and yes, the solution is eagerly wanted.
To toss out just something that works now and fails soon, with the next OS update again, is not how I would love to see it.

I do not see anything new in the AI report. Gemini is surely not my first choice in AI after testing it with a few hundred deep researches over a long time, comparing it to a few others, the fantasy it has, and its ignorance of preferences stands out in my selections of AI entities: I mention that, as I have written a lot of feedback to Google; I surely feel when a problem seems to make no progress.

I have reported all problems with the preview, shared where I can. Adding anything to this thread at this point will have little effect. What is effective is using the tech support! That is the most powerful option right now.
Please use the tech support options.
https://www.maxon.net/en/support-center

Cheers