WinUAE 2.4.0 beta series

[Dr.Venom]

Originally Posted by Toni Wilen

Adjust config file sound buffer setting manually? (but make sure you do not enter Sound GUI panel because it will check limits)

I already tried that, but somehow that doesn't seem to have an effect. Tried all kind of values, but it seems to revert to closest "valid" setting. Or should the values be some multiple or power of X? Tried settings of 16, 256, 1024, etc.. Trying an extreme small value, setting "sound_max_buff=1", should at least cause some trouble, but it doesn't seem to have any effect. Also extremes on the other side, using very large values, doesn't seem to work, other than giving latency comparable to largest official setting. The log also reverts to the standard reporting in BUF=64 (1024) for whatever smaller value than sound_max_buf=2048 (current lowest "official" setting) I use in the config file.. This is without going in the sound tab on startup. But maybe I'm doing something wrong or missing something? Would love to test a few buffer settings that would on average compare to ~10 or ~20 ms latency, just to see if my computer can manage it with the current beta's..

Edit: all tested with wasapi exclusive (on Auzen X-FI)

There won't be options because this can't be changed without restart.
But I guess it is time to make it the default, but first I'll add small modification: always enumerate dinput devices and use dinput mode if device type does not have DIDEVTYPE_HID flag.

Cool

[Toni Wilen]

Originally Posted by Dr.Venom

I already tried that, but somehow that doesn't seem to have an effect. Tried all kind of values, but it seems to revert to closest "valid" setting.

I missed one check that limits min value to 512., will be removed in next beta.

I also noticed HID game controller support has few more annoying issues:

1) "RAW" name instead of real name. Getting real name seems to be very complex. (Name that appears in device manager)
2) Windows XP has strange issues. I think safest solution is to only allow rawhid by default if Vista or newer.

[Dr.Venom]

Originally Posted by Toni Wilen

I missed one check that limits min value to 512., will be removed in next beta.

Great. Will it then take any value, or need it be a multiple of some base value?

I also noticed HID game controller support has few more annoying issues:

1) "RAW" name instead of real name. Getting real name seems to be very complex. (Name that appears in device manager)
2) Windows XP has strange issues. I think safest solution is to only allow rawhid by default if Vista or newer.

That would work for me.

And for Windows XP users it will still work by using the commandline option then?

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2400b8.zip

Beta 8:

- Fixed D3D RTG hardware cursor stupid divide by zero crash introduced in b6
- Old "Include CD/DVD drives.." now always mounts in CDFS + uaescsi.device mode (uaescsi.device is automatically enabled)
- Approximate CPU speed and 68020: divide A500 instruction cycle counts by 4.
- RTG vsync and >=100Hz display didn't work correctly.
- RTG vsync and non-fastest CPU speed mode fixed.
- Removed RTG autovsync setting, it does not make any sense.
- Fixed D3D + no filter crash in some situations.
- CDFS CD mounted drives are now bootable but only if media is present when drive is mounted to prevent ugly "No disk present in device CDx:" requesters.
- Display vertical position was wrong if A2024 or Graffiti emulation was enabled.
- AROS ROM updated.
- Low latency USB HID game controller raw input mode is now the default (except if Windows XP, it should work but enumerated device paths are wrong), old custom input mappings compatibility is not guaranteed, DirectInput is still used for any non-HID devices.
- Fixed HID analog stick handling if reported range was -val to +val instead of 0 to +val, also other small updates.
- USB HID device name detection improved, less generic names, better match with DirectInput device names.

Test all input devices and report any strange behavior!

[Retroplay]

Joystick input is messed up for me now.
Left is broken and right is always on.
This is the drivers I use: XBCD 0.2.7 drivers.

I have zoned the drivers if you want to investigate further.

Is there any way to enable old input method again as that works flawless for me ?

[Toni Wilen]

Originally Posted by Retroplay

J
Is there any way to enable old input method again as that works flawless for me ?

Yes but thats not the point.

Does http://www.winuae.net/files/b/winuae.zip fix it?

[Retroplay]

Unfortunately not, now only fire button is registerered.

[Dr.Venom]

Originally Posted by Toni Wilen

I missed one check that limits min value to 512., will be removed in next beta.

