Solved 18.03.16 screen resolution problem.
-
@alpermis Can you stay on auto mode, launch a N64 game, quit, and make a new support archive please ?
-
@alpermis hoh and remove
system.es.videomode=auto
it's buggy, but will be fixed -
I changed system.es.videomode=auto -> system.es.videomode=CEA 4 HDMI (as you asked)
Started a N64 game then I quit the game. Screen resolution turned bad. And here is the archive ;
https://file.ac/d8MQldK1ta8/ -
Another thing might help; I use hdmi to dvi cable. So monitor is in dvi mode.
-
@alpermis ok, try this fix by running SSH commands:
mount -o remount, rw / rm /usr/lib/python2.7/site-packages/configgen/utils/videoMode.pyc wget -O /usr/lib/python2.7/site-packages/configgen/utils/videoMode.py https://gitlab.com/recalbox/recalbox-configgen/raw/0769d875ca343ddffd19721e96595e92511470f2/configgen/utils/videoMode.py
No need to reboot, just start games from ES including N64
tell me if it fixed your problem -
This post is deleted! -
The same.
mount -o remount, rw /
rm /usr/lib/python2.7/site-packages/configgen/utils/videoMode.pyc
wget -O /usr/lib/python2.7/site-packages/configgen/utils/videoMode.py https://gitlab.com/recalbox/recalbox-configgen/raw/0769d875ca343ddffd19721e96595e92511470f2/configgen/utils/videoMode.py
--2018-03-18 14:08:29-- https://gitlab.com/recalbox/recalbox-configgen/raw/0769d875ca343ddffd19721e96595e92511470f2/configgen/utils/videoMode.py
Resolving gitlab.com (gitlab.com)... 52.167.219.168
Connecting to gitlab.com (gitlab.com)|52.167.219.168|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4489 (4.4K) [text/plain]
Saving to: '/usr/lib/python2.7/site-packages/configgen/utils/videoMode.py'/usr/lib/python2.7/site-packag 100%[====================================================>] 4.38K --.-KB/s in 0s
2018-03-18 14:08:30 (12.8 MB/s) - '/usr/lib/python2.7/site-packages/configgen/utils/videoMode.py' saved [4489/4489]
Archive when screen was bad;
https://file.ac/2CUs1SYzhsY/ -
@alpermis ok, investigating
-
@alpermis new fix :
mount -o remount, rw / rm /usr/lib/python2.7/site-packages/configgen/utils/videoMode.pyc wget -O /usr/lib/python2.7/site-packages/configgen/utils/videoMode.py https://gitlab.com/recalbox/recalbox-configgen/raw/0bc27e90248812a62f80de94810434acbf7ac418/configgen/utils/videoMode.py
the rm could fail, not a problem
-
It seems fixed Thank you very much.
I noticed couple of other issues. Im gonna try to be sure about those and open other threds. -
@alpermis great thank you for participating in the debugging
-
nickel chrome plus de probleme avec la n64 , merci
-
Wow thank you. This issue has been resolved. It originated in dreamcast and n64.
-
@rizzie happened with systems having a forced resolution
-
@substring said in 18.03.16 screen resolution problem.:
The log shows
[ 44.50] configgen/videoMode.py(isSupported:68): The resolution for 'CEA 4 HDMI' is not supported by your monitor [ 44.53] configgen/videoMode.py(autoMode:115): auto mode -> CEA 4 HDMI not supported, fallback to default
@barto28 has the very same problem, but switching to auto mostly resolved the problem but for N64.
I just wonder where's the path of that log file please? I'd like to see what's going on, on my Recalbox. Thanks.
-
@tekkenism
~/logs/recalbox.log
, you can also see it from the webmanager -
@substring said in 18.03.16 screen resolution problem.:
@tekkenism
~/logs/recalbox.log
, you can also see it from the webmanagerPerhaps I'll sound silly but I disabled Webmanager and that Media Player, for..ermm...saving a bit more RAM. Eh?
Anyway, I'll nano that log file from time to time. Recalbox is a stable thing, I really want to -contrinute- it to be rock-solid! -
@tekkenism no need to nano, just view it through network share