campvis-public issueshttps://gitlab.lrz.de/CAMP/campvis-public/-/issues2017-12-03T17:14:26+01:00https://gitlab.lrz.de/CAMP/campvis-public/-/issues/1Fix colorspace GLSL shader2017-12-03T17:14:26+01:00Ghost UserFix colorspace GLSL shaderThe `colorspace.frag` utility shader has some broken implementations of the color space conversions. The exact problem is not yet determined, however RGB->XYZ->Lab->XYZ->RGB is no perferct roundtrip if you change for instance the a-compo...The `colorspace.frag` utility shader has some broken implementations of the color space conversions. The exact problem is not yet determined, however RGB->XYZ->Lab->XYZ->RGB is no perferct roundtrip if you change for instance the a-component in Lab space.
This needs to be evaluated in detail - perhaps we need additional gamma adjustment - I saw that in some demo code snippets.
https://gitlab.lrz.de/CAMP/campvis-public/-/issues/7Sharing render output between two canvases is broken2017-12-03T17:14:26+01:00Ghost UserSharing render output between two canvases is brokenWhen creating two pipelines sharing the same dataContainer having the same `_renderTargetID`, the sharing of the render output is broken.
1. When interacting with one pipeline, the output of the other does not get updated (setPipelineDi...When creating two pipelines sharing the same dataContainer having the same `_renderTargetID`, the sharing of the render output is broken.
1. When interacting with one pipeline, the output of the other does not get updated (setPipelineDirty() is not called, missing onDataContainerAdded overload in AbstractPipeline)
2. Even if that is added, the other canvas often just shows a black screen.https://gitlab.lrz.de/CAMP/campvis-public/-/issues/8Tabbed View Inspector resize issue2017-12-03T17:14:26+01:00Ghost UserTabbed View Inspector resize issueWhile using the tabbed display option, there are weird issues with the render result sizes.
At least one bug occurs: the DataContainerInspector still shows the old RenderData size of the window prior to switching to tabbed mode.
While using the tabbed display option, there are weird issues with the render result sizes.
At least one bug occurs: the DataContainerInspector still shows the old RenderData size of the window prior to switching to tabbed mode.
https://gitlab.lrz.de/CAMP/campvis-public/-/issues/9GPU memory leak when multiple OpenGL contexts are active2017-12-03T17:14:26+01:00Ghost UserGPU memory leak when multiple OpenGL contexts are activeAs soon as they are multiple OpenGL contexts active at the same time, GPU memory leaks occur because some textures are not deleted correctly anymore.
According to early debugging sessions, `glDeleteTextures()` is called correctly. How...As soon as they are multiple OpenGL contexts active at the same time, GPU memory leaks occur because some textures are not deleted correctly anymore.
According to early debugging sessions, `glDeleteTextures()` is called correctly. However, the GPU memory is not freed as the memory monitor of GPU-Z suggests (as well as the general performance). As soon, as I manually make that call exclusive/synchronized, the memory leak seems to not occur again.
[This article](https://www.opengl.org/wiki/Memory_Model) is not too specific how OpenGL handles concurrent deletion of textures/buffers. However, we definitely take care of correct thread-context management. It might be a nVidia driver bug as well... :/