Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing after creating F3D Materials #477

Open
Villagerjj opened this issue Nov 19, 2024 · 5 comments
Open

Crashing after creating F3D Materials #477

Villagerjj opened this issue Nov 19, 2024 · 5 comments

Comments

@Villagerjj
Copy link

Everything looks fine after creating a F3D material, but after a few seconds, the viewport freezes, and blender crashes with this:

amdgpu: The CS has cancelled because the context is lost. This context is innocent.

Blender version: 4.3.0

Settings:
image

Blender also crashes after selecting the "Fix color preferences" button after making a new material

I will roll back to blender 4.2.3 and see if things still work

@Villagerjj
Copy link
Author

Everything works fine in blender 4.2.3

@Mystyle-48
Copy link

I am encountering a similar crash in Blender 4.3.2 when importing a skeleton, going to the Materials tab, and waiting for existing F3D materials to load. Here is a log:
blender_debug_output.txt

Reverting to 4.2 (4.2.5) also resolves the crash on my end.

@Lilaa3
Copy link
Collaborator

Lilaa3 commented Dec 23, 2024

I am encountering a similar crash in Blender 4.3.2 when importing a skeleton, going to the Materials tab, and waiting for existing F3D materials to load. Here is a log:
blender_debug_output.txt

Reverting to 4.2 (4.2.5) also resolves the crash on my end.

Your log doesn't seem to show anything about the crash?

@Mystyle-48
Copy link

Your log doesn't seem to show anything about the crash?

Odd. That was the only log I was able to generate. Based on the Blender docs there should be a crash log ending with .crash.txt, but there doesn't seem to be one in my %TEMP% folder.

@Yanis002
Copy link
Contributor

Yanis002 commented Dec 23, 2024

(open the console when you got the error and send a screenshot of what it shows)

(edit: nvm I didn't realised it was crashing, though recording the console might help anyway)
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants