Retexture Project

[knowom]

Originally Posted by Nydosa

Sorry to help further necro a necro-ed post, but I think those interested in alternative textures would find this thread very interesting.

http://forum.shardsofdalaya.com/showthread.php?t=28215

Funny how much a little surface change could make the game interesting in a whole new way.

Yeah I saw that thread and forgot all about it. Grinkles second post response in that thread is what I had in mind about cosmetically altering zone textures.

I wasn't looking to use custom textures not previous a part of EQ however like he did in his case, but simply have a way to pick and choose textures that EQ does in fact use and swap them around as I like between various zones.

Like if I could turn a wooden textured building into a mossy stone, granite, or brick one instead as a example. I want it in my case for zone lines to better match different custom zone line transitions from one zone line to the other.

Is it possible to just rename zone texture files and use them for different zones? Like could I reuse Rivervale textures for Freeport zones? and vice verse?

If that's the case a simple .bat file would be a easy way to customize zones that could be distributed legally just having it backup old textures to a folder and then having it copy, rename, and overwrite (replace) the previous textures with the ones you wanted to swap over.

This guy also has some texture modification stuff people might find interesting.
http://www.project1999.org/forums/sh...d.php?t=121490

[Galelor]

Originally Posted by knowom

Is it possible to just rename zone texture files and use them for different zones? Like could I reuse Rivervale textures for Freeport zones? and vice verse?

If that's the case a simple .bat file would be a easy way to customize zones that could be distributed legally just having it backup old textures to a folder and then having it copy, rename, and overwrite (replace) the previous textures with the ones you wanted to swap over.

It is going to be more complicated than a .bat file because of the way textures are actually stored. (I have been doing some texture modifications and I post as daffie/galelor on the SoD/P99 forums respectively.) I will even go so far as to say that the version of eq you have running effects how you modify the textures. As an example, SoD textures appear upright once extracted with eqspy while p99 and live seem to be inverted. There are also other differences. (I can't think of any other way to explain this unless the SoD guys extracted, modified, reintroduced all textures, and then rewrote the engine to use the textures in an upright position... I highly doubt this is the case...)

That said, the textures are fairly well organized by location/name. Depending on the texture sizing, it may be possible take background textures from one zone to use them in another zone.

[lerxst2112]

Originally Posted by Galelor

As an example, SoD textures appear upright once extracted with eqspy while p99 and live seem to be inverted. There are also other differences. (I can't think of any other way to explain this unless the SoD guys extracted, modified, reintroduced all textures, and then rewrote the engine to use the textures in an upright position... I highly doubt this is the case...)

They don't need to extract anything, they have the source material used to build the files in the first place. It's not uncommon for a file format to change over time as features and optimizations are done to an engine. It wouldn't surprise me in the least if they decided that storing the files a different way worked better for them in more recent clients.

[Galelor]

Originally Posted by lerxst2112

They don't need to extract anything, they have the source material used to build the files in the first place. It's not uncommon for a file format to change over time as features and optimizations are done to an engine. It wouldn't surprise me in the least if they decided that storing the files a different way worked better for them in more recent clients.

Usually, textures are grouped from between 50-400 per file... The only way I have found to quickly make any meaningful changes is by isolating each texture through extraction using S3Dspy.

How do you modify individual textures if you don't 'extract' them from the .s3d, .eqg, and .pak files?

EDIT- I see what you mean now. I don't think SoD made any major changes to the engine or reading of the textures. I think that was done by Sony in subsequent versions of the EQ client. I will plug the SoD guys as being far and away my favorite EQ emulator

[knowom]

I just came across this forum thread tonight that got me thinking about this subject a bit further.

http://www.project1999.org/forums/sh...ad.php?t=87281

It's a program to fix transparent textures and according to the wiki it's legal as it includes no copyrighted files basically it just patch edits your current s3d files with transpfx.exe and a .bat file that tells the executable what to patch.

Looking at the .bat with notepad++ I see both chr.s3d and obj.s3d files along with a bunch of .bmp texture files and some sort of commands it's issues transpfx.exe to do to them and what not.

I'd be curious if the .bat could be manipulated to patch different s3d files textures to replace them with other ones of your liking to do something like for example inverting nro to a ice covered zone like great divide and you do the reverse for that zone making it into desert.

That's one example for large scale cosmetic changes. Now another example for it's use would be take Zone_points for zone lines that look similar, but don't normally go together like qeytoqrg to lakerathe though do look close to do some texture touch ups on them to fit together as if they always belong next to each other. So it's potential has both cosmetic and physical land reconstruction purposes.

There could very well possibly be some client differences in regards to it, but could be resolved with different .bat patch files for different clients. It could really open up a new avenue of server customization for the EQemu community.