![]() # use triple buffering and thus won't flicker. # For build engine games, use more memory than in the list above so it can # The maximum resolution and color depth the svga_s3 will be able to display # vmemsize: Amount of video memory in megabytes. # Possible values: hercules, cga, cga_mono, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe, amstrad. # machine: The type of machine DOSBox tries to emulate. # language: Select another language file. # overscan: Width of overscan border (0 to 10). # usescancodes: Avoid usage of symkeys, might not work on all operating systems. # then the shader will be used even if the result might not be desired. # pixelshader: Pixelshader program (effect file must be in Shaders subdirectory). Resetmapper only works with the default value. # mapperfile: File used to load/save the key/event mappings from. # Possible values: lowest, lower, normal, higher, highest, pause. # pause is only valid for the second entry. Second entry behind the comma is for when dosbox is not focused/minimized. # waitonerror: Wait before closing the console if dosbox has an error. # autolock: Mouse will automatically lock, if you click on the screen. # Possible values: surface, overlay, opengl, openglnb, openglhq, ddraw, direct3d. # output: What video system to use for output. # windowresolution: Scale the window to this size IF the output device supports hardware scaling. # If you end up with small window on a large screen, try an output different from surface. # Using your monitor's native resolution with aspect=true might give the best results. # fullresolution: What resolution to use for fullscreen: original, desktop or a fixed size (e.g. It can reduce screen flickering, but it can also result in a slow DOSBox. # fulldouble: Use double buffering in fullscreen. # fullscreen: Start dosbox directly in fullscreen. # They are used to (briefly) document the effect of each option. # Lines starting with a # are comment lines and are ignored by DOSBox. (Please use the latest version of DOSBox) It really does feels like my computer should be able to play this properly.Ĭode: # This is the configuration file for DOSBox SVN-Daum. I really want to experience this game properly and the lag is really starting to grate on my nerves.Įdit: I might also add that I'm using Windows 7 (64 bit), with 4GB of RAM. If anyone have any clues on what to try, I would be extremely grateful. and nothing seems to improve the recurring bursts of lag. ![]() I've been spending the last couple of days fiddling around with the settings (different resolutions, 640x480, 800圆00, et.c), I've tested out various options in the DOSbox config file (as well as Gulikoza's custom config) - I've tried changing process priority to highest, increasing the maximum cycles to max, setting the CPU core to dynamic. I really would appreciate any help you've got, if you have any tips or clues on what could be causing this. I know it might sound like a minor issue, but it's really frustrating me and pulling me out of the experience each time it happens (and it's usually a minute or two in between these "bursts" of lag). The problem is that SSP launches perfectly and even runs smoothly for a while however, there will be recurring moments of extremely choppy lag that last for about 10-15 seconds, before the game sort of "jumps back on track" and runs smoothly again. Unfortunately, it wasn't completely the smooth ride I'd hoped it would be, on the technical side. Dosbox, PCEM, and Qemu, have 3dfx support via patches.Hey guys! Being a fan of SS2, I tried to get System Shock Portable to run properly on my computer so I can experience it for the first time. Also you can build dosbox and qemu on armhf platform and they run windows 95/98 and dos. I can run a 2GB hdd image and have 3 cd drives active, so it works but there is not much documentation for this and what can and could work and what wont. But I have dosbox-x setup with win98 and all drivers installed, fallout 2 starcraft and diablo seem to run ok using dx7. Try PCEM as it offers a lot more hardware options and support on windows intel/amd. That's a common sound issue with windows emulation within windows using dosbox or qemu. Honestly i would stay at dx7 for win95, and use dx8 with win98 or just stay at dx7. Try Turning off MMX Emulation if enabled. I mess with windows guest on qemu and dosbox and they both work fairly fine if you integrate chipset drives in the iso and use command line switches for turning acpi support off during install. Whats are you running dosbox on? If its windows on windows that's part of the issue. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |