Mouseover green part highlighting showing up in VAB/SPH, but not in flight.

[curtquarquesso]

So, I'm making some simple parts here. One has an emissive, and one has a swinging arm animation. So far, I've gotten everything work great. The parts have colliders, they animate, and they work.

For some reason, I can't get them to highlight upon mouseover when in flight. In the VAB/SPH, it works fine, and the parts behave as expected, but once launched, they won't highlight. When you mouseover them, instead, the root part that their attached to highlights. You can right click them, and they do respond and still function.

What parameter in Unity have I overlooked? It didn't always do this. I've gotten it working just fine in the past. I don't know what I did before, or what I did this time that's got them all borked.

Any help would be greatly appreciated.

Edited July 1, 2015 by curtquarquesso

[FreeThinker]

I can't see your cursor, is this a joke?

[curtquarquesso]

I can't see your cursor, is this a joke?

Wow. That's really irritating. I didn't notice that. I'm sorry. Apparently, when I take a screenshot, the mouse hides. In all the images, the cursor is on top of the desired part. I'm not sure how to demonstrate this now. I'm referring to the two parts, NOT the capsule. Sorry. :|

[brusura]

Maybe you are missing a collider mesh

[curtquarquesso]

Maybe you are missing a collider mesh

Nope. Definitely not. If the colliders were not present, I wouldn't be able to manipulate them in the VAB. They also interact with other objects in flight as expected. I'm thinking it's a hierarchy thing.

Here's my hierarchy. Can someone tell me this looks right?

Annotated in order:

GameObject

Hinge Base

• Hinge Base Model
  
• Hinge Base Collider
  
• 
  

Boom Arm

• Boom Arm Model
  
• Boom Arm Collider
  
• 
  

The boom arm object has an animation applied to it that rotates the model, and the collider, 180º.

[gooddog15]

I haven't really learned to use emissives yet, but here's the Tantares docking lights hierarchy in Unity if it helps.

collider wise, in the inspector panel, have you tried to apply a mesh collider component (which you can access through Add Component-Physics-Mesh Collider) to your models? Using that instead of making separate childs in the heirarchy may fix the problem.

Edited July 2, 2015 by gooddog15