| 2017-03-11 21:37:55 |
ellie |
bug |
|
|
added bug |
| 2017-03-11 21:37:55 |
ellie |
attachment added |
|
Edited basic.py shadows example to trigger the bug https://bugs.launchpad.net/bugs/1672092/+attachment/4836119/+files/basic.py |
|
| 2017-03-11 21:39:25 |
ellie |
attachment added |
|
Screenshot showing the corrupted shadow after triggering the bug https://bugs.launchpad.net/panda3d/+bug/1672092/+attachment/4836120/+files/Screenshot%20from%202017-03-11%2022-30-52.png |
|
| 2017-03-11 21:39:54 |
ellie |
description |
Using setShadowCaster(True, some_res, some_res) on a light that was created a while ago appears to lead to shadow bugs.
This seems to manifest in various inpredictable ways:
In my actual big project where I first noticed a potential issue, some objects simply stopped throwing a shadow even though I changed absolutely nothing else except just calling setShadowCaster(True, some_new_res, some_new_res) later a while after the light was created.
I then edited the basic shadow example (basic.py) as attached, to reproduce this issue.
In my minimal edit of the basic shadow example as attached, it seems to corrupt the shadow texture in some way (see screenshot attached) and it breaks 'v' which shows nothing as if either it was entirely bugged out or as if it had no buffers to show despite the light obviously using SOME sort of buffer still. If you comment out line 134, where I schedule the bug-introducing task, everything works fine again. |
Using setShadowCaster(True, some_res, some_res) with a resolution different than the initial shadow map resolution the light was created with, on a light that was created a while ago appears to lead to shadow bugs.
This seems to manifest in various inpredictable ways:
In my actual big project where I first noticed a potential issue, some objects simply stopped throwing a shadow even though I changed absolutely nothing else except just calling setShadowCaster(True, some_new_res, some_new_res) later a while after the light was created.
I then edited the basic shadow example (basic.py) as attached, to reproduce this issue.
In my minimal edit of the basic shadow example as attached, it seems to corrupt the shadow texture in some way (see screenshot attached) and it breaks 'v' which shows nothing as if either it was entirely bugged out or as if it had no buffers to show despite the light obviously using SOME sort of buffer still. If you comment out line 134, where I schedule the bug-introducing task, everything works fine again. |
|
| 2017-03-11 21:40:03 |
ellie |
description |
Using setShadowCaster(True, some_res, some_res) with a resolution different than the initial shadow map resolution the light was created with, on a light that was created a while ago appears to lead to shadow bugs.
This seems to manifest in various inpredictable ways:
In my actual big project where I first noticed a potential issue, some objects simply stopped throwing a shadow even though I changed absolutely nothing else except just calling setShadowCaster(True, some_new_res, some_new_res) later a while after the light was created.
I then edited the basic shadow example (basic.py) as attached, to reproduce this issue.
In my minimal edit of the basic shadow example as attached, it seems to corrupt the shadow texture in some way (see screenshot attached) and it breaks 'v' which shows nothing as if either it was entirely bugged out or as if it had no buffers to show despite the light obviously using SOME sort of buffer still. If you comment out line 134, where I schedule the bug-introducing task, everything works fine again. |
Using setShadowCaster(True, some_res, some_res) with a resolution different than the initial shadow map resolution the light was created with, on a light that was created a while ago appears to lead to shadow bugs.
This seems to manifest in various unpredictable ways:
In my actual big project where I first noticed a potential issue, some objects simply stopped throwing a shadow even though I changed absolutely nothing else except just calling setShadowCaster(True, some_new_res, some_new_res) later a while after the light was created.
I then edited the basic shadow example (basic.py) as attached, to reproduce this issue.
In my minimal edit of the basic shadow example as attached, it seems to corrupt the shadow texture in some way (see screenshot attached) and it breaks 'v' which shows nothing as if either it was entirely bugged out or as if it had no buffers to show despite the light obviously using SOME sort of buffer still. If you comment out line 134, where I schedule the bug-introducing task, everything works fine again. |
|
| 2017-03-14 00:05:53 |
ellie |
panda3d: status |
New |
Fix Committed |
|
| 2019-01-10 11:53:47 |
rdb |
panda3d: status |
Fix Committed |
Fix Released |
|
