Ah mais t'es sur Paris ?
J'aurais pu dire coucou : )

À voir pour de futurs événements : )!

We use the same distro :>

I've been using mint for all my freelance and students years, very nice lil distro imo

Best solution

I still need to play it!!!

What happened

It will be public

I'm not the best at software structures (I'm more of a visual guy) so the plugin code base is a bit funky. So I'll not feel like giving support on it : )

It's a fantastic tool, but it has too much features and I had to hack around to make certain things

I really just need a way to set instance transforms and colors and split multimesh instances automatically for optimization

IDK, it depends on the language my subconscious speaks

Yes, I changed it a little, but in the end, I just created two default categories: artistic/technical.

That is, whether or not you know how to code, because I think that's the main difference between users for technical use cases.

The repo exists, I made it last year as a quick test, but the implementation is really naive and to optimized at all

github.com/gtibo/multim...

Anyway, having your opinions and ideas would be great

At that point I don't have a clear idea in mind
But if you're interested I can make an online document that can be edited to write down idea.

I was thinking following this process:

- Create a survey to gather real use cases
- Write a proposal / design document
- Get feedbacks

Don't worry, I totally get your point

+ you can criticize stuff, I'm not a soft lil baby :p

I wanted to make a bsky post to discuss it first and see if it was something that would be worth looking into.

But yeah, I don't want to impose my view and say "things shall be like this!"

The main function of multimesh is to declare transforms with optional color data to display meshes.

This functionality should be (imo) accessible in some way other than through code.

I 100% agree with you that I should do a survey of some sort to collect different opinions :)

That's why I'm talking about another node (that would use multimesh with the renderingserver for example) but not affect the current multimesh node.

The current "issue" with multimesh is that you have to heavily interact with it through code to use it.

This post is also a way for me to open up the debate on this topic and gauge the interest it might generate :).

So please feel free to respond if you feel concerned.

I don't know if many people are in the same situation as me, but would a simple tool like this be useful to you?

I'm posting here because I would need some help if someone is interested (mainly on plugin structure and for the octree).
I'm more of a graphic design guy that know how to code a bit 🫠