I'm having a problem defining sky textures after adding a texture pack into my wad.

[St. Mildly Annoyed]

Hopefully this is my last post here in editing questions for a while now. So I just did a test run a half hour ago with a wad I'm working on, and discovered I have to add the texture pack I'm using into the wad itself in order for it to appear in game. After doing so in slade 3, the only problem I have is that both of my different sky textures become this, even when running in gzdoom.

If you're wondering what I did, I took the original texture wad and copy and pasted it's assets into my wad, below every other asset. I've tried removing a pname and texture modification I did for only two custom skies, but it made no difference when adding or removing the  modification, leaving only the pnames and textures in the wad.

Below mapinfo is the texture wad i'm trying to put in my own wad to get textures to appear in doom runner and slade.

Edited September 13, 2023 by St. Mildly Annoyed

[Stabbey]

How big is your sky texture? Ones which are too large - or too small - could cause a problem. I assume that you're using the correct skytexture= in UMAPINFO or sky1= inMAPINFO?

 

55 minutes ago, St. Mildly Annoyed said:

If you're wondering what I did, I took the original texture wad and copy and pasted it's assets into my wad, below every other asset.

 

If you want help, you shouldn't make us "wonder" what you did. You should post your actual .WAD-in-progress or at least screenshots of how you're organizing the textures in Slade. That would be better help for you than guessing.

 

When you say you copied and pasted the assets, I WONDER (because I cannot KNOW) if you also copied over the markers. I would hope you did, because you cannot just paste unorganized textures into your wad, they need to go between markers. Wall textures between "P_START" and "P_END". All textures you're using should be in both the PNAMES and TEXTURE2 entries.

 

(As an aside, this is unlikely to be related to your problem, but...) It would be a better practice to NOT just dump an entire texture pack into your wad. It will massively inflate the file size, and if you aren't using all those textures, it's not even for a good reason. When testing, you load up the texture pack as an additional resource in the editor. Only after you've finalized the level should you merge the textures - and even then, only merge the ones you're actually using.

Edited September 13, 2023 by Stabbey

[Ash4ash]

Add MAPINFO and have sky1=skyname

[St. Mildly Annoyed]

7 hours ago, Stabbey said:

How big is your sky texture? Ones which are too large - or too small - could cause a problem. I assume that you're using the correct skytexture= in UMAPINFO or sky1= inMAPINFO?

 

 

You cannot just paste unorganized textures into your wad, they need to go between markers. Wall textures between "P_START" and "P_END". All textures you're using should be in both the PNAMES and TEXTURE2 entries.

 

(As an aside, this is unlikely to be related to your problem, but...) It would be a better practice to NOT just dump an entire texture pack into your wad. It will massively inflate the file size, and if you aren't using all those textures, it's not even for a good reason. When testing, you load up the texture pack as an additional resource in the editor. Only after you've finalized the level should you merge the textures - and even then, only merge the ones you're actually using.

I made sure that markers were used. I know that it bloats the wad, but I was planning to merge the textures I need, and then remove all the unnecessary and unused textures once I'm done with each map, so I know what it would look like when actually run as a wad. I'm using otex, and the textures osky35 and 42, which normally look like this.

have turned into this.

Though I think it could be related to a patch name file that I made for the sky textures conflict with another one in the wad itself.

 

Edited September 13, 2023 by St. Mildly Annoyed