[Plugin] GhostComp - v1.4a - 31 Oct 18

[aea]

No working GHOSTCOMP ?

---

---

[Chris Fullmer]

Perhaps you have a group selected instead of a component?

Chris

[Ruturaj]

Hi Fredo,

Thanks you very much ...................

[aea]

YES , WORKING , THANKS .

[xrok1]

a perfect companion to fur. no?

[xrok1]

is there a reason this plug hides the geometry as well as the layer? if it just hid the layer one could use wireframe ghost but still render it, but with the geometry being hidden too it doesn't work that way. any work around for this?

[Magnus123]

Hi Fredo thanks for this awesome plugin! i have a question.... first mi render motor is vray, when i turn a component into a ghost, when i render the components it just a cube a surface or anything depending of the component, theres no way to render the original component being a ghost? the case is that i dont want to render the geometry that the plugins does, only the original component....thank you very much!

[thomthom]

@magnus123 said:

Hi Fredo thanks for this awesome plugin! i have a question.... first mi render motor is vray, when i turn a component into a ghost, when i render the components it just a cube a surface or anything depending of the component, theres no way to render the original component being a ghost? the case is that i dont want to render the geometry that the plugins does, only the original component....thank you very much!

No - there is no proxy function in VfSU. Yet!

[Magnus123]

ok thom thanks for answering mate! i hope that, Yet! its very soon it would be very good! God bless you and thanks for everything!

[Starling75]

Hi, when I try to copy/paste a component + its ghost component generated in a file "1" into another file, it seems, that the relation between them is broken ...

It would be very handy to preserve the relation between original component and ghost during transportation between files.
For example wireframe ghost of a highpoly tree takes a while to generate and it isn't practical to do it every time you insert the tree into new model ..

Very nice toolset Fredo

[fredo6]

@starling75 said:

Hi, when I try to copy/paste a component + its ghost component generated in a file "1" into another file, it seems, that the relation between them is broken ...

It would be very handy to preserve the relation between original component and ghost during transportation between files.
For example wireframe ghost of a highpoly tree takes a while to generate and it isn't practical to do it every time you insert the tree into new model ..

Very nice toolset Fredo

You should keep in mind that GhostComp is a conceptual plugin. Really, what it does should be done in native by SU, and in a much more efficient way. To preserve the links between files for components is simply not possible with the Ruby API as it is today.

Fredo

[ALFRED]

Hello! I am from Russia. Warning! my english is very bad!, Thanks Fredo for a magnificent plug-in , it some kind of rescue for users of weak computers at work in 3d window, by the way, would be very abruptly if this plug-in could be used as "Vray Proxy" Сan Vray use the Ghost components during visualization?

[fredo6]

@alfred said:

Hello! I am from Russia. Warning! my english is very bad!, Thanks Fredo for a magnificent plug-in , it some kind of rescue for users of weak computers at work in 3d window, by the way, would be very abruptly if this plug-in could be used as "Vray Proxy" Сan Vray use the Ghost components during visualization?

Pavel,

I don't know VRay, but I doubt the concept of proxy for Vray matches Ghostcomp.
Actually, Ghostcomp is really conceptual. This is a good example of what Sketchup should do natively, in much better and simple way, including being able to connect the concept to rendering software.

Fredo

[thomthom]

@alfred said:

Сan Vray use the Ghost components during visualization?

V-Ray for SketchUp cannot currently use proxies.

[yolibs]

to make a render is it necessary to turn components to their real version???
or they can be in ghost version?
pls i need help!!

[Gaieus]

Yes, unfortunately.

[rv1974]

This tool is essential for those who send files with repetitive components to 3ds max.
Unfortunatly only after removing this tool I solved the "grey out menus" problem. Is there any chance to update it?

[thomthom]

@rv1974 said:

This tool is essential for those who send files with repetitive components to 3ds max.
Unfortunatly only after removing this tool I solved the "grey out menus" problem. Is there any chance to update it?

Have you updated your FredoLib files? I think most the issues lied within that library, not in the individual plugins. (with an odd exception)

[rv1974]

@thomthom said:

@rv1974 said:

This tool is essential for those who send files with repetitive components to 3ds max.
Unfortunatly only after removing this tool I solved the "grey out menus" problem. Is there any chance to update it?

Have you updated your FredoLib files? I think most the issues lied within that library, not in the individual plugins. (with an odd exception)

Yes I used latest lib pack (not 100% sure). Today I'll try it once more

[TIG]

Fredo

I've found a glitch with the code in 'GhostCompAlgo.rb'

def onActivePathChanged(*args)
	path = Sketchup.active_model.active_path
	return unless path
	comp = path.last
    return unless comp.valid? ###<<<
	return unless is_ghost?(comp)
	ask_confirmation comp
end

If you don't include the extra line I've indicated with ###<<< then you get weird errors in the Ruby Console if you have been editing and then deleting Components... This simple fix ignores recently deleted components etc so no errors...