Ok, I will try. In any case, @Hans is certainly right. A tablet with absolute coordinates is not suitable for controlling a rotation. Absolute coordinates have left and right bounds, and rotation is likely mapped absolutely to -90 degrees on the left and +90 degrees on the right. A mouse, on the other hand, only indicates relative movements, so it allows you to rotate without limits in both directions.
Maybe they are right "Usb-Tablet" and their HID device driver is originally meant to allow touch input via monitor or touch pad (laptop) under AmigaOs4.1 and this already works very well. And even the misuse for pure mouse control works and you can work under AmigaOs4.1.
Demo crashes as soon as I click to open the Inventory (far left button on the interface) under both Software Renderer and without having it enabled.
On the latter case, it completely freezes the system too.
Above behavior on clean installation under OS4.1 F.E. u2 (+hotfix) plus latest AmiUpdate (including MiniGL) on SamEp440-mini.
I didn't know that Gorky17 had a demo to try out, so I gave it a go. I had no problems with the inventory, the demo ran absolutely stable under AmigaOs4.1 FE Update 2 including all available updates via AmiUpdate with software rendering. I would like to play it with higher resolutions, but the game only supports 640x480 in the demo version.
I can't run Quake2 on QEmu. If i try, i get the message "Error: Couldn't create window".
Sorry, I am using Quake2 Beta by Steffen Häuser, this version is still under development. But it offers 3D acceleration, as well as software rendering and already works very well under Qemu/AmigaOs4.1.
You can also test it with PrBoomGL/Quake1/Woof and Duke3dw which you can find on Os4Depot. With all these 3d shooters there is no complete 360 degree rotation, only 180 degrees.
I noticed something else and that is that "-device usb-tablet" does not support 360 degree rotation but only 180 degrees, but I'm not sure if it's the "-device usb-tablet" in general or if your driver doesn't support it under AmigaOs4.1.
I noticed this when I played Quake2 under AmigaOs4.1, I tested it with Display Manger SDL/Cocoa.
I don't know what they changed in their latest test build (fix-exit-free-signal), but there are crashes and DSI here too.
The only version that currently works very well for me is ScummVM 2.8.0 (os4depot) with replaced libcurl.so.12 from MickJT.
Also the use of Odyssey has no influence on ScummVM, as well as starting without .ini and there are no problems. Starting 5 different game engines in a row also worked without problems, all with default stack size.
This also seems like a different behavior of the host window manager. It starts sending events to AmigaOS only when the QEMU screen acquires focus with the first click. If I instead launch in fullscreen, QEMU acquires focus directly and the guest cursor starts working immediately.
I checked it with the Display Manager SDL and you are right, there are no problems. I am currently running Qemu with the display manager option "-display cocoa,zoom-to-fit=on,full-screen=on". "zoom-to-fit" should not normally be necessary as this option to scale or stretch the image to full screen is normally handled by the graphics card or driver. When the Virtio GPU/drivers are available at some point this problem could also be solved.
If I completely omit the display option "zoom-to-fit", there are no problems with the Display Manager Cocoa either. Maybe I will report the problem anyway. Thanks again for this AmigaOs4.1 driver.
Quote:
p.s.: Where did you find the startup audio? It's wonderful. I want it.
I had the same problems because I simply didn't know any better. In my opinion, the function should have been activated as an option in the standard settings, as it makes the most sense. I had to ask other users to explain it to me and I couldn't figure it out myself.
I have tested your driver version 0.9 and it works very well under AmigaOs4.1. Host and guest mouse pointer are exactly the same in movement and also the mouse wheel can be used now. Thank you very much.
What I have noticed, however, is that the first time I use AmigaOs4.1 the host mouse pointer is displayed.....as soon as I make an entry with the mouse, the guest takes over. This only happens at the first start of AmigaOs4.1. If I reboot within the session there are no problems, I think it is because the driver is initialized the first time?
Also I had an older Qemu GL build where I had problems with mouse input slowdown, again no more problems as soon as I use "-device usb-tablet" as input device and host and guest mouse are in sync.
As usual, the video is for demonstration purposes only and I will remove it later so as not to slow down the thread
It does not matter what's your host pointing device. The driver in the guest only sees the emulated tablet or mouse and should drive that. It does not know where the events come from on the host OS so even if you have a mouse but use -device usb-tablet the guest will see a tablet. The difference between usb-mouse and usb-tablet is that mouse sends relative move coordinates (e.g. x: +5, y: -2) while tablet sends absolute values (x: 1012, y: 44) so with usb-mouse the guest calculates the position which may be affected by mouse acceleration settings in Prefs and could get out of sync with the host pointer while with a tablet the position is given so the pointer will be where it should be.
I already understood that and AlfredOne had already explained it. Because it means that the mouse pointer of the host and guest are synchronized with the driver and there are no differences. This is exactly the reason why I welcome this driver. And if it already solves future problems I am of course glad that someone has written it for Qemu/AmigaOs4.1 and we can use it as an alternative.
I'll add wheel support as soon as I find some free time tonight and send you the updated hidtablet.usbfd driver here. then I thought of integrating the code into the hidtouch.usbfd driver which will thus manage tablet devices as well as touchscreens.
That's great! Thank you very much, that's very kind of you. Unfortunately I don't have a laptop and can only test your driver with the mouse, but as mentioned before, it works very well now. Apart from the missing mouse wheel support.
Ok, it is clearly due to the Display Manager Cocoa with the output SDL there are no problems and your driver does what it should.
Balaton I am using Qemu Master without the fullscreen Cocoa patch from Akihiko Odaki, I am not sure if the patch has made it into the Master sources yet as there were changes made by Peter Maydell shortly after the last series.
It seems that Akihiko Odaki's patch series is still not included in Qemu Master, so I added the patch series again. With the last patch series of Akihiko Odaki version 12 it works as under the SDL output. Thanks for the tip.
@AlfredOne
Thanks for this driver and the support of the tablet HID device it works What is of course missing is support for the mouse scroll wheel.
I tested both fullscreen and windowed mode and I don't have your problem. Can you make a video?
To understand the problem I have recorded a video...here you can clearly see the problems, via the title bar of AmigaOs4.1 it is still possible to call up the menus, but you are not allowed to move the mouse pointer to the edge of the screen. I am not sure if the problem can be solved....but see for yourself...
Well, still the ISI crash when starting ScummVM without an .ini file.
Got the unfreed signals with scummvm -version
and a crash after loading for different engines and quit
But more importantly would be your YouTube crashes and other random ones you got, since now the stack has been raised to 8 MB internally
I have tested your trial version a bit and recorded the whole start of ScummVM when creating the .ini file.
I am sure that if you use a freshly booted AmigaOs4.1 system and run ScummVM for the first time there are no problems with the creation of the .ini file.
But I could see some error messages in the log which did not lead to a crash.
[elf] .hash 0x7F8CB000-0x7F8CB4CC Workbench:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynsym 0x7F8CB4CC-0x7F8CBFAC Workbench:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynstr 0x7F8CBFAC-0x7F8CC78A Workbench:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.data 0x7F8CC78C-0x7F8CC7A4 Workbench:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.dyn 0x7F8CC7A4-0x7F8CCB1C Workbench:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.plt 0x7F8CCB1C-0x7F8CCC9C Workbench:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
The complete logs can be taken from here it only shows the execution of ScummVM at the first start without .ini.
Then I did my usual tests Odyssey...YouTube the whole thing I repeated 3 times in one and the same session. There were no problems at all.... but on test 3 it turned out that I ran out of memory and it caused DSI and crashes. I am not sure but I suspect that Odyssey does not free the memory after quitting and it causes ScummVM to crash or show DSI error messages.
Maybe a problem only under Qemu/AmigaOs4.1, but I've never had a problem with insufficient memory. Can you report something similar? On my machine AmigaOs4.1 FE is up to date including all updates and also the latest version of elf.library is used which was/is recently available via AmiUpdate. I use Odyssey version 1.23...
Of course, it could also be that MPlayer (latest version Os4Depot) does not release the memory and continues to use it after exiting when using Odyssey/YT.rexx via MPlayer.
Edited by Maijestro on 2024/3/1 19:22:31 Edited by Maijestro on 2024/3/1 19:25:34
I didn't realize there was also the menu problem. Does this also happen when you're in fullscreen?
I mainly use Qemu/AmigaOs4.1 in full screen because it gives me a better experience. When I use AmigaOs4.1 I don't want to be disturbed by my host system or be reminded that I am still in emulation
Since you ask me that, I assume that there are no problems in windowed mode, but I haven't tested it yet.
The 2 mouse cursors, host and guest, visible at the same time, I think are inevitable. In "tablet" mode, as soon as the cursor leaves the emulated AmigaOS screen, the host cursor appears, but the Amiga cursor no longer receives events and remains stationary in the last position.
Ok, as already mentioned, the problem is that AmigaOs4.1 menus can no longer be called up via the title bar because the host then takes over.
Otherwise, the host and guest mouse pointers are exactly the same speed when used.
No it's not used that way, you just added a card but did not connect a disk to it. See 'info qtree' command in QEMU monitor to see what devices are there and where they are connected. On pegasos2 and amigaone the via-ide buses are ide.0 and ide.1, the sii3112 will be ide.2 and ide.3 so you'd need to use one of these to connect the disk through the sii3112.
I only got this information about Qemu Monitor, but I don't think it will be helpful.
Basically I just want to test if there is any change in the speed of the hard disk when using this card, but since it is an emulation trade it probably doesn't matter.
I don't know how to connect my real SSD, but I tried it with a virtual HD and yes it works without any problems, the HD also uses the SmartFileSystem. This time Media ToolBox also recognizes the HD.
I also added the device "-device sii3112" under the Pegasos2 machine AmigaOs4.1 booted without problems, but I am not sure if the device is actually used. Under SysMon the card is recognized.
I assume that the driver is supported by the guest side, since it is also recognized. Shouldn't Media ToolBox also display this Card when it is actually used?
sii3112ide.device 53.22 (28.6.2017)
[sii3112ide/dev_init] Found chip #0
[sii3112ide/init_port] ---> Port 0
[sii3112ide/init_port] IOBase 00001300, AltBase 0000130A
[sii3112ide/init_port] bmcr_base 00001320
[sii3112ide/init_port] MMIOBase 84280000
[sii3112ide/init_port] Config not forced, scanning port 0...
[sii3112ide/reg_config] assuming device 0 is TYPE_NONE
[sii3112ide/reg_config] there is no device 0 (sc 00 sn 00)
[sii3112ide/init_port] 0 device(s) on port
[sii3112ide/init_port] ---> Port 1
[sii3112ide/init_port] IOBase 00001310, AltBase 0000131A
[sii3112ide/init_port] bmcr_base 00001328
[sii3112ide/init_port] MMIOBase 84280000
[sii3112ide/init_port] Config not forced, scanning port 1...
[sii3112ide/reg_config] assuming device 0 is TYPE_NONE
[sii3112ide/reg_config] there is no device 0 (sc 00 sn 00)
[sii3112ide/init_port] 0 device(s) on port
[sii3112ide/dev_init] Nothing started, bailing out
I will test it later on the Sam460 machine.
Edited by Maijestro on 2024/3/1 16:21:02 Edited by Maijestro on 2024/3/1 16:28:27 Edited by Maijestro on 2024/3/1 16:28:44
you got an emal to share? PM me..i'll try a link to you direfctly then
Thank you....now it has worked. I will test their new version extensively tonight. You wrote that you also had crashes with your new version, how can it be reproduced?
Otherwise I'll run the tests as usual where it always crashed.
I tested your USB driver briefly under AmigaOs4.1 it seems to work well, but when I click on the title bar of the workbench or move the mouse cursor to the edge of the image I see 2 mouse cursors, host and guest. Pay attention to the left side of the picture:
Qemu/AmigaOs4.1 HID tablet:
The driver or the new HID device is recognized by AmigaOs4.1. I could only record it with my cell phone.....
Edit:The problem is that the AmigaOs4.1 menu can no longer be called up from the title bar.
Edited by Maijestro on 2024/3/1 16:40:21 Edited by Maijestro on 2024/3/1 16:40:36
If you ever forget the link, just go to my user page and click on the website link
I've tried using your download link and also directly via your profile website but it always results in me not being able to download any data. I also tried it with my cell phone
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
