Closed
Bug 614111
Opened 14 years ago
Closed 14 years ago
Direct3D 9 (non-ex) Devices cannot be reset
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | beta8+ |
People
(Reporter: bas.schouten, Assigned: bas.schouten)
References
Details
Attachments
(1 file, 1 obsolete file)
|
4.22 KB,
patch
|
jrmuizel
:
review+
|
Details | Diff | Splinter Review |
For a while now we've had D3D9 devices use a VertexBuffer in D3DPOOL_DEFAULT. This is fine but it means the buffer needs to be released and recreated when a device reset is performed on a non D3D9-ex device (for example after screenlock), otherwise the device reset will fail and we will consider the device lost beyond hope and recreate all layer managers.
Attachment #492482 -
Flags: review?(jmuizelaar)
| Assignee | ||
Comment 2•14 years ago
|
||
Add missing return true.
Assignee: nobody → bas.schouten
Attachment #492482 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #492482 -
Flags: review?(jmuizelaar)
Comment 3•14 years ago
|
||
sounds like we need to change this from nominated for 2.0 to blocking beta8 to reduce the volume of the #1 top crash on trunk (bug 611597).
Comment 4•14 years ago
|
||
Can we just used D3DPOOL_MANAGED to avoid loosing the vertex buffer on device reset?
Updated•14 years ago
|
blocking2.0: ? → beta8+
Updated•14 years ago
|
Attachment #492489 -
Flags: review+
| Assignee | ||
Comment 5•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•