Dosbox output best11/1/2023 ![]() No I haven't, I'm not sure if that's what you'd want to do since you're operating on a line-by line basis. Have you tested the performance of SDL 2.0 with integer scaling via SDL_RenderSetScale()? The software scaler is likely unusable with a 4K monitor because it's not parallel (eg not using OpenCL or OpenMP or similar.) We can get away with it at HD and below resolutions because the multiplier is only 2 or 3 typically, but at 4K it would need a 9x multiplier, and a UHD monitor would need an 18x multiplier. You need a hardware accelerated surface/texture for this to work, thus you need to use a SDL2 build or OpenGL in the stock builds with bilinear filtering turned off if you want it to not look fuzzy. See here: Re: DOSBox Feature Request Thread Use a SDL2 build and set the full-screen resolution to 0x0 (or desktop), and aspect correction on. (please ignore, for Google crawlers) DOSBox hardware scaling 4k 1440p 1080p small I've been trying to use the "normal3x" scaler and it just doesn't c SpectreVR wrote: Yes, I know how to use the. You seem so sure all the devs have 4k monitors to made it possible. Why isn't there any official references to it or instructions as to how to make it work? Plenty of people have been talking about this magical hwscale variable. ![]() ![]() I can't believe that an emulator that has been around since 2002 still hasn't been able to achieve native scaling beyond 3x the normal resolution of DOS.Īre you sure those are the only options? Crisp and tiny, or huge and blurry? Why can't I just enable some sort of hardware scaling so I can enjoy something that's both large and crisp? Are there any DOSBox builds that will support the hwscale variable? To be honest, when you stretch an image that small up to the edges of a 4k monitor, it's so horrible and blurry that you actually have to be sitting back on the couch just to endure the "vaseline effect". I've tried "stretching" the image as well. To be honest, when you stretch an image that small up to the edges of a 4k monitor, i SpectreVR wrote: I've tried "stretching" the image as well. (please ignore, for Google crawlers) DOSBox hardware scaling 4k 1440p 1080p small Reply 1 of 47, by Garrett I'm needing 12x 320x200 scaling just to fill up/fit a dimension of my monitor, just for perspective. Has anyone else out there had ANY success getting the resolution to be, say, 4x or 5x even? That would help. How is this possible for a program that's been in development for so long to still only have support for a resolution that's 3x the size of 320x200? I'm pretty sure that there were resolutions larger than that when DOSBox development STARTED. HWSCALE has been purged from this page and there's no support for it apparently. conf Wiki page, and apparently the highest I can go is 3x scaling with any scaler. It's just so small I almost have to give up on DOSBox. I've been hurting my eyes and getting headaches trying to play Might and Magic, Albion, Oregon Trail Deluxe, etc on it. On a 4K monitor, this is barely even legible. It's setting me to a little 960圆00 window in the middle of the screen. I've been trying to use the "normal3x" scaler and it just doesn't cut it. ![]() VGA 320x200 games have the odd small stutter, as they are 70Hz.Yes, I know how to use the. CGA and EGA games run completely smooth (as they were 60Hz refresh originally), 320x240 VGA mode X is smooth too. It works surprisingly well, albeit with letterboxing as most DOS games are only 200 high. For this reason I start DOSBox in windowed mode, then send ALT-ENTER after 5 seconds to select fullscreen mode. I use multimonitortool to select 320x240 mode before starting DOSBox, and change back to 640x480 interlaced after DOSBox quits.įor some reason, setting fullscreen = true causes DOSBox to freeze on startup. Output at 320x240 60Hz to a 15KHz display using CRTEmudriver on ATI 5450 under Win 7 Embedded.įullscreen = false # prevents freeze on startupįulldouble = true # needed to prevent tearingįullresolution = original # selects 320x240Ĭycles = fixed 40000 # needed as max mode causes slowdown My objective was to get pixel-perfect, unfiltered output with as smooth scrolling as possible and no tearing. DOSBox 0.74-3 (latest stable) seemed to work the best, the forked versions with VSync & Direct3D exhibited various issues. Spent a while playing around with various versions of DOSBox. Not Groovymame related I know, but thought this might be useful for someone.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |