Model is loadnig to KSP incorrectly

[PatPL]

Like in title.

Images: http://imgur.com/a/S6BqW

First image: model in blender

Second image: model in KSP

Yes, it's re-modelled, and re-textured battery.

Download: https://www./folder/l3428r6u4438d/Model

[nli2work]

what's your part config look like? This appears to be more of a config/folder setup problem

[PatPL]

Here it is: https://www./folder/l3428r6u4438d/Model

@edit

I have noticed now i wrote "loadnig" in the Title. Sorry.

Edited September 27, 2014 by PatPL

[nli2work]

your MU file is still the battery. the model.mu got mixed up somewhere along the way.

name the export file to something more descriptive than "mode" in Unity and you can avoid this problem.

[PatPL]

When I exported model to .dae, and changed model extension in parts.cfg, in KSP my part looked like Kerbal Engineer Redux flight control without texture.

What is the best extension for KSP?

@edit

.3ds file made my part not load to KSP at all.

Edited September 28, 2014 by PatPL

[SpannerMonkey(smce)]

This may seem like a silly question but are you putting the model through unity? rather than just dropping your dae in the gamedata mod folder.

[PatPL]

i'm just dropping my .dae or .mu in gamedata mod folder

[nli2work]

When I exported model to .dae, and changed model extension in parts.cfg, in KSP my part looked like Kerbal Engineer Redux flight control without texture.

it's a name conflict. you have multiple configs with the same part name; KSP loads their meshes interchangebly.

create a folder for your exported part; put your part config; MU/DAE; and textures into that folder.

in the part config file at the very top there is a line "name = "; change that to something unique and descriptive; like "theScienceBox"; so you can recognized it and KSP doesn't mix it up with battery or KER flight control.

then change your "mesh =" line to point to your MU/DAE file.

as long as the MU, Config, and texture are in the same folder and somehwere inside of Gamedata; the part should load correctly.

[PatPL]

But the name is changed to "name = theBOX"

and the mesh is always set to the mesh, i have made (if there's model.dae in folder, i write "mesh = model.dae", if it's model.mu file, i write "mesh = model.mu")

Every part my mod adds has it's own folder.

[nli2work]

then you are exporting the mesh incorrectly. The MU file I checked earlier had the battery mesh, and that's what KSP will load. it doesn't know the file name isn't supposed to be the mesh that's in the file. and the texture the file is looking for is not in the same folder as the mesh, and so shows up white in game.

check out this video to make sure you didn't miss any thing in the export process.

[PatPL]

Your video tutorial worked! THANKS!!!

I have made my own model and texture too.

Thanks nli2work and SpannerMonkey for helping (And wasting their time because i'm too lazy to find answer in internet)

Edited September 28, 2014 by PatPL