View Single Post
Old 16 September 2016, 11:10   #22
sodapop
Registered User
 
sodapop's Avatar
 
Join Date: Oct 2010
Location: France
Posts: 99
Jesus !
Maybe my explanations were not clear enough, not being that fluent in English...

No, actually what I meant was : what you did with 3.2.2 is not present in 3.3.0 anymore...

Quote:
WinUAE 3.2.2 (21.12.2015)
=========================

3.2.0 bugs fixed:

- JIT FPU 32-bit and 64-bit compatibility fixes.
- Interlace mode blank screen in some configurations.
- Slirp network mode high CPU usage.
- Some programs that use AGA subpixel scrolling had horizontal
jittering.
- Per-monitor high DPI update still caused repeated GUI window
closing/opening.

Other bug fixes:

- Game controllers suddenly stopped working. Most likely only happened
under Windows 10 and only in some setups.
- MIDI out devices missing (x64 only).
- Serial port transmit buffer was not always flushed.
- 68020+ BFFFO undocumented offset calculation fixed.

Updates:

- AVIOutput in capture before filtering mode: width is now always divisible
by 16 pixels and height is always even for best codec compatibility.
- Useless, very basic and invisible touch screen mouse and joystick overlay.
- Load config with joystick that is not connected, fall back to previously
loaded (default.uae) setting instead of always falling back to keyboard
layout A.

- Out of bounds RTG coordinates are now clipped to valid region instead of
rejecting whole operation.
- Keyboard names (if available) are now listed in Input panel device list.
- Built-in HRTmon update v2.36.
- Phoenix Board SCSI emulation.
Plus, no matter if you select a joystick in port 2 as default or not, it will be always "keyboard layout A" by default (from a fresh 3.3.0 installation) unless you specificly choose <none> as default (but in this case, it will always be <none> even if a joystick is plugged).

So, basically, just put back what you had done in 3.2.2 please
sodapop is offline  
 
Page generated in 0.06254 seconds with 11 queries