AlfredOne wrote:@Hans Yes, it works. I tested this driver on QEmu 8.1 (Pegasos2) too, connecting USB touchscreen monitors and configuring USB passthrough.
Could you perhaps explain in general terms how to pass USB devices to Qemu?
TheMagicSN wrote:No, mplayer is not used with MiniGL.
It is called like
mplayer -vo sdl -ao sdl filename
by Q2.
The difference between the two intros (assuming Steam install) is the first (id logo) uses q2’s internal .cin format while the real intro uses .ogv in the codec the makers of the Steam version chose (which is appearently a bit slow on mplayer which caused you to think it would use MiniGL i assume).
Ok, I found the error, in the SDL Prefs under AmigaOs4.1 the SDL output was set to OpenGl. Because I installed Wazp3D on my system, the videos worked, but had a red tint (Wazp3D) bug.
SDL Prefs settings on software works much better, but makes the videos play a little slow,Video and sound are asynchronous. The videos also have a very high resolution of 1920x1080, I checked this with a video converter under MacOs. But with 3D acceleration this shouldn't be a problem anymore.
Edited by Maijestro on 2023/11/23 17:15:45 Edited by Maijestro on 2023/11/24 7:52:26
AlfredOne wrote:@Hans Yes, it works. I tested this driver on QEmu 8.1 (Pegasos2) too, connecting USB touchscreen monitors and configuring USB passthrough.
That's really cool that it works...that should definitely be interesting for Hans, as far as I know he uses Qemu on a laptop with AmigaOs4.1.
And yes, currently only the Pegasos2 machine offers full USB support.
TheMagicSN wrote:maijestro and me compared speed (not with H2/Sin, but with my Q2 port).
Seems his M1 Mac with QEmu is in speed slightly below (comparing software renderers) my x1000 in native speed (1280x720 Q2 demo1.dm2 timedemo was 24 fps on his QEmu setup, 30 fps on the x1000 natively). Will still compare with my i7 with QEmu with the same game and graphics resolution.
It runs really smoothly even in higher resolutions beyond 800x600 16bit. There are still some problems with playing the cutscenes, apparently MPlayer uses MiniGL, at least for the main intro, but otherwise it's going really well at the moment. I've noticed other errors here and there, but we'll do that privately. Still, I'm impressed...
Thanks for the test version of WarpSnes, I also get the same result as @kas1e. As soon as I switch to full screen resolution 1600x900 8/16 bit there is only a black screen output, the emulator continues to run but you can hear it in the sound.
That's great news. I also like to use iBrowse under AmigaOs4.1 because this browser is really very fast.
I do have one small criticism, your browser is really an independent development under AmigaOs, but I currently think the price of 54.99 euros is a bit too expensive without CSS support.
I think your 30% discount promotion is very good and you should keep it forever, it's a very good price. I'll be honest, I've only ever used iBrowse as a demo version at the moment, but I'll be purchasing iBrowse 3 to continue supporting your work.
Thank you for continuing to work on iBrowse for many years.
I think I'm already using it, it's the EvoTheme, but in the screenshot you showed it looks a little different, maybe the image was edited afterwards. Thanks anyway
it looks like the partition with jfxs is locked during boot 4.1FE as rw. It can only be ro. I recently checked this.
I also did a few tests with the JFXS file system and it is really very fast compared to SFS2, as @geennaam already mentioned it is write-protected, booting the system partition is possible, but you cannot write to this HD.
I don't know why work on JFXS stopped, maybe there were license disputes or developers weren't paid. But it is of course very unfortunate that we cannot use this file system to its full extent.
balaton wrote:@MigthyMax Now there are at least 3 people working on virtio drivers independently. Isn't it time to collaborate on a virtio.library to avoid duplicated work? Is there anybody who wants to publish their virtio access routines under an open source license to make them a standard way to access virtio devices on AmigaOS that everybody can use?
Is it possible to use a real gamepad (usb) with Qemu and AmigaOs4.1? Qemu Pegasos2 supports USB.
Most of the games I currently play on AmigaOs4.1 work very well with a keyboard, but games like MegaMario/XRick/SMC etc. would play much better with a joystick or gamepad.
TheMagicSN wrote:I just sent the WarpSNES Source-code to kas1e, who volunteered to work on the open bugs.
I volunteer to update the code to latest snes9x myselves. But might be not before the weekend that I work on that (I asked kas if he can get it running with recent compilers till then, and send me the code back then, after that I will work on updating to SNES9x 1.60 (please note might take some while due to high project load, but still that specific project is dear to me )
This is fantastic news, WarpSnes is really cool. The GUI is kept simple and the roms run smoothly. I too would be very happy if we could get the scaling problem under control. I would also volunteer to be a beta tester.
flash wrote:I wonder if we could expect a new enhancer release for non AEON hardware. I'd like to see for next Christmas a special release for first generations on AmigaNG systems and new virtual QEMU boards (Gfx Virtio driver?). I think there's some room to sell digital copies of this software for all OS4 users, adding some features missing in AmigaOS 4.1fe and let all OS4 user to be in pair each other as much as possible. IMHO limiting fragmentation of a really small market is an important goal to reach.
I am also using Enhancer Software 2.2 and under Qemu AmigaOs4.1 there is currently no problem with it, all packages are installed properly and work. Apart from the drivers that are intended for real machines. Enhancer software is configured so that the user can decide for himself what he thinks is useful or not.
Improvements for all platforms on which AmigaOs4.1 is currently running can be made available via Enhancer Software 2.x and a separate version would be a waste of resources. In my opinion.
I've done some testing with MPlayer-WIP SDL12-Compat and it works really well with pure SDL output. No more problems with SDL output. However, there is currently still a problem with the -fs output or switching Amiga+F to fullscreen mode.
I recorded a short video to demonstrate how it currently works, in some sections you can also see the bugs.
@all
This is the result of SDL12-Compat it not only serves Qemu with AmigaOs4.1, but also works on real machines. So please support the project that we can make SDL12-Compat available for AmigaOs4.1, please help smarkusg to finish this work in the best possible way.
I repeat sdl12-compat is currently the standard on modern operating systems such as Linux, MacOS, Windows because sdl1 has been merged with sdl 2 functions and is compatible with all sdl1 applications that we have under AmigaOs4.1. It would be a shame not to be able to have it under AmigaOs4.1.
Of course, SDL2 ports should continue to be done using the libraries that @capehill made available to us.
First, thank you for your work on Qemu for the AmigaOne systems; I'm super excited to see this coming to fruition.
I read through the forum here and came up with this process to git and build Qemu with AmigaOne support for my Ubuntu 20.04 Intel-based Linux box.
Your source is not the right one, please use:
https://github.com/qemu/qemu.git
The AmigaOneXe machine has only recently been added to Qemu Master, the Balaton source will also be available later, but he himself told me that he needs to bring his sources up to the Master level, including some patches that are currently still needed.
I recommend you the following way:
git clone https://github.com/qemu/qemu.git
cd qemu
Using AmigaOS 4.1 Classic in this case. Verbatim words by (Tony) in various topics dedicated to 4.1 And personally tested (boot is faster)
The hardware control chain process of the "boot" machine By enabling floppy and cdrom, AmigaOS boot is much faster. Disabling the floppy and cd-rom makes booting slower.
In practice, not finding the cdrom and floppy will make booting slower.
Qemu does not emulate Classic PPC hardware where custom chips also have to be emulated, Amiga PPC Classic hardware is heavily dependent on the floppy drive because it looks for it first, I don't think the NG Amigas are that.
So if e.g. If a1floppy.device is deactivated in the kernel/kick layout, this driver will not be loaded at all, hardware and AmigaOs4.1 will not look for it. But that's just a theory.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
)
I had a lot of fun watching your video.
