View Issue Details

IDProjectCategoryView StatusLast Update
0003179The Dark ModCodingpublic18.08.2012 06:30
ReporterSpringheel Assigned Toangua  
PrioritynormalSeveritynormalReproducibilityhave not tried
Status resolvedResolutionfixed 
Product VersionTDM 1.08 
Target VersionTDM 1.08 
Summary0003179: Light gem doesn't react to torches in Score to Settle
DescriptionThe torches still work properly in 1.07.

It seems to be related to the light shader, lights/fire_walltorch_falloff_exp3. When I remove the spawn arg from the torch, I get a bright light gem. Since the shader hasn't changed (it's been there since 2006), I'm suspecting that one of the render changes in the source are responsible.

"Haven't taken a look at the thread, but I assume it's being the light uses shaderParm4, it's a one line fix, but I don't have d3/a compiler/anything to test atm, just going on the material."

http://forums.thedarkmod.com/topic/13954-light-gem-doesnt-react-to-torches-in-score-to-settle-anymore/
TagsNo tags attached.

Activities

angua

angua

15.08.2012 16:29

manager   ~0004760

The line
    m_Lightgem_rv.time = gameLocal.GetTime();
was missing in lightgem.cpp, the render view was unable to see time dependant changes in light shaders such as the torch flickering.
Springheel

Springheel

17.08.2012 21:12

administrator   ~0004766

Looks like there are still cases that are not solved: http://forums.thedarkmod.com/topic/14003-testing-108/page__view__findpost__p__292835
angua

angua

18.08.2012 06:30

manager   ~0004767

Flicker table was mising.

Issue History

Date Modified Username Field Change
19.07.2012 13:24 Springheel New Issue
19.07.2012 13:24 Springheel Status new => assigned
19.07.2012 13:24 Springheel Assigned To => Serpentine
15.08.2012 16:19 angua Assigned To Serpentine => angua
15.08.2012 16:29 angua Note Added: 0004760
15.08.2012 16:29 angua Status assigned => resolved
15.08.2012 16:29 angua Resolution open => fixed
17.08.2012 21:12 Springheel Note Added: 0004766
17.08.2012 21:12 Springheel Status resolved => new
18.08.2012 06:30 angua Note Added: 0004767
18.08.2012 06:30 angua Status new => resolved