Jump to content

TomTango

New Members
  • Posts

    2
  • Joined

  • Last visited

Reputation

3 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @hraban and @zer0Kerbal Thanks for the pointers, I already had 2.21f1 among my half dozen unity installs for work and had not noticed the required versioning as 2.2f1, I've added 2.2 to the list and i'm not seeing any more problems. Just in case any one else comes across this post, I'll add that I had also used "\" in the MODEL path rather than "/" and this was causing the second (or at lest one of the causes of) the second error. Stupid oversight error I know, but it wasn't obvious to me.
  2. Hi all This is my first time adding custom parts to KSP, A bit late to the party I know. I'm having a very frustrating problem that I just can't nail down using part tools. I've been attempting this for nearly two days now and just cant for the life of me find the cause. I have followed the instructions here : https://forum.kerbalspaceprogram.com/index.php?/topic/160487-parttools-updated/ I model in blender and export as FBX, load into unity, add my mesh, define a material, etc and export However KSP.log is showing the error : and then subesquently further down the log I am a unity developer by trade, I have been since 2014, so the error makes some sense to me but I can not seem to fix it. I have debugged so far by reverting to using a simple cube object, plain grey diffuse texture using KSP/Diffuse shader and my file structure for the assets in GameData is "CLSTango/Parts/Infinity/" containing the assets diffuse.dds, normal.dds, infini-truss-01.mu and infinity-trusses.cfg all that seems correct to me. The error is not in cfg file as I tried pointing the model variable to a stock squad asset and it loaded fine. I am currently assuming that this is something to do with my object hierarchy in unity, but I have tried every combination of parenting the mesh transform and the collider transform I can think of all with the same result. I have clean installed a copy of Unity 2019.2.21f1 and begun again with a fresh .blend file in case there was some corruption in there somewhere, no difference and now I'm at a bit of a loss. Has anyone got any idea where I am going wrong here?
×
×
  • Create New...