Hi,

@Cairyn said in The asymmetric matrix inversion issue:

I guess it depends on the point you want to make...

I would mostly agree, but my point point was more the other way around. Not that shearing is a thing you commonly want to do, but the fact the you should be aware that c4d.Matrix will not enforce an orthogonal basis. Because if you thought it does, you could for example think that

my_frame = c4d.Matrix(v3=my_normal)

would be a sufficient way to construct an orthogonal frame where my_normal is k and then carry out some transforms with it and wonder what the heck is going wrong.

@Cairyn said in The asymmetric matrix inversion issue:

This has, in fact, been a point I thought long and hard about...

What I meant with that passage was the story which has been attributed to many famous programmers who left a complicated piece of code only commented with "and here comes the tricky part". Usually told as a testament to both their technical genius and their communicative shortcomings. The often (at least silently) admired notion is that "everything is self explanatory for a smart person". Which of course is neither true nor very "cool". I feel you are drifting a bit into that direction.

About the linear algebra stuff. In my opinion there is no wrong or right there, you can do a good job with a very coarse and with a very fine model. Although I think often the geometrical meaning of linear algebra has been neglected in teachings about it. Especially Cinema's "matrices" (which in my book do not really qualify as matrices) can be very well explained as linear maps which will automatically will make all four principal transforms intuitively clear. Everything that is left then is to explain that matrices are just another way to write a linear map, i.e. a linear combination of vectors representing a coordinate system.

Cheers,
zipit

Hey guys,

just wanted to let you know, that I've cracked the case in the meantime.

Here are my findings:

def convert_matrix_left_to_right(m): # http://www.techart3d.com/2016/02/convert-left-handed-to-right-handed-coordinates/ # m = op.GetMg() new_m = c4d.Matrix( m.off, m.v1*-1, m.v2, m.v3) return new_m def rotate_y_axis_180(): # Construct your own matrix based on rotation of axis # https://www.mathworks.com/help/phased/ref/roty.html x = c4d.Vector(-1, 0, 0) y = c4d.Vector(0, 1, 0) z = c4d.Vector(0, 0, -1) off = c4d.Vector(0, 0, 0) return c4d.Matrix(off, x, y, z) def GetGlobalRotation(obj): m = obj.GetMg() new_m = rotate_y_axis_180() * convert_matrix_left_to_right(m) return c4d.utils.MatrixToHPB(new_m, order=c4d.ROTATIONORDER_XYZGLOBAL)

Indeed you have to convert from a left-handed (c4d) (hpb) to a right-handed (houdini) (xyz) coordinate system... plus I've found that you need to add 180° to the y axis, so I constructed a matrix in rotate_y_axis_180 that I can multiply to my converted matrix.

Hope it helps someone...

Thank you guys for your input! Have a great weekend and stay safe!

Cheers,
Lasse

Unfortunately, differently from std lib where it's possible to define and init a vector pretty easily using one-line statement( std::vector<int> a (10, 100);) this looks like being not currently possible with maxon::BaseArray() and you need to make it the usual way.

Best, R

@zipit My sincerest gratitude for your help. Not only did you get my project unblocked, but you answered my follow-up questions. I have learned a lot from you. Thank you!

@zipit Absolutely incredible work! So elegant! Thank you very much 😃

@m_adam Thank you for the reply and confirmation!

@Cairyn @zipit @m_magalhaes

Thanks for the detailed response. After installing the C++ environments, it works as expected.
Sorry new to this. As I only have python to reference for.

I also managed to build the plug-ins using this guide:
https://developers.maxon.net/forum/topic/10967/compiling-the-cinema-4d-r20-c-sdk-examples

I have replied your post at C4DCafe.

"The c4d.documents.LoadDocument returns you a BaseDocument, which you then need as argument for the InsertBaseDocument and SetActiveDocument."

@trideshnik said in How to decompile cdl64 file?:

Hmm.. so..

Comrades, before getting the necessary information, I was told 100500+ times about copyright. Everyone saw fit to indicate this.

Dear, do you think that the person asking this question needs a triple copyright notice? If you do not want to answer or help, no one is forcing you, but making idiots out of people is bad form. I got a ton of off-topic information. reasoning, warnings. and only a fraction of the information I need. so nice.
but.
Thanks to those who indicated the direction in which to dig.

P.S. it seems to me that this is such a lifestyle. okay) khkhgxghzhuxvvldqkdfnhuv

This answer is considered irrespecutful and contradicts the collaboration spirit of the forum. User banned.

