-textureshadows not reading my lights.rad file correctly

Jan 20, 2010
1,317
902
I made my lights.rad file as I would normally, like so:

Code:
forcetextureshadow models/props_construction/construction_fence256.mdl
forcetextureshadow models/props_construction/construction_fence128.mdl
forcetextureshadow models/props_construction/construction_fence128_corner.mdl
forcetextureshadow models/props_construction/construction_fence512.mdl
forcetextureshadow models/props_construction/construction_fence64.mdl

However, when I compile it reads the file but seems to skip right over these lines. It seems to be exclusive to Construction Pack stuff too. So I'm really not sure what to do.

Anyone have any ideas?
 

YM

LVL100 YM
aa
Dec 5, 2007
7,135
6,056
Is it possible that it uses the same texture as models/props_doomsday/dd_woodfence_128.mdl ?? because I ran into issues with the doomsday wooden fences not working. I could get the coalmines ones working but not doomsday's

I have no idea why.

@Lampenpam models/ doesn't break it, my lights.rad uses models/ for every line and everything except the doomsday fences work
 
Jan 20, 2010
1,317
902
Is it possible that it uses the same texture as models/props_doomsday/dd_woodfence_128.mdl ?? because I ran into issues with the doomsday wooden fences not working. I could get the coalmines ones working but not doomsday's

I have no idea why.

@Lampenpam models/ doesn't break it, my lights.rad uses models/ for every line and everything except the doomsday fences work

I honestly have no idea. I can't seem to figure it out. This steampipe thing has been this way for like 2 years and we're still finding shit that is broken because of it. :|
 

Blade x64

Logical insanity
aa
Sep 3, 2009
239
633
It could be a case where vrad simply can't properly read in the textures, even with the model properly defined. I've had this issue on certain csgo props, where in the end I had to disable their shadows entirely. I'd suspect it has to do with the texture or model being different from what vrad likes.
 
Jan 20, 2010
1,317
902
It could be a case where vrad simply can't properly read in the textures, even with the model properly defined. I've had this issue on certain csgo props, where in the end I had to disable their shadows entirely. I'd suspect it has to do with the texture or model being different from what vrad likes.

They used to work just fine, though. When I'd compile back before SteamPipe it was perfect. Now... no dice. I'm not sure what specifically caused it.
 
Mar 23, 2013
1,013
347
I now remeber that once had the same problem with the same models from the construction pack. I thought my solution had to do with the "models/" in the rad file. I checked my vmf and appearently I didn't solve the problem, just disabled shadows and used block light for some parts.