ykhwong wrote:

There will be little support for the unofficial CVS builds.

That said, I continue to have this problem as well, despite the fixes in the latest build, with a "failed to reset device" error on exit. I note the English board on Daum Cafe seems to no longer be there, and I hope it's not because of people haranguing him about it, since I know it was mentioned a lot after the previous build.

Does my build work or are there also problems?

23.06.07 worked fine for me with an identical config. I do get "SDL:D3D:Cannot Lock Texture, fallback to compatible mode" whenever I start either build, though.

It must be the menu or an incompatibility with some other patch then...

That is the incompatibility with menu patch if dosbox crashes with fullscreen+direct3d.
Set output to direct3d in configfile and use "-nogui -fullscreen" for dosbox.exe.
Though it could be just a temporary fix, it should work. I am trying to make it work, but no success.

I'm not familiar with the gui code, but can't you disable gui for fullscreen? 😀

@Targaff: that's just a fix for Windows 2000. You do have w2k, right? 😀 It's nothing to worry about...

Disabling GUI for fullscreen did not work. Using sdl_windowid for menu bar patch, it is programed: when going to fullscreen, sdl_windowid is unset while the sdl_windowid is set when going back to window.
You can find some "winid_chk();" in sdlmain.cpp. (see menu patch thread in the beta tesing forum) I am still trying to find another way... 😀

Thanks for the switches, ykhwong, they worked fine - actually you can ALT-ENTER to fullscreen if you don't use -fullscreen to start (though I do still get a crash if you try the other direction - "Exit to error: could not set video mode 640x400-32: Couldn't get user specified window"; dunno if that's any help in finding where the problem lies?)

gulikoza: yeah, w2k. I figured since I got it regardless of the build that it wasn't an issue, I just didn't understand it 😉

Edit: actually I seem to get that error coming out of fullscreen regardless of what output I'm using...

Fixed.

Many thanks!

Been awol for a bit, come back to update on this and it's already FIXED! Thank you all for helping, especially ykhwong for a quick fixed build. Will test it after work tonight and give feedback here.

Tested Direct3D with the new build. Works flawlessly now, can Alt+Enter in and out as I want, even switch shaders on the fly with the menu. Thank you for that.
However I saw virtually no improvement over using output=surface and HQ2X scaler. Is this normal? I would have assmued that offloading the scaling operation to the GPU would free up a good few CPU cycles to run the actual game?

I tried direct3d scaler normal2x with various shaders, and it didn't make any difference in performance from surface and hq2x. 😒

Depends on the graphic intensity of the game (how many times it refreshes the screen...)
Also be sure not to use normal2x with shaders. Normal2x implies a software 2x stretch before the pixelshaders...

Is there a way to use direct3d to scale in windowed mode then? a 320x200 window is rather small, and hard to see. aDn some things are handy to play windowed.

windowresolution= 😀

In my builds, I also have a hardware2x scaler, which is the same as normal2x, but uses hardware stretching where available...

Ok... Something is definitely fishy. ykhwong's new build that I played an hours worth of Ultima Underworld on earlier, now has the exact same problem as before. Crashes when going to fullscreen, direct3d just doesn't work at all. get failed to reset device errors several times in the output console window.

Not touched the conf file, not done anything strange to my PC at all. It just stopped.

[edit]
It seems to "work" intermittently, once every few times it works and I can go to full screen. Very rarale does it allow me to go back to windowed without crashing tho.

By "work" I mean it does nothing at all.
When I use ouput surface, original resolutions and scaler hq2x I get nice upscaling as you'd expect.

When I chose direct3d, hq2x.fx shader, and no scaler, it doesn't matter if I use original resolution or set a specific one, I get the original jagged edge low resolution, no difference at all. Very odd.