IsamuKondera

Contest Entry: "Arctic KOTS" Nickname: IsamuKondera Server: EU Seamless Texture colored: Ingame Texture for those that wanna use it: With Color coding: <color0>0.553 0.553 0.553 1.000</color0> <color1>0.118 0.329 0.416 1.000</color1> <color2>0.071 0.196 0.404 1.000</color2> <color3>0.071 0.118 0.259 1.000</color3> Ingame Screenshots: Cruiser Battleship Destroyer Carrier

There are 4 textures in total. Try to adjust the "dd0" to "dd2" variants and don't use the dds file. It will work then. To edit the dd0 file rename it to dds, open it in your prefered image editing program and then save it again as dds and rename it back to dd0 or dd1 or dd2 depending which original you edited. My suggestion is: Simply open the dd0 file, which is the biggest one (4069x4069) and then resize the outcome and make dd1 50% of the size of dd0 and dd2 50% the size of dd1.

A simple Mod for the new port "Designers Table" Adjusts some blueprints into images of Kantai Collection characters. Preview: Download (~33MB) (No Password required) (readme may still show 0.8.8.0. Always use the latest version folder for it) Mod still working with 0.8.8.1

You obviously need indices. An indice just tells you which vertex is connected to which one. 3 vertexes create a triangle when you have an indice with 3 values. So I guess we will see indices with just 2 values to connect 2 vertices with the r value. Thats just a guess though. Will have to write a provisional extractor first to make it humanly readable for me. Also: xyznuvr{ # exists only when type=="xyzuvr" (most likely for wire models) r:4  # float } This must be at least 12 bytes long. Otherwise it doesn#t work.

Some quick search via google: Getting Tangent and bitangent data: https://blender.stackexchange.com/questions/26116/script-access-to-tangent-and-bitangent-per-face-how Extending the import and export menu: https://blender.stackexchange.com/questions/56829/python-extend-select-similar-menu Overall the blender addon would be probably the easiest part. And I would also start with this one because here you can define the file properties. I also think that it is a bad idea to touch the armor stuff. So my suggestion is: Let's start with the blender addon first in this way: 1. Creating Menu functions 2. Export (with file dialog) 3. Import (with file dialog) When this is done we can start concentrating on the primitive file. Regarding the posisble wiremodel attribute... Could it be the... radius? like r? That would explain the nature of it. Two vertices beeing connected and the radius telling the software how to render it. UV mapping inclusive. We should test this once. Because if it is the radius we would have to think how to implement it.

I guess at this point it's probably easier to write an addon for blender, because they actually have a documentation, and just adjust the obj file so it meets our requirements. And call it specifically something like sobj which stands for Ship Object then or something like that. You can then still export it via FBX to other 3D suits but blender will be the main target because it's free to use.

My guess for the first unkown:4 is a so called "magic value" or "magic number" which is used to see if it is from the same filetype as you expect.