![]() It would be best if the problem is specific which can be established by testing. I just don't know, it seems it might have something to do with a palette change, but how/why does that cause it? But, that brings me back to what's causing the issue. Not that big a deal, since DOSBox needs a special compile of SDL in the first place, just put that fix in as well. But first, from what I'm reading, the problem isn't with DOSBox but with SDL. If I had a better grasp on what was causing the problem, maybe I could do something to fix it. Most of what I do is cut and paste code from other places. I'm not much of a programmer, just enough to alter code that already exists, and then only if it's not too complicated. It's not that I don't like the patch, it just that with it's age it no longer directly applies, and I don't understand the patch □ Maybe it's my meds or lack of sleep, but I can't seem to get a clear picture of what the problem is in the first place. You may submit your own patch if you don't like the other one. I tried setting an environment variable SDL_VIDEODRIVER=windib and that appeared to fix the problem, till I discovered that it killed scaling □ For some reason, scaling only works with ddraw for me, and with windib ddraw always "fails to create" the surface and switches to normal mode.Īnd, no, I just spent $200 upgrading to Windows 7 because I had to, I'm not spending another $200 to upgrade to an even worse OS for at least a year. Reading the thread it sounds like its caused by DOSBox changing the intro screen to red when switching to full screen. What exactly is causing the issue? Scanning the linked web site, it sound like it's caused by trying to change the entire palette. Not sure I want to risk making changes blind, when I don't understand the underlying problem in the first place. It won't apply automatically because the locations have changed, and when I find the locations manually, I find that the text has been changed too. Otherwise keep on false if you like the aspect ratio of your resolution setting.That thread is 5 years old, isn't there a better fix for this yet? The fix listed there (the diff patch file at least,) doesn't seem to apply any more. In the same way your desktop resolution like 1920x1080 will be converted to 1440x1080. If you've set a resolution with another aspect ratio, like 1280x480, this will be converted to 640x480. Change aspect=false to aspect=true if you run DOSBox in full screen mode (this maintains 4:3 aspect ratio.In some cases ddraw also has a lower CPU load. You might try output=ddraw if your hardware doesn't support OpenGL. Change output=surface to output=openglnb (uses graphics hardware and maintains crisp image with scaling).You can enter any resolution you want but remember that DOS games were made for screens with a 4:3 width/height aspect ratio. When using a window, change windowresolution=original to windowresolution=1280x960 (or use 1024x768 for a smaller window).Change fullresolution=original to fullresolution=desktop.Use fullscreen=false for DOSBox in a window.Windows 10 and Windows 11: Press the Windows key + Q, type in dosbox, and the options file DOSBox 0.7x Options should appear in the search results, click it.At startup, the window is also kind of small. With default settings, DOSBox in full screen looks blurry or fuzzy and squashed in case of wide screens. As most DOS games are made for screens with a resolution of 320x240 pixels, DOSBox needs to scale the image. Here at DOSGamers, we like our DOS games to look clear and just like the original. ![]() ![]() Changing the DOSBox resolution and image quality To enhance image quality, continue reading. Do this again, and you return to the DOSBox window. To use DOSBox in full screen, press the ALT key and, while pressing the ALT key, press the Enter key.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |