Download Latest Version meshpartitioning.zip (41.6 kB)
Email in envelope

Get an email when there's a new version of Blender Mesh Object Partition

Home
Name Modified Size InfoDownloads / Week
2-24-11 2011-02-24
2-17-11 2011-02-17
1-27-11 2011-02-01
previous 1-26-11 2011-01-26
meshpartitioning.zip 2011-02-25 48.2 kB
ReadMe 2011-02-24 3.4 kB
mesh_data_build_ver6.py 2011-01-26 7.4 kB
maintestbuild_ver19_testsample.py 2011-01-25 44.2 kB
Totals: 8 Items   103.2 kB 0
Programs are designed to be run from Blender text editor. Source code is python 3.0 + . Modules are DictManager, shelveObjectDictmanager, buildListBuilder, shelveObjectBuild and shelveObjectRetrieve, buildDependicesList, childIdentifier, and PatchesFromSelectedVertices which should be loaded in the correct blender python os path. One can find the correct OS path in blender's python console using the commands: 

>>import os 
>>os.path 

From there select a desired folder list from path list and transfer files accordingly. There are two separate methods used for instancing mesh objects, one is to method used the child_mesh_create_ver2 script, and another used child_mesh_create_ver3 script.  The differences between either script are as follows:

1.  child_mesh_create_ver2 creates based upon a user selection area of a given parent mesh object, a set of child mesh patch objects approximating such selection area.  Note: while this at a minimum should cover all of a user selection area with regards to a set of child mesh objects, this may generally exceed the area of coverage of such user selection.

2.  child mesh_create_ver5 creates based upon a user selection area of a given parent mesh object, one virtual child patch mesh object approximating such selection area.  This virtual patch is semi permanent and may be later erased depending upon a users frequent use of such script, and based upon the number of virtuals that may exist on the shelve file.  

Using child_mesh_create_ver2 requires the following sequence of scripts run:  
Sequentially one need select a desired object in blender to partition, and then run the maintestbuild script first, and then sequentially run the batchparentchildindexing script, mesh_data_build_ver5.py.  In 'edit mode' after selecting a desired mesh selection area, and then toggling from 'edit mode' to 'object mode', run child_mesh_create_ver2.py . 

Using child_mesh_create_ver5 is as follows:
After selecting the desired object to partition, run the maintestbuild script.  Then in 'Edit mode' select a desired portion of such mesh object.  Toggle from 'Edit mode' to 'Object mode' and then run the script child_mesh_create_ver3.  

At the moment one can update and refresh parent child object virtuals passing to all parent virtuals on the virtual parent node path.  This basically means that one can update a child virtual mesh object and all parent virtual objects including original base object will be updated:
having selected a corresponding child virtual mesh object, modifying coordinates (including both use of subdivisions and modifying vertex coordinate data), and then running the script 'datretref.py'.  At the moment retrieve refresh data is not stored on shelve file.  Thus the any desired permanent changes should be saved in blender.

In the modules folder I have included a python script reinitaliseshelved5dat.py that allows one, if run from blender to erase data contents on the 'shelved5.dat'.  Should one desire to remove old data, etc.

Please see the sourceforge developers forum at

https://sourceforge.net/projects/blendermeshobje/forums/forum/1368289/topic/4070780

if further interested in code details of this project.


Script is currently designed around Blender 2.56 Beta, can't guarantee this works around other versions. Data is stored in a shelve data file in base directory in a file called 'shelved5.dat'. 
Source: ReadMe, updated 2011-02-24