I have a virtual XP station at work that I do all my programming
(easier to “reset” or quickly remove if needed)
I’m using the latest VirtualBox.
SDL 1.2 runs great. “Native” speeds.
But when I try to run some of the tests from 1.3 I get the same error:
Couldn’t create texture: CreateDevice(): NOTAVAILABLE
While it isn’t that big of a deal I was just wondering if there is a reason why
SDL doesn’t fall back to using the old software renderer, or at least something
similar.
If it doesn’t do it automatically, is there a way to test for it and make the
needed adjustments programmatically?
It does have a software fallback, so I’m not sure why it’s failing.
I’m looking at this now.On Thu, Nov 5, 2009 at 8:32 AM, Micah Brening <micah.brening at gmail.com> wrote:
Hello Everyone!
I have a virtual XP station at work that I do all my programming
(easier to “reset” or quickly remove if needed)
I’m using the latest VirtualBox.
SDL 1.2 runs great. ?“Native” speeds.
But when I try to run some of the tests from 1.3 I get the same error:
Couldn’t create texture: CreateDevice(): NOTAVAILABLE
While it isn’t that big of a deal I was just wondering if there is a reason why
SDL doesn’t fall back to using the old software renderer, or at least something
similar.
If it doesn’t do it automatically, is there a way to test for it and make the
needed adjustments programmatically?
Thanks!On Thu, Nov 5, 2009 at 8:32 AM, Micah Brening <micah.brening at gmail.com> wrote:
Hello Everyone!
I have a virtual XP station at work that I do all my programming
(easier to “reset” or quickly remove if needed)
I’m using the latest VirtualBox.
SDL 1.2 runs great. ?“Native” speeds.
But when I try to run some of the tests from 1.3 I get the same error:
Couldn’t create texture: CreateDevice(): NOTAVAILABLE
While it isn’t that big of a deal I was just wondering if there is a reason why
SDL doesn’t fall back to using the old software renderer, or at least something
similar.
If it doesn’t do it automatically, is there a way to test for it and make the
needed adjustments programmatically?
On Thu, Nov 5, 2009 at 8:32 AM, Micah Brening <@Micah_Brening> wrote:
Hello Everyone!
I have a virtual XP station at work that I do all my programming
(easier to “reset” or quickly remove if needed)
I’m using the latest VirtualBox.
SDL 1.2 runs great. ?“Native” speeds.
But when I try to run some of the tests from 1.3 I get the same error:
Couldn’t create texture: CreateDevice(): NOTAVAILABLE
While it isn’t that big of a deal I was just wondering if there is a reason why
SDL doesn’t fall back to using the old software renderer, or at least something
similar.
If it doesn’t do it automatically, is there a way to test for it and make the
needed adjustments programmatically?
On Thu, Nov 5, 2009 at 8:32 AM, Micah Brening <> wrote:
Quote:
Hello Everyone!
I have a virtual XP station at work that I do all my programming
(easier to “reset” or quickly remove if needed)
I’m using the latest VirtualBox.
SDL 1.2 runs great. “Native” speeds.
But when I try to run some of the tests from 1.3 I get the same error:
Couldn’t create texture: CreateDevice(): NOTAVAILABLE
While it isn’t that big of a deal I was just wondering if there is a reason
why
SDL doesn’t fall back to using the old software renderer, or at least
something
similar.
If it doesn’t do it automatically, is there a way to test for it and make
the
needed adjustments programmatically?