- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 13 2019
Pushed new branch T26653-MasterIntegrationFixes.
All remaining issues solved by @maleike. I reintroduced the rendering mode preference but instead of switching between "Standard" (default, basically equivalent to "nothing") and "Depth Peeling" it now allows to switch between "No anti-aliasing" and "Fast Approximate Anti-Aliasing (FXAA)" (default). Depth peeling is always enabled as it only kicks in if there are translucent objects in the scene and in the worst case it is preferable to have not the fasted rendering instead of having a broken rendering. The future will show if we there is really a need to additionally add quality options regarding depth peeling.
I remember having seen this error but I thought I fixed it. Currently, I cannot reproduce it, using the latest master 8a6a7a85.
Could you give a precise description of the steps to take in order to reproduce this bug?
Nov 12 2019
Nov 11 2019
Nov 9 2019
Nov 8 2019
sorry that this took me a month to get to
this is due to radius behavior changes
Nov 7 2019
Pushed new branch T26797-redesignPAplugin.
Nov 6 2019
Pushed new branch T26796-openclindexfix.
Pushed new branch T26796-opencloversightfixed.
traced the error to the DAS.cl
Pushed new branch T26785-incluceCLtoolsInBuildConfig.
also occurs in clean build - in addition: opening the Workbench for the first time after build causes a crash
note that I did not use a clean build
Also PointSets have a similar problem with opacity now.
It works with the current master branch.