Modeling Help

[FictionXVI]

Okay I don't know if this is the right place for this but I am having some issues with my model. So basically what's happening is I'm making a model in blender than moving it from blender to Unity. That all works out fine everything looks right.

But when I actually put it into the game it ends up shrinking in height like this

You see how its like half the height it was in unity? I have no idea why it's happening as (if you couldn't tell by the model and it's texture) I'm new to all this and just starting out.... soooo ideas?

[nli2work]

reset all your scales in blender and unity before export to KSP

[FictionXVI]

Okay this might sound dumb but by reset my scales do you mean set all the scales back to one?

[nli2work]

yes. reset to 1, or 100%. also post your config file and inspector panel for the part so there's more info for people who can help.

[Quiznos323]

I'm having some modeling issues too..

I see you got your part into the game, awesome! I'm having a lot of trouble with that... I made a post over on the Reddit to try and sort out the issue, and people offered some help, but I'm still stuck. Would you mind helping me out since you have successfully gotten a part to load? I really would like to get into modding and make a parts pack but this is a huge hangup! Here's the Reddit post: http://en-us.reddit.com/r/KerbalSpaceProgram/comments/2eve9t/having_trouble_loading_my_custom_part_into_ksp/

It has a dropbox link with all of the files I used to make the part. Thanks!

[nli2work]

try setting your import Rig to "None"

[Quiznos323]

Like this?

Edited August 29, 2014 by Quiznos323

[nli2work]

yes. Originally it appears you have the Animator component applied. KSP does not recognize Animator and that may be preventing the part from loading.

you can also get rid of the "node_collider"; simply add Box Collider to the "Die" object; you should see green cube outline. and you'd be good for collision stuff. Gamedie is the holder object for the object "Die" correct? it has no components on it besides "Transform". just reset it's transform to 0,0,0 XYZ, 0,0,0 Rotation; and 1,1,1 Scale. apply parttools to it. no need for the game object above it.

Heirarchy looks like this

Gamedie // top level; remove space or use underscore for spaces; Transform and PartTool components.

• Die //mesh object with Mesh Filter; Mesh Renderer; and Box collider components
  

Edited August 29, 2014 by nli2work

[Quiznos323]

Ok gotcha. Alright so I set it up how you explained above, without the GameObject, like so:

The only thing that I did different was that I set the collider to be my mesh named node_collider. I think this works...although Unity somehow increased the scale of it by a little so that it touches the faces of the die. Is there a way to scale just the collider down?

After rewriting this and putting it in my GameData folder it still won't load, so idk what the heck is goin on XD

Edit: I also don't see my mod folder being loaded in the progress bar on start-up, do you know why this may be?

Edited August 29, 2014 by Quiznos323

[nli2work]

change part.CFG to part.cfg

your assets are working fine. KSP wasn't loading the config file because of capitalization

[Quiznos323]

Oh..so you got it to load into the game with that change?

Also silly question: Do you know how I can change the window settings to see the extension on all files? Looks like I can't see the ".cfg" on the end of "part" lol

Edit: nvm, got it to show!

Edited August 29, 2014 by Quiznos323

[nli2work]

Control Panel

• Folder Options
  
  • View Tab
    
    • Hide extentions for known file types //uncheck this box
      

[Quiznos323]

Ok, awesome. So it appears that my part is now doing something in the progress bar, however, whenever I try to stick my folder in GameData the bar stops loading about 3/4 of the way through and doesn't load any of the game parts at all....but at least it's doing something now lol

It stops on: Squad/Spaces/PodCockpit/Internal/PodCockpit

Edited August 29, 2014 by Quiznos323

[SpannerMonkey(smce)]

Hi not replied to you before as it all seemed in hand and i kept getting ninja'd anyhow, it loads fine from me in 64bit with just the CFG changed to cfg.

when the game hangs on loading at a specific point press ALT F2 and a little window will appear and it's very likely the problem will be stated there, as it loads for me I suspect you may have an issue with something not related to the die.

And just so you know what to expect when it does load., If it was me I'd make them kas grabbable and see if you could hack into the bounce module from the world cup dlc, then the kerbs could play dice for a ride home, lowest score rides on the ladder:)

[nli2work]

Ok, awesome. So it appears that my part is now doing something in the progress bar, however, whenever I try to stick my folder in GameData the bar stops loading about 3/4 of the way through and doesn't load any of the game parts at all....but at least it's doing something now lol

It stops on: Squad/Spaces/PodCockpit/Internal/PodCockpit

need to look at the Output_log.txt for this one. check KSP_Data folder for Output_log.txt... search it for PodCockpit and step through till you see some error messages. usually a missing texture will stop a model from loading and stop the startup loading process.

[Quiznos323]

Ok I did what you both suggested and looked at the log and the Alt+F2 Debug Console as it loaded, and this is what they gave me:

Edit: Found this too

I'm not sure what this means haha.

And that is a great idea SpannerMonkey, I will definitely try to do that once I get it loaded in

Thanks for being patient and helpful btw!

Edited August 30, 2014 by Quiznos323

[SpannerMonkey(smce)]

Hiya, that unfortunately doesn't tell us much, however go to KSP data folder and check the output data log.txt for a comprehensive list of what is actually happening as the game loads. It's usually rather large , so if you cant identify the error zip up a copy and make it available to DL and I'm sure one of us will figure out whats going on.

[raidernick]

That exception means you have an error in your cfg file somewhere.

[nli2work]

Podcockpit loaded fine

looks like a faulty FX definition in QT_Die_1m. wrong syntax probably.

[Quiznos323]

Yup, you guys were right, it was two cfg errors. Someone over on the reddit figured out that it was specifically that one of my node sizes was 0.0 instead of either 0, 1, 2, 3, etc. Also my name in General Parameters did not match the part folder name, so I changed the folder name to QT_Die_1m to match the name. After that it loaded fine!

I was going to send it to the mun but I have to be somewhere this morning lol

Anyways, thank you all so much for the help, this has been a good learning experience!