2011-10-10 09:38:02 +00:00
|
|
|
/*
|
2002-10-12 11:37:38 +00:00
|
|
|
* 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
|
2008-01-07 19:13:47 +00:00
|
|
|
* of the License, or (at your option) any later version.
|
2002-10-12 11:37:38 +00:00
|
|
|
*
|
|
|
|
* 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,
|
2010-02-12 13:34:04 +00:00
|
|
|
* Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
|
2002-10-12 11:37:38 +00:00
|
|
|
*
|
|
|
|
* The Original Code is Copyright (C) 2001-2002 by NaN Holding BV.
|
|
|
|
* All rights reserved.
|
|
|
|
*/
|
|
|
|
|
2019-02-18 08:08:12 +11:00
|
|
|
/** \file
|
|
|
|
* \ingroup bke
|
2011-02-27 20:40:57 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
#include <stdio.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <string.h>
|
|
|
|
#include <math.h>
|
|
|
|
|
|
|
|
#include "MEM_guardedalloc.h"
|
|
|
|
|
2009-11-10 20:43:45 +00:00
|
|
|
#include "BLI_math.h"
|
2008-10-01 03:35:53 +00:00
|
|
|
#include "BLI_kdopbvh.h"
|
2011-01-07 18:36:47 +00:00
|
|
|
#include "BLI_utildefines.h"
|
2014-08-15 15:29:08 +10:00
|
|
|
#include "BLI_math_color.h"
|
2002-10-12 11:37:38 +00:00
|
|
|
|
|
|
|
#include "DNA_key_types.h"
|
|
|
|
#include "DNA_object_types.h"
|
|
|
|
#include "DNA_material_types.h"
|
2006-07-31 15:53:03 +00:00
|
|
|
#include "DNA_brush_types.h"
|
2008-03-14 18:08:27 +00:00
|
|
|
#include "DNA_node_types.h"
|
Merge of first part of changes from the apricot branch, especially
the features that are needed to run the game. Compile tested with
scons, make, but not cmake, that seems to have an issue not related
to these changes. The changes include:
* GLSL support in the viewport and game engine, enable in the game
menu in textured draw mode.
* Synced and merged part of the duplicated blender and gameengine/
gameplayer drawing code.
* Further refactoring of game engine drawing code, especially mesh
storage changed a lot.
* Optimizations in game engine armatures to avoid recomputations.
* A python function to get the framerate estimate in game.
* An option take object color into account in materials.
* An option to restrict shadow casters to a lamp's layers.
* Increase from 10 to 18 texture slots for materials, lamps, word.
An extra texture slot shows up once the last slot is used.
* Memory limit for undo, not enabled by default yet because it
needs the .B.blend to be changed.
* Multiple undo for image painting.
* An offset for dupligroups, so not all objects in a group have to
be at the origin.
2008-09-04 20:51:28 +00:00
|
|
|
#include "DNA_color_types.h"
|
2011-02-12 14:38:34 +00:00
|
|
|
#include "DNA_particle_types.h"
|
2014-05-03 18:51:53 +09:00
|
|
|
#include "DNA_linestyle_types.h"
|
2002-10-12 11:37:38 +00:00
|
|
|
|
|
|
|
#include "IMB_imbuf.h"
|
|
|
|
|
|
|
|
#include "BKE_main.h"
|
|
|
|
|
2017-12-07 15:36:26 +11:00
|
|
|
#include "BKE_colorband.h"
|
2002-10-12 11:37:38 +00:00
|
|
|
#include "BKE_library.h"
|
|
|
|
#include "BKE_image.h"
|
2004-07-26 21:44:55 +00:00
|
|
|
#include "BKE_material.h"
|
2002-10-12 11:37:38 +00:00
|
|
|
#include "BKE_texture.h"
|
|
|
|
#include "BKE_key.h"
|
2005-12-21 22:21:43 +00:00
|
|
|
#include "BKE_icons.h"
|
2008-03-14 18:08:27 +00:00
|
|
|
#include "BKE_node.h"
|
2009-01-18 10:41:45 +00:00
|
|
|
#include "BKE_animsys.h"
|
2011-05-01 03:57:53 +00:00
|
|
|
#include "BKE_colortools.h"
|
2013-10-20 13:01:07 +00:00
|
|
|
#include "BKE_scene.h"
|
|
|
|
|
|
|
|
#include "RE_shader_ext.h"
|
2002-10-12 11:37:38 +00:00
|
|
|
|
2006-01-04 12:13:13 +00:00
|
|
|
/* ****************** Mapping ******************* */
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
TexMapping *BKE_texture_mapping_add(int type)
|
2006-01-04 12:13:13 +00:00
|
|
|
{
|
2012-05-06 15:15:33 +00:00
|
|
|
TexMapping *texmap = MEM_callocN(sizeof(TexMapping), "TexMapping");
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
BKE_texture_mapping_default(texmap, type);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2011-11-07 17:35:20 +00:00
|
|
|
return texmap;
|
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_mapping_default(TexMapping *texmap, int type)
|
2011-11-07 17:35:20 +00:00
|
|
|
{
|
|
|
|
memset(texmap, 0, sizeof(TexMapping));
|
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
texmap->size[0] = texmap->size[1] = texmap->size[2] = 1.0f;
|
|
|
|
texmap->max[0] = texmap->max[1] = texmap->max[2] = 1.0f;
|
2009-11-10 20:43:45 +00:00
|
|
|
unit_m4(texmap->mat);
|
2011-11-07 17:35:20 +00:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
texmap->projx = PROJ_X;
|
|
|
|
texmap->projy = PROJ_Y;
|
|
|
|
texmap->projz = PROJ_Z;
|
|
|
|
texmap->mapping = MTEX_FLAT;
|
2013-09-25 20:28:49 +00:00
|
|
|
texmap->type = type;
|
2006-01-04 12:13:13 +00:00
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_mapping_init(TexMapping *texmap)
|
2006-01-04 12:13:13 +00:00
|
|
|
{
|
2013-09-25 20:28:49 +00:00
|
|
|
float smat[4][4], rmat[4][4], tmat[4][4], proj[4][4], size[3];
|
2011-11-07 17:35:20 +00:00
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (texmap->projx == PROJ_X && texmap->projy == PROJ_Y && texmap->projz == PROJ_Z &&
|
2012-05-20 19:49:27 +00:00
|
|
|
is_zero_v3(texmap->loc) && is_zero_v3(texmap->rot) && is_one_v3(texmap->size))
|
|
|
|
{
|
2011-11-07 17:35:20 +00:00
|
|
|
unit_m4(texmap->mat);
|
|
|
|
|
|
|
|
texmap->flag |= TEXMAP_UNIT_MATRIX;
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
/* axis projection */
|
2013-09-25 20:28:49 +00:00
|
|
|
zero_m4(proj);
|
|
|
|
proj[3][3] = 1.0f;
|
2011-11-07 17:35:20 +00:00
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (texmap->projx != PROJ_N)
|
2012-05-06 15:15:33 +00:00
|
|
|
proj[texmap->projx - 1][0] = 1.0f;
|
2012-03-24 06:18:31 +00:00
|
|
|
if (texmap->projy != PROJ_N)
|
2012-05-06 15:15:33 +00:00
|
|
|
proj[texmap->projy - 1][1] = 1.0f;
|
2012-03-24 06:18:31 +00:00
|
|
|
if (texmap->projz != PROJ_N)
|
2012-05-06 15:15:33 +00:00
|
|
|
proj[texmap->projz - 1][2] = 1.0f;
|
2011-11-07 17:35:20 +00:00
|
|
|
|
|
|
|
/* scale */
|
2013-09-25 20:28:49 +00:00
|
|
|
copy_v3_v3(size, texmap->size);
|
|
|
|
|
|
|
|
if (ELEM(texmap->type, TEXMAP_TYPE_TEXTURE, TEXMAP_TYPE_NORMAL)) {
|
|
|
|
/* keep matrix invertible */
|
2013-10-01 03:56:02 +00:00
|
|
|
if (fabsf(size[0]) < 1e-5f)
|
2013-10-01 16:40:11 +00:00
|
|
|
size[0] = signf(size[0]) * 1e-5f;
|
2013-10-01 03:56:02 +00:00
|
|
|
if (fabsf(size[1]) < 1e-5f)
|
2013-10-01 16:40:11 +00:00
|
|
|
size[1] = signf(size[1]) * 1e-5f;
|
2013-10-01 03:56:02 +00:00
|
|
|
if (fabsf(size[2]) < 1e-5f)
|
2013-10-01 16:40:11 +00:00
|
|
|
size[2] = signf(size[2]) * 1e-5f;
|
2013-09-25 20:28:49 +00:00
|
|
|
}
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2013-09-25 20:28:49 +00:00
|
|
|
size_to_mat4(smat, texmap->size);
|
|
|
|
|
2011-11-07 17:35:20 +00:00
|
|
|
/* rotation */
|
2013-09-25 20:28:49 +00:00
|
|
|
eul_to_mat4(rmat, texmap->rot);
|
|
|
|
|
2011-11-07 17:35:20 +00:00
|
|
|
/* translation */
|
2013-09-25 20:28:49 +00:00
|
|
|
unit_m4(tmat);
|
|
|
|
copy_v3_v3(tmat[3], texmap->loc);
|
|
|
|
|
|
|
|
if (texmap->type == TEXMAP_TYPE_TEXTURE) {
|
|
|
|
/* to transform a texture, the inverse transform needs
|
|
|
|
* to be applied to the texture coordinate */
|
2014-07-21 18:55:12 +10:00
|
|
|
mul_m4_series(texmap->mat, tmat, rmat, smat);
|
2013-09-25 20:28:49 +00:00
|
|
|
invert_m4(texmap->mat);
|
|
|
|
}
|
|
|
|
else if (texmap->type == TEXMAP_TYPE_POINT) {
|
|
|
|
/* forward transform */
|
2014-07-21 18:55:12 +10:00
|
|
|
mul_m4_series(texmap->mat, tmat, rmat, smat);
|
2013-09-25 20:28:49 +00:00
|
|
|
}
|
|
|
|
else if (texmap->type == TEXMAP_TYPE_VECTOR) {
|
|
|
|
/* no translation for vectors */
|
|
|
|
mul_m4_m4m4(texmap->mat, rmat, smat);
|
|
|
|
}
|
|
|
|
else if (texmap->type == TEXMAP_TYPE_NORMAL) {
|
|
|
|
/* no translation for normals, and inverse transpose */
|
|
|
|
mul_m4_m4m4(texmap->mat, rmat, smat);
|
|
|
|
invert_m4(texmap->mat);
|
|
|
|
transpose_m4(texmap->mat);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* projection last */
|
|
|
|
mul_m4_m4m4(texmap->mat, texmap->mat, proj);
|
2011-11-07 17:35:20 +00:00
|
|
|
|
|
|
|
texmap->flag &= ~TEXMAP_UNIT_MATRIX;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
ColorMapping *BKE_texture_colormapping_add(void)
|
2011-11-07 17:35:20 +00:00
|
|
|
{
|
2012-05-06 15:15:33 +00:00
|
|
|
ColorMapping *colormap = MEM_callocN(sizeof(ColorMapping), "ColorMapping");
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
BKE_texture_colormapping_default(colormap);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2011-11-07 17:35:20 +00:00
|
|
|
return colormap;
|
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_colormapping_default(ColorMapping *colormap)
|
2011-11-07 17:35:20 +00:00
|
|
|
{
|
|
|
|
memset(colormap, 0, sizeof(ColorMapping));
|
|
|
|
|
2017-12-07 15:52:59 +11:00
|
|
|
BKE_colorband_init(&colormap->coba, true);
|
2011-11-07 17:35:20 +00:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
colormap->bright = 1.0;
|
|
|
|
colormap->contrast = 1.0;
|
|
|
|
colormap->saturation = 1.0;
|
2006-01-04 12:13:13 +00:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
colormap->blend_color[0] = 0.8f;
|
|
|
|
colormap->blend_color[1] = 0.8f;
|
|
|
|
colormap->blend_color[2] = 0.8f;
|
|
|
|
colormap->blend_type = MA_RAMP_BLEND;
|
|
|
|
colormap->blend_factor = 0.0f;
|
2006-01-04 12:13:13 +00:00
|
|
|
}
|
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
/* ******************* TEX ************************ */
|
|
|
|
|
ID-Remap - Step one: core work (cleanup and rework of generic ID datablock handling).
This commit changes a lot of how IDs are handled internally, especially the unlinking/freeing
processes. So far, this was very fuzy, to summarize cleanly deleting or replacing a datablock
was pretty much impossible, except for a few special cases.
Also, unlinking was handled by each datatype, in a rather messy and prone-to-errors way (quite
a few ID usages were missed or wrongly handled that way).
One of the main goal of id-remap branch was to cleanup this, and fatorize ID links handling
by using library_query utils to allow generic handling of those, which is now the case
(now, generic ID links handling is only "knwon" from readfile.c and library_query.c).
This commit also adds backends to allow live replacement and deletion of datablocks in Blender
(so-called 'remapping' process, where we replace all usages of a given ID pointer by a new one,
or NULL one in case of unlinking).
This will allow nice new features, like ability to easily reload or relocate libraries, real immediate
deletion of datablocks in blender, replacement of one datablock by another, etc.
Some of those are for next commits.
A word of warning: this commit is highly risky, because it affects potentially a lot in Blender core.
Though it was tested rather deeply, being totally impossible to check all possible ID usage cases,
it's likely there are some remaining issues and bugs in new code... Please report them! ;)
Review task: D2027 (https://developer.blender.org/D2027).
Reviewed by campbellbarton, thanks a bunch.
2016-06-22 17:29:38 +02:00
|
|
|
/** Free (or release) any data used by this texture (does not free the texure itself). */
|
2012-05-05 14:03:12 +00:00
|
|
|
void BKE_texture_free(Tex *tex)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
ID-Remap - Step one: core work (cleanup and rework of generic ID datablock handling).
This commit changes a lot of how IDs are handled internally, especially the unlinking/freeing
processes. So far, this was very fuzy, to summarize cleanly deleting or replacing a datablock
was pretty much impossible, except for a few special cases.
Also, unlinking was handled by each datatype, in a rather messy and prone-to-errors way (quite
a few ID usages were missed or wrongly handled that way).
One of the main goal of id-remap branch was to cleanup this, and fatorize ID links handling
by using library_query utils to allow generic handling of those, which is now the case
(now, generic ID links handling is only "knwon" from readfile.c and library_query.c).
This commit also adds backends to allow live replacement and deletion of datablocks in Blender
(so-called 'remapping' process, where we replace all usages of a given ID pointer by a new one,
or NULL one in case of unlinking).
This will allow nice new features, like ability to easily reload or relocate libraries, real immediate
deletion of datablocks in blender, replacement of one datablock by another, etc.
Some of those are for next commits.
A word of warning: this commit is highly risky, because it affects potentially a lot in Blender core.
Though it was tested rather deeply, being totally impossible to check all possible ID usage cases,
it's likely there are some remaining issues and bugs in new code... Please report them! ;)
Review task: D2027 (https://developer.blender.org/D2027).
Reviewed by campbellbarton, thanks a bunch.
2016-06-22 17:29:38 +02:00
|
|
|
BKE_animdata_free((ID *)tex, false);
|
|
|
|
|
|
|
|
/* is no lib link block, but texture extension */
|
2012-03-24 06:18:31 +00:00
|
|
|
if (tex->nodetree) {
|
2018-12-14 15:20:33 +01:00
|
|
|
ntreeFreeNestedTree(tex->nodetree);
|
2008-11-12 22:03:11 +00:00
|
|
|
MEM_freeN(tex->nodetree);
|
ID-Remap - Step one: core work (cleanup and rework of generic ID datablock handling).
This commit changes a lot of how IDs are handled internally, especially the unlinking/freeing
processes. So far, this was very fuzy, to summarize cleanly deleting or replacing a datablock
was pretty much impossible, except for a few special cases.
Also, unlinking was handled by each datatype, in a rather messy and prone-to-errors way (quite
a few ID usages were missed or wrongly handled that way).
One of the main goal of id-remap branch was to cleanup this, and fatorize ID links handling
by using library_query utils to allow generic handling of those, which is now the case
(now, generic ID links handling is only "knwon" from readfile.c and library_query.c).
This commit also adds backends to allow live replacement and deletion of datablocks in Blender
(so-called 'remapping' process, where we replace all usages of a given ID pointer by a new one,
or NULL one in case of unlinking).
This will allow nice new features, like ability to easily reload or relocate libraries, real immediate
deletion of datablocks in blender, replacement of one datablock by another, etc.
Some of those are for next commits.
A word of warning: this commit is highly risky, because it affects potentially a lot in Blender core.
Though it was tested rather deeply, being totally impossible to check all possible ID usage cases,
it's likely there are some remaining issues and bugs in new code... Please report them! ;)
Review task: D2027 (https://developer.blender.org/D2027).
Reviewed by campbellbarton, thanks a bunch.
2016-06-22 17:29:38 +02:00
|
|
|
tex->nodetree = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
MEM_SAFE_FREE(tex->coba);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
ID-Remap - Step one: core work (cleanup and rework of generic ID datablock handling).
This commit changes a lot of how IDs are handled internally, especially the unlinking/freeing
processes. So far, this was very fuzy, to summarize cleanly deleting or replacing a datablock
was pretty much impossible, except for a few special cases.
Also, unlinking was handled by each datatype, in a rather messy and prone-to-errors way (quite
a few ID usages were missed or wrongly handled that way).
One of the main goal of id-remap branch was to cleanup this, and fatorize ID links handling
by using library_query utils to allow generic handling of those, which is now the case
(now, generic ID links handling is only "knwon" from readfile.c and library_query.c).
This commit also adds backends to allow live replacement and deletion of datablocks in Blender
(so-called 'remapping' process, where we replace all usages of a given ID pointer by a new one,
or NULL one in case of unlinking).
This will allow nice new features, like ability to easily reload or relocate libraries, real immediate
deletion of datablocks in blender, replacement of one datablock by another, etc.
Some of those are for next commits.
A word of warning: this commit is highly risky, because it affects potentially a lot in Blender core.
Though it was tested rather deeply, being totally impossible to check all possible ID usage cases,
it's likely there are some remaining issues and bugs in new code... Please report them! ;)
Review task: D2027 (https://developer.blender.org/D2027).
Reviewed by campbellbarton, thanks a bunch.
2016-06-22 17:29:38 +02:00
|
|
|
BKE_icon_id_delete((ID *)tex);
|
|
|
|
BKE_previewimg_free(&tex->preview);
|
2002-10-12 11:37:38 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_default(Tex *tex)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
2019-03-12 16:59:04 +11:00
|
|
|
/* BLI_assert(MEMCMP_STRUCT_AFTER_IS_ZERO(tex, id)); */ /* Not here, can be called with some pointers set. :/ */
|
First step to handle missing libs/datablocks when reading a file.
Idea is, instead of ignoring completely missing linked datablocks, to
create void placeholders for them.
That way, you can work on your file, save it, and find again your missing data once
lib becomes available again. Or you can edit missing lib's path (in Outliner),
save and reload the file, and you are done.
Also, Outliner now shows broken libraries (and placeholders) with a 'broken lib' icon.
Future plans are also to be able to relocate missing libs and reload them at runtime.
Code notes:
- Placeholder ID is just a regular datablock of same type as expected linked one,
with 'default' data, and a LIB_MISSING bitflag set.
- To allow creation of such datablocks, creation of datablocks in BKE was split in two step:
+ Allocation of memory itself.
+ Setting of all internal data to default values.
See also the design task (T43351).
Reviewed by @campbellbarton, thanks a bunch!
Differential Revision: https://developer.blender.org/D1394
2015-10-20 14:44:57 +02:00
|
|
|
|
2014-07-21 12:02:05 +02:00
|
|
|
tex->type = TEX_IMAGE;
|
|
|
|
tex->ima = NULL;
|
2012-05-06 15:15:33 +00:00
|
|
|
tex->stype = 0;
|
|
|
|
tex->flag = TEX_CHECKER_ODD;
|
2013-03-04 13:18:14 +00:00
|
|
|
tex->imaflag = TEX_INTERPOL | TEX_MIPMAP | TEX_USEALPHA;
|
2012-05-06 15:15:33 +00:00
|
|
|
tex->extend = TEX_REPEAT;
|
|
|
|
tex->cropxmin = tex->cropymin = 0.0;
|
|
|
|
tex->cropxmax = tex->cropymax = 1.0;
|
2009-07-22 17:20:04 +00:00
|
|
|
tex->texfilter = TXF_EWA;
|
2009-07-21 13:20:35 +00:00
|
|
|
tex->afmax = 8;
|
2012-05-06 15:15:33 +00:00
|
|
|
tex->xrepeat = tex->yrepeat = 1;
|
|
|
|
tex->sfra = 1;
|
|
|
|
tex->frames = 0;
|
|
|
|
tex->offset = 0;
|
|
|
|
tex->noisesize = 0.25;
|
|
|
|
tex->noisedepth = 2;
|
|
|
|
tex->turbul = 5.0;
|
|
|
|
tex->nabla = 0.025; // also in do_versions
|
|
|
|
tex->bright = 1.0;
|
|
|
|
tex->contrast = 1.0;
|
|
|
|
tex->saturation = 1.0;
|
|
|
|
tex->filtersize = 1.0;
|
|
|
|
tex->rfac = 1.0;
|
|
|
|
tex->gfac = 1.0;
|
|
|
|
tex->bfac = 1.0;
|
2004-04-03 13:59:27 +00:00
|
|
|
/* newnoise: init. */
|
|
|
|
tex->noisebasis = 0;
|
|
|
|
tex->noisebasis2 = 0;
|
|
|
|
/* musgrave */
|
|
|
|
tex->mg_H = 1.0;
|
|
|
|
tex->mg_lacunarity = 2.0;
|
|
|
|
tex->mg_octaves = 2.0;
|
|
|
|
tex->mg_offset = 1.0;
|
|
|
|
tex->mg_gain = 1.0;
|
|
|
|
tex->ns_outscale = 1.0;
|
|
|
|
/* distnoise */
|
|
|
|
tex->dist_amount = 1.0;
|
|
|
|
/* voronoi */
|
|
|
|
tex->vn_w1 = 1.0;
|
|
|
|
tex->vn_w2 = tex->vn_w3 = tex->vn_w4 = 0.0;
|
|
|
|
tex->vn_mexp = 2.5;
|
|
|
|
tex->vn_distm = 0;
|
|
|
|
tex->vn_coltype = 0;
|
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
tex->iuser.ok = 1;
|
|
|
|
tex->iuser.frames = 100;
|
|
|
|
tex->iuser.sfra = 1;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2007-09-02 17:25:03 +00:00
|
|
|
tex->preview = NULL;
|
2002-10-12 11:37:38 +00:00
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_type_set(Tex *tex, int type)
|
2010-06-22 09:13:30 +00:00
|
|
|
{
|
|
|
|
tex->type = type;
|
|
|
|
}
|
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
Tex *BKE_texture_add(Main *bmain, const char *name)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
|
|
|
Tex *tex;
|
|
|
|
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
tex = BKE_libblock_alloc(bmain, ID_TE, name, 0);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
BKE_texture_default(tex);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
return tex;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_mtex_default(MTex *mtex)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
2014-07-21 12:02:05 +02:00
|
|
|
mtex->texco = TEXCO_UV;
|
2012-05-06 15:15:33 +00:00
|
|
|
mtex->mapto = MAP_COL;
|
|
|
|
mtex->object = NULL;
|
|
|
|
mtex->projx = PROJ_X;
|
|
|
|
mtex->projy = PROJ_Y;
|
|
|
|
mtex->projz = PROJ_Z;
|
|
|
|
mtex->mapping = MTEX_FLAT;
|
|
|
|
mtex->ofs[0] = 0.0;
|
|
|
|
mtex->ofs[1] = 0.0;
|
|
|
|
mtex->ofs[2] = 0.0;
|
|
|
|
mtex->size[0] = 1.0;
|
|
|
|
mtex->size[1] = 1.0;
|
|
|
|
mtex->size[2] = 1.0;
|
|
|
|
mtex->tex = NULL;
|
|
|
|
mtex->colormodel = 0;
|
|
|
|
mtex->r = 1.0;
|
|
|
|
mtex->g = 0.0;
|
|
|
|
mtex->b = 1.0;
|
|
|
|
mtex->k = 1.0;
|
|
|
|
mtex->def_var = 1.0;
|
|
|
|
mtex->blendtype = MTEX_BLEND;
|
|
|
|
mtex->colfac = 1.0;
|
|
|
|
mtex->norfac = 1.0;
|
|
|
|
mtex->varfac = 1.0;
|
|
|
|
mtex->dispfac = 0.2;
|
|
|
|
mtex->colspecfac = 1.0f;
|
|
|
|
mtex->mirrfac = 1.0f;
|
|
|
|
mtex->alphafac = 1.0f;
|
|
|
|
mtex->difffac = 1.0f;
|
|
|
|
mtex->specfac = 1.0f;
|
|
|
|
mtex->emitfac = 1.0f;
|
|
|
|
mtex->hardfac = 1.0f;
|
|
|
|
mtex->raymirrfac = 1.0f;
|
|
|
|
mtex->translfac = 1.0f;
|
|
|
|
mtex->ambfac = 1.0f;
|
|
|
|
mtex->colemitfac = 1.0f;
|
|
|
|
mtex->colreflfac = 1.0f;
|
|
|
|
mtex->coltransfac = 1.0f;
|
|
|
|
mtex->densfac = 1.0f;
|
|
|
|
mtex->scatterfac = 1.0f;
|
|
|
|
mtex->reflfac = 1.0f;
|
|
|
|
mtex->shadowfac = 1.0f;
|
|
|
|
mtex->zenupfac = 1.0f;
|
|
|
|
mtex->zendownfac = 1.0f;
|
|
|
|
mtex->blendfac = 1.0f;
|
|
|
|
mtex->timefac = 1.0f;
|
|
|
|
mtex->lengthfac = 1.0f;
|
|
|
|
mtex->clumpfac = 1.0f;
|
|
|
|
mtex->kinkfac = 1.0f;
|
2015-01-14 12:29:19 +01:00
|
|
|
mtex->kinkampfac = 1.0f;
|
2012-05-06 15:15:33 +00:00
|
|
|
mtex->roughfac = 1.0f;
|
2018-02-15 11:22:44 +01:00
|
|
|
mtex->twistfac = 1.0f;
|
2012-05-06 15:15:33 +00:00
|
|
|
mtex->padensfac = 1.0f;
|
|
|
|
mtex->lifefac = 1.0f;
|
|
|
|
mtex->sizefac = 1.0f;
|
|
|
|
mtex->ivelfac = 1.0f;
|
|
|
|
mtex->dampfac = 1.0f;
|
|
|
|
mtex->gravityfac = 1.0f;
|
|
|
|
mtex->fieldfac = 1.0f;
|
|
|
|
mtex->normapspace = MTEX_NSPACE_TANGENT;
|
2013-01-16 14:36:13 +00:00
|
|
|
mtex->brush_map_mode = MTEX_MAP_MODE_TILED;
|
2015-01-31 17:23:30 +11:00
|
|
|
mtex->random_angle = 2.0f * (float)M_PI;
|
2014-12-26 23:51:27 +01:00
|
|
|
mtex->brush_angle_mode = 0;
|
2002-10-12 11:37:38 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
MTex *BKE_texture_mtex_add(void)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
|
|
|
MTex *mtex;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
mtex = MEM_callocN(sizeof(MTex), "BKE_texture_mtex_add");
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
BKE_texture_mtex_default(mtex);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
return mtex;
|
|
|
|
}
|
|
|
|
|
2010-09-03 14:53:54 +00:00
|
|
|
/* slot -1 for first free ID */
|
2015-03-29 03:16:55 +11:00
|
|
|
MTex *BKE_texture_mtex_add_id(ID *id, int slot)
|
2010-09-03 14:53:54 +00:00
|
|
|
{
|
|
|
|
MTex **mtex_ar;
|
|
|
|
short act;
|
|
|
|
|
|
|
|
give_active_mtex(id, &mtex_ar, &act);
|
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
if (mtex_ar == NULL) {
|
2010-09-03 14:53:54 +00:00
|
|
|
return NULL;
|
|
|
|
}
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
if (slot == -1) {
|
2010-09-03 14:53:54 +00:00
|
|
|
/* find first free */
|
2012-10-21 05:46:41 +00:00
|
|
|
int i;
|
2012-05-06 15:15:33 +00:00
|
|
|
for (i = 0; i < MAX_MTEX; i++) {
|
2010-09-03 14:53:54 +00:00
|
|
|
if (!mtex_ar[i]) {
|
2012-05-06 15:15:33 +00:00
|
|
|
slot = i;
|
2010-09-03 14:53:54 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2012-03-24 06:18:31 +00:00
|
|
|
if (slot == -1) {
|
2010-09-03 14:53:54 +00:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
/* make sure slot is valid */
|
2012-03-24 06:18:31 +00:00
|
|
|
if (slot < 0 || slot >= MAX_MTEX) {
|
2010-09-03 14:53:54 +00:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mtex_ar[slot]) {
|
|
|
|
id_us_min((ID *)mtex_ar[slot]->tex);
|
|
|
|
MEM_freeN(mtex_ar[slot]);
|
2012-05-06 15:15:33 +00:00
|
|
|
mtex_ar[slot] = NULL;
|
2010-09-03 14:53:54 +00:00
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
mtex_ar[slot] = BKE_texture_mtex_add();
|
2010-09-03 14:53:54 +00:00
|
|
|
|
|
|
|
return mtex_ar[slot];
|
|
|
|
}
|
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
/**
|
|
|
|
* Only copy internal data of Texture ID from source to already allocated/initialized destination.
|
2019-02-04 20:39:59 +01:00
|
|
|
* You probably never want to use that directly, use BKE_id_copy or BKE_id_copy_ex for typical needs.
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
*
|
|
|
|
* WARNING! This function will not handle ID user count!
|
|
|
|
*
|
2018-12-12 12:50:58 +11:00
|
|
|
* \param flag: Copying options (see BKE_library.h's LIB_ID_COPY_... flags for more).
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
*/
|
|
|
|
void BKE_texture_copy_data(Main *bmain, Tex *tex_dst, const Tex *tex_src, const int flag)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
if (!BKE_texture_is_image_user(tex_src)) {
|
|
|
|
tex_dst->ima = NULL;
|
2015-02-23 18:22:09 +11:00
|
|
|
}
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
|
|
|
|
if (tex_dst->coba) {
|
|
|
|
tex_dst->coba = MEM_dupallocN(tex_dst->coba);
|
|
|
|
}
|
|
|
|
if (tex_src->nodetree) {
|
|
|
|
if (tex_src->nodetree->execdata) {
|
|
|
|
ntreeTexEndExecTree(tex_src->nodetree->execdata);
|
2011-09-05 21:01:50 +00:00
|
|
|
}
|
2017-10-19 12:31:58 +02:00
|
|
|
/* Note: nodetree is *not* in bmain, however this specific case is handled at lower level
|
|
|
|
* (see BKE_libblock_copy_ex()). */
|
2019-02-04 15:34:31 +01:00
|
|
|
BKE_id_copy_ex(bmain, (ID *)tex_src->nodetree, (ID **)&tex_dst->nodetree, flag);
|
2008-11-12 22:03:11 +00:00
|
|
|
}
|
2016-07-19 16:27:40 +02:00
|
|
|
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
if ((flag & LIB_ID_COPY_NO_PREVIEW) == 0) {
|
|
|
|
BKE_previewimg_id_copy(&tex_dst->id, &tex_src->id);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
tex_dst->preview = NULL;
|
|
|
|
}
|
|
|
|
}
|
2015-01-09 09:52:51 +01:00
|
|
|
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
Tex *BKE_texture_copy(Main *bmain, const Tex *tex)
|
|
|
|
{
|
|
|
|
Tex *tex_copy;
|
2019-02-04 20:38:01 +01:00
|
|
|
BKE_id_copy(bmain, &tex->id, (ID **)&tex_copy);
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
return tex_copy;
|
2002-10-12 11:37:38 +00:00
|
|
|
}
|
|
|
|
|
2011-03-03 18:53:07 +00:00
|
|
|
/* texture copy without adding to main dbase */
|
2015-03-29 03:16:55 +11:00
|
|
|
Tex *BKE_texture_localize(Tex *tex)
|
2011-03-03 18:53:07 +00:00
|
|
|
{
|
2018-11-15 16:28:07 +01:00
|
|
|
/* TODO(bastien): Replace with something like:
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
*
|
2018-11-15 16:28:07 +01:00
|
|
|
* Tex *tex_copy;
|
|
|
|
* BKE_id_copy_ex(bmain, &tex->id, (ID **)&tex_copy,
|
|
|
|
* LIB_ID_COPY_NO_MAIN | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_NO_USER_REFCOUNT,
|
|
|
|
* false);
|
|
|
|
* return tex_copy;
|
|
|
|
*
|
|
|
|
* NOTE: Only possible once nested node trees are fully converted to that too. */
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
|
2011-03-03 18:53:07 +00:00
|
|
|
Tex *texn;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2018-12-04 12:30:24 +01:00
|
|
|
texn = BKE_libblock_copy_for_localize(&tex->id);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-05-05 14:03:12 +00:00
|
|
|
/* image texture: BKE_texture_free also doesn't decrease */
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
if (texn->coba) texn->coba = MEM_dupallocN(texn->coba);
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2011-03-03 18:53:07 +00:00
|
|
|
texn->preview = NULL;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (tex->nodetree) {
|
2012-05-06 15:15:33 +00:00
|
|
|
texn->nodetree = ntreeLocalize(tex->nodetree);
|
2011-03-03 18:53:07 +00:00
|
|
|
}
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2018-11-15 16:36:35 +01:00
|
|
|
texn->id.tag |= LIB_TAG_LOCALIZED;
|
|
|
|
|
2011-03-03 18:53:07 +00:00
|
|
|
return texn;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2002-10-12 11:37:38 +00:00
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
2016-07-20 19:49:45 +02:00
|
|
|
void BKE_texture_make_local(Main *bmain, Tex *tex, const bool lib_local)
|
2002-10-12 11:37:38 +00:00
|
|
|
{
|
2016-07-20 19:49:45 +02:00
|
|
|
BKE_id_make_local_generic(bmain, &tex->id, true, lib_local);
|
2002-10-12 11:37:38 +00:00
|
|
|
}
|
|
|
|
|
2014-05-03 18:51:53 +09:00
|
|
|
Tex *give_current_linestyle_texture(FreestyleLineStyle *linestyle)
|
|
|
|
{
|
|
|
|
MTex *mtex = NULL;
|
|
|
|
Tex *tex = NULL;
|
|
|
|
|
|
|
|
if (linestyle) {
|
|
|
|
mtex = linestyle->mtex[(int)(linestyle->texact)];
|
|
|
|
if (mtex) tex = mtex->tex;
|
|
|
|
}
|
|
|
|
|
|
|
|
return tex;
|
|
|
|
}
|
|
|
|
|
|
|
|
void set_current_linestyle_texture(FreestyleLineStyle *linestyle, Tex *newtex)
|
|
|
|
{
|
|
|
|
int act = linestyle->texact;
|
|
|
|
|
|
|
|
if (linestyle->mtex[act] && linestyle->mtex[act]->tex)
|
|
|
|
id_us_min(&linestyle->mtex[act]->tex->id);
|
|
|
|
|
|
|
|
if (newtex) {
|
|
|
|
if (!linestyle->mtex[act]) {
|
2015-03-29 03:16:55 +11:00
|
|
|
linestyle->mtex[act] = BKE_texture_mtex_add();
|
2014-05-03 18:51:53 +09:00
|
|
|
linestyle->mtex[act]->texco = TEXCO_STROKE;
|
|
|
|
}
|
|
|
|
|
|
|
|
linestyle->mtex[act]->tex = newtex;
|
|
|
|
id_us_plus(&newtex->id);
|
|
|
|
}
|
|
|
|
else if (linestyle->mtex[act]) {
|
|
|
|
MEM_freeN(linestyle->mtex[act]);
|
|
|
|
linestyle->mtex[act] = NULL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-04-01 11:34:00 +11:00
|
|
|
bool give_active_mtex(ID *id, MTex ***mtex_ar, short *act)
|
2009-10-12 16:00:39 +00:00
|
|
|
{
|
2012-04-28 06:31:57 +00:00
|
|
|
switch (GS(id->name)) {
|
2014-05-03 18:51:53 +09:00
|
|
|
case ID_LS:
|
|
|
|
*mtex_ar = ((FreestyleLineStyle *)id)->mtex;
|
|
|
|
if (act) *act = (((FreestyleLineStyle *)id)->texact);
|
|
|
|
break;
|
2012-05-06 15:15:33 +00:00
|
|
|
case ID_PA:
|
|
|
|
*mtex_ar = ((ParticleSettings *)id)->mtex;
|
|
|
|
if (act) *act = (((ParticleSettings *)id)->texact);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
*mtex_ar = NULL;
|
|
|
|
if (act) *act = 0;
|
2014-04-01 11:34:00 +11:00
|
|
|
return false;
|
2009-10-12 16:00:39 +00:00
|
|
|
}
|
|
|
|
|
2014-04-01 11:34:00 +11:00
|
|
|
return true;
|
2009-10-12 16:00:39 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void set_active_mtex(ID *id, short act)
|
|
|
|
{
|
2012-05-06 15:15:33 +00:00
|
|
|
if (act < 0) act = 0;
|
|
|
|
else if (act >= MAX_MTEX) act = MAX_MTEX - 1;
|
2009-10-12 16:00:39 +00:00
|
|
|
|
2012-04-28 06:31:57 +00:00
|
|
|
switch (GS(id->name)) {
|
2014-05-03 18:51:53 +09:00
|
|
|
case ID_LS:
|
|
|
|
((FreestyleLineStyle *)id)->texact = act;
|
|
|
|
break;
|
2012-05-06 15:15:33 +00:00
|
|
|
case ID_PA:
|
|
|
|
((ParticleSettings *)id)->texact = act;
|
|
|
|
break;
|
2017-08-28 11:19:58 +02:00
|
|
|
default:
|
|
|
|
break;
|
2009-10-12 16:00:39 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-10-09 09:50:49 +00:00
|
|
|
Tex *give_current_brush_texture(Brush *br)
|
|
|
|
{
|
2010-01-03 08:37:18 +00:00
|
|
|
return br->mtex.tex;
|
2009-10-09 09:50:49 +00:00
|
|
|
}
|
|
|
|
|
2009-10-12 13:12:45 +00:00
|
|
|
void set_current_brush_texture(Brush *br, Tex *newtex)
|
|
|
|
{
|
2012-03-24 06:18:31 +00:00
|
|
|
if (br->mtex.tex)
|
2010-01-03 08:37:18 +00:00
|
|
|
id_us_min(&br->mtex.tex->id);
|
2009-10-12 13:12:45 +00:00
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (newtex) {
|
2012-05-06 15:15:33 +00:00
|
|
|
br->mtex.tex = newtex;
|
2009-10-12 13:12:45 +00:00
|
|
|
id_us_plus(&newtex->id);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-02-12 14:38:34 +00:00
|
|
|
Tex *give_current_particle_texture(ParticleSettings *part)
|
|
|
|
{
|
2012-05-06 15:15:33 +00:00
|
|
|
MTex *mtex = NULL;
|
|
|
|
Tex *tex = NULL;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (!part) return NULL;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
mtex = part->mtex[(int)(part->texact)];
|
|
|
|
if (mtex) tex = mtex->tex;
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2011-02-12 14:38:34 +00:00
|
|
|
return tex;
|
|
|
|
}
|
|
|
|
|
|
|
|
void set_current_particle_texture(ParticleSettings *part, Tex *newtex)
|
|
|
|
{
|
2012-05-06 15:15:33 +00:00
|
|
|
int act = part->texact;
|
2011-02-12 14:38:34 +00:00
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (part->mtex[act] && part->mtex[act]->tex)
|
2011-02-12 14:38:34 +00:00
|
|
|
id_us_min(&part->mtex[act]->tex->id);
|
|
|
|
|
2012-03-24 06:18:31 +00:00
|
|
|
if (newtex) {
|
|
|
|
if (!part->mtex[act]) {
|
2015-03-29 03:16:55 +11:00
|
|
|
part->mtex[act] = BKE_texture_mtex_add();
|
2012-05-06 15:15:33 +00:00
|
|
|
part->mtex[act]->texco = TEXCO_ORCO;
|
|
|
|
part->mtex[act]->blendtype = MTEX_MUL;
|
2011-02-12 14:38:34 +00:00
|
|
|
}
|
2018-06-17 17:05:51 +02:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
part->mtex[act]->tex = newtex;
|
2011-02-12 14:38:34 +00:00
|
|
|
id_us_plus(&newtex->id);
|
|
|
|
}
|
2012-03-24 06:18:31 +00:00
|
|
|
else if (part->mtex[act]) {
|
2011-02-12 14:38:34 +00:00
|
|
|
MEM_freeN(part->mtex[act]);
|
2012-05-06 15:15:33 +00:00
|
|
|
part->mtex[act] = NULL;
|
2011-02-12 14:38:34 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Giant commit!
A full detailed description of this will be done later... is several days
of work. Here's a summary:
Render:
- Full cleanup of render code, removing *all* globals and bad level calls
all over blender. Render module is now not called abusive anymore
- API-fied calls to rendering
- Full recode of internal render pipeline. Is now rendering tiles by
default, prepared for much smarter 'bucket' render later.
- Each thread now can render a full part
- Renders were tested with 4 threads, goes fine, apart from some lookup
tables in softshadow and AO still
- Rendering is prepared to do multiple layers and passes
- No single 32 bits trick in render code anymore, all 100% floats now.
Writing images/movies
- moved writing images to blender kernel (bye bye 'schrijfplaatje'!)
- made a new Movie handle system, also in kernel. This will enable much
easier use of movies in Blender
PreviewRender:
- Using new render API, previewrender (in buttons) now uses regular render
code to generate images.
- new datafile 'preview.blend.c' has the preview scenes in it
- previews get rendered in exact displayed size (1 pixel = 1 pixel)
3D Preview render
- new; press Pkey in 3d window, for a panel that continuously renders
(pkey is for games, i know... but we dont do that in orange now!)
- this render works nearly identical to buttons-preview render, so it stops
rendering on any event (mouse, keyboard, etc)
- on moving/scaling the panel, the render code doesn't recreate all geometry
- same for shifting/panning view
- all other operations (now) regenerate the full render database still.
- this is WIP... but big fun, especially for simple scenes!
Compositor
- Using same node system as now in use for shaders, you can composit images
- works pretty straightforward... needs much more options/tools and integration
with rendering still
- is not threaded yet, nor is so smart to only recalculate changes... will be
done soon!
- the "Render Result" node will get all layers/passes as output sockets
- The "Output" node renders to a builtin image, which you can view in the Image
window. (yes, output nodes to render-result, and to files, is on the list!)
The Bad News
- "Unified Render" is removed. It might come back in some stage, but this
system should be built from scratch. I can't really understand this code...
I expect it is not much needed, especially with advanced layer/passes
control
- Panorama render, Field render, Motion blur, is not coded yet... (I had to
recode every single feature in render, so...!)
- Lens Flare is also not back... needs total revision, might become composit
effect though (using zbuffer for visibility)
- Part render is gone! (well, thats obvious, its default now).
- The render window is only restored with limited functionality... I am going
to check first the option to render to a Image window, so Blender can become
a true single-window application. :)
For example, the 'Spare render buffer' (jkey) doesnt work.
- Render with border, now default creates a smaller image
- No zbuffers are written yet... on the todo!
- Scons files and MSVC will need work to get compiling again
OK... thats what I can quickly recall. Now go compiling!
2006-01-23 22:05:47 +00:00
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
|
2015-07-18 22:36:09 +02:00
|
|
|
void BKE_texture_pointdensity_init_data(PointDensity *pd)
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
{
|
2008-11-10 00:14:35 +00:00
|
|
|
pd->flag = 0;
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
pd->radius = 0.3f;
|
2008-10-01 03:35:53 +00:00
|
|
|
pd->falloff_type = TEX_PD_FALLOFF_STD;
|
2008-10-22 01:31:46 +00:00
|
|
|
pd->falloff_softness = 2.0;
|
Point Density texture
The Point Density texture now has some additional options for how
the point locations are cached. Previously it was all relative to
worldspace, but there are now some other options that make things
a lot more convenient for mapping the texture to Local (or Orco).
Thanks to theeth for helping with the space conversions!
The new Object space options allow this sort of thing to be possible
- a particle system, instanced on a transformed renderable object:
http://mke3.net/blender/devel/rendering/volumetrics/pd_objectspace.mov
It's also a lot easier to use multiple instances, just duplicate
the renderable objects and move them around.
The new particle cache options are:
* Emit Object space
This caches the particles relative to the emitter object's
coordinate space (i.e. relative to the emitter's object center).
This makes it possible to map the Texture to Local or Orco
easily, so you can easily move, rotate or scale the rendering
object that has the Point Density texture. It's relative to the
emitter's location, rotation and scale, so if the object you're
rendering the texture on is aligned differently to the emitter,
the results will be rotated etc.
* Emit Object Location
This offsets the particles to the emitter object's location in 3D
space. It's similar to Emit Object Space, however the emitter
object's rotation and scale are ignored. This is probably the
easiest to use, since you don't need to worry about the rotation
and scale of the emitter object (just the rendered object), so
it's the default.
* Global Space
This is the same as previously, the particles are cached in global space, so to use this effectively you'll need to map the texture to Global, and have the rendered object in the right global location.
2008-09-29 04:19:24 +00:00
|
|
|
pd->source = TEX_PD_PSYS;
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
pd->point_tree = NULL;
|
2008-10-02 01:38:12 +00:00
|
|
|
pd->point_data = NULL;
|
* New point density update: Turbulence
This addition allows you to perturb the point density with noise, to give
the impression of more resolution. It's a quick way to add detail, without
having to use large, complex, and slower to render particle systems.
Rather than just overlaying noise, like you might do by adding a secondary
clouds texture, it uses noise to perturb the actual coordinate looked up
in the density evaluation. This gives a much better looking result, as it
actually alters the original density.
Comparison of the particle cloud render without, and with added turbulence
(the render with turbulence only renders slightly more slowly):
http://mke3.net/blender/devel/rendering/volumetrics/pd_turbulence.jpg
Using the same constant noise function/spatial coordinates will give a
static appearance. This is fine (and quicker) if the particles aren't
moving, but on animated particle systems, it looks bad, as if the
particles are moving through a static noise field. To overcome this, there
are additional options for particle systems, to influence the turbulence
with the particles' average velocity, or average angular velocity. This
information is only available for particle systems at the present.
Here you can see the (dramatic) difference between no turbulence, static
turbulence, and turbulence influenced by particle velocity:
http://mke3.net/blender/devel/rendering/volumetrics/turbu_compare.mov
2008-10-06 12:25:22 +00:00
|
|
|
pd->noise_size = 0.5f;
|
|
|
|
pd->noise_depth = 1;
|
|
|
|
pd->noise_fac = 1.0f;
|
|
|
|
pd->noise_influence = TEX_PD_NOISE_STATIC;
|
2017-12-07 15:52:59 +11:00
|
|
|
pd->coba = BKE_colorband_add(true);
|
2008-11-09 01:16:12 +00:00
|
|
|
pd->speed_scale = 1.0f;
|
|
|
|
pd->totpoints = 0;
|
2009-08-17 22:09:36 +00:00
|
|
|
pd->object = NULL;
|
2009-11-04 08:44:42 +00:00
|
|
|
pd->psys = 0;
|
2012-05-06 15:15:33 +00:00
|
|
|
pd->psys_cache_space = TEX_PD_WORLDSPACE;
|
2011-05-01 03:57:53 +00:00
|
|
|
pd->falloff_curve = curvemapping_add(1, 0, 0, 1, 1);
|
|
|
|
|
|
|
|
pd->falloff_curve->preset = CURVE_PRESET_LINE;
|
|
|
|
pd->falloff_curve->cm->flag &= ~CUMA_EXTEND_EXTRAPOLATE;
|
|
|
|
curvemap_reset(pd->falloff_curve->cm, &pd->falloff_curve->clipr, pd->falloff_curve->preset, CURVEMAP_SLOPE_POSITIVE);
|
2014-04-01 11:34:00 +11:00
|
|
|
curvemapping_changed(pd->falloff_curve, false);
|
2015-07-18 22:36:09 +02:00
|
|
|
}
|
2011-05-01 03:57:53 +00:00
|
|
|
|
2015-07-18 22:36:09 +02:00
|
|
|
PointDensity *BKE_texture_pointdensity_add(void)
|
|
|
|
{
|
|
|
|
PointDensity *pd = MEM_callocN(sizeof(PointDensity), "pointdensity");
|
|
|
|
BKE_texture_pointdensity_init_data(pd);
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
return pd;
|
2018-06-17 17:05:51 +02:00
|
|
|
}
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
PointDensity *BKE_texture_pointdensity_copy(const PointDensity *pd, const int UNUSED(flag))
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
{
|
|
|
|
PointDensity *pdn;
|
Point Density texture
The Point Density texture now has some additional options for how
the point locations are cached. Previously it was all relative to
worldspace, but there are now some other options that make things
a lot more convenient for mapping the texture to Local (or Orco).
Thanks to theeth for helping with the space conversions!
The new Object space options allow this sort of thing to be possible
- a particle system, instanced on a transformed renderable object:
http://mke3.net/blender/devel/rendering/volumetrics/pd_objectspace.mov
It's also a lot easier to use multiple instances, just duplicate
the renderable objects and move them around.
The new particle cache options are:
* Emit Object space
This caches the particles relative to the emitter object's
coordinate space (i.e. relative to the emitter's object center).
This makes it possible to map the Texture to Local or Orco
easily, so you can easily move, rotate or scale the rendering
object that has the Point Density texture. It's relative to the
emitter's location, rotation and scale, so if the object you're
rendering the texture on is aligned differently to the emitter,
the results will be rotated etc.
* Emit Object Location
This offsets the particles to the emitter object's location in 3D
space. It's similar to Emit Object Space, however the emitter
object's rotation and scale are ignored. This is probably the
easiest to use, since you don't need to worry about the rotation
and scale of the emitter object (just the rendered object), so
it's the default.
* Global Space
This is the same as previously, the particles are cached in global space, so to use this effectively you'll need to map the texture to Global, and have the rendered object in the right global location.
2008-09-29 04:19:24 +00:00
|
|
|
|
2012-05-06 15:15:33 +00:00
|
|
|
pdn = MEM_dupallocN(pd);
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
pdn->point_tree = NULL;
|
2008-10-02 01:38:12 +00:00
|
|
|
pdn->point_data = NULL;
|
Refactor ID copying (and to some extent, ID freeing).
This will allow much finer controll over how we copy data-blocks, from
full copy in Main database, to "lighter" ones (out of Main, inside an
already allocated datablock, etc.).
This commit also transfers a llot of what was previously handled by
per-ID-type custom code to generic ID handling code in BKE_library.
Hopefully will avoid in future inconsistencies and missing bits we had
all over the codebase in the past.
It also adds missing copying handling for a few types, most notably
Scene (which where using a fully customized handling previously).
Note that the type of allocation used during copying (regular in Main,
allocated but outside of Main, or not allocated by ID handling code at
all) is stored in ID's, which allows to handle them correctly when
freeing. This needs to be taken care of with caution when doing 'weird'
unusual things with ID copying and/or allocation!
As a final note, while rather noisy, this commit will hopefully not
break too much existing branches, old 'API' has been kept for the main
part, as a wrapper around new code. Cleaning it up will happen later.
Design task : T51804
Phab Diff: D2714
2017-08-07 16:39:55 +02:00
|
|
|
if (pdn->coba) {
|
|
|
|
pdn->coba = MEM_dupallocN(pdn->coba);
|
|
|
|
}
|
2011-05-01 05:51:21 +00:00
|
|
|
pdn->falloff_curve = curvemapping_copy(pdn->falloff_curve); /* can be NULL */
|
2008-10-22 06:10:16 +00:00
|
|
|
return pdn;
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_pointdensity_free_data(PointDensity *pd)
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
{
|
|
|
|
if (pd->point_tree) {
|
2008-10-01 03:35:53 +00:00
|
|
|
BLI_bvhtree_free(pd->point_tree);
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
pd->point_tree = NULL;
|
|
|
|
}
|
2008-10-01 03:35:53 +00:00
|
|
|
if (pd->point_data) {
|
|
|
|
MEM_freeN(pd->point_data);
|
|
|
|
pd->point_data = NULL;
|
|
|
|
}
|
2012-03-24 06:18:31 +00:00
|
|
|
if (pd->coba) {
|
2011-03-16 18:21:31 +00:00
|
|
|
MEM_freeN(pd->coba);
|
|
|
|
pd->coba = NULL;
|
|
|
|
}
|
2011-05-01 05:51:21 +00:00
|
|
|
|
|
|
|
curvemapping_free(pd->falloff_curve); /* can be NULL */
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
}
|
|
|
|
|
2015-03-29 03:16:55 +11:00
|
|
|
void BKE_texture_pointdensity_free(PointDensity *pd)
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
{
|
2015-03-29 03:16:55 +11:00
|
|
|
BKE_texture_pointdensity_free_data(pd);
|
* Volumetrics
Removed all the old particle rendering code and options I had in there
before, in order to make way for...
A new procedural texture: 'Point Density'
Point Density is a 3d texture that find the density of a group of 'points'
in space and returns that in the texture as an intensity value. Right now,
its at an early stage and it's only enabled for particles, but it would be
cool to extend it later for things like object vertices, or point cache
files from disk - i.e. to import point cloud data into Blender for
rendering volumetrically.
Currently there are just options for an Object and its particle system
number, this is the particle system that will get cached before rendering,
and then used for the texture's density estimation.
It works totally consistent with as any other procedural texture, so
previously where I've mapped a clouds texture to volume density to make
some of those test renders, now I just map a point density texture to
volume density.
Here's a version of the same particle smoke test file from before, updated
to use the point density texture instead:
http://mke3.net/blender/devel/rendering/volumetrics/smoke_test02.blend
There are a few cool things about implementing this as a texture:
- The one texture (and cache) can be instanced across many different
materials:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_instanced.png
This means you can calculate and bake one particle system, but render it
multiple times across the scene, with different material settings, at no
extra memory cost.
Right now, the particles are cached in world space, so you have to map it
globally, and if you want it offset, you have to do it in the material (as
in the file above). I plan to add an option to bake in local space, so you
can just map the texture to local and it just works.
- It also works for solid surfaces too, it just gets the density at that
particular point on the surface, eg:
http://mke3.net/blender/devel/rendering/volumetrics/pointdensity_solid.mov
- You can map it to whatever you want, not only density but the various
emissions and colours as well. I'd like to investigate using the other
outputs in the texture too (like the RGB or normal outputs), perhaps with
options to colour by particle age, generating normals for making particle
'dents' in a surface, whatever!
2008-09-28 08:00:22 +00:00
|
|
|
MEM_freeN(pd);
|
|
|
|
}
|
2011-11-13 12:17:27 +00:00
|
|
|
/* ------------------------------------------------------------------------- */
|
* Volume Rendering: Voxel data
This commit introduces a new texture ('Voxel Data'), used to load up saved voxel
data sets for rendering, contributed by Raúl 'farsthary' Fernández Hernández
with some additional tweaks. Thanks, Raúl!
The texture works similar to the existing point density texture, currently it
only provides intensity information, which can then be mapped (for example) to
density in a volume material. This is an early version, intended to read the
voxel format saved by Raúl's command line simulators, in future revisions
there's potential for making a more full-featured 'Blender voxel file format',
and also for supporting other formats too.
Note: Due to some subtleties in Raúl's existing released simulators, in order
to load them correctly the voxel data texture, you'll need to raise the
'resolution' value by 2. So if you baked out the simulation at resolution 50,
enter 52 for the resolution in the texture panel. This can possibly be fixed in
the simulator later on.
Right now, the way the texture is mapped is just in the space 0,0,0 <-> 1,1,1
and it can appear rotated 90 degrees incorrectly. This will be tackled, for now,
probably the easiest way to map it is with and empty, using Map Input -> Object.
Smoke test: http://www.vimeo.com/2449270
One more note, trilinear interpolation seems a bit slow at the moment, we'll
look into this.
For curiosity, while testing/debugging this, I made a script that exports a mesh
to voxel data. Here's a test of grogan (www.kajimba.com) converted to voxels,
rendered as a volume: http://www.vimeo.com/2512028
The script is available here: http://mke3.net/projects/bpython/export_object_voxeldata.py
* Another smaller thing, brought back early ray termination (was disabled
previously for debugging) and made it user configurable. It now appears as a new
value in the volume material: 'Depth Cutoff'. For some background info on what
this does, check:
http://farsthary.wordpress.com/2008/12/11/cutting-down-render-times/
* Also some disabled work-in-progess code for light cache
2008-12-13 05:41:34 +00:00
|
|
|
|
2015-02-23 18:22:09 +11:00
|
|
|
/**
|
|
|
|
* \returns true if this texture can use its #Texture.ima (even if its NULL)
|
|
|
|
*/
|
|
|
|
bool BKE_texture_is_image_user(const struct Tex *tex)
|
|
|
|
{
|
|
|
|
switch (tex->type) {
|
|
|
|
case TEX_IMAGE:
|
|
|
|
{
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
* Volume Rendering: Voxel data
This commit introduces a new texture ('Voxel Data'), used to load up saved voxel
data sets for rendering, contributed by Raúl 'farsthary' Fernández Hernández
with some additional tweaks. Thanks, Raúl!
The texture works similar to the existing point density texture, currently it
only provides intensity information, which can then be mapped (for example) to
density in a volume material. This is an early version, intended to read the
voxel format saved by Raúl's command line simulators, in future revisions
there's potential for making a more full-featured 'Blender voxel file format',
and also for supporting other formats too.
Note: Due to some subtleties in Raúl's existing released simulators, in order
to load them correctly the voxel data texture, you'll need to raise the
'resolution' value by 2. So if you baked out the simulation at resolution 50,
enter 52 for the resolution in the texture panel. This can possibly be fixed in
the simulator later on.
Right now, the way the texture is mapped is just in the space 0,0,0 <-> 1,1,1
and it can appear rotated 90 degrees incorrectly. This will be tackled, for now,
probably the easiest way to map it is with and empty, using Map Input -> Object.
Smoke test: http://www.vimeo.com/2449270
One more note, trilinear interpolation seems a bit slow at the moment, we'll
look into this.
For curiosity, while testing/debugging this, I made a script that exports a mesh
to voxel data. Here's a test of grogan (www.kajimba.com) converted to voxels,
rendered as a volume: http://www.vimeo.com/2512028
The script is available here: http://mke3.net/projects/bpython/export_object_voxeldata.py
* Another smaller thing, brought back early ray termination (was disabled
previously for debugging) and made it user configurable. It now appears as a new
value in the volume material: 'Depth Cutoff'. For some background info on what
this does, check:
http://farsthary.wordpress.com/2008/12/11/cutting-down-render-times/
* Also some disabled work-in-progess code for light cache
2008-12-13 05:41:34 +00:00
|
|
|
|
Giant commit!
A full detailed description of this will be done later... is several days
of work. Here's a summary:
Render:
- Full cleanup of render code, removing *all* globals and bad level calls
all over blender. Render module is now not called abusive anymore
- API-fied calls to rendering
- Full recode of internal render pipeline. Is now rendering tiles by
default, prepared for much smarter 'bucket' render later.
- Each thread now can render a full part
- Renders were tested with 4 threads, goes fine, apart from some lookup
tables in softshadow and AO still
- Rendering is prepared to do multiple layers and passes
- No single 32 bits trick in render code anymore, all 100% floats now.
Writing images/movies
- moved writing images to blender kernel (bye bye 'schrijfplaatje'!)
- made a new Movie handle system, also in kernel. This will enable much
easier use of movies in Blender
PreviewRender:
- Using new render API, previewrender (in buttons) now uses regular render
code to generate images.
- new datafile 'preview.blend.c' has the preview scenes in it
- previews get rendered in exact displayed size (1 pixel = 1 pixel)
3D Preview render
- new; press Pkey in 3d window, for a panel that continuously renders
(pkey is for games, i know... but we dont do that in orange now!)
- this render works nearly identical to buttons-preview render, so it stops
rendering on any event (mouse, keyboard, etc)
- on moving/scaling the panel, the render code doesn't recreate all geometry
- same for shifting/panning view
- all other operations (now) regenerate the full render database still.
- this is WIP... but big fun, especially for simple scenes!
Compositor
- Using same node system as now in use for shaders, you can composit images
- works pretty straightforward... needs much more options/tools and integration
with rendering still
- is not threaded yet, nor is so smart to only recalculate changes... will be
done soon!
- the "Render Result" node will get all layers/passes as output sockets
- The "Output" node renders to a builtin image, which you can view in the Image
window. (yes, output nodes to render-result, and to files, is on the list!)
The Bad News
- "Unified Render" is removed. It might come back in some stage, but this
system should be built from scratch. I can't really understand this code...
I expect it is not much needed, especially with advanced layer/passes
control
- Panorama render, Field render, Motion blur, is not coded yet... (I had to
recode every single feature in render, so...!)
- Lens Flare is also not back... needs total revision, might become composit
effect though (using zbuffer for visibility)
- Part render is gone! (well, thats obvious, its default now).
- The render window is only restored with limited functionality... I am going
to check first the option to render to a Image window, so Blender can become
a true single-window application. :)
For example, the 'Spare render buffer' (jkey) doesnt work.
- Render with border, now default creates a smaller image
- No zbuffers are written yet... on the todo!
- Scons files and MSVC will need work to get compiling again
OK... thats what I can quickly recall. Now go compiling!
2006-01-23 22:05:47 +00:00
|
|
|
/* ------------------------------------------------------------------------- */
|
2013-06-02 03:59:19 +00:00
|
|
|
bool BKE_texture_dependsOnTime(const struct Tex *texture)
|
2008-08-05 14:42:04 +00:00
|
|
|
{
|
2014-01-14 04:59:58 +11:00
|
|
|
if (texture->ima && BKE_image_is_animated(texture->ima)) {
|
2014-12-01 17:11:18 +01:00
|
|
|
return true;
|
2010-10-19 10:26:53 +00:00
|
|
|
}
|
2012-03-24 06:18:31 +00:00
|
|
|
else if (texture->adt) {
|
2012-07-07 22:51:57 +00:00
|
|
|
/* assume anything in adt means the texture is animated */
|
2014-12-01 17:11:18 +01:00
|
|
|
return true;
|
2008-08-05 14:42:04 +00:00
|
|
|
}
|
2012-03-24 06:18:31 +00:00
|
|
|
else if (texture->type == TEX_NOISE) {
|
2012-07-07 22:51:57 +00:00
|
|
|
/* noise always varies with time */
|
2014-12-01 17:11:18 +01:00
|
|
|
return true;
|
2011-07-10 17:04:56 +00:00
|
|
|
}
|
2014-12-01 17:11:18 +01:00
|
|
|
return false;
|
2008-08-05 14:42:04 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* ------------------------------------------------------------------------- */
|
2013-10-20 13:01:07 +00:00
|
|
|
|
2017-02-06 12:23:03 +01:00
|
|
|
void BKE_texture_get_value_ex(
|
2015-03-21 22:10:43 +11:00
|
|
|
const Scene *scene, Tex *texture,
|
2017-02-06 12:23:03 +01:00
|
|
|
float *tex_co, TexResult *texres,
|
|
|
|
struct ImagePool *pool,
|
|
|
|
bool use_color_management)
|
2013-10-20 13:01:07 +00:00
|
|
|
{
|
|
|
|
int result_type;
|
|
|
|
bool do_color_manage = false;
|
|
|
|
|
|
|
|
if (scene && use_color_management) {
|
|
|
|
do_color_manage = BKE_scene_check_color_management_enabled(scene);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* no node textures for now */
|
2017-02-06 12:23:03 +01:00
|
|
|
result_type = multitex_ext_safe(texture, tex_co, texres, pool, do_color_manage, false);
|
2013-10-20 13:01:07 +00:00
|
|
|
|
|
|
|
/* if the texture gave an RGB value, we assume it didn't give a valid
|
|
|
|
* intensity, since this is in the context of modifiers don't use perceptual color conversion.
|
|
|
|
* if the texture didn't give an RGB value, copy the intensity across
|
|
|
|
*/
|
|
|
|
if (result_type & TEX_RGB) {
|
|
|
|
texres->tin = (1.0f / 3.0f) * (texres->tr + texres->tg + texres->tb);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
copy_v3_fl(&texres->tr, texres->tin);
|
|
|
|
}
|
|
|
|
}
|
2017-02-06 12:23:03 +01:00
|
|
|
|
|
|
|
void BKE_texture_get_value(
|
|
|
|
const Scene *scene, Tex *texture,
|
|
|
|
float *tex_co, TexResult *texres, bool use_color_management)
|
|
|
|
{
|
|
|
|
BKE_texture_get_value_ex(scene, texture, tex_co, texres, NULL, use_color_management);
|
|
|
|
}
|
2017-05-30 15:40:14 +02:00
|
|
|
|
2018-02-19 14:33:48 +01:00
|
|
|
static void texture_nodes_fetch_images_for_pool(Tex *texture, bNodeTree *ntree, struct ImagePool *pool)
|
2017-05-30 15:40:14 +02:00
|
|
|
{
|
|
|
|
for (bNode *node = ntree->nodes.first; node; node = node->next) {
|
|
|
|
if (node->type == SH_NODE_TEX_IMAGE && node->id != NULL) {
|
|
|
|
Image *image = (Image *)node->id;
|
2018-02-19 14:33:48 +01:00
|
|
|
BKE_image_pool_acquire_ibuf(image, &texture->iuser, pool);
|
2017-05-30 15:40:14 +02:00
|
|
|
}
|
|
|
|
else if (node->type == NODE_GROUP && node->id != NULL) {
|
|
|
|
/* TODO(sergey): Do we need to control recursion here? */
|
|
|
|
bNodeTree *nested_tree = (bNodeTree *)node->id;
|
2018-02-19 14:33:48 +01:00
|
|
|
texture_nodes_fetch_images_for_pool(texture, nested_tree, pool);
|
2017-05-30 15:40:14 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Make sure all images used by texture are loaded into pool. */
|
|
|
|
void BKE_texture_fetch_images_for_pool(Tex *texture, struct ImagePool *pool)
|
|
|
|
{
|
|
|
|
if (texture->nodetree != NULL) {
|
2018-02-19 14:33:48 +01:00
|
|
|
texture_nodes_fetch_images_for_pool(texture, texture->nodetree, pool);
|
2017-05-30 15:40:14 +02:00
|
|
|
}
|
|
|
|
else {
|
|
|
|
if (texture->type == TEX_IMAGE) {
|
|
|
|
if (texture->ima != NULL) {
|
2018-02-19 14:33:48 +01:00
|
|
|
BKE_image_pool_acquire_ibuf(texture->ima, &texture->iuser, pool);
|
2017-05-30 15:40:14 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|