| Anonymous | Login | Signup for a new account | 2013-05-25 09:01 PDT |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0001229 | LuxRender | LuxBlend | public | 2012-05-11 16:09 | 2012-08-06 04:50 | ||||
| Reporter | gazzatav | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | crash | Reproducibility | random | ||||
| Status | closed | Resolution | not fixable | ||||||
| Platform | amd 64bit | OS | Ubuntu | OS Version | 11.04 | ||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0001229: v1.0rc luxblend panel becomes unusable | ||||||||
| Description | On occasion the Luxblend panel in Blender becomes a set of empty dropdown menus and it is necessary to restart Blender again to get Luxblend working. | ||||||||
| Steps To Reproduce | Seems to happen at random, most lately when I started to create a new matte material for the luxball.blend file. had just chosen a diffuse colour when it happened. | ||||||||
| Additional Information | attached screenshot shows panel after crash. Solution: use a Blender 2.62 or later ( 2.63 ? not 100% sure ) | ||||||||
| Tags | No tags attached. | ||||||||
| Mercurial Changeset # | 3661:2cac701 | ||||||||
| Requires Documentation Update | No | ||||||||
| Requires Exporter Update | |||||||||
| Attached Files |  luxrenderfailcrop.png [^] (57,330 bytes) 2012-05-11 16:09
| ||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0003393) SATtva (developer) 2012-05-11 23:04 |
This is a known problem with Blender API which gets provoked when you change some property really fast like dragging a color picker with a mouse. Some concurrency issue i guess (especially since it's really hard to reproduce). The easiest way to avoid it or make really unlikely to happen is to input values by hand or at least not drag sliders and color pickers. I'm not sure whether we should close the bug since it's not directly related to LuxBlend. Maybe LordCrd could once again try to debug Blender internals? |
|
(0003510) jensverwiebe (developer) 2012-08-06 04:44 edited on: 2012-08-06 04:47 |
The question here is not what luxblend/pylux was used, but the Blender version. Recent changes in api after 2.62 ( if i remember right ) should completely overcome this issue. This bug can be closed, i added a Blender recommendation in top information. Jens |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-05-11 16:09 | gazzatav | New Issue | |
| 2012-05-11 16:09 | gazzatav | File Added: luxrenderfailcrop.png | |
| 2012-05-11 23:04 | SATtva | Note Added: 0003393 | |
| 2012-08-06 04:44 | jensverwiebe | Note Added: 0003510 | |
| 2012-08-06 04:47 | jensverwiebe | Note Edited: 0003510 | View Revisions |
| 2012-08-06 04:50 | jensverwiebe | Status | new => closed |
| 2012-08-06 04:50 | jensverwiebe | Resolution | open => not fixable |
| 2012-08-06 04:50 | jensverwiebe | Additional Information Updated | View Revisions |
|
Issue History |
| Copyright © 2000 - 2012 MantisBT Group |
 |