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 4660 - Direct3D vs SetLogical
Summary: Direct3D vs SetLogical
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: render (show other bugs)
Version: HG 2.0
Hardware: All Windows 10
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords: target-2.0.10
Depends on:
Blocks:
 
Reported: 2019-06-09 01:45 UTC by Ryan C. Gordon
Modified: 2019-06-11 18:49 UTC (History)
0 users

See Also:

Attachments
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-09 01:45:37 UTC 
I don’t have a lot of details about this other than I ran into it recently. It looks like changing the tenderer logical size fails on Direct3D 9 if you do it mid-frame. For example, if you are drawing to a specific size, but turn off logical scaling to render text at full resolution, rendering will fail. Setting the logical size and leaving it alone seems to work though, so it’s some state change issue. D3d11 untested.

Might be simple, need to trace through it.

--ryan.
Comment 1 Ryan C. Gordon 2019-06-09 02:33:49 UTC 
I bet this is the same issue as Bug #4459...
Comment 2 Ryan C. Gordon 2019-06-11 18:49:02 UTC 
This is working now, a likely dupe of Bug #4459.

--ryan.