IVA issue

[raidernick]

So I am attempting to make an IVA for my skylab using nli2work's tutorial video. This is a complete nightmare for me as it is not working at all. The iva is loading detached from the station, half inside the ground at an angle. I can move the station and the iva stays stuck in the ground where it loaded. The kerbals are sitting all over the place inside the station, on the walls and ceiling, not where I placed the transforms. This happens no matter what I do, I can make a simple cube in blender, import it to unity, place a transform for 1 kerbal and put it into the game and it will do the same exact damn thing, load inside the ground detached from the part.

[SpannerMonkey(smce)]

Hi just a quick thought and the usual cause of the internal external problem, is your exterior on the internal space layer(20).

I don't know how you have you're hierarchy set up but make sure that the exporter object has no scale applied, doesn't really matter about the children

[raidernick]

I know about the scale issues. The part tools are on a blank game object set at scale 1. For the sake of testing I have nothing on any layers.

[SpannerMonkey(smce)]

To work correctly the IVA has to be on layer 20 Internal Space, don't know of any way to have and iva work without being on this layer. The only other issue that can cause similar behavior is occasionally if you have an rpm transparent pod in the vicinity of a pod that doesn't, the non rpm pod may show it's internals.

Edited November 1, 2014 by SpannerMonkey(smce)

[CaptainKipard]

in the vicinity of a pod that doesn't the non rpm pod may show it's internals.

In the vicinity of a pod that doesn't the rpm pod may show?

That doesn't the rpm pod may show?

What? lol.

Are you trying to be the next has anyone really been far even as decided?

[nli2work]

looks like the internal is not on Internalspace or Kerbals layer. if not set to any layers the internal will spawn at the center of launch pad, I made that mistake more than my fingers and toes can count.

[Orionkermin]

It can also be on layer 16 (kerbal) the difference being that things in layer 16 show up in the face cam in the corner and things on layer 20 will not. Both show up in IVA view.

Edit: Beat to the punch...

[SpannerMonkey(smce)]

Are you trying to be the next has anyone really been far even as decided?

and that also makes loads of sense I suppose.

sorry we can't all be as perfect as you!

Try being helpful, instead of negative sarcastic or generally unpleasant, it wont hurt you know.

[CaptainKipard]

Alright. I can spell it out without the jokes.

I do not understand that sentence.

Please rephrase it.

Edited November 1, 2014 by Cpt. Kipard

[nli2work]

Spanner's right re. TransparentPod module as well, I didn't mention it since it didn't look like your IVA was using it. Pods without JSITransparentPod will have their IVA displaced outside when in the vicinity of a Pod with JSITransparentPod. JSI includes MM patch that applies JSINonTransparentPod module too Pods that do not have TransparentPod to prevent this from happening accidentally.

this is all because of the strange way Squad decided to orient the Internals relative to the Externals.

[raidernick]

Thanks nli I will try that now. I'm assuming all child objects must be on the layer as well not just the parent gameobject?

EDIT: Tried putting them both on layer 16 or 20, no difference. It still spawns outside the station inside the ground. I do not have JSI installed.

Edited November 1, 2014 by raidernick

[nli2work]

you have to name the layers too. "Internal Space" - 20; and "Kerbals" - 16

all IVA objects must be on one of those layers, not just the parent. easiest thing is select the top level object (one with parttools script), change the layer, and click add child objects in the window that pops up.

Edited November 1, 2014 by nli2work

[raidernick]

you have to name the layers too. "Internal Space" - 20; and "Kerbals" - 16

all IVA objects must be on one of those layers, not just the parent. easiest thing is select the top level object (one with parttools script), change the layer, and click add child objects in the window that pops up.

That is exactly what I did and no luck.

[philotical]

Alright. I can spell it out without the jokes.

I do not understand that sentence.

Please rephrase it.

