M3hdi

Your english is great – I really wouldnt have known.

I think I know what the problem might be. The clue was that you said your IDE is set to french. I remember Air Legends failing Peer Review once because when played on Xboxes in the France & Italy regions it did weird things. Giant Models to be specific.
It turned out to be a problem with similar Parse/Convert code. If I remember correctly France & Italy use a comma character (”,”) to delimit the fractional part of a number. In most english language locales we use a period, or decimal point character (”.”).

The solution was to add an extra parameter to all the Parse & Convert statements that dealt with numbers.

for instance, I changed….

float x0 = float.Parse(subdivisionNode.Attributes["x"].Value);

to…

float x0 = float.Parse(subdivisionNode.Attributes["x"].Value, CultureInfo.InvariantCulture.NumberFormat);

(CultureInfo can be found in System.Globalization)

I hope this solves it for you. Let me know how you go.

Cheers,

Sharky

float x0 = float.Parse(subdivisionNode.Attributes["x"].Value);

it says that “the input string format is incorrect” (i tried my best to translate the error text cause i’m from france and the interface language of my IDE is set to french :p )

i’ve tried to modify the xml file, changed its location and its path, and several other code modification but without success.
so please sharky, can you help me fix this problem ?

Ps : sorry for my lame english, my command of it still not perfect yet

I think you might be getting confused between your compiled output files and the actual source files.

If you’re seeing .XNB files you must be looking at the compiled output, not the source Content.

When you compile Game Studio takes your source Content like your models (.FBX, .x, etc….), and textures (.jpg, .bmp, .tga, .dds, etc….) and puts them in a propriatory .XNB format along with your compiled application.

(I’m pretty sure you can’t take an .XNB file and put it in another games source.)

You must have already copied the p1_wedge.FBX model from the Microsoft sample into the viewer source Content\Meshes. This is the one you’d edit as I described above. NOT, the compiled XNB file under \bin\x86\Debug\Content\Meshes.

thanks for your help though, even your quick version is a lot more effective than the singular sphere i was using before

for now i am going to use your .xml and run with it to see how it goes.

So my viewer code makes a few assumptions:

I’ll get onto the spheres later, but…

Assumption 1:
It loads a Texture file independent of any Texture files referenced inside the FBX model. Meaning, I load my texture in code, rather than rely on XNA loading it based on the content of the FBX model. (these would be loaded automatically by XNA as part of the Model load).
However, I like to keep my choice of texture separate from the model for flexibility in my games. i.e. I might want player selectable skins for a given model.

Now I see the RelativeFilename in the FBX file just happens to be correct for where you’ll have placed the wedge_p1_diff_v1.tga file in the viewer source. (Otherwise you’d get an error compiling)

Assumption 2:
My viewer code assumes the texture file loaded will always match the model name, so besides changing that behaviour in the code you’d want to rename the wedge_p1_diff_v1.tga file to p1_wedge.tga.

Here’s are the steps I did to get it working in my viewer code.

- create a p1_wedge.xml file into the MeshInfo folder (copying one of the others).
- add the p1_wedge.fbx file to the Content\Meshes
- add the wedge_p1_diff_v1.tga texture into the Content\Textures
- BUT, then rename it to p1_wedge.tga (to match the model name).

Renaming it however will make the Model not compile because of the texture references inside the FBX file, so I comment those out as follows:

- Fortunately the Microsoft’s FBX model has been exported in ASCII format so you can open the FBX file and search for any “Filename:” & “RelativeFilename:” bits. (There might be several)

- comment them out by putting a “;” at the beginning of the lines.

e.g.
;Filename: “C:/Documents and Settings/a-mdudl/My Documents/maya/projects/default//textures/spacewars/tga/renamed/wedge_p1_diff_v1.tga”
;RelativeFilename: “..\textures\wedge_p1_diff_v1.tga”

Now the model should render, with the texture.

Now to fix the BoundingSpheres edit the p1_wedge.xml file as follows.

- there needs to be a “MeshPart” element in the Xml file for each mesh you find in the FBX model and the id is used to find the right one, so these need to be named correctly.

To get the correct names of these MeshPart’s search the FBX file for “Model::”

e.g. finds lines something like this…

Model: “Model::p1_wedge_geo1″, “Mesh” {

so you’d give your MeshPart id=”p1_wedge_geo1″

In that FBX file I can only see one “Model::” that seems to be some kind of Mesh. The others seem to be some kind of “Camera” type. (I’m not familiar with the FBX format at all. Just a guess)

Here’s my quick hack at an arrangement of spheres…
The blog wouldn’t let me post the p1_wedge.xml here as a comment, so download it instead from here

Like I said, I don’t really know the FBX format at all, but it’s interesting that for Microsoft’s model seems to have 3 MeshParts if you break point in the DrawModel() method. Each with the same Name. Not sure why. Perhaps something to do with different Materials defined also in the FBX file?

Hope that works for you.
All that stuff about the textures is really for my viewer logic. In your game you can do whatever you want, but the BoundingSpheres is what you’re really after right?

i tried copying my files into the proper place, and because im inexperienced with XMLs, i just copied yours and renamed it.

When i ran the program, i saw my ship, but no bounding spheres anywhere!

i tried commenting out the mesh.draw line in the model drawing code to see if my ship was covering up the boundingspheres, but they simply werent there. im not sure what i did wrong…

can anyone help me out? im looking to keep this ship model because it looks cool and i dont want to rework my game.

I’m not sure the exact problem, but you’ve prompted me to finally update the sample to work with XNA v3.0. Something I’ve had mostly done, but unreleased for a while.

The code in this version will be quite out of synch with the tutorial, but the principal is the same.

Take another look at this page, as I have appended an update and link to the new source.

Any idea please?