Thanks for fixing it . A500 cycle-exact is running soooo well with beta 8, it's like a dream. Buffer setting can be reliably reduced to 1024 (half of current "official" lowest setting!). A setting of 512 even works quite well also...

Given how well it works, it might be a suggestion to lower the current lowest official sound buffer setting of "1" from 2048 to 1024, make setting "2" at 2048, etc.. Following through that would result in a setting "7" at 65536. This is probably also more useful, as the current setting 7 (buffer of 131072) results in a "can't initialize sound" (on my setup at least) and probably also isn't used by anyone anymore?

I don't know what the status of the fastest possible mode is in this beta, but it doesn't work as reliably as the A500 cycle-exact mode for me. There's still the starving of the sound buffer shortly after starting WHDLoad games and demos from RTG workbench. This happens even at buffer setting 4..

Input device enumeration seems to work properly for me in beta 8. Just a question to verify with the bootlog. If the bootlog reports
"RawInput enumeration..
RAWINPUT: found 10 devices"
(and then lists the devices)
and ends with
"DirectInput enumeration.. Game controllers..
Windowsmouse initialization..

This would mean that it succesfully is using RawInput for all attached controllers, and none will be setup with DirectInput, correct?

[Toni Wilen]

Looks like HID device descriptors can have "features"..

I now have tested following devices:

- XBox 360 pad (both wired and wireless and also wired + XBCD)
- PS2 pad via adapter
- Gamecube pad via adapter
- Competition Pro USB
- Tiny stick on Logitech G13

They now work correctly except G13 stick. It reports logical minimum = -127, logical maximum = 127 but actual reported values are from 0 to 255. It gets even worse, because min is negative (interesting HID feature, saves 1 bit if range is fully positive), range becomes 0..127.[wraps around here].-128..-1!

Linux HID driver has a quirks list that forces logical min=0, max=255 but it does not include G13. It is possible stick is not real HID joystick but "emulated" by Logitech's software.

Perhaps I'll just take the Linux quirks list and also add G13 to it..

EDIT: Done, winuae.zip updated.

[Retroplay]

My (not 360) modded XBOX Controller with 9 pin joystick connector works now.
Thanks.

[mr.vince]

WinUAE 2.3.3 runs AmiKit, latest beta always crashes. Not sure if this is connected to RTG... logs attached.

[Toni Wilen]

Originally Posted by mr.vince

WinUAE 2.3.3 runs AmiKit, latest beta always crashes. Not sure if this is connected to RTG... logs attached.

Seems to be RTG related. Looks like "special" modes (those with "!" = driver supported but for some reason may not be compatible with current monitor or rrsomething like that) shouldn't be included in RTG mode list..

This accidentally changed in recent enumeration update.

[mr.vince]

Thanks, working now.

[Leandro Jardim]

WinUAE crashed while it was trying to read a compressed cd image with 7z. The attachment has the configurations, the logs and dumps too.

[Toni Wilen]

Originally Posted by Leandro Jardim

WinUAE crashed while it was trying to read a compressed cd image with 7z. The attachment has the configurations, the logs and dumps too.

Dump from unofficial beta = useless.

[Leandro Jardim]

This is not a problem... Voilá! I updated the link...

[Toni Wilen]

Originally Posted by Leandro Jardim

This is not a problem... Voilá! I updated the link...

Ok, unfortunately dump does not really say what went wrong..
Does it also crash if you select CD32 quickstart mode, select the same CD image (don't care it isn't real CD32 image), and start emulation?
Does it only crash if you change the image when emulation is already running?
Does it happen when using last official version?

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2400b9.zip

Beta 9:

