madminstrel / meltdown Goto Github PK

The path add a "/" ; when we add a Pass, the path are not good.

Always crash when baking in blender 2.76+

Impossible to used a shortcut "e" for call a pipette in your fieeld ; i don't know if it's a blender limit or a forget function with your addon.

I can't seem to log in on Blender Artist, either I forgot my password or whatever. But I want to thank you for making this addon. Really it's the most efficient baking addon I've used so far. Anti-aliasing is awesome.

And since this is an issue tracker, I did have some issue with it but I think it's not that big. If I changed the object name and just click meltdown, it give me error. Well because the name changed. When I delete everything in the "T" tool bar and re-added everything accordingly, it works again. But I do keep a place holder bake job on top of others to make sure it will be always working. I hope this may help you figure out any problem for your addon.

And, I would think it's better to add a progress bar since the current version just make the software freeze for a sec, and the job is done. Which is already amazing for less costly bakes. :P

PS: I'm currently trying to figure out how to automatically adjust 3D-viewport clipping distance. I do use UE4Tools and I set blender default scene scale to sync with UE4. Thus the clipping is causing many minor annoyance. I do have a few lines of python code on setting it to constant value but I have no idea how to make them into a button inside the "N" panel's 3D view. Would you mind pointing me to the right file for this?

napisałem prostą metodę która sprawdza czy obiekty hipoly mają materiały, jeżli nie to wyświetli nazwę obiektu i przerwie skrypt:
def is_empty_mat(self,context):
mds = bpy.context.scene.meltdown_settings
pair = mds.bake_job_queue[self.job].bake_queue[self.pair]
pair_list = mds.bake_job_queue[self.job].bake_queue
if pair.highpoly != "":
if pair.hp_obj_vs_group == "GRP":
for object in bpy.data.groups[pair.highpoly].objects:
if len(object.material_slots)==0 or object.material_slots[0].material is None:
self.report({'INFO'}, 'Object: '+object.name+' has no Material!')
return True
else:
if len(bpy.data.objects[pair.highpoly].material_slots)==0 or bpy.data.objects[pair.highpoly].material_slots[0].material is None:
self.report({'INFO'}, 'Object: '+bpy.data.objects[pair.highpoly].name+' has no Material!')
return True
return False

Były by super gdybyś wrzucił to do mastera.
funkcję tą najlepiej wywołać w głównym operatorze MeltdownBakeOp zaraz na starcie funkcji execute:

def execute(self, context):
if self.is_empty_mat(context):
return {'CANCELLED'}