Jump to content
  • Advertisement
Sign in to follow this  
Ixeus

Mesh format changes 9.0b and c?

This topic is 5134 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I've looked around various sites, including this one, and can't find a straight answer to this issue. Since 9.0c SDK I've been unable to open any mesh files other than the ones that came with the SDK demo (or ones I've created using the Mesh viewer that came with the SDK) I get an error trying to load it, just saying "unable to load specified file" Maybe I'm just out of the loop or something, but there seems to be a difference here, I'm guessing it has to do with managed/unmanaged branch off. Is the format different now? If so, are there any exporters available? (p.s. it also fails to load when using the code in c# Mesh.LoadFromFile(...);) Thanks a lot of the help :)

Share this post


Link to post
Share on other sites
Advertisement
The format didn't change, but the XFile parser got a little less forgiving about syntax in terms of { } and such. I think some exporters mess this up from time to time. (Milkshape in some instances? I'm not sure.)

Make sure braces matches up in the files.

Share this post


Link to post
Share on other sites
Quote:
Original post by RenderTarget
I think some exporters mess this up from time to time. (Milkshape in some instances? I'm not sure.)


Yes, the Milkshape X-File exporter messes the files up. While they load fine in DX 9.0b, the won't on 9.0c. But you can fix this removing the redundant braces in the X-file. The D3DX debug library show the exact line where parsing failed.

Share this post


Link to post
Share on other sites
Sweet, I'll give that a bash quick... have you tried this before? If this should fail, are there any other possible problems?

(What you said does make sense actually)

Just as a side note, say I want to create 2 sphere's one twice as big as the other in radius, do I do this in the mesh, or do I use the same mesh and scale them in the application appropiately?
(that is without distorting the textures)

Thanks,
Ixeus

Share this post


Link to post
Share on other sites
Greetings!

You say DX 9.0c will not load the files? Hm. Try to load that .x file into the DX MESH VIEWER Utility. If it loads, save it again (File/Save). It will genereate a pure Micro$oft .X file with the DX sdk, not with some work arround functions like milkshape.

Share this post


Link to post
Share on other sites
That's what I was talking about, it wouldn't load in the viewer, unfortunately I haven't gotten around to trying the { } fixes yet, I'll have a look this morning :)

Share this post


Link to post
Share on other sites
Mmmmmm, the { } mismatch, I couldn't spot any as such. Seems a little deeper than that. I'm sure you're right about the syntax, but this seems awfully painful to search through a 300KB file for "incorret" syntax. Is there a converter that could fix these problems by chance, I have over 20 meshes that fail to load :(

Regards
Ixeus

Share this post


Link to post
Share on other sites
The D3DX debug library tells you in which line the parsing failed, you can then easily eliminate the redundant braces.

Or you could switch to a better exporter ;)

Share this post


Link to post
Share on other sites
I suppose that's question of the week, what IS a better exporter? I am using conv3ds currently for those 3ds files I've found online :)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!