[Plugin] Image 2 Model
-
You set the image size as you import it, but you can reset it later after reading its pixel sizes and basing the inch sizes on those, pro-rata...
The basic code to add an image is:
image-entities.add_image(path_to_file, insertion_point, width, [height])
The width/height are in inches.
The last argument [height] is optional, if omitted it is taken as being in proportion to the width you have set.
An added image typically arrives 'flat' at the ORIGIN - if it's a plant or tree you'll probably want to stand it up on its end - you can apply a simple rotation transformation:tr=Geom::Transformation.rotation(ORIGIN,X_AXIS,90.degrees) image.transform!(tr)
You might also want to shunt the image so that the center of its bas is at the ORIGIN rather than it bounds.min ? Here a simple translation is needed:
tr=Geom::Transformation.translation([image.width/2,0,0].vector_to([0,0,0])) image.transform!(tr)
-
TIG, Great minds think alike. I originally tried moving the Image bottom center to the Model ORIGIN before making it first a Group then a Component but didn't change the point the Image rotated about when Orbiting. I had to move the Component.transformation.origin instead.
One thing that I can't seem to resolve is the fact that although I do a "viewFront:" and a "viewZoomExtents:" before doing the .save, the model, when opened, has not been saved that way.
-
@sdmitch said:
Adam, Would you post an image that I could test. I have been working on your plugin and I want see if it works the same with one of your images as it does with mine.
Gaieus has a point regarding sizing the images/components.
Here is one of my hi-res .png files for testing.
Yes, I did forget to mention a few steps. The routine is -
-
Import and place 'image' in front viewport.
-
Center on axis as pivot point
-
Explode image
-
Select all
-
Make Component (Check always face camera, shadows face sun
-
Enter component edit and select outer edges and hide them.
-
Exit component and 'Save as' image name.
Thanks for looking into it Sam and for the help TIG. If something can be manifested it would save hours of tedious work.
-
-
Adam, Your image worked exactly like mine so I have attached Image 2 Model I. When you execute the plugin, The Open panel will allow you to select the source folder for the images. Next, the Save panel will allow you to select the destination folder for the models. An inputbox will let you choose whether the image is to be "stood up" and the width for the images. Since this is a "batch" process these options will be applied to all images in the source folder.
I still haven't resolved the problem of the saved file not being frontview and zoomed extents. It seems that it saves the model however the default template is setup.
Check it out and let me know how it worked for you.
batch process images into components that are saved in a model file
-
Works great with one exception. Can you perhaps set it to save just the newly created component and not save a copy of "Susan" along with each new .skp? Perhaps that's is the issue you are already referring to. I need to be able to compile these plants through the component folder. Other than that it's working like a charm!!
Also, just noticed that the component is still an "image". Possible to explode that down before the component conversion? Not sure if the final .skp files will work with all render engines with 'images' embedded.
-
If Susan is showing up it because she is in your default template.
I take a look at exploding.
-
You could always some code at the start to erase all model entities...
Sketchup.active_model.entities.erase_entities(Sketchup.active_model.entities.to_a)
[or aSketchup.active_model.entities.clear
[edit]]
Then.purge_unused
for all model components, materials, layers and styles before adding the new image into the now sanitized model.
Surelyimage.explode
will do the desired extra step ? -
Added a .clear! to make sure the new file is empty. Exploded the image and hide the edges.
-
The 'entities.clear' only erases the instance of Susan [and any other stuff placed in the default template].
BUT the definition still remains in the SKP, as do any now-unused related materials, layers etc.
It's best to have a '.purge_unused' for these after the '.clear'... -
I haven't been able to find .purge_unused.
sorry, I did find it for materials and styles.
Searching returned no results.
-
Your search tool is faulty...
https://developers.google.com/sketchup/docs/ourdoc/definitionlist#purge_unused
https://developers.google.com/sketchup/docs/ourdoc/materials#purge_unused
https://developers.google.com/sketchup/docs/ourdoc/layers#purge_unused
https://developers.google.com/sketchup/docs/ourdoc/styles#purge_unused -
I did the search, .purge_unused, at
https://developers.google.com/sketchup/docs/
which is the Ruby API page and it found nothing. Apparently it was the "." that cause the failed search. Lots of results without it.
-
First post updated with [plugin] tag.
Got a bit busy and haven't had a chance to truly say thanks! SDMitch, I owe you a beer! Plugin works great. Thanks again!
-
@sdmitch said:
Added a .clear! to make sure the new file is empty. Exploded the image and hide the edges.
I opened the PNG image, the view does not show
-
Just wanted to say thanks for this plugin, it really is super helpful!
-
@Earthmover
can You do a quick explanation video tutorial?
thanks!!
Advertisement