@ Atom - no need for a new software, the script is rather long (more than 2000 rows) so many of its re-usable parts are in modules. THis way it runs faster + I plan to produce some other scripts that use the same procs from the same modules. Sooo… only copy the modules into you Python scripts directory.
@ stvndysn - script is still NOT perfect… have you read about its Limitations?? I’d be interested on what mesh the error occurs… Please share
Well… the car is nice but it consists of 7-8 independent meshes which are more or less bent 2D-meshes + lack of connections between the parts. This causes the problem… So far script cannot work correctly with this type of meshes. It would be a matter of further development. I will have in mind the case you showed, thanks!
The BODY of the car (where the problem mentioned appears) has overlapping edges and free edges. My idea is, “normally”, to clear such edges/faces before the real script processing but so far the meshes are processed “AS IS”… I’ve mentioned that in the other thread, where more details about the script are given.
Here’s one of the problems in the MUSTANG:
1980,1981 and 1982 cannot be connected correctly cause script detects them as lying on 1 geometric prime line. There are connections (1980,1981) and (1981,1982) and it is OK, but there is a connection (1980,1982) which means (1980,1981,1982) is a zero-face as the triangle has area = 0… => problem in processing…
would it be possible to have only one script
would be faster to handle in one folder
i know you said it’s big but many times i prefer to copy the script in one local folder and run it from there
Here’s a version of the script that does not require modules and does not throws output unless in case of some error or for short info displayed at the console… I was able to clean the code of procs no longer used but it still needs cleaning to get completely taken out from development/tesing mode. And I was wrong about the speed - its the same when in one .py file, just harder to develop it further which will be required
In fact, my idea is, when script ready & working w/o problems with flat co-planar faces and collinear edges, to modify it in such a way that it processes meshes for which it would be possible to smooth some surfaces like apple cover, human cheek, car roof… I dont know if it is achievable but… I thinking on HOW-TO do it.
appreciate your efforts
and certain other peoples will too!
hope to see the next version in near futur
i’ll keep an neye on it!
and hope it makes it in blender modfier for 2.5
by the way i did a test on a sibdivided cube
and i got a strange sound coming out of my PC
any idea what it is?
but otherwise seems to work fine - it is removing extra vertices!
another one would be if you can
put the messages on the console directly inside the GUI
so you can see the different phases
but that would be nice only it’s not a major thing
That’s why we’re making this script but be aware that it isn’t fully optimised yet and it still has some limitations with some types of mesh topology so timings are not garanteed to be practical.
@ Dazzle - links here are results of the other thread…
@ Ricky - I dont know how much time it will take - depends on how many resulting faces (body faces) will be there. Non-planar faces DO count in this version. One issue of significant optimisation will be to keep non-planar faces untouched even without the need to re-draw them. Sooo if you have 700,000 non-planar faces out of your 800,000 - time will be LOOOONGER… Second issue that has strong influence on processing time is how many flat resulting faces will be there. If you have 10 resulting faces with contour of 1000 verts will be faster than 1000 faces with 10 verts