It's an engine AND compiler limit, because if you try to load a texture
512x512 the engine will spit it back and say its too big, it won't
even try to scale it down, this is why I've limited my texture loading to 1024x1024, to kind of conform to the limits, but still be a lot above.
Also my loading does MipMap as well for the sake of speed over distances.
Basically you still use low-res textures in the map, and in the wad, d3d still uses the wad, OpenGL loads either Jpeg or TGA off the hard drive, provided they exist. If they don't, it uses the wad texture as usual. So the only advantage is in OpenGL, and when the hires texture exists.
It uses texture compression and aniso on the hires images if the video card supports them (if we include a hi-res pack, you'll need to have a good card or it'd probably end up slow as molasses rolling up a hill in a square can in the middle of January at the south pole, or probably just crash).
Course, you don't have to use 'em, I'm just providing the option =D and I think it's a nice option =D
Mind you, I don't know if the aniso even works properly (haven't really tested yet, and I have a feeling it *requires* the aniso calls to be set every time the texture is bound, which I have no control over unless I render the map myself)
Wow. That quite perfect :)
And what about the performance? Any issues when using many of those hi-res texes? I guess not, 1024x1024 shouldn't be too large for modern graphic cards ;)
Rockefeller
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
