Jump to content
The Dark Mod Forums

old_worn_greybrick broke?


Fidcal

Recommended Posts

There's an error in one of the material files. In tdm_stone_brick.mtr the def for..

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick

 

the diffuse map I think should be...

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick_tiling_1d

 

...and I presume the def name too. The dds file is there. But when I tried changing the def then I get a leak so it's beyond my understanding at the moment! Can someone fix this for me? It appears OK in Dark Radiant, the ed tga version is OK.

Link to comment
Share on other sites

the diffuse map I think should be...

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick_tiling_1d

 

The filename would either have the name extension (tiling_1d) OR be in a tiling_1d folder, but not both. I think it's the former.

Link to comment
Share on other sites

Yes, that fixed it thanks - it was the folder. Should I commit this? This is the original...

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick
{
stone

qer_editorimage textures/darkmod/stone/brick/old_worn_greybrick_ed_tiling_1d
bumpmap		 textures/darkmod/stone/brick/old_worn_greybrick_local_tiling_1d
diffusemap	  textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick

{
	if ( parm11 > 0 )
	blend	   gl_dst_color, gl_one
	map		 _white
	rgb		 0.40 * parm11
}
{
	if ( parm11 > 0 )
	blend	   add
	map		 textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick
	rgb		 0.15 * parm11
}
}

This is my changed version......

 

// Author: Gleeful
textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d
{
stone

qer_editorimage textures/darkmod/stone/brick/old_worn_greybrick_ed_tiling_1d
bumpmap		 textures/darkmod/stone/brick/old_worn_greybrick_local_tiling_1d
diffusemap	  textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d
{
	if ( parm11 > 0 )
	blend	   gl_dst_color, gl_one
	map		 _white
	rgb		 0.40 * parm11
}
{
	if ( parm11 > 0 )
	blend	   add
	map		 textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d
	rgb		 0.15 * parm11
}

Link to comment
Share on other sites

Don't change the actual name of the material. The material name includes /tiling_1d/ so that the texture will be organized in a 'tiling_1d' folder by DR.

 

You can commit the change to the actual diffusemap filepath, however, thanks.

Link to comment
Share on other sites

OK - I think the top line is the material name? Changed it to...

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick

 

But that broke it again. Next tried...

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick_tiling_1d

 

But that fails also. Shader not found. Should I create a folder and move the dds file in there. And if so, should I change its name from

 

old_worn_greybrick_tiling_1d.dds to old_worn_greybrick.dds

Link to comment
Share on other sites

I don't know what you mean. If the texture paths are correct, then the shader will work properly, regardless of what the name of it is. You might get a shader not found error if your map points to a different name than the one on the material entry, but that's the map's fault.

Link to comment
Share on other sites

The diffusemap was wrong (as Fidcal reported in the first post),

 

Right, but that shouldn't have any affect on the material name.

Link to comment
Share on other sites

OK now. What happened was that the old path still showed in DR (presumably because it was still on the brush) and the new folder was right at the end under T and I had assumed the Windows convention and was looking at the start. Now committing the new material file...

 

Error: Commit failed (details follow):

Error: Your file or directory 'tdm_stone_brick.mtr' is probably out-of-date

Error: The version resource does not correspond to the resource within the transaction. Either the requested version resource is out of date (needs to be updated), or the requested version resource is newer than the transaction root (restart the commit).

 

Nothing is easy :)

Link to comment
Share on other sites

The commit failed, because I uploaded the corrected file in the meantime, so SVN recognised yours as "out of date". To resolve this, you usually start an SVN Update which reports the files in conflicing state, Tortoise lets you choose the version you want to use when you right-click on the offending file (marked in red).

Link to comment
Share on other sites

As if that ain't enough although it shows OK in DR but in doom I get...

 

WARNING: ******* leaked *******

WARNING: Couldn't load image: textures/darkmod/stone/brick/tiling_1d/old_worn_

greybrick

 

And it seems to leak right through the texture.

 

So it seems to me likely that top line is used by Doom not just DR? and should be...

 

textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick_tiling_1d

 

Saved it. Reloaded Doom. Dmap...

 

WARNING: ******* leaked *******

WARNING: Couldn't load image: textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick

 

'old_worn_greybrick' without also '_tiling_1d' is not used anywhere in the def so don't know where it is getting that from. Path too long?

Link to comment
Share on other sites

Just as well the commit failed if the def is still not right This is the whole thing. The first line, as said I have tried without the end _tiling_1d and it still fails. I've been over and over it and can't see what I've done wrong...

// Author: Gleeful
textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick_tiling_1d
{
stone

qer_editorimage textures/darkmod/stone/brick/old_worn_greybrick_ed_tiling_1d
bumpmap		 textures/darkmod/stone/brick/old_worn_greybrick_local_tiling_1d
diffusemap	  textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d

{
	if ( parm11 > 0 )
	blend	   gl_dst_color, gl_one
	map		 _white
	rgb		 0.40 * parm11
}
{
	if ( parm11 > 0 )
	blend	   add
	map		 textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d
	rgb		 0.15 * parm11
}
}

