Use the official release of Dosbox then and you won't have that error pop up at all 😀

(and please try to get to the point more quickly when posting in topic specific forums, your text up there is kind of hard to read because it offers too much "useless" information in the beginning and that makes it hard to find where it gets relevant 😀)

[MOVED]

Nothing to do with DOSBox development. Probably a direct3D or driver related issue. You are not even using official DOSBox 0.72 but another build.

It seems that sometimes opening the shader file fails. I see you are not using the default config file...maybe this changes working directory and then the shader cannot be found. Can you try using the default config file?

If I had known this forum was gonna be this much fun, I would've joined long ago.

'Useless' information ???
How about 'useless' replies.
Since the 'official' dosbox doesn't implement DirectX in it's .conf, it's a pretty safe bet that the X1507 error will go away. And if you never get on a mustang, you probably won't get ever get bucked off, either. You will, however, get an error saying that 'direct3d' is not an output type, if you can imagine that.

Let's see...
Oh yeah, direct3D, driver issue...
Just about sums up the entire damn environment in a 'windows' box, wouldn't you say ???.
I don't care what's up on the display...dosbox...spreadsheets...browsers.. you name it. ALL screen output goes through the video card, ALL video cards require drivers, and ALL require DirectX of one color or another....so yeah, it's a direct3D, driver thing, along with everything else on a rig from the second you light it off.

With regards to whether my post related to dosbox 'development' or not, I would have thought that all the fine effort Gukikoza was putting into the 'build' was 'development'. I guess I stand corrected...Gulikoza must just be 'f######' around' with dosbox and not developing much of anything except bad habits, maybe. Just so you know, when I searched this forum initially for 'X1507' issues, The 'Dosbox Development' forum was the one that popped up in the results. The thread itself wasn't that illuminating...some folks encountered it, but no one seemed to have a definitive remedy. Gulikova replied that it was strange, but realey offered no more than that. So move the post any damn where you want to, but the dev forum was where the issue had already popped up. so it WAS a logical place to post, whether you agree or not. BTW, I DO run the official version of dosbox. I ALSO run the other builds cause it's just plain fun turnin' knobs and seeing what works and what don't.

Gulikoza....
Thanks for your reply. I will fool with it when I have more time.
Just let me say that in all other aspects your build works flawlessly for my games.
The ACES collection, Slipstream 5000, Wolf 3D
Every damn platformer under the sun and too many asteroid variants to mention.
Good work.

Like to stay longer and 'chew the fat', but duty calls.
I really enjoy this forum...sorry if I woke the baby.

Thanks to all the responders, enjoyed the lively banter.
Lookin' forward to more when I get back in out of the bushes.
(Did I mention how much fun this forum was ???)

Yes, the forums are fun, and no, not everything requires directx.

http://www.si-gamer.net/gulikoza/

NOTE: These builds are NOT supported by the DOSBox authors! If you have a problem they might or might not accept your bug report! Some of the features are still in development, they might not work on all systems! I do not accept any responsibility, the pre-compiled versions are available for your convenience only and will be updated when I feel like it 😀

'Useless' information ???
How about 'useless' replies.

the more useless information from you the more useless replies - quite simple relation there and it's up to you to limit this 😀

Since the 'official' dosbox doesn't implement DirectX in it's .conf, it's a pretty safe bet that the X1507 error will go away.

almost nothing to do wit the conf, but with the Dosbox code...

Oh yeah, direct3D, driver issue...
Just about sums up the entire damn environment in a 'windows' box, wouldn't you say ???.
I don't care what's up on the display...dosbox...spreadsheets...browsers.. you name it. ALL screen output goes through the video card, ALL video cards require drivers, and ALL require DirectX of one color or another....so yeah, it's a direct3D, driver thing, along with everything else on a rig from the second you light it off.

As wd writes not everything requires DirectX or, according to your logic, you wouldn't even need Gulikoza's build...

Why do you even need DirectX support? Are the games you want to run behaving better/faster?

Please see this thread Re: Direct3D patch