Several Asset Browser Issues

blkmsk

Hi there^^
I have two asset browser issues right now:

The first is that I'm unable to export the latest version of one or more assets as a ZIP file through the asset browser since version 2025.3.1. The export seems to work fine but when I try to re-import the ZIP file via 'Create' -> 'Import Asset' in the asset browser I get a error message:

"Error importing assets:

fileformat[asset.impl.cpp(4541)]"

Here is a recent video showing the issue in version 2026.0.0 and 2025.3.3

I already posted about it here and reported it as a bug back then.
As the issue still persists in version 2026 is there any idea when this will be fixed?
For now I can still export my assets and provide them to the users with version 2025.2.1
but I would rather not have to do this in a 'legacy' version.

And this brings me to my second issue:

Within one of my scripts I pull some of the above described assets from the asset browser based on the method described in one of the example scripts here.

The original assets are already a couple of years old and I think the asset id's were created in version 2023 but since then this method has been working fine.
Now in version 2026 when I try to pull those assets from the asset browser with the script, cinema 4D is freezing and stops responding.

So I tried creating a new asset with a new asset id in version 2026. With this new asset the script is working in version 2026 but using it in previous version now again freezes Cinema 4D.

Here is a short video showing the issue in version 2026 and 2025.3.3
Is there any idea how I could solve this issue?

Thank you in advance for your time and your efforts!
best,

Ben

edit @ferdinand: Consolidated postings.

Ok here is a short follow up:

After removing all objects from this rig except for the master control I managed to boil the problem down to a python tag on the master control to reset certain userdata fields.
When I also remove the tag and save a new asset version I can load the asset via python in both C4D 2025.3.3 and 2026. When the tag is there, C4D 2026 is freezing when I try to load it via python (or the other way arround, when the new asset version was saved in 2026).

It also works fine in both versions when its just a 'blank' python tag.

The code of the tag is based on the 'reset userdata' python tag of the 'sporty toon rig' rigging example scene from the C4D asset browser.

Loading the sporty toon rig asset via python works fine in both versions, but when I copy the code from the sporty rig into the python tag on my rig or simply copy the whole master control with the python tag from the sporty rig into my rig and save it as a new asset C4D is freezing as well.

Here is a short capture again

Ok I think this piece of code is causing the issue but I dont know why.

import c4d

def message(msg_type, data):
    if msg_type == c4d.MSG_NOTIFY_EVENT:
        event_data = data['event_data']
        if event_data['msg_id'] == c4d.MSG_DESCRIPTION_COMMAND:

            print("test")

def main():
    bc = c4d.BaseContainer()
    obj = op.GetObject()
    if not obj.FindEventNotification(doc, op, c4d.NOTIFY_EVENT_MESSAGE):
        obj.AddEventNotification(op, c4d.NOTIFY_EVENT_MESSAGE, 0, bc)

Without those lines loading the asset via python works fine in both versions.
But of course, this way the python tag does not work.
Disabling the python tag also doesnt help.

ferdinand

Hello @blkmsk,

Thank you for reaching out to us. Please follow our Support Procedures. Your postings were violating multiples:

Singular Question: The initial posting of a support topic must contain a singular question. Do not ask ten things at once, that makes it extremely hard to answer topics. [...]

Singular Posting: Users often discover additional information or even a solution before we can answer. Please consolidate your questions into a singular posting by editing your last posting. [...]

Briefness: Your posting should explain in the first sentence where your problem lies. Avoid writing lengthy paragraphs about tangential subjects [...]

Repeatable: Your claims or problem should be repeatable for us. [...]

Just to name a few. I have consolidated your postings, please read the support procedures guide for future postings. You do not have to follow it to the letter, but we should be all following its general spirit.

About your questions

It is not that I would not see that you have put effort into this, links and video recordings do not manifest out of thin air. But the current form unfortunately fails to convey relevant information for your second question.

[...] I'm unable to export the latest version of one or more assets as a ZIP file through the asset browser since version 2025.3.1. The export seems to work fine but when I try to re-import the ZIP file via 'Create' -> 'Import Asset' in the asset browser I get a error message: fileformat[asset.impl.cpp(4541)]"

That would be an end user bug because there is no code invloved, please report it via the support-center. Without an exact version the file and line number is not too much worth as our source code often changes drastically, even for minor version increments. But this is a call deep inside an internal system. I think it tries to resolve IDs in your zip there. Which could hint at your zip database being somehow malformed. But you have to discuss this with end user support.

