Collider Mesh Appears In-Game

[2001kraft]

Hello!
I am currently in the process of refurbishing my dome. I created a brand-new model, along with a custom collider mesh made out of triangular prisms.

Here are the screenshots from Unity, where everything appears to be fine:

However, in-game the dome looks like this (the size is correct, it's supposed to be 10m in diameter):

^ Proof that it's the collision mesh that's messing things up for me, and not the actual texture(s) that I'm using.

I am really confused as to what I should do at this point. I tried everything, including moving the colliders up and down the hierarchy, applying the mesh renderer and applying an empty texture to it, and a bunch of other things, only to end up with the same result. What should I do? Am I doing something wrong?

 

Edited February 12, 2017 by 2001kraft
grammar, spelling, etc.

[InsaneDruid]

Some questions:

first: why so many individual colliders? This could be done with one, half-spheric icosphere mesh as the collider, coulnt it? You cant walk into it anyway, or can you? Is the "empty" underside (from the physics engine point of view) really neccessary?

Then, what is group_0 and instance_0? From the image of the unity Assets explorer it looks like they have mesh data, too? Or not?

I would look for the problem in this area.

First, I would delete the colliders and export it without them, check ingame. I bet the problem still occurs. Then delete the group_0, check, delete instance_0 and check ingame again. This way you can really identify the problematic mesh.

You could export this dome as a unity package then we all could have a look.

Edited February 12, 2017 by InsaneDruid

[2001kraft]

11 hours ago, InsaneDruid said:

first: why so many individual colliders? This could be done with one, half-spheric icosphere mesh as the collider, coulnt it? You cant walk into it anyway, or can you? Is the "empty" underside (from the physics engine point of view) really neccessary?

Yes; due to the fact that you need to be able to put things inside of the dome. This big dome exists mainly as a base object for all the other dome sizes, along with the fact that you can easily use it in collaboration with the other glass panes to create an entrance into the dome, and use it as a base then.

11 hours ago, InsaneDruid said:

Then, what is group_0 and instance_0? From the image of the unity Assets explorer it looks like they have mesh data, too? Or not?

Group 0 is to just group them all together. Same with Instance 0. It's just a grouping object. Although what you're saying is true, I'm starting to wonder if their presence is necessary at all. They don't have any mesh data of their own.

<UPDATE>

I removed both Objects. The problem still persists in-game (no screenshot necessary, as it all just stayed the same).

I also tried moving the collider triangular prism into the corresponding prism group in the Actual Mesh; nothing changed.

</UPDATE>

11 hours ago, InsaneDruid said:

First, I would delete the colliders and export it without them, check ingame. I bet the problem still occurs. Then delete the group_0, check, delete instance_0 and check ingame again. This way you can really identify the problematic mesh.

The problem does not occur without the colliders, it's their mesh that appears in the first place (if you mean the actual mesh, that is). The problem occurs without the Mesh Collider component also.

11 hours ago, InsaneDruid said:

You could export this dome as a unity package then we all could have a look.

Here's the unity package:

https://www.dropbox.com/s/ss7aer2vrq8zd41/nDome.zip?dl=0

Edited February 12, 2017 by 2001kraft

[2001kraft]

Okay, problem solved.

The issue was with my export location; I didn't see the new file where I removed the mesh renderer.

Thank you for your help regardless!

[Enceos]

@2001kraft I believe you can merge all your colliders into one, but don't tick the convex box under the Mesh Collider component. Same with your windows, the less individual objects your part has in its hierarchy the more performance friendly it is. Colliders affect CPU, objects affect GPU.

Edited February 13, 2017 by Enceos

[flywlyx]

On 2/13/2017 at 8:00 AM, Enceos said:

@2001kraft I believe you can merge all your colliders into one, but don't tick the convex box under the Mesh Collider component. Same with your windows, the less individual objects your part has in its hierarchy the more performance friendly it is. Colliders affect CPU, objects affect GPU.

It seems KSP tick convex itself now, a Unity 5 feature per somebody's word.

If there is a way to get around it ,please let me know

[Enceos]

@flywlyx You're probably right, I forgot I heard that somewhere before.