View Issue Details

IDProjectCategoryView StatusLast Update
0004062DarkRadiantSound Systempublic07.01.2016 13:04
Reporterhypov8 Assigned Togreebo  
PrioritylowSeveritytextReproducibilityalways
Status closedResolutionfixed 
PlatformwindowsOS7OS Version32
Product Version2.0.2 
Target Version2.0.3Fixed in Version2.0.3 
Summary0004062: Slashes in sound shader names / shader file decls problematic
Descriptionthere was a previous bug 0003851
it would not load sound files with a forward slash
i am getting a simular error with the sound shader names

if i select a shader name like sounds/xx/123
it shows up in the entity window as just 123

if they are backslash, it uses the whole path, and uses this in entity window.
 
if it has forward slashes, its in a tree with + signs to expand the folder. then only its name is forwarded to entity window.
it will also not allow you to play the sound file

example shader

sound\world\city1
{
    minDistance 1
    maxDistance 15
    volume 1
    sound\world\city1
}
sound/world/city2
{
    minDistance 1
    maxDistance 10
    volume 1
    sound\world\city2
}

TagsNo tags attached.
Attached Files
sound_shdr.png (14,281 bytes)   
sound_shdr.png (14,281 bytes)   

Relationships

related to 0003851 closedgreebo Backslash in sound shaders fools DR 

Activities

Issue History

Date Modified Username Field Change
26.01.2015 02:42 hypov8 New Issue
26.01.2015 02:42 hypov8 File Added: sound_shdr.png
26.01.2015 04:03 greebo Relationship added related to 0003851
26.01.2015 04:03 greebo Summary sound shader names => Backslashes in sound shader names problematic
26.01.2015 04:15 greebo Summary Backslashes in sound shader names problematic => Slashes in sound shader names / shader file decls problematic
26.01.2015 04:16 greebo Status new => confirmed
27.01.2015 18:11 greebo Assigned To => greebo
27.01.2015 18:11 greebo Status confirmed => assigned
27.01.2015 18:11 greebo Target Version => 2.0.3
27.01.2015 18:12 greebo Status assigned => resolved
27.01.2015 18:12 greebo Fixed in Version => 2.0.3
27.01.2015 18:12 greebo Resolution open => fixed
07.01.2016 13:04 greebo Status resolved => closed