Hello,

It s not my plugin, I only evaluated it.
Contact simlab support with your problem.

Regards

Hans-Peter

Hello,

Generally it is hard or impossible to convert a surface modell to a solid modell file.
From solid to surface only the surface is triangulated and the surface mesh is written.

The question is also what inventor fusion has build from the surface-file?
It might be still a mesh-modell.

Regards

Hans-Peter

Lets just say that the metod I showed allows you to do an ISO view in the direction you prefer...

Hm, the Sketchup function let you do this also.
Rotate fairly into the wanted view and choose ISO and it will be aligned exactly into the prefered view.

Is it not the same as menu:

Camera\Standardviews\Iso

??

Hello,

SimLab 3DPDF (now V3) is the plugin only:
http://www.simlab-soft.com/3d-plugins/3D-PDF-from-sketchup-main.aspx

SimLap Composer (now V2013) is the full product:
http://www.simlab-soft.com/3d-products/simlab-composer-compare-editions.aspx
There is a upgrade price for 2.X

Regards

Hans-Peter

Hello,

On the download page you can read: The plugin is supported on SketchUp 8 ...

So question: Is Sketchup 7 also supported/usable ?

Regards

Hans-Peter

Edit: Got an answer by mail

@unknownuser said:

Yes the plugin should work with both SKP7 and 8 (free and pro)

Best Regards,
SimLab Soft

Oops, just noticed:

	 material.alpha = 0.5

Hello,

The API doc says:

Color.alpha= is only for SketchUp 8.0 M1+

Any other way to set opacity in Sketchup 7 with ruby?

This does also not work:

color_from_rgba = Sketchup;;Color.new(material.color.red, material.color.green, material.color.blue, 128) 
material.color = color_from_rgba

This does what I want:

 model = Sketchup.active_model
 pages = model.pages
 pages.each {|page|
    pages.selected_page = page
    UI.messagebox("Scene; "+page.name)
    view = model.active_view
    new_view = view.zoom_extents
    status = page.update(33) 
    }

But I have to press OK on the messagebox when scene-update has finished.

Edit: Kernel.sleep does not work for that.

OK, things seems not so easy.
The scene tab even does first appear after a autosart ruby has run, so no way to access the scenes via shortcut.

Other idea: Scenes can store the camera loctation. So can a ruby calculate a new camera location for each scene and write the property.
This would not update the screen or change the visible scene. But next time the scene-change is used it updates to the new location.
And the new camera locations are stored for each scenes in onSave.

What Propertys does ZoomExtents set? Is there a equivalent in ruby to calculate the values in the same way?

Regards

Hans-Peter