Patches scaling

Devan · Post by **Devan** » Thu Jul 27, 2006 16:23

I suggest a very little thing - make the patches who aren't defined in hirestex automatically become the same size as in IWAD. For example, if the M_DOOM in the IWAD is 100x50 and Hires M_DOOM in PWAD is 200x100 automatically define it to 100x50 - as in IWAD

Post by **wildweasel** » Thu Jul 27, 2006 16:50

That would break so many existing wads it's not funny. Look at Icarus: Alien Vanguard - the M_DOOM graphic takes up nearly the whole screen. That wouldn't look very good if it were scaled down to 100x50.

Alter · Post by **Alter** » Thu Jul 27, 2006 16:58

Wildweasel is right about scaling patches
it would break many wads which use larger m_doom patches or even full-screen m_doom patches
scaling them makes them sucks so don't count about this being added!

Post by **wildweasel** » Thu Jul 27, 2006 17:19

Seriously, what's wrong with using a hirestex lump? All you need to do is type just one little line:

Code: Select all

remap m_doom hi_doom

Devan · Post by **Devan** » Fri Jul 28, 2006 10:57

then i suggest one more feature with this - color depth checking. If the replacement is 8 bit depth, don't resize it. If it is more than 8 bit depth, resize it automatically

Post by **Graf Zahl** » Fri Jul 28, 2006 10:59

That's as nonsensical as the original because it is not what most mappers would expect. If you want to have a hires replacement use one of the documented methods to do it. They were added for a reason.

Post by **Enjay** » Fri Jul 28, 2006 11:02

Devan wrote:then i suggest one more feature with this - color depth checking. If the replacement is 8 bit depth, don't resize it. If it is more than 8 bit depth, resize it automatically

Why? It's perfectly possible to put a more-than-8-bit image into a WAD that is larger than the original but not want it to scale. It seems silly that a person who didn't want the graphic to change size would then have to be the one to create a lump to make sure it didn't happen.

It's a minimal effort to make a hirestex lump (it must be one of the simplest control lumps). I don't see why a single line of code is causing such a problem.