Sign in to follow this  
Say

why commercial game hate .x file?

Recommended Posts

All tutorial i readed in the web talk about mesh .x file. DirectX just support them, but i've never seen a commercial game that use .x file. Why?

Share this post


Link to post
Share on other sites
There's a few games that use .x files. But most game developers prefer to use their own format so they can be in control of how it works and so on.

Share this post


Link to post
Share on other sites
Most programmers love reinventing the wheel :P

Or perhaps not reinventing the wheel by having to write the D3DX stuff overagain on PS2. Depends how you look at it.

Share this post


Link to post
Share on other sites
.x files are great for beginners and such (myself included). They contain a great amount of features and flexibility and the D3DX loaders make it very easy. Howevver, for many commercial games, the features are either way overkill, or lacking something.

Making your own model format and parser is not extremely difficult, but it is a bit overkill for most indie and personal projects... You will also either need to create your own modeler that supports the file type or create an exporter for another modeler.

Share this post


Link to post
Share on other sites
Another reason I believe they dont use the format is to prevent people from stealing their content. The same goes for audio files and images.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
As a developer if I was to leave my mesh format as .x I leave myself open to modders changing things, which is great for some games, but bad for others, and we all know where those changes lead.

Hot cup of coffee anyone?

Share this post


Link to post
Share on other sites
It's so bloody easy to take content out of a game if you really want to, that's not even an argument.

I agree with whoever said "programmers love to reinvent the wheel."

Share this post


Link to post
Share on other sites
If you run a commercial project and use textures from a professional artist they demand you to pack the textures into a custom format noone can hack that easy otherwise you could simple buy a game and get access to textures that would code several hundret dollars, the same is it with model files, its fine when you can compile new models but it sucks when the user is able to unpack them

this only matters if you bought the license for the models from another developer

if they are your own it don t have to care about it



and x files are nice but just another attempt of microsoft to establish a monopol
there is a project for a industry model format standard which was announced last year, sadly i dont remember its name anymore

Share this post


Link to post
Share on other sites
Quote:
Original post by Illumini
Most programmers love reinventing the wheel :P

Or perhaps not reinventing the wheel by having to write the D3DX stuff overagain on PS2. Depends how you look at it.


I don't think that is really true.. model format is very closely related to the engine guts. DirectX file format is a fairly generic file format (for the most part). Most engines will have to do alot of shuffling to get the data into their geometry format.

I would be sure that alot of developers use DirectX as an intermediate format and than convert it into native engine file streams. It's widely available, better than .3ds and .ase. Maybe eventually Collada will be the end of all of these formats.

Share this post


Link to post
Share on other sites
I agree that .x would make a decent intermeadiate format (although I doubt its used much there since the very idea intermediate formats just complicates things...), even so both my points are true (the importance of either is highly debateable of course :) )

Share this post


Link to post
Share on other sites
i think it is possible and useful create a own file format that include mesh .x file information and other engine information,
So the user can't access to .x file, isn't it?

Share this post


Link to post
Share on other sites
I was planning to use .x meshes in my game. I'll pack and encode them in a PAK file, so I think it will be difficult to extract data for a modder (if I don't give away a copy of the decoder)

Share this post


Link to post
Share on other sites
You're giving away a copy of your decoder, or how will your game be able to decode it otherwise?

An own engine format is very useful to store additional precalculated information, for collision detection, or other stuff.

Share this post


Link to post
Share on other sites
so an hacker could get the decoder from my game but it so hard, anyway it get just an .x file he can't modify it ! he need 3ds file format!

Share this post


Link to post
Share on other sites
I think it would be quite difficult to extract the decoding routine from the engine executable and if someone manages to get it, well, he deserves to open game data.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this