search

animate1978 / MB-Lab

MB-Lab is a character creation tool for Blender 4.0 and above, based off ManuelBastioniLAB
Other
1.76k stars 308 forks source link

Crashing on Mac when choosing viewport shading or render modes #285

Closed raphacn closed 4 months ago

raphacn commented 4 years ago

Describe the bug whenever I choose shading or render blender closes... Got a Imac 27 late 2012 with 32 ram. I have the latest version of blender and tried both the beta and the 1.7.7 version. Everything seems to be fine, I can start creating and all and then somehow whenever I turn to render view or shading, no matter which render mode is set, just crashes

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

Logs To format it correctly, logs should go in between these: Replace the text here with your logs. To turn on the console in Blender 2.80 go to Window>Toggle System Console.

ldo commented 4 years ago

So what exactly is the crash message?

raphacn commented 4 years ago

Hi,

Thanks for the quick response. This is the crashfile.txt

I did a couple other attempts and I was able to see a render viewport using cycles... however when i try to mode to eeve or going to the shader layout it crashes.

anny suggestions?

Em seg., 13 de jul. de 2020 às 20:54, ldo notifications@github.com escreveu:

So what exactly is the crash message?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/animate1978/MB-Lab/issues/285#issuecomment-657888030, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQIXZZOAY7XYHJLGPBMOSYLR3ONDJANCNFSM4OY6W4UQ .

Blender 2.83.2, Commit date: 2020-07-09 05:50, Hash 239fbf7d936f

bpy.ops.object.delete(use_global=False, confirm=False) # Operator Deleted 1 object(s) # Info bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.posemode_toggle() # Operator bpy.ops.object.posemode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.mbast.init_character() # Operator bpy.context.space_data.shading.type = 'RENDERED' # Property bpy.ops.outliner.item_activate(extend=False, deselect_all=True) # Operator bpy.ops.outliner.collection_delete(hierarchy=False) # Operator bpy.ops.outliner.item_activate(extend=False, deselect_all=True) # Operator bpy.context.scene.mblab_character_name = 'f_ca01' # Property bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.posemode_toggle() # Operator bpy.ops.object.posemode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.object.editmode_toggle() # Operator bpy.ops.mbast.init_character() # Operator bpy.context.space_data.shading.type = 'MATERIAL' # Property

backtrace

0 Blender 0x000000010cd87897 BLI_system_backtrace + 55 1 Blender 0x0000000106939898 sig_handle_crash + 392 2 libsystem_platform.dylib 0x00007fff674a8f5a _sigtramp + 26 3 ??? 0x00007f84468c0000 0x0 + 140206095990784 4 ATIRadeonX3000SCLib.dylib 0x00007fff3788b1f8 _ZN3CFG27BackwardTaggingAlongCFAndDFEP5stackIP6IRInstEiPS0_IP5BlockEi + 152 5 ATIRadeonX3000SCLib.dylib 0x00007fff378c545d _ZN9Scheduler14MarkGlobalDefsEv + 2845 6 ATIRadeonX3000SCLib.dylib 0x00007fff378c44b8 _ZN9Scheduler3RunEP3CFG + 1432 7 ATIRadeonX3000SCLib.dylib 0x00007fff378c3f03 _ZN3CFG20ScheduleInstructionsEv + 67 8 ATIRadeonX3000SCLib.dylib 0x00007fff377ebd66 _ZN8Compiler7CompileEP9ILProgram + 838 9 ATIRadeonX3000SCLib.dylib 0x00007fff377eb8e8 _ZN8Compiler13CompileShaderEPhS0_PKj + 424 10 ATIRadeonX3000SCLib.dylib 0x00007fff3798f6ad SCCompileShader + 109 11 AMDRadeonX3000GLDriver 0x0000000119c6b0aa glrATIR800SCCompilePixelShader + 653 12 AMDRadeonX3000GLDriver 0x0000000119cb0379 glrUpdateCtxSysFragmentProgram + 3501 13 AMDRadeonX3000GLDriver 0x0000000119c79da8 gpusLoadCurrentPipelinePrograms + 4336 14 AMDRadeonX3000GLDriver 0x0000000119c9e69d gldUpdateDispatch + 1468 15 GLEngine 0x00007fff497eab33 gleDoDrawDispatchCoreGL3 + 601 16 GLEngine 0x00007fff4979bd07 gleDrawArraysOrElements_Entries_Body + 119 17 GLEngine 0x00007fff4979b1ca glDrawElementsInstancedBaseVertex_GL3Exec + 236 18 libGL.dylib 0x00007fff48b74d1f glDrawElementsInstancedBaseVertex + 45 19 Blender 0x000000010b721aa0 GPU_batch_draw_advanced + 368 20 Blender 0x0000000106ddc34a draw_call_single_do + 682 21 Blender 0x0000000106ddb6c1 drw_draw_pass_ex + 1377 22 Blender 0x0000000106df19c3 EEVEE_materials_draw_opaque + 67 23 Blender 0x0000000106de5bd7 eevee_draw_scene + 871 24 Blender 0x0000000106dd2bed drw_engines_draw_scene + 173 25 Blender 0x0000000106dd21ce DRW_draw_render_loop_ex + 1742 26 Blender 0x000000010745d498 view3d_main_region_draw + 136 27 Blender 0x000000010704c1de ED_region_do_draw + 366 28 Blender 0x0000000106c7bf0c wm_draw_update + 2092 29 Blender 0x0000000106c79a80 WM_main + 48 30 Blender 0x0000000106935fc1 main + 929 31 libdyld.dylib 0x00007fff6719a015 start + 1

animate1978 commented 4 years ago

Just did a quick search on your GPU, it was released 13 years ago. It could be that your GPU just is not able to process certain EEVEE renders, which I am in the same situation at the moment as my GPU is 7 years old and I get really weird viewport rendering.

raphacn commented 4 years ago

You are probably right... i removed some materials and left only the skin and it loaded with eevee. Quite slow... but did. It is probably related. Do you by any chance know if it is worth updating to a new GPU card or we re doomed using macs?

Em ter., 14 de jul. de 2020 às 10:33, animate1978 notifications@github.com escreveu:

Just did a quick search on your GPU, it was released 13 years ago. It could be that your GPU just is not able to process certain EEVEE renders, which I am in the same situation at the moment as my GPU is 7 years old and I get really weird viewport rendering.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/animate1978/MB-Lab/issues/285#issuecomment-658181470, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQIXZZIUBGB6Q6234534YRLR3RNA5ANCNFSM4OY6W4UQ .

animate1978 commented 4 years ago

As I don't have a Mac, I am not sure. But upgrading is your best option I think. I am unfamiliar with the process of upgrading Mac hardware, should not be that difficult I would think?

ldo commented 3 years ago

Looks like you managed to mangle that crash report a bit. While I can discern a traceback, the actual error message is missing. Maybe try copying and pasting again, avoiding the extraneous debris this time?