Page 1 of 1

FIXED: GLSL compile problems with locked DATs 2018.25850

PostPosted: Tue Oct 02, 2018 12:45 pm
by DavidBraun
Windows 2018.25850

I can encounter false positives and false negatives when locking dats that are used as pixel shaders for GLSL Multis. I lock the dat when the shader's working, make a modification that should break it, but it remains compiled. I can also start with an invalid shader, lock it, correct it, but it remains broken.

2018-10-02 11_38_29-TouchDesigner_ C__Users_david.braun_Desktop_GLSL_Compile_bug.1.toe.png
2018-10-02 11_38_29-TouchDesigner_ C__Users_david.braun_Desktop_GLSL_Compile_bug.1.toe.png (133.89 KiB) Viewed 990 times

2018-10-02 11_39_09-TouchDesigner_ C__Users_david.braun_Desktop_GLSL_Compile_bug.1.toe_.png
2018-10-02 11_39_09-TouchDesigner_ C__Users_david.braun_Desktop_GLSL_Compile_bug.1.toe_.png (67.72 KiB) Viewed 990 times

GLSL_Compile_bug.1.toe
(3.74 KiB) Downloaded 48 times

Re: GLSL compile problems with locked DATs 2018.25850

PostPosted: Thu Oct 04, 2018 10:41 pm
by ben
Thanks, we're looking at it.

Re: GLSL compile problems with locked DATs 2018.25850

PostPosted: Thu Oct 11, 2018 9:54 am
by malcolm
This is now fixed, sorry about that. Thanks for the report! Build 2018.26540 or later.