View Issue Details

IDProjectCategoryView StatusLast Update
0002737DarkRadiantRendererpublic11.10.2012 19:04
Reportergreebo Assigned Togreebo  
PrioritynormalSeveritynormalReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.6.0 
Target Version1.6.1Fixed in Version1.6.1 
Summary0002737: After starting DR in Lighting Mode, switching back to Textured mode crashes the app (debug build)
DescriptionDue to uninitialised values an openGL error is raised in GLSLBumpProgram::destroy(). Curiously the corresponding method GLSLBumpProgram::create() is not called when starting DR with Lighting mode enabled - hence the _programObj member is not initialised.
TagsNo tags attached.

Activities

greebo

greebo

22.04.2011 10:16

administrator   ~0003818

The problem is that during startup the render mode might be set to LIGHTING. This is bound to lead to problems though as the OpenGL context is not ready yet and the OpenGLRenderSystem cannot detect whether GLSL programs are available and will assume they're not. This causes the GLProgramFactory to never realise its program objects at startup time. Later on, when switching back to TEXTURED mode the rendersystem will attempt to destroy the GLSL objects, but they have never been created in the first place.

My solution will be to disable starting up in LIGHTING mode. If the registry says to start up in LIGHTING, I'll let the code force it back to TEXTURED.

Issue History

Date Modified Username Field Change
22.04.2011 09:46 greebo New Issue
22.04.2011 09:46 greebo Status new => confirmed
22.04.2011 09:46 greebo Summary After starting DR in Lighting Mode, switching back to Textured mode crashes the app => After starting DR in Lighting Mode, switching back to Textured mode crashes the app (debug build)
22.04.2011 10:14 greebo Assigned To => greebo
22.04.2011 10:14 greebo Status confirmed => assigned
22.04.2011 10:16 greebo Note Added: 0003818
22.04.2011 10:19 greebo Target Version => 1.6.1
22.04.2011 10:41 greebo Status assigned => resolved
22.04.2011 10:41 greebo Fixed in Version => 1.6.1
22.04.2011 10:41 greebo Resolution open => fixed
11.10.2012 19:04 greebo Status resolved => closed