- USB HID game controller support really works now. (HID signed value handling is a bit special) Also added pad quirks list from Linux, some game pads apparently report bad minimum and maximum range values, this also includes Logitech G13 stick which was not listed (reported range is -127 to 127, real range is 0 to 255) and this caused the b8 problem because I assumed it was supposed to work that way which of course broke other correctly working devices with negative minimum range.
- D3D and DirectDraw fullscreen mode monitor selection improved, it wasn't reliable if system had more than 1 display adapter(s). (Win32 EnumDisplayDevices(), DirectDraw and Direct3D monitor indexes are not guaranteed to be same)
- Adjusted sound buffer range, old 1 is new 2, 2 is 3, and so on. Old 7 is too big, most drivers won't accept it and new vsync can work with buffer smaller than old 1. (Buffer size "0" or "1/2" would have been too confusing..) In other words, if you load old configuration, only value shown in GUI increases by one, real buffer size does not change.
- Fixed Graffiti emulation crash in if Graffiti hires mode was detected but emulation was not configured for superhires support. (Only in some situations)
- Disable genlock detected option if A2024 or Graffiti enabled, this is impossible configuration and would only slow down emulation (forces Graffiti emulation to keep looking for command codes continuously)
- PC keyboard emulation mode, maps keys like F12, End, Home etc.. to Amiga key codes (afaik same key codes are also used by AROS, OS4 and MorphOS). Num Lock opens the GUI by default (Only remaining key that is more or less free), all other special UAE key mappings are disabled. Config file only at the moment: input.keyboard_type=pc
- Do not include "raw" display modes (marked as "!") in RTG resolution list.
- Old vsync mode is back (native only, non-fastest CPU mode compatible only)

[Leandro Jardim]

Originally Posted by Toni Wilen

Ok, unfortunately dump does not really say what went wrong..
Does it also crash if you select CD32 quickstart mode, select the same CD image (don't care it isn't real CD32 image), and start emulation?
Does it only crash if you change the image when emulation is already running?
Does it happen when using last official version?

I tried like you said, but it did crash in the two tries. And I used the CD32 Quickstart with the default host configuration.

[Dr.Venom]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae_2400b9.zip

Beta 9:

[...]
- Do not include "raw" display modes (marked as "!") in RTG resolution list.
- Old vsync mode is back (native only, non-fastest CPU mode compatible only)

Unfortunately the switching between two monitors (native <-> RTG) through displaydata got broken somewhere between beta 8 (release 2011.12.27) and public beta 9. In beta 9 the switch doesn't occur. Both native and RTG stay displayed on the same monitor.

Config (with 3 x 'displaydata=' triggers) + 2 logs attached. Seems to be related to the following, resulting in that "setswitch" doesn't get triggered in beta 9.

beta8 (2011.12.27):

40-455 [192 226x312]: P96: Non-unique mode 742x574
40-455 [192 226x312]: 29: 50EB1000  742x 574 UAE: 742x 574
40-456 [192 226x312]: 30: 50041000  800x 600 UAE: 800x 600
40-456 [192 226x312]: 31: 50051000 1024x 768 UAE:1024x 768
40-456 [192 226x312]: 32: 50061000 1152x 864 UAE:1152x 864
40-457 [192 226x312]: 33: 508E1000 1280x 720 UAE:1280x 720
40-457 [192 226x312]: 34: 50901000 1280x 800 UAE:1280x 800
40-457 [192 226x312]: 35: 50071000 1280x1024 UAE:1280x1024
40-458 [192 226x312]: 36: 50941000 1440x 900 UAE:1440x 900
40-458 [192 226x312]: 37: 50981000 1920x1080 UAE:1920x1080
40-921 [216 226x312]: P96FREQ: 312*49.9184 = 15574.5349 / 49.9 = 312
40-922 [216 226x312]: RTG conversion: Depth=4 HostRGBF=9 P96RGBF=9 Mode=4
40-931 [217 162x043]: SetSwitch() - Picasso96 1920x1080x32 (742x287x32)

beta 9:

58-885 [192 226x312]: P96: Non-unique mode 742x574
58-886 [192 226x312]: 26: 50EB1000  742x 574 UAE: 742x 574
59-321 [215 175x007]: warning: 1B88 written to BEAMCON0 PC=101217C8
59-342 [216 000x000]: BEAMCON0 0020 -> 1b88 PC=13ffc996
59-342 [216 000x000]: BEAMCON0=1B88 VTOTAL=023D  HTOTAL=0081
59-342 [216 000x000]:   HSSTOP=0015 HBSTRT=0001  HBSTOP=0021
59-343 [216 000x000]:   VSSTOP=000E VBSTRT=023E  VBSTOP=0016
59-343 [216 000x000]:   HSSTRT=000B VSSTRT=0007 HCENTER=004B
59-345 [216 000x000]: VSync calibration: remembered rate 49.917998Hz (49.917998Hz)