Well i mentioned it many times already... here to make it easier for you:

3DGS version:
1) Open Med
2) Select the vertex you want to manipulate
3) Write the ID down so you remember
4) per script call your vec_for_vertex or whatever using the ID

Unity version:
1) Open your Model Editor
2) Select the vertex you want to manipulate
3) Write the ID down so you remember
4) Per script call your vertices function using "mesh.vertices[ID]"

Got it? Okay?
I'm not thinking in black and white (funny that i am saying this :O) but i just dislike it if conversations are like this:
Person 1: "Feature A is easier in Engine B than C"
Person 2: "No it's not you can just call this and that the same way"
Person 1: "Anyway it is SO MUCH easier in Engine B!"

Which isn't true. It might be i tiny slightly bit easier if you consider that you first need to store the vertices array in Unity before using it

Vector3 myVertices = mesh.vertices;

But that's it and as Slin said, it has other parts that makes it "SO MUCH" easier using Unity than 3DGS.

I never ever wanna start those engine a vs engine b conversations since they are just stupid, but if i feel that someone is spreading wrong information, i can't help and convince them they are wrong

Does your model editor supply also the ID to put in the Vertices[ID]
to retrieve the vertex coords ?
May you tell me what application are you using ?

Nobody understood your explanation
You quoted my answer to Ventilator but the working solution proposed by Ventilator it is not what you said
I suppose that also Ventilator assumed that from a generic modeller you can get the local coords only
To find the ID's you must write, as he said, some lines of codes

btw I am still using version 2.6 because 3.0 has been reported to be buggy
My version does not have a built in model editor while 3.0 has
If in version 3.0 you get also the ID , fine the problem is over

Yes it does, that's what i keep saying here over and over again.

First, i don't think you can speak for "everyone" so please don't make statements like "nobody understood your explanation".

Second, because i'm such a nice guy, i've made a simple test for you in C4D and Unity. The code i used is following:



It just moves the vertex by 3 units up.

Here is the selected vertex in C4D:


Here is a shot from unity using the model and i assigned my script to it and changed vertexID to 105, the one i selected in C4D:


And voila, running the game moves exactly the same vertex!



Questions? Still something to complain? Thanks.

AlbertoT, please continue complaining.
I love those minimal tutorials of Captain_Kiyaku! Woohoow!
(While I am still working with 3DGS because of running projects, I can't wait to work with Unity. In the meantime, these tiny little explanations and tutorials are giving me the feeling that, once upon a time, I will do with Unity what I already achieved in programming with 3DGS.)

Hm, I'm thinking about the next theme... wait! You can't paint on multitextured terrain in Unity!
(Hope, you don't mind my comment, Captain! Errm, "Dichotomic"? What sort of title did you get there, and which moderator gave it to you?)

Interesting news for pupils and students:
You now can get Unity Pro, Unity iOS Pro or Unity Android for just 99$ as educational version...

I really like their pricing policy. Let's see if this will affect the 3DGS policy too...

of course you won't recognize much if you view the whole model but you can simply zoom in with the camera. it shouldn't be a big problem to find the vertices you want then. i did this a few times already.

what do the coords have to do with it? scale doesn't matter.

if the indices stay the same depends on your modeler and pipeline. i guess with some it works, with some not.



by the way, i think most mentioned examples better get done with bones and not by manipulating vertices.

I should have added that to my preview post 8D



@ Pappenheimer, hehe glad my rage test helped you learning something new.
Not sure what you mean with painting on multitextured terrains though, i somehow never use terrains (except the voxel one i generated by myself) but if you use the Unity Terrain you can just draw on it with multiple textures, is that what you mean?

Also i forgot when i've got the "Dichotomic" title, i think i've requested it once or maybe its from those times when mods were allowed to use custom titles. But i just think its a pretty word and i like it's meaning, especially considering my usual artwork.


EDIT:
haven't seen this before, you probably edited it later on:


Well i use 3 (now 3.1) since the beta came out, most of the bugs are fixed already and it's stable as hell for me, never really have any crash unless i produce them (infinite loop, etc). But i could imagine that there are still bugs making the engine crash when using terrain editor, or tree editor or whatever, but i usually don't need it, so i dont know if its stable or not.
But it is much more stable than 2.6 (at least for me! it often depends on what you are doing + your system).

There is no build in model editor in unity, why would it need that, you can use so many file formats and unity automatically exports it for you to fbx.

I was talking about your model editor of choice like Maya, C4D, 3ds, lightwave, blender, whatever. They all usually show vertex ID's (if not i would ask for my money back :P).

actually I was not complaining I simply understood from the rather syntetic Unity3d manual that you can only create and manipulate meshes at run time
I take note that C4D ( 1500 usd ) supply also the ID's which you can use to access the vertices in the Unity3d Vertices array but I have some doubt that you can do it with :

The editor of your choice

As a little bit nervous member claimed

Should the end user be bound to specific high end modelers to exploit all the Unity features , in this case I would cOmplain

C4D was just an example, i'm pretty sure you can read those infos in blender as well. You could even import your .fbx to med and use the id's, they are probably the same too.

I am not nervous at all It's just raging me if people keep complaining about problems that not exist, even when other people show them pretty much how easy it is.

It's not unity's problem if you can't find your vertices ID. It doesn't offer a modeling tool since you can use whatever you want. If 3dgs wouldn't have MED, you would have the same "problem" finding your vertex id, wouldn't you?
Unity offers you to access vertices by a given ID so that's absolutely all you would need.

Suppose you want to select a group of vertices to form a specific pattern with a reasonable accuracy
For example a "beating heart" same as you can see in some cartoons
You would agree that it is not that easy to do it zooming in / out a 10000 vertices model



This is exactly my concern
I am more confident in built in tools rather than relying on universal converter
Maybe in this case there is no any problem
However ask the Cinema 4 users how happy they are of the FBX exporter od the new R12 release




Generally speaking , I agree
But with some organic deformation ex the beating heart I dont think that bones are the best solution
uUnity does not suppot vertex animation ( Unless I am still wrong )
In some situation vertices animation it is still the way to go

Last just to avoid nervous reactions
We are talking about minor issues
In general I am convinced that Unity is as flexible as 3dgs