We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4779 - Direct3D 11: vertex buffer is always recreated
Summary: Direct3D 11: vertex buffer is always recreated
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: render (show other bugs)
Version: 2.0.10
Hardware: x86_64 Windows 10
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords: target-2.0.12
Depends on:
Blocks:
 
Reported: 2019-08-30 14:33 UTC by Alex
Modified: 2019-09-20 20:48 UTC (History)
0 users

See Also:

Attachments
Fixes render buffer recreation (509 bytes, patch)
2019-08-30 14:33 UTC, Alex 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2019-08-30 14:33:36 UTC 
Created attachment 3938 [details]
Fixes render buffer recreation

There is a line in the code missing. Because of that a new vertex buffer is created on each draw call. This reduces performance significantly.
Comment 1 Ryan C. Gordon 2019-09-02 04:14:32 UTC 
Good catch, this patch is now https://hg.libsdl.org/SDL/rev/44b0a095f4b7, thanks!

--ryan.
Comment 2 Ryan C. Gordon 2019-09-20 20:47:37 UTC 
We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).

As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!

Thanks,
--ryan.
Comment 3 Ryan C. Gordon 2019-09-20 20:48:40 UTC 
We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).

As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!

Thanks,
--ryan.