Author Topic: Surfaceparm order?  (Read 2934 times)

MrFish

  • Posts: 201
  • Turrets: +16/-500
Surfaceparm order?
« on: May 25, 2010, 06:34:19 pm »
Is there an order surfaceparms need to be in? Something as simple as this-

textures/*****/forcefeild

{   

   surfaceparm nodraw
   surfaceparm nolightmap
   surfaceparm nomarks
   surfaceparm slick

}

shows up as notexture. And I think it's because it's not in order or something. Also, it's just a hunch, but if its in subraces that that mean loop?
ex-

textures/*****/heart
{
   
   q3map_surfacelight 600
   {
      map textures/nintendo_land/heart.png
      blendfunc blend
   }
}

UniqPhoeniX

  • Spam Killer
  • *
  • Posts: 1376
  • Turrets: +66/-32
Re: Surfaceparm order?
« Reply #1 on: May 25, 2010, 09:34:08 pm »
EDIT: Umm...nvm.
I'm quite certain the order of surfaceparms doesn't matter. Where is the shader file? Don't you get any errors/warnings in console? Try removing the empty line after 'textures/*****/forcefeild'.
The stuff in sub-braces basically defines a layer of the shader, and you can have several layers drawn on top of each other.
« Last Edit: May 25, 2010, 10:00:22 pm by UniqPhoeniX »

MrFish

  • Posts: 201
  • Turrets: +16/-500
Re: Surfaceparm order?
« Reply #2 on: May 25, 2010, 11:20:01 pm »
shaders - /base/scripts/<file>
textures - /base/textures/...
map - /base/maps/...

Removed the line and nothing happened (whitespace is fine).

I did look at the warnings. I learned there is no surfaceparm "solid" :P


(all non-warning related messages removed)
Quote
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: Unknown surfaceparm: "solid"
WARNING: surface at ( -1311  -6016    320) (  1670  -6016   1472) too large for desired samplesize/lightmapsize/lightmapscale combination, increased samplesize from 16 to 24
WARNING: surface at ( -1311  -6016    -32) (  1670  -6016    320) too large for desired samplesize/lightmapsize/lightmapscale combination, increased samplesize from 16 to 24
WARNING: surface at (  1520  -3802   1536) (  3320  -1648   1536) too large for desired samplesize/lightmapsize/lightmapscale combination, increased samplesize from 16 to 18
WARNING: surface at (  1294  -3009   1536) (  3178  -1640   1536) too large for desired samplesize/lightmapsize/lightmapscale combination, increased samplesize from 16 to 18
WARNING: surface at (   512  -3802   1536) (  3320  -1648   1536) too large for desired samplesize/lightmapsize/lightmapscale combination, increased samplesize from 16 to 23
... 30 more of this same warning ...

I removed the solid surfaceparm and recompiled but no good.

UniqPhoeniX

  • Spam Killer
  • *
  • Posts: 1376
  • Turrets: +66/-32
Re: Surfaceparm order?
« Reply #3 on: May 25, 2010, 11:42:39 pm »
None of those warnings are related to it. Any warnings in tremulous console? Any chance of another shader file overwriting yours (/which scripts/filename.shader)? I assume you did add the shader file name to shaderlist.txt?... I can't think of anything else that might cause this. I assume radiant can find the shader?

MrFish

  • Posts: 201
  • Turrets: +16/-500
Re: Surfaceparm order?
« Reply #4 on: May 26, 2010, 12:03:50 am »
Quote
I assume you did add the shader file name to shaderlist.txt?

No i didn't, but all of my blendfuncs and even my skybox worked without this. But adding it to the shaderlist ended up fixing all of my existing problems! A little confused but happy nontheless!

Thanks again :D