openMSX ARM without X-Window
There is an export variable that makes SDL run on framebuffer, instead of on X. I don't remember it, but google is our friend...
There is also a "window manager" program called Screen. It's just an extension to the console. I have tried it out for a few minutes just to experiment but supposedly it can run SDL applications in full screen.
Try something like:
export SDL_VIDEODRIVER=fb
(or something similar). YOu need to tell SDL to use the framebuffer videodriver.
Also, you should edit your settings.xml and set the scaling factor to "1", which will give you a 320x240 rendering output.
export SDL_VIDEODRIVER=fb
(or something similar). YOu need to tell SDL to use the framebuffer videodriver.
Also, you should edit your settings.xml and set the scaling factor to "1", which will give you a 320x240 rendering output.
It works with the following:
export SDL_VIDEODRIVER=fbcon
However, I'm not able to use the scale_factor to 1 (the emulator still exists telling me that it's unable to use 640x480). Is not there any settings.xml example configuration file? Mine looks like this:
export SDL_VIDEODRIVER=fbcon
However, I'm not able to use the scale_factor to 1 (the emulator still exists telling me that it's unable to use 640x480). Is not there any settings.xml example configuration file? Mine looks like this:
<settings> <video> <scale_factor>1</scale_factor> </video> </settings>
create this file:
/home/karloch/.openMSX/share/settings.xml
with this content:
This is the minimal settings file if you only want to override the default scale_factor, assuming that you're using openMSX 0.6.0.
/home/karloch/.openMSX/share/settings.xml
with this content:
<!DOCTYPE settings SYSTEM 'settings.dtd'>
<settings>
<settings>
<setting id="scale_factor">1</setting>
</settings>
</settings>
This is the minimal settings file if you only want to override the default scale_factor, assuming that you're using openMSX 0.6.0.
Ok, the emulator finally, at least, runs. But it looks like the SDL doesn't manage well the console display. The display is duplicated along the screen (one display to the left and another to the right). Also, it's only long to half weight of the screen. It's like the resolution would be 220x120 or something like that. Of course, the CBIOS text screen can't be even read, although the blue screen and the letters are there.
karloch: I suppose it's easier to talk to us on IRC: #openMSX on Freenode.net. (I have no clue what's going on, and wouter and mth are probably capable of investigating it with you!)
Running the emulator from the X (I'm using kdrive server) will make it run like a charm, it's a lot faster that I would expected. It's a bit slower than fMSX, but this one is unable to play sound correctly on the device while openMSX does this correctly. Although openMSX is slower, Nemesis 1 was still very playable. A little speedup would make it perfect.
I have took a look to the tunning tips of the manual, but I don't know how to apply them since I don't know the settings.xml syntax and the emulator console is not very readable... Help would be appreciatted
I have took a look to the tunning tips of the manual, but I don't know how to apply them since I don't know the settings.xml syntax and the emulator console is not very readable... Help would be appreciatted
Cool! Just get on IRC and we can give you some direct tips on how to work things out.
One thing you can do: run openMSX on a normal PC, set it up for optimal performance according to the performance tips section (simple scale_algorithm, scale_factor 1, set maxframeskip to a higher value (like 10), set the 'frequency' setting to 22050), save your settings and then copy the settings.xml file to your other device. (Or type it over...)
I suppose you don't have hardware accelerated OpenGL on that machine, which could have made some imporovements
One thing you can do: run openMSX on a normal PC, set it up for optimal performance according to the performance tips section (simple scale_algorithm, scale_factor 1, set maxframeskip to a higher value (like 10), set the 'frequency' setting to 22050), save your settings and then copy the settings.xml file to your other device. (Or type it over...)
I suppose you don't have hardware accelerated OpenGL on that machine, which could have made some imporovements
Karloch did it







By karloch
Scribe (490)
17-03-2006, 11:39