he ment, that JSI transparent pod and similar addons have a side effect if not used correctly (as I do usually I'm afraid)

the side effect is, that if you have two ships loaded, one with JSI and one without, the ship without JSI installed will unwantedly display it's internal model outside of the ship.

looks like the pic in OP.

JSI causes this on those instances and it needs some additional code in the JSI-ship's plugin to prevent it..

The sentence was complicated due to the contents nature - and if you are not familiar with the problem, you'll have ofcourse no clue what he talks about..

but for me it was clear the first time.. - I faced the issue allready my selfe..

I hope that helped to clear the simple missunderstanding..

Edit: it seems that info was obsolete before I posted it lol

oh well.. - it's that kind of day..

[nli2work]

That is exactly what I did and no luck.

the internal gets left behind when the ship starts to move correct? if internal is attached to the vessel, then it's a matter of figuring out the correct orientation in Unity, that could take a little trial and error.

if internal is left behind after you've added the layers and set the objects to the correct layers then I don't know. are you able to spawn the internal through part tools panel? do the external and internal line up correctly when you have their top level parent objects at 0,0,0; 0,0,0; 1,1,1?

if you've checked all those and they fit correctly then I can't really say. I'll have to look at the unity project.

[raidernick]

the internal gets left behind when the ship starts to move correct? if internal is attached to the vessel, then it's a matter of figuring out the correct orientation in Unity, that could take a little trial and error.

if internal is left behind after you've added the layers and set the objects to the correct layers then I don't know. are you able to spawn the internal through part tools panel? do the external and internal line up correctly when you have their top level parent objects at 0,0,0; 0,0,0; 1,1,1?

if you've checked all those and they fit correctly then I can't really say. I'll have to look at the unity project.

Yes it gets left behind when the ship moves. The layers are added, I can spawn it and they line up correctly(though this doesn't REALLY matter as long as it is attached I can rotate it easily to properly line up, but I can't even get it to be attached). Infact, I am using the km special parts internal DIRECTLY from the existing unity project dtobi gave me. I can export it directly as he had it set up and it doesn't work. If I make any changes to it it also doesn't work. I can't explain it.

I'm uploading the unity project for you to look at, I saved it without the layers applied to the internal, but trust me I did try it with the parent and all child objects applied with the layers and it still didn't work.

Edited November 1, 2014 by raidernick

[CaptainKipard]

I hope that helped to clear the simple missunderstanding..

Edit: it seems that info was obsolete before I posted it lol

oh well.. - it's that kind of day..

Yes thanks. Don't worry. Redundancy beats bad punctuation, especially on text media where you don't hear the intonation.

[nli2work]

taking a look. it's probably something simple we over looked. which version are the blender files from? 2.72?... okay looks like things are importing okay.

Edited November 1, 2014 by nli2work

[raidernick]

taking a look. it's probably something simple we over looked. which version are the blender files from? 2.72?

yes it is from 2.72

[nli2work]

your layers and settings all look in order, I didn't change anything at all. exported skylab and IVA, everything works fine. gonna send you the exported part and configs. nothing I can see on Unity side that would cause the behavior you have. maybe something with the configs? I have no idea. Maybe problem with Unity version? I exported with 4.2.2

Edited November 1, 2014 by nli2work

[raidernick]

I am using unity 4.5.2. If I take the exact project you just sent me and export it without making any changes it doesn't work. The config is the same as the original config that worked, I have not changed it. It's some magical problem that I can't explain why it's happening.

[nli2work]

I'm as stumped as you are... it's a long shot but send me the ksp parts w/ configs (original and new). maybe something in the logs.

so far the only difference between our two setups is unity version, and I'm pretty sure you are no the only one using 4.5.2 to make IVAs.

[raidernick]

sent it with some more info.

[nli2work]

I don't know... everything works okay when I export them here. no error in the logs either.

[raidernick]

I guess I just can't do iva's then. I'll stick to just external parts.

Edited November 3, 2014 by raidernick