![]() auto will switch to dynamic if available and # Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x. # then the scaler will be used even if the result might not be desired. ![]() ![]() # scaler: Scaler used to enlarge/enhance low resolution modes. # aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!. # frameskip: How many frames DOSBox skips before drawing one. # There is generally no speed advantage when raising this value. # though few games might require a higher value. # This value is best left at its default to avoid problems with some games, # memsize: Amount of memory DOSBox has in megabytes. # captures: Directory where things like wave, midi, screenshot get captured. # Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe. # machine: The type of machine DOSBox tries to emulate. # language: Select another language file. 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: auto, opengl, software. # renderer: Choose a renderer driver if output=texture or output=texturenb. # Possible values: surface, texture, texturenb. # 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. # vsync: Sync to Vblank IF supported by the output device and renderer (if relevant). # 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) The former is not supported anymore on the Pi4 - the latter works, but it's not 100% behaving the same as on a Pi3.But they are not all the same : # This is the configuration file for DOSBox 0.74. The PI4 has a different kind of driver (it's basically emulated on top of the DRM/KMS primary video plane) which doesn't support resolution changing, as in the previous PI models.įor the Pi3, the scaling might have worked with 2 methods - either the fbcon SDL1 driver did the scaling to a resolution supported by the framebuffer, or the scaling was done by using the SDL1 dispmanx driver (PI specific). "it's to do with the framebuffer video driver included in the sdl1 library used by dosbox. Others are also finding the exact same issue as yourself, and I found this : My post was "Dosbox on a Pi4, at the moment, will never perform better than on a Pi3 it seems. There was another thread Id posted on re poor Dosbox and it's poor performance on the Pi4 - this may help? Below is one frame of video 1 (the half-way transparent green and magenta area is caused by my TV): I also noticed that even with vsync=true the game shows some tearing effects. Video 3 - vsync=false / joystick=none (shows the same issue as in video 2):Īs a side note, when setting joystick=none, the virtual keyboard in DOSBox does not work anymore, or to be precise: it cannot be operated with the joystick anymore (works fine when using a USB mouse). Video 2 - vsync=false / joystick=auto (game runs fine in the first few seconds, but after that drops down to 10-15 fps): Video 1 - vsync=true / joystick=auto (game runs fine, but crackles and stutters in other games when moving the mouse): I made some videos for comparison with different settings for vsync and the joystick (apologies for the flickering and ghosting - I'm still in love with my old plasma TV ). Unfortunately it did not solve the issue. Sorry for responding late! I tried it out today. Said in DOSBox: Games stutter and audio crackles while moving the mouse:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |