(SOLVED) Flickering model textures glitch

[deepstrasz]

So, I am trying to create this

Spoiler

out of this

Spoiler

While the cluster one looks good in Magos' and Retera's, ingame and in the editor it's like in the attached video or even worse.

 

[GhostWolf]

It would be a lot better to use one bone and only duplicate the vertices.

Either way, can you try to split it to two geosets?

 

[deepstrasz]

It would be a lot better to use one bone and only duplicate the vertices.

Either way, can you try to split it to two geosets?

I tried leaving only one bone and the same visual glitch happens.
Tried copying only one time, the same thing :\

 

[GhostWolf]

One bone to keep the model optimized, nothing to do with the issue at hand.

Can you upload a model that is only copied one time, to be sure it's not hitting the (unknown?) maximum vertices per geoset.

Tried switching all sorts of things around, this is a weird issue indeed.

 

[deepstrasz]

Can you upload a model that is only copied one time, to be sure it's not hitting the (unknown?) maximum vertices per geoset.

Well, not that the original model is the one named cobblestones01 CM.mdx.
So basically what I did now, is to copy it one time (attachment).
I'm using Retera's Model Editor by the way. I've never encountered this issue before.

 

[GhostWolf]

It looks to me like it's related to the optimization thing with bones being invisible when they reference a geoset animation that says they should be invisible.

If the geoset attached to that bone is rendered, it gives a similar behavior, of it flickering around the screen sometimes, rendering at the center of the map sometimes, or even being attached to some random other node in the map, like another unit.

But why in this case? What are we missing?

 

[deepstrasz]

I get the same result even if I crop the original rock cluster to one stone.
Don't know why I thought this would change anything.
Funny is that not only does it flicker now but also moves around like a sort of orb effect on an attachment point.

---

Cluster model edit's info. Not sure if it helps with anything:

Spoiler

Calculating extents doesn't help with anything. Why would it...

There's a lot of stuff in the Geoset Manager, lists for Vertices, Faces...

---

Bizarre... the texture glitch appears ingame even if taken off via the Material Manager. Even after setting the Material to none in the Geoset Manager...

 

[GhostWolf]

@General Frank do you see a reason for oddness?

 

[General Frank]

I'll try to look into this tomorrow.

 

[deepstrasz]

I'll try to look into this tomorrow.

Hey Frank, any luck on this matter?

 

[General Frank]

Try this.

 

[deepstrasz]

Try this.

Sadly, the same thing upon copy pasting it:

Spoiler

 

[General Frank]

Can I see that model then?

 

[deepstrasz]

Can I see that model then?

Sure. Sorry I didn't think to upload it.

 

[General Frank]

I don't understand why you use additional geosets for the new parts instead of having the mesh being copied inside the same geoset.

 

[deepstrasz]

I don't understand why you use additional geosets for the new parts instead of having the mesh being copied inside the same geoset.

You mean, to extend those purple squares and just copy the vertices?

I always get a new bone:

Spoiler

That is basically copying like before when I started the thread and it's the same issue.

 

[General Frank]

Oh. Why do you need a new bone AND a new geoset then?
It this how Retera's thing works?

Try this though.

 

[deepstrasz]

Oh. Why do you need a new bone AND a new geoset then?
It this how Retera's thing works?

Yeah, I guess. I don't even tick the bones on and the copying creates one.

Spoiler

Great, how did you do it? I want to make it look more natural like a road, put things tightly together, rotate etc.

Aha, so all within one collision box with a bone in the middle.

 

[General Frank]

Yeah, I guess. I don't even tick the bones on and the copying creates one.

Spoiler

View attachment 361550

Great, how did you do it? I want to make it look more natural like a road, put things tightly together, rotate etc.

Aha, so all within one collision box with a bone in the middle.

Well, you need to ALL geometry in one geoset and attached to one bone.
Try it.

 

[deepstrasz]

Well, you need to ALL geometry in one geoset and attached to one bone.
Try it.

Should I attach the vertices to one bone and set the bone as a parent to the collision box? Or how does it work?

 

[General Frank]

You don't need a collision box at all.
I just added it for completion.

You should attach all vertices in the geoset to the same bone.
There shall only be one geoset and bone.

 

[deepstrasz]

You should attach all vertices in the geoset to the same bone.
There shall only be one geoset and bone.

If only Retera's would let me/want to save the model...

 

[General Frank]

If only Retera's would let me/want to save the model...

Maybe because I don't use Retera's I don't get the bugs?

 

[deepstrasz]

Maybe because I don't use Retera's I don't get the bugs?

I did a test now not selecting all vertices to be linked to that one bone but every copied part separately. Did this test with fewer copies. It worked.
Gonna do this with more and come back.

EDIT:

Spoiler

Thanks Frank!

 

[GhostWolf]

So what was actually the issue?

 

[General Frank]

I have a feeling that this might have been it:

I set GeosetId to 'Multiple', but it seems Retera's gives it a number.

 

[deepstrasz]

@Retera any ideas why such a thing might have happened?
Was the original model broken from your point of view?

 

[GhostWolf]

My first test was to set all of the bones to be "multiple" or the actual geoset, neither of which helped. I still don't understand what was even the issue lol.

 

[deepstrasz]

My first test was to set all of the bones to be "multiple" or the actual geoset, neither of which helped. I still don't understand what was even the issue lol.

I guess, it was spamming the bones and after one bone without proper linking of the vertices to it. As I wrote, I had to set attach each copy of the rock clusters separately to that one bone. Before I just selected all copies and attached them to the bone but then Retera's didn't want to save the model anymore, it kept doing nothing as if I had to wait indefinitely.
Before all of this, I was just copying the rock cluster and each time it made a new bone with it, possibly hence the visual glitch?
I'm not sure what exactly Frank did, but I used his edited version to make the copies afterwards.

 

[General Frank]

I imported the geoset into Milkshape, copied it eight times, put all geometry in one geoset and exported that geoset.
I used the exported geoset and merged it with your original model.