It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
try to edit memsize from 16 to 63
I wonder if GOG will update all dosbox games to this new version...
avatar
FulVal: Super Space Invaders '91 crash after intro

edit: output=opengl works properly only for emulate 320x200 resolution, not all other... only ddraw output can do this for all other resolutions, and scanlines with output=opengl works only for 320x200... with ddraw are still bad, so yes, it need some more tweaks (with all other resolutions scanlines works only with scan2x forced, but with bad scanlines... so i think that shaders are needed)
I missed the edits.. The topic doesn't get "fresh" when edited.

Well, I primary tested the opengl scaling with 320x200, as that is a very common resolution in the games that I have installed.
So it is possible I missed a problem.
Your description is a bit hard to follow though. What doesn't work ? As you are mixing a lot of information on that one long line.
With fullresolution=original and with all other resolutions, but not Native resolution i can see that all scanlines are very bad with output=opengl; scanlines are good only with native resolution but only with games that use 320x200 and 320x240 resolution

with all other output with all resolutions scanlines are very bad
Post edited September 13, 2018 by FulVal
avatar
stephane910: Have you implemented a game fixe for Lands of lore 2 and crash in Huline Jungle Village with dosbox or is it scheduled for dosbox 0.75?
https://www.gog.com/forum/lands_of_lore_series/memory_allocation_of_1309694_bytes_failed/page1
No, not specifically. I wasn't aware of it being a problem, so I have never debugged it.. While sounding cheap. This is something you should take up with GOG support. They are the ones selling you it. (It isn't being cheap. I have no idea on how they have setup the game, what kind of patches they applied) It seems that -lowmem fixes it ? There are tons of things to try.. loadfix -f before starting, increasing the memory size as stated by fulval, possibly using another protected mode extender.
avatar
FulVal: With fullresolution=original and with all other resolutions, but not Native resolution i can see that all scanlines are very bad with output=opengl; scanlines are good only with native resolution but only with games that use 320x200 resolution

with all other output with all resolutions scanlines are very bad
Okay, so you are using scanlines. and they look bad according to you.
How about openglnb ? Does that change it ?
Post edited September 13, 2018 by Qbix
Nope, that output works as ddraw and overlay, so bad...

only opengl is good, but only for 320x200 and 320x240 games
(remember that these scanlines are NOT the same real scanlines that all CRT displays have)
Post edited September 13, 2018 by FulVal
avatar
FulVal: Nope, that output works as ddraw and overlay, so bad...
scan2x or scan3x and windowed or fullscreen ?
What is your dpi (display scaling) set to ? (100% or higher?)
I am sorry for the questions. The scaling code of dosbox is complex and it is influenced by a lot of things.
avatar
FulVal: Nope, that output works as ddraw and overlay, so bad...
avatar
Qbix: scan2x or scan3x and windowed or fullscreen ?
What is your dpi (display scaling) set to ? (100% or higher?)
I am sorry for the questions. The scaling code of dosbox is complex and it is influenced by a lot of things.
I've tested only fullscreen for now; with scan3x all scanlines are too black

this scanlines problem happen with all emulators...

dpi 100%, it's a 1080p display


with 4:3 display is different
Post edited September 13, 2018 by FulVal
avatar
Qbix: scan2x or scan3x and windowed or fullscreen ?
What is your dpi (display scaling) set to ? (100% or higher?)
I am sorry for the questions. The scaling code of dosbox is complex and it is influenced by a lot of things.
avatar
FulVal: I've tested only fullscreen for now; with scan3x all scanlines are too black

this scanlines problem happen with all emulators...

dpi 100%, it's a 1080p display

with 4:3 display is different
too black ? What colour do you want them to have then ? Got to check how they look in 320x200 fullscreen then.
with scan2x are better
avatar
FulVal: with scan2x are better
I have checked it out a bit.
With scan2x you have for the lines:
Input (line 1)
Black
Input (line 2)
Black
Input (line 3)
Black

With scan3x, dosbox (and maybe others as well)
you have:
Input (line 1)
Black
Black
Input (line 2)
Black
Black

Thus the black parts are larger and thus it appears darker.

(scan3x (or any 3x scaler, means that we go from 1 input line, to 3 output lines)
I am pondering a bit on how it could be improved.

It would be easy to change it to
Input (line 1)
Input (line 1)
Black
Input (line 2)
Input (line 2)
Black

But then it might be too light.

Although it might be better to have
Input (line 1)
Black
Input(line 1)
Black
Input(line 2)
Black
Input (line 3)
Black
Input(line 3)

Which would be more difficult to code.
Or:
Input (line 1)
Input (line 1)
Black
Black
Input(line 2)
Input(line 2)
Black
Black
Input(line 3)
Input(line 4)
Black
Black

Which might be ever harder to add..
Ultimately it depends a bit on personal preference...

Might need to make some screenshots of the different cases and get some opinions (including yours) to see what is preferred.
Post edited September 14, 2018 by Qbix
Some example are here https://www.google.it/search?safe=active&hl=it&tbm=isch&source=hp&biw=1920&bih=969&ei=A6ObW9aYM8utswHM6YPADQ&q=scanlines+crt&oq=scanlines+crt&gs_l=img.3..0i8i30k1.1035.3657.0.3761.10.10.0.0.0.0.177.808.8j1.9.0....0...1ac.1.64.img..1.9.808.0..0j0i30k1j0i10i30k1.0.DpY7PO0H46o

but i think that it's impossible

https://upload.wikimedia.org/wikipedia/commons/4/4d/Pixel_geometry_01_Pengo.jpg
Post edited September 14, 2018 by FulVal
Judging from those screenshots
line 1
line 1
black
line 2
line 2
black

would be more accurate compared to the current
line 1
black
black
line 2
black
black

However to get it really similar with that flowing like stuff, a shader would be needed.

In the case of scan 3x, it might not look too bad if some black spots were introduced in the horizontal direction as well...
so
1 2
3 4
as input would result in:
1 1 B 2 2 B
1 1 B 2 2 B
B B B B B B
3 3 B 4 4 B
3 3 B 4 4 B
B B B B B B

vs
1 1 1 2 2 2
1 1 1 2 2 2
B B B B B B
3 3 3 4 4 4
3 3 3 4 4 4
B B B B B B


(and the current one for reference:
1 1 1 2 2 2
B B B B B B
B B B B B B
3 3 3 4 4 4
B B B B B B
B B B B B B
Please give the attached images a look.

The llbhor might be a bit over the top. But the llb feels better than current

(anybody reading this, feel free to comment on it.)
This is about the scan3x scaler, which "simulates" scanlines in a simple way.
scan3x_current => how it is in 0.74-2
scan3x_llb => middle line swapped compared 0.74
scan3x_llbhor => middle line swapped + fake vertical black lines
Attachments:
Post edited September 14, 2018 by Qbix
I don't recall exactly the correct looks of scanlines for me, but among those 3 images, I'd say:

scan3x_current -> seems way too dark..
scan3x_llb -> maybe the best one?
scan3x_llbhor -> uh.. no, that looks like a grid
Post edited September 14, 2018 by phaolo