TexTools for Blender

kabu · January 6, 2018, 11:07am

Hello, first of all kudos to you for your tool, is really handy
I’m trying it and I frequently get this blocking error:

blender(16458,0x7fffcb0683c0) malloc: *** error for object 0x10af56210: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug

I’m using 2.79 on Os X Sierra

EDIT: Tools version is 0.70

FayScrin · January 6, 2018, 1:23pm

At last it happened! For the first time a neat addon with your own icons and design!
Anyone who makes addons, please pay attention to how to design your work. It is important! It is very good that a lot of people write good additional functionality, but without proper external design, such add-ons turn the blender into a mess. Especially when the blender icons are used for its functions as icons for addon functions. It is not right. Stop doing this! The Internet is full of neat free icons for any needs. You can always design your work and make it unique and understandable without copying other icons created entirely for other functions of the program.

Special thanks to the creator of this addon for a good example of how it should be! And of course for the functionality too.

jpthrash · January 6, 2018, 3:53pm

I have been doing more testing and I came up with some feedback.

When I bake multiple meshes into a single normal map I seem to be getting a mixture of tangent and object space results.

(sorry for the low res map)
Another thing is when I “Lock Selection” of a baking list, deselect everything in the 3d view and press bake I get this error message.

textools_lock_sel.png703×192 18.2 KB
Lastly is the organization of the baking list itself, it doesn’t seem to be alphabetical but random. Not sure if it’s by design but to me, it feels more logical to order the list by name.

For a final suggestion, when baking to a single map, it would be great to be able to input the name of the map (as an addition to picking the first name in the list automatically) just in case you want to have different versions of the same bake.

I hope you find this feedback useful.

renderhjs · January 6, 2018, 4:21pm

@Kabu
Unfortunately there is not much I can find out with just that information on google. Can you tell me what tools you used? I have not encountered these issues myself so far.

@jpthrash
Thanks again for your detailed feedback and testing.

Tangent/Object Normals: I believe this happens when one of the pairs does not have a high poly set, e.g. you bake the Normals of a low poly object on itself. Will have a further look if its not something else.
Bake error: I’ll address the error later today, I know what it is.
Sorting by name: Working on that right now, sorting alphabetically is easy and obvious, thanks

so3Datel Was kind enough to give me one of his detailed gun models with many intersecting high and low poly objects. I am testing right now with his scene to improve the name pairing and some tools to fix object naming.

1D_Inc · January 7, 2018, 9:16am

Thank you)
By the way, we were waiting for AA in baked normals so much time… Thank you so much for this!

Marc_Clint_Dion · January 7, 2018, 10:28am

I’m not sure how familiar you are with baking in Cycles so I’ll make no assumptions.

Objects that are hidden in the scene will still contribute to the bake since “hidden” is just a GLSL Viewport thing.

Here is an example that shows a model that was baked on a layer that has a hidden cube. The hidden cube still contributes to the AO calculation.

If you want to exclude objects from the bake you should be able to use the following options that are found under the Object Properties panel. The python commands are shown at the top of the screen in the Info Area.

Now it doesn’t matter if the objects are hidden or not, they should be excluded.

Good luck.

kabu · January 7, 2018, 12:27pm

Attachments

renderhjs · January 7, 2018, 6:19pm

@1D_Inc :
Regarding Anti Alias: No worries, it was actually much easier than I thought. The image object in blender actually has a resize method oddly named ‘scale’ which samples the image unlike what I read before.


#Resize image
image.generated_width = new_width
image.generated_height = new_height
image.scale(new_width, new_height)

@veti & @jpthrash
Oooops, you guys are right I actually baked in Object space (so silly of me), thought the code was right and perhaps something else was wrong. All fixed now

@Marc Clint Dion
Thanks for the input, I was aware of the ignore flags but didn’t know that hiding objects are not affecting the bake or AO bake in particular. I actually just noticed that just restricting render-able for the cube object solves it as well with less properties to change.

So what I did now is to ‘restrict render’ all all objects of the visible scene that are not part of the bake objects. And obviously restore this afterwards. This also works with isolating, here is a demo:

@kabu
Thanks for the detailed log and sample file. I still haven’t been able to reproduce it but I will try to put in some safety checks, e.g. ‘None’ objects etc. Your error doesn’t throw any python violations, instead it seems to be more low level like memory or pointer wise.
My wife has a MacBook and OSX, I will give it a try this evening on the Mac, see if I can reproduce the bug.

renderhjs · January 7, 2018, 6:43pm

Update Version 0.7.2

Download
Blender TexTools 0.7.2.zip
GIT: https://bitbucket.org/renderhjs/textools-blender

Changes

Sort bake sets
Items are sorted alphabetically by set names, easier to navigate now.

Warn icons
Displays warning for objects that don’t have UV’s, don’t have low poly objects or a miss match for low poly and cage object count.

Tangent normal
Fixed the normal space back to tangent space instead of object space

Fixed Bug with object selection
There was a previous bug with odd selection states that would throw errors when baking, this is now fixed.