So I tried creating a new asset with a new asset id in version 2026. With this new asset the script is working in version 2026 but using it in previous version now again freezes Cinema 4D.

This is all a bit hazy for me, better reproductions steps in accordance with our support guidelines would help here a lot. I watched your first video, and you seem to load some complex rig, and then run a Script Manager script, and then Cinema 4D freezes. But you seem to have also other Python code in your scene. This is pretty much all a black box for me and therefore very hard to answer.

When you have problems with that zip database of yours, I would first make sure that this is not the same issue, i.e., make sure that whatever assets you try to load, are sourced from a non-tainted database. Ideally the built-in database.
Event notifications are private for a reason and can easily be the cause for crashes. I think you used the toon rig in your videos and it unfortunately uses event notifications in its Python code. So, I guess you got it from there. But when you changed something about the toon rig or its code, this could lead to freezes. NOTIFY_EVENT_MESSAGE is however one of the more harmless event notifications and it is somehwhat unlikely that it is the cause.

My recommendation would be to first sort out if your database is not somehow malformed. If that does not help, please show us your code and scene files, without them, we cannot help you. Please put some time into boiling down your issue. There are so many moving parts here such as your zip database, and that ultra complex toon rig. Ideally you show us something that fails with out builtin database in a simple scene.

Cheers,
Ferdinand

blkmsk

Hi Ferdinand,

Thanks for your reply and consolidating my post. And sorry for violating the support procedures! I will keep that in mind for future postings!

@ferdinand said in Several Asset Browser Issues:

That would be an end user bug because there is no code invloved, please report it via the support-center. Without an exact version the file and line number is not too much worth as our source code of changes drastically, even for minor version increments. But this is a call deep inside an internal system. I think it tries to resolve IDs in your zip there. Which could hint at your zip database being somehow malformed. But you have to discuss this with end user support.

I dont think that is an 'end user bug' as I'm experience this on multiple machines since version 2025.3.1 and I already reported this as a bug on 13.07.2025 to the maxon support (Bug ID: 604301). here is a quote from the maxon support reply to this:

"I was able to reconstruct the same error here and did not found a report of this problem.
As this looks like a bug to me, I forwarded the topic to our development for further investigation and fixing. I hope our developer will be able to fix the behaviour soon."

So I was just asking here if there is any information when this could be fixed.

@ferdinand said in Several Asset Browser Issues:

This is all a bit hazy for me, better reproductions steps in accordance with our support guidelines would help here a lot. I watched your first video, and you seem to load some complex right, and then run a Script Manager script, and then Cinema 4D freezes. But you seem to have also other Python code in your scene. This is pretty much all a black box for me and therefore very hard to answer.

When you have problems with that zip database of yours, I would first make sure that this is not the same issue, i.e., make sure that whatever assets you try to load, are sourced from a non-tainted database. Ideally the built-in database.
Event notifications are private for a reason and can easily be the cause for crashes. I think you used the toon rig in your videos and it unfortunately uses event notifications in its Python code. So, I guess you got it from there. But when you changed something about the toon rig or its code, this could lead to freezes. NOTIFY_EVENT_MESSAGE is however one of the more harmless event notifications and it is somehwhat unlikely that it is the cause.
My recommendation would be to first sort out if your database is not somehow malformed. If that does not help, please show us your code and scene files, without them, we cannot help you. Please put some time into boiling down your issue. There are so many moving parts here such as your zip database, and that ultra complex toon rig. Ideally you show us something that fails with out builtin database in a simple scene.

I will prepare a reproduceable example with the builtin database and get back to you as soon as possible.

Thanks again for your time and effort and sorry again for my messy posts!
Ben

ferdinand

Hey @blkmsk,

I did not say that your posting was messy I of course understand that one sometimes can get a bit overwhelmed when in the middle of things, and that it is then quite hard to be super organized. As I said, it was clearly visible that you put effort into this.

Regarding your bug isssue. In general, I do not like interfering too much with other devs work, and something in our bug tracker being marked as fixed, does not necessarily mean that it will make it into a release. But I pulled up your bug issue #604301 and there is long discussion between devs and QAs going on. Our build system made a comment roughly 72 hours ago, that a fix has been submitted, and shortly after that that is has been fixed (i.e., the build suceeded).

This is however only a fix, not a verified fix (i.e., no QA has yet confirmed that what the devs came up with actually fixes the problem), it could still be rolled back. For details you better talk with end user support when this is urgent for you. Alin from end user supports seems to have handeled this.

Cheers,
Ferdinand