can it be you try to use a similuar lookin xmodel of cod2 with a new skin you made cause that error you get is the same when you try usein cod2 models in uo .....just an idea

and no you cant edit xmodels with a hexeditor

Moviestar - you just need the name of the new texture to be exactly the same length as the old one. I am currently nearing completion of a mod that adds about 10 custom player skins to the multiplayer game. To do it I had to add additional soldier types for each skin. I copied the stock player models and their ancillary gear, then using a hexeditor, renamed the various textures references on the models, and also renamed the actual textures to match.

End result:- you can specify any allied team on any gametype on any map, using any stock or custom skin that is in the mod.

I must emphasise, none of the skins are my work, only the coding that allows them all to work together.

And no wrong version error.

Edit.
My home server is running now. Look for :-
BigLan AWE Server **enable downloads**

And yes **enable downloads** means just that!!!


edited on Jun. 17, 2007 09:18 am by general99

So all you have done is reskin basicaly and messed with hex values that there was no need to change...cooooool... pointless but cooooool as we were talking about the model itself and not skin hex values.

edited on Jun. 17, 2007 12:52 pm by moviestar

ive hex'ed player models too, this was needed as i only wanted the player models to be on maps wen its zom gametype (makin a zombie mod) and not on maps wen its not that gametype

it is possible to hexedit xmodels to change their geometry through trial and error, but obviously it's completely pointless.

using a hex editor to the textures of trees, plants, and anything else that uses transparencies works well for making the xmodel look different though

you could try making the winky as a brush model, milkshape will export models as quake 3 .maps which will work in greydiant