Today I installed Google Sketchup in my Ubuntu Linux 6.06 (thanks WINE)!
Works fine, (with exception of the menu) but the only export options is Google Earth and Google Sketchup(KMZ).
But, since Google released the format of KMZ files (using a bad Collada file) the JMS script don’t work anymore.
These 2 constants are needed to give a visual thickness in Blender .
I exported a cube of 1x1x1 meter from sketchup and found with a very simple equation how the x, y and z should be multiplied to get a cube of 1.0 x 1.0 x 1.0 in blender .
Can you see the difference? If some “geometry”(i.e. faces) is in file, then the importation is ok, else (a pure 2D file) the importer doesn’t work.
The problem is in the code below:
if POLYGON_NUMBER==0 :
And an automatic “remove double” will be fine too.
Anyway, my dream is becaming true import DWG in Blender
Do you really believe that I import nt or posix just for the separator ?
Recall : the module Blender.sys (which is just a double and, in fact, re-level to nt and posix modules ) makes the scripts unusable on PowerPC G3/G4 and MorphOS . This is already in the bug tracker . It seems that this part of the current guidelines aims to prevent the use of the bundle scripts on non-conventional OS .
Guillaume “Yomgui” Roguez, maintainer of the blender portage on Morphos, already asked me to do not use this Blender.sys and directly work with the python’s official os and os.path modules .
MorphOS - is unsupported, the maintainer needs to address this bug.
Guillaume “Yomgui” Roguez needs to fix this, sure this importer may work, but a whole lot more in blender will not.
of course removing me.update() cant be done thaughtlessly, best way to do it is to have a dummy mesh for filling that you reuse, that way editmode enter/exit is fast. and you only have to update the NMesh once.
You miss the point about secure data-
It dosent realy even apply to an importer because an importer dosent modify existing data.
Data safty is only an issue for scripts that are improperly use the api - Leaving the users mesh modified withoput finishing or distroying teh data,
scripts that correctly use Mesh are just as safe as NMesh.
It dosent realy even apply to an importer because an importer dosent modify existing data.
Should not but it could .
Data safty is only an issue for scripts that are improperly use the api -
Chances to improperly modifiy data are tragicaly higest, without any rescue, with Mesh . Thing that you absoloutely do not want to understand .
Leaving the users mesh modified withoput finishing or distroying teh data,
scripts that correctly use Mesh are just as safe as NMesh.
In french : “des salades !”
In fact, your project is to do not let the choice to the user : use Mesh or nothing . But this means that users will loose their time to make a data copy when NMesh did it automatically . In fact, as I already said in an other thread, NMesh works as Blender works internaly, making a copy for editing and Mesh doesn’t .