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 4675 - Direct3D renderer on Windows XP?
Summary: Direct3D renderer on Windows XP?
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: render (show other bugs)
Version: HG 2.0
Hardware: x86 Other
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords: target-2.0.12
Depends on:
Blocks:
 
Reported: 2019-06-18 23:05 UTC by Ryan C. Gordon
Modified: 2019-10-11 15:10 UTC (History)
0 users

See Also:

Attachments
screenshot (1.54 MB, image/png)
2019-10-11 15:07 UTC, Ryan C. Gordon 		Details
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 Ryan C. Gordon 2019-06-18 23:05:53 UTC 
Bug #4093 mentions that the Direct3D 9 renderer was rejected on Windows XP, falling back to OpenGL. See if this is still happening!

--ryan.
Comment 1 Ryan C. Gordon 2019-07-30 17:49:38 UTC 
(Sorry if you get several emails like this, we're marking a bunch of bugs.)

We're hoping to ship SDL 2.0.11 on a much shorter timeframe than we have historically done releases, so I'm starting to tag bugs we hope to have closed in this release cycle.

Note that this tag means we just intend to scrutinize this bug for the 2.0.11 release: we may fix it, reject it, or even push it back to a later release for now, but this helps give us both a goal and a wishlist for the next release.

If this bug has been quiet for a few months and you have new information (such as, "this is definitely still broken" or "this got fixed at some point"), please feel free to retest and/or add more notes to the bug.

--ryan.
Comment 2 Ryan C. Gordon 2019-09-20 20:47:34 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:43 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 4 Ryan C. Gordon 2019-10-11 15:07:59 UTC 
Created attachment 3982 [details]
screenshot


It definitely works now, if it didn't before!

--ryan.
Comment 5 Ryan C. Gordon 2019-10-11 15:08:28 UTC 
Closing bug.

--ryan.
Comment 6 Ryan C. Gordon 2019-10-11 15:10:57 UTC 
(For completeness, this was tested on a stock install of 32-bit _and_ 64-bit XP, patched to the latest service packs and patches that automatic updates offered. The VC2015 runtime was installed so testsprite2 would start, but that's all. 64-bit XP worked correctly with both 32-bit and 64-bit versions of testsprite2.)

--ryan.