header general

CC4-Tex.wad blocks Iwad Brightmaps.pk3?

  • SArais
  • SArais's Avatar Topic Author
  • Demon
  • Demon
More
5 years 11 months ago - 5 years 11 months ago #1 by SArais
I'm a bumbling idiot and don't understand why this is, cc4-tex likes to block any brightmaps for some reason (seems to be tied to texture1/pnames). Anybody got an easy fix for a codelet/wadlet?

Optimally speaking, it should INHERIT from these textures, not overwrite them, so that all textures read the original BM textures and say "ok hey yeah, the parent texture is brightmapped, copy it over to here"

Left = CC4-Tex active
Right = No CC4-Tex

It carries over to textures seemingly not overwritten either.
Last edit: 5 years 11 months ago by SArais.

Please Log in or Create an account to join the conversation.

  • Blue Shadow
  • Blue Shadow's Avatar
  • Administrator
  • Administrator
More
5 years 11 months ago #2 by Blue Shadow
Replied by Blue Shadow on topic CC4-Tex.wad blocks Iwad Brightmaps.pk3?
It probably has something to do with the iwad keyword in the brightmaps' definitions:

ZDoom Wiki wrote: If the iwad keyword is present within the definition, then the brightmap will not be applied if the image is replaced by a loaded PWAD. This is useful so that if the user is loading a PWAD that replaces a given enemy, the brightmap doesn't end up trying to apply itself to a graphic which no longer represents the same thing, possibly resulting in an incorrectly-lit enemy or decoration. In general, you don't need to worry about adding this keyword if you're creating brightmaps for your custom creations.


Source

Please Log in or Create an account to join the conversation.

  • SArais
  • SArais's Avatar Topic Author
  • Demon
  • Demon
More
5 years 11 months ago #3 by SArais
Replied by SArais on topic CC4-Tex.wad blocks Iwad Brightmaps.pk3?
yep.

Please Log in or Create an account to join the conversation.