Exclude Objects from Bake
Ignores all objects that are not part of the bake set selection from the Bake process, e.g. AO maps.

gestoryscht · January 8, 2018, 3:44am

First of all thanks for your great work. This is a real timesaver!
But I have a question - is it possible to implement a skew correction mode for the baking side?

I could imagine this would require a additional implementation or are complete override of the bake engine, but maybe?

so3Datel · January 8, 2018, 3:44am

i think it is not important at all, but I report it for you, maybe it’s be interesting for you

In Settings > Addons deactivate TexTools 0.71 and press Remove
Press Install from file and choose TexTools 0.72 (new version TexTools will be installed)
Press Enable an Addon - it gives an error message

I can repeate this error if I install back v.071, reteate this ^^ action and install v.072
Here is blend file, I dont know if it need in this case

sorry for my english

Attachments

TexToolsReinstallError.blend (459 KB)

jpthrash · January 8, 2018, 5:38am

The progress on this add-on is insane, thanks a lot.

I was wondering if there is going to be some more advanced options for baking, for example with normal maps, I would like to be able to choose between tangent and object space, DirectX or OpenGL, etc.

kabu · January 8, 2018, 7:11am

Yes, it looks like an error from low-level C source code. I’ll try that on windows.
It is related to UV managing only anyway, baking works correctly.
I’m trying that now but I’ve to setup a full complex object for baking…
Thank you.

dyf · January 8, 2018, 11:50am

@renderhjs
the transmission tools of this uvtools addon is what i’m talking about. see https://youtu.be/ERGf8X5ex28?t=1m56s
the problem with uvtools is it changes the shape of the uv island drastically, not just straightens the edgeloops

anon80875028 · January 8, 2018, 12:08pm

Really cool features and good to see an addon in blender with custom icons instead only text to make a really easy to read interface.

Nutti · January 9, 2018, 4:28am

Hi,

Thanks for making nice add-on.
This add-on makes the UV/Bake workflow much better in Blender.

And, I must apologize for implementing the overlapping UV feature in Magic UV.
I did not notice that there is a feature request from @fiendish55.

BTW, I would like to give some information about the requested UV features.

Align UV

@dyf gave a improvement request about Align UV .
This feature seems that it is similar to the transmission mode in UV_Tool.
UV_Tool: https://blenderartists.org/forum/showthread.php?294904-AddOn-UV_Tool

This add-on was merged into Magic UV now.
So, if you want implementing this feature, below code may help you.

github.com

nutti/Magic-UV/blob/8afff927faa56c73cea3abb86c850607b061d2b2/uv_magic_uv/muv_auv_ops.py

# <pep8-80 compliant>

# ##### BEGIN GPL LICENSE BLOCK #####
#
#  This program is free software; you can redistribute it and/or
#  modify it under the terms of the GNU General Public License
#  as published by the Free Software Foundation; either version 2
#  of the License, or (at your option) any later version.
#
#  This program is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  You should have received a copy of the GNU General Public License
#  along with this program; if not, write to the Free Software Foundation,
#  Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
#
# ##### END GPL LICENSE BLOCK #####

This file has been truncated. show original

However, I think this is a bit complicated implementation.
I wonder if there is a more clear implementation.

UVW Map

I think Sure UV map realizes this feature as @1D_Inc.
Sure UVW Map: https://blenderartists.org/forum/showthread.php?236631-Addon-Simple-Box-UVW-Map-Modifier

I contacted the original author and allowed me to merge this feature in Magic UV.
Below code may be helped you.

github.com

nutti/Magic-UV/blob/8afff927faa56c73cea3abb86c850607b061d2b2/uv_magic_uv/muv_wsuv_ops.py

# <pep8-80 compliant>

# ##### BEGIN GPL LICENSE BLOCK #####
#
#  This program is free software; you can redistribute it and/or
#  modify it under the terms of the GNU General Public License
#  as published by the Free Software Foundation; either version 2
#  of the License, or (at your option) any later version.
#
#  This program is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  You should have received a copy of the GNU General Public License
#  along with this program; if not, write to the Free Software Foundation,
#  Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
#
# ##### END GPL LICENSE BLOCK #####

This file has been truncated. show original

This may not be the feature you wanted.
If this is not related to your feature, please ignore it.

I’m sorry if you are in bothersome.
Thanks and sorry for the long post.

so3Datel · January 9, 2018, 5:45am

Maybe you’re right and you’ll come up with a more elegant solution, but I will tries explained to you what I mean

In 2.8 we will have Collections/Layers. And I propose put LP to the one layer, HP to the another layer, and chose these layers in TexTools, for example: LP layer - for low poly; HP layer - for hight poly.
Create equal materials for each equal lp and hp objects. And use this materials for indication what is what will be baked. Maybe not ID, but materials names or colors.

Personally I think it is more organize (layers) and visually readable (colors) for control and check what will be baking to low poly.
For more simple situations I propose use standard solution From selected to Active.
Upd: but this can’t be useful if you try baking material ID for masking for texturing.
sorry for my english