- User Since
- Feb 21 2014, 11:05 AM (290 w, 4 d)
Tue, Sep 3
Wed, Aug 28
Tue, Aug 27
Jul 19 2019
By curiosity, I tried to use the config.ocio file from 2.80 in 2.79 and there is no issue while using the config file of 2.79 in 2.80 still have not identical render with the two files I've uploaded. It's then probably not related to the new ocio file and something has been broken in 2.80.
Hope it helps.
Jul 16 2019
The exposure/gamma setting make noise only when audio scrubbing is checked.
Indeed, I was reporting the bug on my laptop. Here is my working machine where it does the same for both issues:
Operating system: Linux-3.10.0-327.el7.x86_64-x86_64-with-centos-7.2.1511-Core 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77
Jul 11 2019
This is a different topic. I'm not talking about display result with Filmic that dipslay sRGB files less contrasted which is normal.
Jun 4 2019
May 7 2019
Aug 27 2018
May 8 2018
There is also two other issues related to the bl_app_templates_system folder if it is not placed into the Blender installation but in another folder and set to Blender when launched with env variable or --env-system-scripts: the template is not listed in the UI but the command bpy.ops.wm.read_homefile(use_splash=True, app_template="my_template") is switching to the right template except the __init__.py file which is not excecuted at all.
Apr 27 2018
Actually, there is still an issue. While being in a template, make a new file (CTRL+N) will set the default Blender instead of the default template (except if the user has save his local "config" prefs before).
Mar 22 2018
Thanks for the fix.
A template is already in production where I work and it seems to work very well in 2.79a.
Jan 31 2018
Oh sorry, I thought I did it.
Jan 12 2018
Sep 13 2017
I've tested it in the final 2.79 release and the issue is still there. bl_app_templates_system in the system path is not recognized.
Aug 21 2017
Still not working in RC2.
Aug 18 2017
Aug 14 2017
Feb 23 2017
Oh sorry for the bad report!
And thank you for the answer :)
Feb 22 2017
Jan 15 2017
Nov 2 2016
Sep 16 2016
Sep 8 2016
Ok, thanks. Good to know it's not a bug.
Unfortunately for our studio, we're using GP color layer only as an annotation tool in the VSE and we don't want to add complexity with color palette. If this is like that, we'll deal with it anyway! ;)
Jun 10 2016
Thank you so much! It's a lot more usable now and I already use it! :)
Jun 8 2016
Mar 15 2016
Yes this is with the default startup.blend.
Nov 21 2015
Sorry to have considered this as a bug.
Mar 31 2015
Mar 26 2015
Yes, it works with the last build.
Mar 19 2015
I've just tested the same file on another computer which is on Windows 7 and it doesn't crash.
Mar 14 2015
Feb 28 2015
Feb 15 2015
Yes it's working now fine with SDL 2.0 installed.
I will try to reproduce the issue I had on Windows and report it.
Feb 13 2015
Actually, it doesn't work that well in Windows either : if I have only one Blender open, the joystick is not recognized. If I launch a second Blender application, the Joystick is recognized the first time I run the BGE, but if I run it a second time, or more, it is not recognized anymore.
Sep 1 2014
Ok, I can explain more with an example file but I don't know how to modify my post or delete it to create a new one.
Aug 2 2014
Indeed, the problem is probably because of the drivers that has maybe changed on Ubuntu 14.04. I've tested back the 2.69 version of Blender on my updated Linux OS and this difference between Windows and Linux is also there. I hadn't this difference before on Ubuntu 12.04.
Jul 27 2014
Jun 5 2014
I have the same issue on Win7 64 with Blender 2.7. I cannot access to the network path (\\network\path\) unless it is mapped as a drive.