Well, although I know nothing about Deus Ex modding, another quick Google search turned up these tutorials:

http://tack.planetdeusex.gamespy.com/Ho ... tures.html
http://tack.planetdeusex.gamespy.com/Ho ... tures.html

The key line being:



The obvious advantage to doing Method 2 would be that you can do a bulk package, rather than Method 1 which looks like its texture by texture.

Hopefully that helps you somewhat.

Oh, importing them into standard packages is fine. But using that method requires the use of .PCX files, which the compiler (which we have to use to get the textures to compress right) is ignoring.

Oh I see. So you can't compile them without the other compiler, which they aren't letting you having. Couldn't you send them the files for them to compile? That way, they could check to see if you were trying to do anything bad.

And another question that I've been meaning to ask: How did you manage to take screenshots of the new textures? Did you use a different method?

I think Dave manually inserted the textures into an existing UTX, not sure how he did it though since opening the editor and trying to import them usually crashes it. This is why he's able to screen capture the textures but not entire levels. Once he gets the info he needs you'll see fully HD levels

The way Dave is trying to do it is an automatic compilation because there are just way too many textures to import manually.

What Dave's having trouble with is getting an automated compiler that will do it all for him and the guy he's been in contact with apparently knows but hasn't responded.

Correct me if I'm wrong.

*Corrects*

Well, you're kind of right. I import them through UnrealEd and have to adjust the drawscale. This has several drawbacks:

1.I have to go into the properties of each texture. Deus Ex has 2200. That's a lot of manual work.
2.It only supports 8-bit (256 pallete) textures. Although, with the compression we hope to use (DXT1) those probably look better anyway.
3.With these packages, using the merge method, you can turn the high-resolution textures on and off with a .INI command. And they work fine in UnrealEd (some textures using the current method appear skewed across surfaces meaning you can't align them properly).

I'm sorry for sounding so...impertinent (for want of a better word), but what type of compression do you have to use? Couldn't you just package them using a different type of compression?

Anyway, I hope you find a solution soon!

S3TC - or DXT, what modern games (and Unreal Engine 2 uses). The advantage is how it handles compression, as in, it's pre-compressed rather then the GPU having to compress it meaning that more textures can be on screen without slowing down the game. And the packages are around 70% the size doing it using standard Unreal P8 compression.

Plus it won't crash the editor and can be turned on and off.

ETlight pokes DaveW with a shar... smooth stick

Lol etlight

question would it be better to just keep working on the textures and handling the issue later than trying to build a mini-mod now?

Of course, that's what I'm doing Although I've been messing around with a potential standalone game I'm going to be making for the past few days. Back to work properly soon...honest.

Is it me, or is this the only thread not locked?

It's you.

Definitely you.

It's the same thing for me so at least you are not alone.

Same here.