Spring RTS Engine

When both the mod and the map wanted to change the default DetailTex (=the texture that is overlayed all over the map to give it a grainy texture), it used to be the map that won. And that was fine.

Now, it's the mod who win. And that is a bug. How the ground looks belongs to the map, not to the mod! So the map detailtex should have the priority over the mod detailtext, not the other way around!


Edit: Actually, it's not just a question of priority, the map detailtext is plain ignored. Or is it because my mod has Depend0=springcontent.sdz; which specify a detailtex?

Anyway fixxit!

If you need an exemple just play any mod on the map Direct_Memory_Access_0.5c_beta.sd7. It should have fine green circuitry like that, but it has not anymore since new Spring version.

The released 77b4 and the unrelased 0.77b5 (R6828) still suffer from that bug.

I feel so ignored!

Edit: Nevermind, it was fixed. I just needed the new base files as well. Thanks to whoever fixed it!

The map should specify it's own detail texture if it does not want to get overridden.

Also a minor note; there is no need to specify springcontent.sdz as a dependancy now - it is always loaded.

The behavior was incorrect in 77b3 and 77b4.

The behavior has been fixed for 77b5.

Thanks!

in the old version of gundam I overrode the detail texture to maintain the desired aesthetic. Allowing the project to specify it's own specific detail texture or other resources is not a bug but a feature. I don't know why it would be seen as a bug. Oh well the devs have spoken.

Hmm, did you even read what I wrote?

zwzsg wrote:When both the mod and the map wanted to change the default DetailTex (=the texture that is overlayed all over the map to give it a grainy texture), it used to be the map that won. And that was fine.

Nope it was the mod that would win. Which was my point. That was "working as designed"

zwzsg wrote:Now, it's the mod who win. And that is a bug. How the ground looks belongs to the map, not to the mod! So the map detailtex should have the priority over the mod detailtext, not the other way around!

So I replied with the fact that you can specify your own detail texture. Now if you name it the same as the detail texture specified in spring it would probably load the one stored in the mod over the one in spring. Maybe I miss understood what you were asking.

As far as I know it should go: Map>Mod>springfiles

I think the map is loaded after the modfiles.

The way I understood your post was that you were upset that spring would allow the mod to override the detail text. I remembered 76 allowing for custom detail textures just fine(centerrock I believe used one).

So I may have misunderstood your point but asking if I read it is more than a bit condescending and forb likes to post that sort of reply. Please avoid that forbism.

smoth wrote:

zwzsg wrote:When both the mod and the map wanted to change the default DetailTex (=the texture that is overlayed all over the map to give it a grainy texture), it used to be the map that won. And that was fine.

Nope it was the mod that would win. Which was my point. That was "working as designed"

Nope at your nope! Well, actually, depends about how long ago we refer:
In 74b3,75b2,76b1, the map DetailTex would win over the mod DetailTex -> Good!
In 0.77b3 and 0.77b4 the mod DetailTex would win over the map DetailTex -> Bad!
In 0.77b5 the map DetailTex wins again over the mod DetailTex -> Good!

So I replied with the fact that you can specify your own detail texture.

I knew that. In may 2007 a released a map with a custom detailtex.

Now if you name it the same as the detail texture specified in spring it would probably load the one stored in the mod over the one in spring.

No. To overide a detailtex, I do not use the way of including a file with the same name. Instead, I use the tags designed for that, which are:
/mods/../gamedata/resources.tdf [resources]{[graphics]{detailtex=path/filename.tga; for the mod
and /maps/../name.smd [MAP]{DetailTex=otherfile.png; for the map.

As far as I know it should go: Map>Mod>springfiles

At least we agree on that.

The way I understood your post was that you were upset that spring would allow the mod to override the detail text.

Depends.
- I was upset that mod DetailTex override map detailtex in last two spring release.
- I am happy that mod DetailTex override /base/springcontent.sdz default detailtex.

I remembered 76 allowing for custom detail textures just fine(centerrock I believe used one).

Indeed. Back in 76b4, I made the kernel panic mod use an uniform detailtex (as grainy doesn't fit that mod), and I made a K.P. map, D.M.A, use a detail tex with circuitry (as I wanted only that map to use that detailtex). And it worked fine in 74b3,75b2,76b1 (and probably others): The mod overrode the default grainy detailtex on most maps by a plain grey one, and the DMA maps would use its own circuitry detailtex. And I made that thread when I saw 75b3 didn't work the same.

So I may have misunderstood your point but asking if I read it is more than a bit condescending and forb likes to post that sort of reply. Please avoid that forbism.

I should just stop arguing. The bug has been fixed, and we both agree that: it should go: Map>Mod>springfiles