Tweet
inkub0: hi one more time 
Just now i download your texture pack and FTE Engine and after some compares both combinations of textures/engines discover few obviously facts:
1) As you told, we already use different methods, and many texture sets incompatible one with other. Different styles - my "dirty" and your "clean", most textures cannot be replaced from other set.
2) But at least 30% we can recombine and gain GOOD result.
For example - your texture set can provide excellent graphic quality in "photo source search" method - when you really use same original object, like Pharaon's tomb or ornaments, many doors seems very very cool, ect.
From other side, with your natural grass texture on big plane exist some problem, when pattern seen and repeated. I try different grass texture and found pattern less visible on big planes (compare rtex080 for example).
Or compare rtex425, or see gold from rtex386 (but there i put not Egypt, American coin from 19 century)
And there many other cases when replacing texture can have place.
So i suggest make collaborative retexture pack from both sets.
Or we can do 2 repacks with combine something about 30% one from other.
3) In your texture structure exist texture overlay (bug with same textures in different levels), for example texture on wall from levels "demo" in level egypt1
We need one structure without overlay (my structure work without overlay, you may see that structure and copy any files from there as you wish)
4) All packs we better be create from tga files (them low or no compressed, but quality lossless)
At final, about engines. There same troubles - different ways.
jsHexen2 can provide less graphic features than FTA (as i see, FTA include better lighting system, use bump mapping, bloom and other), but jsHexen2 allow clean original gameplay without bugs (except bugs original Hexen2, of course, if they there was).
So, there now few paths - remove bugs from FTA (i was played in FTA 4 levels H2 and meet some bugs with camera, moved objects and water), or upgrade graphics features of jsHexen2 - bloom can be fast added from UQE bloom.c or even from FTA, i think in FTA used better method with correct resamples.
Or combine Darkplaces with GllHexen, but when i try explore Darkplace source i found what my beer bottles was depleted
So, in any case - task equal, we need to make a hippopotamus with a rhinoceros to make love
Just now i download your texture pack and FTE Engine and after some compares both combinations of textures/engines discover few obviously facts:
1) As you told, we already use different methods, and many texture sets incompatible one with other. Different styles - my "dirty" and your "clean", most textures cannot be replaced from other set.
2) But at least 30% we can recombine and gain GOOD result.
For example - your texture set can provide excellent graphic quality in "photo source search" method - when you really use same original object, like Pharaon's tomb or ornaments, many doors seems very very cool, ect.
From other side, with your natural grass texture on big plane exist some problem, when pattern seen and repeated. I try different grass texture and found pattern less visible on big planes (compare rtex080 for example).
Or compare rtex425, or see gold from rtex386 (but there i put not Egypt, American coin
from 19 century)And there many other cases when replacing texture can have place.
So i suggest make collaborative retexture pack from both sets.
Or we can do 2 repacks with combine something about 30% one from other.
3) In your texture structure exist texture overlay (bug with same textures in different levels), for example texture on wall from levels "demo" in level egypt1
We need one structure without overlay (my structure work without overlay, you may see that structure and copy any files from there as you wish)
4) All packs we better be create from tga files (them low or no compressed, but quality lossless)
At final, about engines. There same troubles - different ways.
jsHexen2 can provide less graphic features than FTA (as i see, FTA include better lighting system, use bump mapping, bloom and other), but jsHexen2 allow clean original gameplay without bugs (except bugs original Hexen2, of course, if they there was).
So, there now few paths - remove bugs from FTA (i was played in FTA 4 levels H2 and meet some bugs with camera, moved objects and water), or upgrade graphics features of jsHexen2 - bloom can be fast added from UQE bloom.c or even from FTA, i think in FTA used better method with correct resamples.
Or combine Darkplaces with GllHexen, but when i try explore Darkplace source i found what my beer bottles was depleted
So, in any case - task equal, we need to make a hippopotamus with a rhinoceros to make love
Comment