Link to comment
Share on other sites

It works on my end, I just checked using a test room with that texture.

 

Did you restart DarkRadiant (or at least Flushed & Reloaded the shaders)? Doom must also be restarted for the changes to take effect. Make sure you have the latest SVN revision of the .mtr file (hit SVN > Revert if it's marked red or delete it and redownload it).

 

When the image is missing the map compiler might report leaks, this will go away as soon as the image is found again.

Link to comment
Share on other sites

No, I give up now till tomorrow. I've spent hours on this now. I've updated from the SVN the material file and the entire dds brick folder in case the filename of the dds has also been changed. No it hasn't. It is still old_worn_greybrick_tiling_1d.dds and there is no new old_worn_greybrick.dds.

 

. I no longer get the leak error

. It shows correctly in DR

.Yes I have many times closed both Doom and DR and re-opend them.

 

I still get WARNING: Couldn't load image: textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick (I'm not surprised since there is no such file; I'm just surprised it works for you.)

 

The map now plays but the texture is black (and it is well lit)

 

I cannot understand how it can refer to a old_worn_greybrick when there is no such file yet this is now your mtr file not mine...

 

diffusemap textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick

 

The only file in the dds brick folder is old_worn_greybrick_tiling_1d

 

Next I am looking to see if the 'virtual' foldere 'tiling_1d had now become a real folder on the drive. No it hasn't. And I have updated the whole brick folder.

 

It's not April 13th and you're.. no...

 

I'll sleep on it. :)

Link to comment
Share on other sites

Couldn't load image: textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick (I'm not surprised since there is no such file

 

When the editor refers to 'images' it is actually refering to the material name (the first line of the material entry). So if your material file has an entry called "textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick" then it should be loading it. If the actual FILE is misnamed or missing, then you won't get that message but you'd get a black (or otherwise distorted) wall.

Link to comment
Share on other sites

No, there's nothing left to commit for me, it was only the diffusemap link that was wrong. The files and folders are all correct - I have the same files as in the repository.

 

Let's check the contents of your folders: This is my DDS folder darkmod\dds\textures\darkmod\stone\brick, it should contain the diffusemap file old_worn_greybrick_tiling_1d.dds.

 

The shader is defined in tdm_stone_brick.mtr and should look exactly like this:

// Author: Gleeful
textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick
{
stone

qer_editorimage textures/darkmod/stone/brick/old_worn_greybrick_ed_tiling_1d
bumpmap		 textures/darkmod/stone/brick/old_worn_greybrick_local_tiling_1d
diffusemap	  textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d

{
	if ( parm11 > 0 )
	blend	   gl_dst_color, gl_one
	map		 _white
	rgb		 0.40 * parm11
}
{
	if ( parm11 > 0 )
	blend	   add
	map		 textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d
	rgb		 0.15 * parm11
}
}

 

Are you sure the material file tdm_stone_brick.mtr is marked green on your end (no local changes)?

Link to comment
Share on other sites

Yesterday evening it had a red exclamation I think it was because I had changed it. Then I did an update and it changed to green. But the diffusemap is shown as...

 

diffusemap textures/darkmod/stone/brick/tiling_1d/old_worn_greybrick

 

That seems to be the error and yet that error only appeared after I updated! If you look back in this thread you see my version had it correct...

 

diffusemap textures/darkmod/stone/brick/old_worn_greybrick_tiling_1d

 

I'll check it all again after breakfast :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recent Status Updates

    • nbohr1more

      The FAQ wiki is almost a proper FAQ now. Probably need to spin-off a bunch of the "remedies" for playing older TDM versions into their own article.
      · 1 reply
    • nbohr1more

      Was checking out old translation packs and decided to fire up TDM 1.07. Rightful Property with sub-20 FPS areas yay! ( same areas run at 180FPS with cranked eye candy on 2.12 )
      · 3 replies
    • taffernicus

      i am so euphoric to see new FMs keep coming out and I am keen to try it out in my leisure time, then suddenly my PC is spouting a couple of S.M.A.R.T errors...
      tbf i cannot afford myself to miss my network emulator image file&progress, important ebooks, hyper-v checkpoint & hyper-v export and the precious thief & TDM gamesaves. Don't fall yourself into & lay your hands on crappy SSD
       
      · 7 replies
    • OrbWeaver

      Does anyone actually use the Normalise button in the Surface inspector? Even after looking at the code I'm not quite sure what it's for.
      · 7 replies
    • Ansome

      Turns out my 15th anniversary mission idea has already been done once or twice before! I've been beaten to the punch once again, but I suppose that's to be expected when there's over 170 FMs out there, eh? I'm not complaining though, I love learning new tricks and taking inspiration from past FMs. Best of luck on your own fan missions!
      · 4 replies
×
×
  • Create New...