Cannot convert from X to o3d

Anzahl der Beiträge : 90 Anmeldedatum : 20.08.09 Ort : Groningen (NL)

While taking my first steps into creating crossings and the lot, I can't seem to convert my x-format meshes into o3d-format. The converter does yield an o3d-file, but when I try to use this file (through an .sco, obviously) in either the map editor or street editor, it is invisible. No error message either, just invisible. The only message I get is when I reload the saved map including the converted file, stating the file could not be found and whether I would like to exchange it.

Any ideas? bounce

Software used is 3D Crafter, latest version (not Blender, I know)

Maybe the sco still refers to a material which is not used in your new object? Try deleting all [matl] entries after the [mesh] definition.

Cas schrieb:: (not Blender, I know)

But exactly this could be the problem: The o3d conversion tool cannot convert EVERY x format but sometimes has problems with x files made by other 3d programs. One of the reasons to try blender! Wink

But you also can try to import your x file into blender and export it again...

Marcel

Anzahl der Beiträge : 90 Anmeldedatum : 20.08.09 Ort : Groningen (NL)

Marcel Kuhnt schrieb:

Cas schrieb:: (not Blender, I know)

But exactly this could be the problem: The o3d conversion tool cannot convert EVERY x format but sometimes has problems with x files made by other 3d programs. One of the reasons to try blender! Wink

But you also can try to import your x file into blender and export it again...

Marcel

Hm yeah, I figured.

I assume you keep the structure of the o3d-format to yourself? Would be great to be able to write a plugin to export to o3d directly..

Anzahl der Beiträge : 90 Anmeldedatum : 20.08.09 Ort : Groningen (NL)

Below is 3DC's DirectX-output for a cube with asphalt-texture applied. Is there something wrong maybe with the order?

Spoiler:

Code:: xof 0302txt 0032
Header {1; 0; 1;}

// Created by 3DCrafter

Material mat_0 {
1.00E+00;1.00E+00;1.00E+00;1.00E+00;;
0.00E+00;
1.00E+00;1.00E+00;1.00E+00;;
2.00E-01;2.00E-01;2.00E-01;;
TextureFileName {
"str_asphdrk.BMP";
}
}

Frame Scene {

FrameTransformMatrix {
1.00E+00, 0.00E+00, 0.00E+00, 0.00E+00,
0.00E+00, 1.00E+00, 0.00E+00, 0.00E+00,
0.00E+00, 0.00E+00, 1.00E+00, 0.00E+00,
0.00E+00, 0.00E+00, 0.00E+00, 1.00E+00;;
}

Frame Group {

FrameTransformMatrix {
1.00E+00, 0.00E+00, 0.00E+00, 0.00E+00,
   0.00E+00, 1.00E+00, 0.00E+00, 0.00E+00,
   0.00E+00, 0.00E+00, 1.00E+00, 0.00E+00,
   0.00E+00, 0.00E+00, 0.00E+00, 1.00E+00;;
}

Mesh Cube {
14;
-5.00E-01; -5.00E-01; -5.00E-01;,
-5.00E-01; 5.00E-01; -5.00E-01;,
5.00E-01; 5.00E-01; -5.00E-01;,
5.00E-01; -5.00E-01; -5.00E-01;,
5.00E-01; -5.00E-01; 5.00E-01;,
5.00E-01; 5.00E-01; 5.00E-01;,
-5.00E-01; 5.00E-01; 5.00E-01;,
-5.00E-01; -5.00E-01; 5.00E-01;,
-5.00E-01; 5.00E-01; -5.00E-01;,
-5.00E-01; 5.00E-01; 5.00E-01;,
5.00E-01; 5.00E-01; 5.00E-01;,
5.00E-01; 5.00E-01; -5.00E-01;,
5.00E-01; -5.00E-01; -5.00E-01;,
-5.00E-01; -5.00E-01; -5.00E-01;;
5;
4;0,1,2,3;,
4;4,5,6,7;,
4;8,9,10,11;,
4;12,11,5,4;,
4;7,6,8,13;;
MeshMaterialList {
1;
1;
0;;
{mat_0}
}
MeshNormals {
5;
0.00E+00; 0.00E+00; -1.00E+00;,
0.00E+00; 0.00E+00; 1.00E+00;,
0.00E+00; 1.00E+00; 0.00E+00;,
1.00E+00; 0.00E+00; 0.00E+00;,
-1.00E+00; 0.00E+00; 0.00E+00;;
5;
4;0,0,0,0;,
4;1,1,1,1;,
4;2,2,2,2;,
4;3,3,3,3;,
4;4,4,4,4;;
}
MeshFaceWraps {
5;
0;; 0;;,
0;; 0;;,
0;; 0;;,
0;; 0;;,
0;; 0;;;
}
MeshTextureCoords {
14;
-1.00E+00; 0.00E+00;,
-1.00E+00; -1.00E+00;,
0.00E+00; -1.00E+00;,
0.00E+00; 0.00E+00;,
0.00E+00; 0.00E+00;,
0.00E+00; -1.00E+00;,
-1.00E+00; -1.00E+00;,
-1.00E+00; 0.00E+00;,
0.00E+00; -1.00E+00;,
0.00E+00; 0.00E+00;,
-1.00E+00; 0.00E+00;,
-1.00E+00; -1.00E+00;,
-1.00E+00; 0.00E+00;,
0.00E+00; 0.00E+00;;
}
}
}
}

Heres the definition of an x-file Blender export:

Code:: Material Mat3 {
1.0; 1.0; 1.0; 1.0;;
1.0;
1.0; 1.0; 1.0;;
0.0; 0.0; 0.0;;
TextureFilename { "regen_front.tga"; }
} // End of Material

I'm not sure if this may cause problems, but try changing the exponential notation of the values into "standard" notation as shown above.

Anzahl der Beiträge : 90 Anmeldedatum : 20.08.09 Ort : Groningen (NL)

Rüdiger Hülsmann schrieb:: I'm not sure if this may cause problems, but try changing the exponential notation of the values into "standard" notation as shown above.

Tried that, but didn't make any difference pale

Anzahl der Beiträge : 90 Anmeldedatum : 20.08.09 Ort : Groningen (NL)

Interesting: ran an exported x-file through a tool called MeshConvert (part of the Microsoft DirectX SDK) to 'recreate' the mesh file and it finally worked. Now to investigate the exact modifications the tool applies cyclops

» How to convert .sco to .sli ?
» How to convert bus to omsi?
» OMSI X Convert
» FBW bus convert to Omsi || RELEASED
» How to convert Buses from VBUS to OMSI?