Looking for texture editor for xp

[coporal_punishment 0]

I'm looking for a texture editor which works on XP, I know there are ones which edit the p3ds texture location but it doesn't work on XP.

I herd of rumors there is one which works on XP but i can't seem to find it anywhere and i've serched the forums.

If you find a link of have a copy please post.

[Crowley 0]

You mean the texture positioning? I'm still fairly new to texturing, but isn't that done in O2?

[coporal_punishment 0]

Nope its not texture positioning, basically when you make a model you assign the textures to be from \lol_infantry\hello.pac (this will get the textures from lol_infantry.pbo) in the p3d but when you want to retexture the addon you and you don't want it to replace the original addon you have to draw the textures from another file i.e. \cpl_infantry\hello.pac (this will get the textures from cpl_infantry.pac).

Naturally you can edit addons in o2 but if the addon is in mdol format it can't be opend because the encryption is not compatible with o2 released by BIS.

There is a program which allowed you to re-designate where to draw the textures but it doesn't seem to work with Windows XP.

[sander 14]

Hi,

Changing the texture paths can be accomplished with a hexadecimal editor program. In my opinion it is best to use one which has some basic text editing functions, such as replacing particular strings throughout a file (thus for instance replacing all instances of \lol_infantry\ with \cpl_infantry\). It is advisable to use paths and names that exactly match the length of the original to prevent problems with some models. A search engine query should yield a choice of various programs that offer hexadecimal editing functions under XP.

Regards,

Sander

[ag_smith 0]

Yeah, but the problem is: what if these strings have diffrent length? Anybody knowing any remedy for that?

[sander 14]

Hi,

Sometimes it is just necessary to accept the constraints and try to work within them. The workaround for the problem you mention is to change the path and texture names to fit the length required. If the original pathname for instance is 8 characters long and you wish to use one that is six characters long, you would have to add two characters to the name of the texture files, both the actual texture files as well as those in the p3d file. Likewise if for instance one desires a 10 character path name instead of an 8 character one, two characters should be removed from the names of the texture files.

Examples

\lol_infantry\body_front.pac

to be changed to

\cpl_marine\aabody_front.pac

or

\lol_infantry\body_front.pac

to be changed to

\cpl_specialops\body_fro.pac

Regards,

Sander

[ag_smith 0]

I appreciate your willing to help me but I 've run up against something that can't be solved this way. That's why I asked that question above.

[dm 9]

The path length is ONLY "critical" in MLOD models.

Once binarised, ODOL models can have the path length changed as much as you want. Just another oddity of the two file formats.

I'd suggest googling (or checking ofp.info or ofpec) for Mike Schells "OFP Texture Swap" utility. I've got it on XP Pro, and it works fine.

[Crowley 0]

Nope its not texture positioning, basically when you make a model you assign the textures to be from \lol_infantry\hello.pac (this will get the textures from lol_infantry.pbo) in the p3d but when you want to retexture the addon you and you don't want it to replace the original addon you have to draw the textures from another file i.e. \cpl_infantry\hello.pac (this will get the textures from cpl_infantry.pac).

Right, since responding initially I figured out just what you meant.

[coporal_punishment 0]

Nope its not texture positioning, basically when you make a model you assign the textures to be from \lol_infantry\hello.pac (this will get the textures from lol_infantry.pbo) in the p3d but when you want to retexture the addon you and you don't want it to replace the original addon you have to draw the textures from another file i.e. \cpl_infantry\hello.pac (this will get the textures from cpl_infantry.pac).

Right, since responding initially I figured out just what you meant.

Nah i'm just a bad explainer and thnx for your help everyone