Abandon IVAs in favor of an Internal mesh on all .mu with crew capacity

[ialdabaoth]

Merging the IVAs into the model MU will provide several simultaneous advantages:

- it will allow modellers to more easily check the position of windows, etc. when building their IVA meshes

- it will solve rendering / lighting / shadowing "quirks" that happen in-game, since everything will be using the same transforms

- it will make mod distribution simpler, since a single file now handles all IVA and EVA meshes

[NoMrBond]

Sounds reasonable, simply have the IVA as a child mesh of the current 'externally visible' mesh which can be revealed when needed, i.e. when seen through viewports/windows (has a defining config flag internalVisible = 1) or when switching to IVA mode

If you don't want it always visible then you can flag it to No, and have opaque/no windows

[sumghai]

Thirded.

That being said, I still think that Props should be retained.

EDIT: Perhaps MODEL{} nodes could also be used to directly append .mu files of internal models to the base parts, to allow asset reuse?

Edited June 9, 2014 by sumghai

[Javster]

Great idea. Finally we can see Kerbals through windows!!

[Random Tank]

This'd be cool for interiors on stations; you could actually have Kerbals walking (flying?) around them! +1

[Superfluous J]

You don't want me to have ANY framerate, do you?

[Random Tank]

You don't want me to have ANY framerate, do you?

No, I'm taking yours and adding it to mine. Also, as you now won't need your copy of KSP, can I have it? Pwease?

[Kasuha]

I'm expecting horde of clipping/z-buffer errors if we get IVAs implemented this way and I'm not sure if we'll get anything better than opportunity to see inside through windows in return.

Of course I have nothing against help for mod creators, modelling EVA and IVA together would certainly make some things easier. But for the game itself I don't think it is important to keep them together.

[ialdabaoth]

That shouldn't really happen; just because a mesh is present doesn't mean it has to be rendered in a given frame (witness: the collider meshes)

All combining them into one .mu does is make it easier to put them into the same transform; the logic of whether to render IVA meshes can stay identical to present.