@Hypex

Quote:

I haven't had any such problems with the X1000. What version of CFE is installed on your X1000?

@afxgroup
@walkero

https://amigaworld.net/modules/newbb/v ... _id=42094&forum=33#802409

You probably have a problem with the screen mode you were using with the workbench.

1) Can you boot without the startup sequence?
2) Could you tell me what version of RadeonRX.chip you are using?
3) Do you remember which workbench screenmode you use?

Hi @TiredOfLife,
How exactly did you roll back to update 2?

Have you checked that the RadeonRX.chip file is still present in the Kickstart directory and that it is among the modules loaded in the Kicklayout file?

@daveyw
What version of SFS are you using?

Hello,
I'm resurrecting this thread just to let you know that with the Update 3 of OS4.1 Final Edition, QEMU's USB Tablet device should work properly. Therefore, the hidtablet.usbfd driver I attached in this thread is no longer needed.

@skygecko

Hi,
my Sil3132 controller works perfectly on my Sam460LE.
Please, can you post a photo of your Sil3132 card?

I use PFtp.

Have you tried changing the PCI slot where you mount the graphics card?

@Maijestro

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.

@Maijestro

I can't run Quake2 on QEmu.
If i try, i get the message "Error: Couldn't create window".

I have:
- minigl.library v2.24
- Warp3D.library 53.27

Where am I doing wrong?

@Maijestro

Quote:

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.

p.s.: Where did you find the startup audio? It's wonderful. I want it.

@all
The driver is ready:
- added wheel support
- added more checks to prevent it from taking control of devices that are already managed well by hid.usbfd.

I can't upload here.
Anyone interested, can pm me their email, and I will send the driver.
Note: this is a temporary driver to better use QEMU tablet device, but should work with similar devices.
The ultimate goal is to integrate everything into hidtouch.usbfd (only the part that is not yet managed in hid.usbfd).

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.

@Maijestro

In fullscreen it should never happen. It is behaving as if it were window mode and the AmigaOS window ended one line before the screen border.
I tried both on my laptop screen and on an external 4k monitor and in fullscreen I can reach the edge without the host cursor appearing.
What options do you use to launch QEmu?

@Maijestro
I tested both fullscreen and windowed mode and I don't have your problem. Can you make a video?

@Maijestro

I didn't realize there was also the menu problem.
Does this also happen when you're in fullscreen?

@Maijestro

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.

@Maijestro

The difference is how QEMU emulates a pointing device.
Normally QEMU shows a touchpad or a mouse as a standard HID mouse, so AmigaOS4.1 sees a HID mouse and receives from QEMU events with relative movements in x and y. In this case the official hid.usbfd driver of amigaos handles this in the right way.
You can verify that events received are relative x,y by looking at the mouse cursor positions in the emulated AmigaOS4.1 and the "real" mouse cursor of the host system: they do not match. In general it is not a problem, except in particular cases (see Hans's post).

Alternatively, QEMU can emulate the pointing device as a HID tablet instead of a HID mouse. In this case, QEMU does not expose a mouse, but exposes a tablet as an input device and sends absolute coordinates to AmigaOS4 such that the AmigaOS4 mouse cursor coincides with the host operating system's mouse cursor. Hans reported that this mode would be useful when using the Virtio GPU device.
The problem is that the amigaos hid.usbfd driver cannot currently manage the tablet device.

So I wrote a driver that handles a tablet device.
Using the HID protocol, this driver can actually manage all tablet like devices, but I was wondering if it wasn't worth making the driver more selective, so that it works only when it detects the QEMU emulated tablet.

@vagappc

sketchblock reads pressure.