Change BSP texture dynamically

[gopostal]

I know I'm grasping at straws but I thought I'd float this here. Is there a way to dynamically alter a normal room's texture via script after the match has started? I spent last night trying to cheat it via decoration, mover, etc and nothing was flicker-free. Is it really just not possible given the way BSP is done?

I don't want to go crazy just swap the base texture of the room once. AFAIK it can't be done but this is the place to ask.

[Krull0r]

What about scripted textures? I know that qcomputers can change scripted textures while triggering.

But I have no Idea how to create such a script for scripted textures.

[makemeunreal]

You should try askin' this on UT99.org too. Lots of coders there.

[gopostal]

I looked at scripted textures but there are issues with color palettes so it's not a good fit. I really need a way to declare the texture change via script and not via some nested trigger/dispatcher thing. I've seen those go wonky too many times online. I was hoping someone had figured out a hacky way to make it work. Not surprised it hasn't been done. I've been thinking on it for two days and don't see an answer.

*Edit because I can't spell.

[Kajgue]

Only .pcx and .bmp textures need to be imported with a palette/indexed colours, .dds textures don't need a palette.

[Masterkent]

Is there a way to dynamically alter a normal room's texture via script after the match has started?

What do you mean by altering a texture: changing properties of the texture object itself (this would be observable in every place where the texture is used and potentially can be observable even after a map change) or attaching a different texture to a particular surface of a Brush?

The former can easily be done for 227 clients if you know the name of the texture. F.e.

Code: Select all

      local Texture Tex;
      Tex = Texture(FindObject(class'Texture', "GenEarth.ground.Grass"));
      if (Tex != none)
      {
            Tex.Palette = Palette'GenFluid.Palette179';
            ConsoleCommand("Flush");
      }

The latter most likely cannot be done by means of UScript only, albeit I can't be 100% sure, because there is a possibility that I overlooked something.

I spent last night trying to cheat it via decoration, mover, etc and nothing was flicker-free.

Decals should be flicker-free in most cases (in some cases they can flicker though). But they won't be rendered if the user disabled decals client-side, and attaching them to rotating movers probably won't work well.

[gopostal]

I had not thought of using decals. Years back I made a spray-tag mod and so I dug that out and ran a quick test. I think this might work for the limited use I need. Even if the client has disabled decals it won't change anything besides them missing some of the changes to the walls.

As a further question, and this is the reason I abandoned the spray tags mod in the first place, can the rotation value of the decal be controlled? I could never figure out a way and the tags ended up randomly rotated, ruining the effect. If I can clamp rotation then I can tightly control placement of the decal and match it's size to the wall I'm wanting to repaint and also prevent any overlap.

This decal idea is great and might be a good way to continue. Thanks for the idea MK!

[Masterkent]

As a further question, and this is the reason I abandoned the spray tags mod in the first place, can the rotation value of the decal be controlled?

Rotation of the decal's image can be defined by the second argument of Decal.AttachDecal:

Code: Select all

simulated native function Texture AttachDecal( float TraceDistance, optional vector DecalDir );

[gopostal]

Tested and fixed, this works just fine. Thank you Masterkent! This way is a bit hacky but I do get full control over the wall colors now and I can change them at will.