Hi @Danchyg1337, thanks for reaching out to us.

The approach you've pointed out can work to activate a ToolData with a specific preset. You've to register a CommanData for every preset you'd like your ToolData to use and, if needed, you can register your ToolData passing the PLUGINFLAG_HIDEPLUGINMENU to avoid that the generic ToolData appears among the menus.

Best, Riccardo

@m_magalhaes said in Support of Scene Nodes development:

@iluxa7k said in Support of Scene Nodes development:

Several suggestions at c4d cafe forums, if will be time to read them

Do you have any link for us ?
I know that a couple of Maxon guys are already looking closely to that forum (and others)

https://www.c4dcafe.com/ipb/forums/forum/289-scene-nodes-workflows-discussion/

https://www.c4dcafe.com/ipb/forums/topic/111961-nodes-road-map/?&page=5#comments

https://www.c4dcafe.com/ipb/forums/topic/111939-maxon-announces-cinema-4d-r23-overview-discussion/?page=22&tab=comments#comment-721276

Hi @x_nerve the ID used is not the correct one you should use: 431000021 for edge mode and 431000030 for point mode, unfortunately, there are no symbols for these tools.

Cheers,
Maxime.

Hi:

After a trial run, the script was tested successfully. By setting the name suffix of Python Tag, the problem of repeated running of Tag can be solved.

Taking c4d.DIRTYFLAGS_SELECT as an example, if the point, line, and surface selections change, it will execute, otherwise it won't.

The Python script code is as follows:

import c4d #e-mail: xiuziye@qq.com def main(): Name = op.GetName() Objects = op.GetObject() Changed = Objects.GetDirty(c4d.DIRTYFLAGS_SELECT) Text = ["xit" + str(Changed)[-1]] if str(Name).count(Text[0][:-1]) != 0 : if str(Name).find(Text[0][:-1]) != str(Name).rfind(Text[0][:-1]) : if str(Name)[str(Name).rfind(Text[0][:-1]):] == Text[0] : if str(Name).find(Text[0][:-1]) <= 0: #Do not execute, exit the program. print ("Does not perform.") op.SetName(str(Text[0])) return else: #Do not execute, exit the program. op.SetName(str(Name)[:str(Name).find(Text[0][:-1])] + str(Text[0])) print ("Does not perform.") return else: if str(Name).find(Text[0][:-1]) <= 0: op.SetName(str(Text[0])) print ("Perform.") else: op.SetName(str(Name)[:str(Name).find(Text[0][:-1])] + str(Text[0])) print ("Perform.") else: if str(Name)[str(Name).rfind(Text[0][:-1]):] == Text[0] : #Do not execute, exit the program. print ("Does not perform.") return else: op.SetName(str(Name)[:str(Name).find(Text[0][:-1])] + str(Text[0])) print ("Perform.") else: print ("Perform.") op.SetName(str(Name) + str(Text[0])) print ("pass") #The next thing to execute.

Hi @bentraje as you already figured out in the documentation for R21+ this is necessary because each version (c4dpy, CommandLine, TRS, TRC) now have their own preference folder and doesn't share anymore the one from c4d.

Cheers,
Maxime.

ok tx...

It seems the old c4dtools were integrated into c4ddev
sadly c4ddev is nothing for the occasional c4d python hacker .-)

the "beginners guides" are on "todo" for years, now and probably wont get completed anymore.
it does not look like Niklas is still engaged in the c4d world.

@zipit Thanks!

Hi:

This is a bit of a hassle, but can still be scripted, who CARES about an extra polygon.

import c4d def main(): polygons = op.GetAllPolygons() points = op.GetAllPoints() point = [c4d.Vector(10000, 10000, 10000),c4d.Vector(9999, 10000,10000), c4d.Vector(9999, 10000, 10001),c4d.Vector(10000, 10000, 10001)] point_indexe = [[len(points) + i ,point[i]] for i in range(len(point))] op.ResizeObject(len(points) + len(point),len(polygons) + 1) set_point = [op.SetPoint(k[0], k[1]) for k in point_indexe] op.Message(c4d.MSG_UPDATE) c4d.EventAdd() if __name__=='__main__': main()

Hi Fernando, feel free to have the developer writing directly to our sdk support email box.

Best, R

Wow, very nice! There's a huge progress, it now works pretty fast.
Thanks for adding the wishlist items. 🙂

Grand merci pour ce Plugin tellement simple et facile d'utilisation. Grand merci...
Many thanks for this Plugin so simple and easy to use. Big thanks

The issue is fixed by the way. 😉