Homographic transformation

Still pretty much a work in progress, the attached addresses some of the Rhino 6 issues. The problem stemmed primarily from the new Point4d format RhinoCommon uses for Rhino 6.

As it stands, the plugin will not process polycurves. Everything needs to be exploded down to individual curve elements.

All morphed curves are placed on the current layer. Intended game plan would be to maintain original curves layer in subsequent betas.

The Command progresses in the same steps as shown here in the AutoCAD version.
Proj2D Initial

Proj2D extended

The Plugin is only Windows compatible.

The downloaded Zip file will most probably need to be ‘Unblocked’ prior to use with a Windows OS

Projective2d.zip (18.2 KB)

TesterVer6.3dm (41.2 KB)

1 Like

Good afternoon Seant,
wow! your work is really good: congratulations.
The plugin works perfectly in Rhino (thanks!). The only thing is that the starting shape is always (by default) an ortogonal rectangle… and I need sometimes to start with a trapezoid. The rest… is perfect.
Your plugin for AutoCad is very interesting too (STSC_Projective2d). I am fighting to install it in my computer (I don´t know why AutoCad doesn´t show me the add). I will try to use to create military perspectives (in spain we call military view to the axonometric perspective but with the XY plane in real dimension (well, scaled of course)): https://es.wikipedia.org/wiki/Perspectiva_militar
Kind regards and thank you again :))

True. I did not include much user friendliness. The routine does require at least one Orthographic reference frame - which will always be the first framework selected.
The mapping, however, can go both “from Ortho” or “to Ortho”.

Mapping between two non-orthographic references frame would be a two step process, requiring an intermediate Ortho reference frame.

That format probably will not change in the near future.

The Autodesk train has chugged on without me. AutoCAD 2016 is my latest release - hence the Exchange Add-in’s compatibility is similarly limited. I have no way to debug beyond that.

I have been lead to believe that the routine will work in later versions, but the user has to be comfortable installing the DLL themselves.

1 Like

That is a great plugin.
I would like to use it in my research; how do you suggest citing it?
Thanks in advance

Hello N Mohareb. Could you elaborate on your question, “how do you suggest citing it . . .” ?

Is that a question on how to register it with Rhino?

1 Like

N Mohareb was probably asking for the information about the plugin to use when listing it in an academic paper as one of the tools used.

1 Like

Alright. Not a question I had given any thought.

Perhaps: Public Domain Software, written ‘hunt and peck’ style by amateur (but enthusiastic) programmer, Sean Tessier

Not a citation to ‘Wow’ the readers, but the basic truth.

Thanks SEANT, and thanks David as that is precisely what I asked about. I have academic research to do, and I will use the SEANT plugin, so I would like to give credit to SEANT and include the work as a reference. So that’s what I’ve asked: how should it be cited as a reference?
Best regards