I guess this was a bug in 17.0 that got fixed in 18.0?
Than the bug is still here! 17.0 and 18.0 (Intel gpu)??? (low and mid range laptop)
ARM is OK.
I will check later fedora on pixelbook running fedora.
Accumulator, it seems that the "faulty" bars are on turboR machines ? Be carefull if your code contains wait loops in assembly, they will run much faster in turboR mode and might cause the difference ?
EDIT: Ah no, you also have a faulty screenshot with a Philips... Maybe the 50Hz / 60Hz difference ?
Both same.... One 50hz and one 60hz
Could it is related to intel HD Graphics 500, Mesa, 22.42 and i915 driver?
Which file is related to colors?
Try: set renderer SDL
in the console (F10) to check if it makes any difference.
This might be a far shot, but just to make sure... check your accuracy setting with set accuracy
in the console (default key to show the console is F10 as Manuel mentioned above)
if it is not pixel then set accuracy pixel
Maybe examine your "~/.openMSX/share/settings.xml" file for any unexpected setting values (this file only contains settings that differ from their default value).
Another guess: maybe you selected a different clock speed for the emulated Z80?
Problem found!!!!!
It is an settings.xm l / catapult setting.
The problem arises when you Reset all values in Video Controls. It Resets all to 0! and gamma to 0.1...
It reduces also the gamma values.
Scanline 0 is 0k
Blur 0 is ok
glow 0 can be OK
Gamma (Reset) goes to 0.1, this should be 1.0 in my opinion...
After changing in Catapult the gamma to 1
or removing the line in settings.xml... PERFECT!
Version of OpenMSX 16 and up works....
In settings.xml you can modify or just remove the line:
<setting id="gamma">0.1</setting>
The correct default setting for gamma
is 1.1. It compensates for the different gamma between CRT displays and the gamma used by modern PCs.