D3D HQ2X Filter Problem with WinUAE 2.1.0+

Ambermoon · 31 July 2010, 15:25

Since version 2.1.0 I'm completely unable to get D3D filters to work correctly.

I have attached some images showing the problem and my settings, which shows the effect much better than trying to explain it here.

Version 2.0.1 is the last version that works for me, the newer builds seem to do something pretty strange. Compared to the unfiltered image one can clearly see that some filtering is applied, but it's obviously not what you would expect from the hq2x filter.

D3D in Misc. Tab is activated, Direct3D is the latest version, filtershaders are the latest version and I even tried to build new configurations from scratch to be sure no old settings do any harm. But that didn't help either.

Maybe I'm doing something wrong, maybe this a bug. I just don't know.

Main System Specs: Core2 Quad 6600, 4GB, Windows 7, ATI 4890

Thanks in advance for looking at this!

Photon · 31 July 2010, 15:50

Hmm... it finds the gfxcard, but you could also check that '4800 Series' is also in the config files you create (I think). At least I think that if the config loads some old gfxcard entry from a config there could be a mismatch.

Nowadays when I upgrade hardware or WinUAE, I always rename the old WinUAE directory and install latest stable with installer to an empty folder, and then create configs from scratch. But I've broken this rule before and have had all kinds of problems with getting configs to load/save/update when I change in the UI.

So try the 'clean slate' thing, start with quickstart config, set hq2x and save config. Then post here & attach the config. That would help Toni I think.

Ambermoon · 31 July 2010, 15:55

I'm not able to post more attachments atm (limit exceeded), so here the logfiles as code:

winuaebootlog

Code:

WinUAE 2.2.0 (2010.06.28) (6.1 [2]) 32-bit 6.F0B 4
(c) 1995-2001 Bernd Schmidt   - Core UAE concept and implementation.
(c) 1998-2010 Toni Wilen      - Win32 port, core code updates.
(c) 1996-2001 Brian King      - Win32 port, Picasso96 RTG, and GUI.
(c) 1996-1999 Mathias Ortmann - Win32 port and bsdsocket support.
(c) 2000-2001 Bernd Meyer     - JIT engine.
(c) 2000-2005 Bernd Roesch    - MIDI input, many fixes.
Press F12 to show the Settings Dialog (GUI), Alt-F4 to quit.
End+F1 changes floppy 0, End+F2 changes floppy 1, etc.
'C:\Program Files\Sonstige\WinUAE\winuae.exe'
EXE: 'C:\Program Files\Sonstige\WinUAE\', DATA: 'C:\Program Files\Sonstige\WinUAE\', PLUGIN: 'C:\Program Files\Sonstige\WinUAE\'
CLOCKFREQ: QPF 2.81MHz (2.81MHz, DIV=1)
Max hardware surface size: 8192x8192
DriverCaps: 95c07fc1 806ab230 0002e311 22ad5420 00000000 00000000
DDCAPS_BLT,DDCAPS_BLTQUEUE,DDCAPS_BLTFOURCC,DDCAPS_BLTCOLORFILL,DDCAPS_BLTSTRETCH,DDCAPS_CANBLTSYSMEM,DDCAPS_COLORKEY,DDCAPS_COLORKEYHWASSIST,DDCAPS_GDI,DDCAPS_OVERLAY,DDCAPS_3D,DDCAPS2_CANRENDERWINDOWED,DDCAPS2_FLIPNOVSYNC,DDCAPS2_FLIPINTERVAL,DDCAPS2_NONLOCALVIDMEM,DDCAPS2_WIDESURFACES,DDCKEYCAPS_DESTBLT,DDCKEYCAPS_SRCBLT
HELCaps   : f4c08241 00000001 00000200 0003fce3 00000000 00000347
DDCAPS_BLT,DDCAPS_BLTCOLORFILL,DDCAPS_BLTSTRETCH,DDCAPS_CANBLTSYSMEM,DDCAPS_CANCLIP,DDCAPS_CANCLIPSTRETCHED,DDCAPS_COLORKEY,DDCAPS_3D,DDCAPS_PALETTE,DDCAPS2_CERTIFIED,DDCKEYCAPS_SRCBLT
Enumerating display devices.. 
'Primärer Anzeigetreiber' 'display' NULL
'ATI Radeon HD 4800 Series   ' '\\.\DISPLAY1' 67685559-3106-11D0-B97100AA00342F9F
Sorting devices and modes..
Desktop: W=1920 H=1200 B=32. MaxW=1920 MaxH=1200 CXVS=1920 CYVS=1200
0: 640x480, 16-bit (59,60)
1: 640x480, 32-bit (59,60)
2: 720x480, 16-bit (59,60)
3: 720x480, 32-bit (59,60)
4: 720x576, 16-bit (59,60)
5: 720x576, 32-bit (59,60)
6: 800x600, 16-bit (59,60)
7: 800x600, 32-bit (59,60)
8: 848x480, 16-bit (59,60)
9: 848x480, 32-bit (59,60)
10: 1024x768, 16-bit (59,60)
11: 1024x768, 32-bit (59,60)
12: 1152x648, 16-bit (59,60)
13: 1152x648, 32-bit (59,60)
14: 1152x864, 16-bit (59,60)
15: 1152x864, 32-bit (59,60)
16: 1280x720, 16-bit (!50,59,60)
17: 1280x720, 32-bit (!50,59,60)
18: 1280x768, 16-bit (59,60)
19: 1280x768, 32-bit (59,60)
20: 1280x800, 16-bit (59,60)
21: 1280x800, 32-bit (59,60)
22: 1280x960, 16-bit (59,60)
23: 1280x960, 32-bit (59,60)
24: 1280x1024, 16-bit (59,60)
25: 1280x1024, 32-bit (59,60)
26: 1360x768, 16-bit (59,60)
27: 1360x768, 32-bit (59,60)
28: 1360x1024, 16-bit (59,60)
29: 1360x1024, 32-bit (59,60)
30: 1400x1050, 16-bit (59,60)
31: 1400x1050, 32-bit (59,60)
32: !1440x480, 16-bit (!14,!15)
33: !1440x480, 32-bit (!14,!15)
34: !1440x576, 16-bit (!12)
35: !1440x576, 32-bit (!12)
36: 1440x900, 16-bit (59,60)
37: 1440x900, 32-bit (59,60)
38: 1600x1200, 16-bit (59,60)
39: 1600x1200, 32-bit (59,60)
40: 1680x1050, 16-bit (59,60)
41: 1680x1050, 32-bit (59,60)
42: 1776x1000, 16-bit (59,60)
43: 1776x1000, 32-bit (59,60)
44: 1920x1080, 16-bit (59,60)
45: 1920x1080, 32-bit (59,60)
46: 1920x1200, 16-bit (59,60)
47: 1920x1200, 32-bit (59,60)
'Primärer Anzeigetreiber (1920*1200)', 48 display modes (enabled)
Desktop: W=1920 H=1200 B=32. MaxW=1920 MaxH=1200 CXVS=1920 CYVS=1200
0: 640x480, 16-bit (59,60)
1: 640x480, 32-bit (59,60)
2: 720x480, 16-bit (59,60)
3: 720x480, 32-bit (59,60)
4: 720x576, 16-bit (59,60)
5: 720x576, 32-bit (59,60)
6: 800x600, 16-bit (59,60)
7: 800x600, 32-bit (59,60)
8: 848x480, 16-bit (59,60)
9: 848x480, 32-bit (59,60)
10: 1024x768, 16-bit (59,60)
11: 1024x768, 32-bit (59,60)
12: 1152x648, 16-bit (59,60)
13: 1152x648, 32-bit (59,60)
14: 1152x864, 16-bit (59,60)
15: 1152x864, 32-bit (59,60)
16: 1280x720, 16-bit (!50,59,60)
17: 1280x720, 32-bit (!50,59,60)
18: 1280x768, 16-bit (59,60)
19: 1280x768, 32-bit (59,60)
20: 1280x800, 16-bit (59,60)
21: 1280x800, 32-bit (59,60)
22: 1280x960, 16-bit (59,60)
23: 1280x960, 32-bit (59,60)
24: 1280x1024, 16-bit (59,60)
25: 1280x1024, 32-bit (59,60)
26: 1360x768, 16-bit (59,60)
27: 1360x768, 32-bit (59,60)
28: 1360x1024, 16-bit (59,60)
29: 1360x1024, 32-bit (59,60)
30: 1400x1050, 16-bit (59,60)
31: 1400x1050, 32-bit (59,60)
32: !1440x480, 16-bit (!14,!15)
33: !1440x480, 32-bit (!14,!15)
34: !1440x576, 16-bit (!12)
35: !1440x576, 32-bit (!12)
36: 1440x900, 16-bit (59,60)
37: 1440x900, 32-bit (59,60)
38: 1600x1200, 16-bit (59,60)
39: 1600x1200, 32-bit (59,60)
40: 1680x1050, 16-bit (59,60)
41: 1680x1050, 32-bit (59,60)
42: 1776x1000, 16-bit (59,60)
43: 1776x1000, 32-bit (59,60)
44: 1920x1080, 16-bit (59,60)
45: 1920x1080, 32-bit (59,60)
46: 1920x1200, 16-bit (59,60)
47: 1920x1200, 32-bit (59,60)
'ATI Radeon HD 4800 Series    (1920*1200)', 48 display modes (enabled)
Display buffer mode = 1
Enumerating DirectSound devices..
Enumerating WASAPI devices...
openal32.dll 6.14.357.25
Enumerating OpenAL devices..
Enumeration end
0:WA: Default Audio Device
1:WA: SPDIF-Out (Creative SB X-Fi)
2:WA: Lautsprecher (Creative SB X-Fi)
3:DS: Primärer Soundtreiber
4:DS: Lautsprecher (Creative SB X-Fi)
5:DS: SPDIF-Out (Creative SB X-Fi)
6:AL: Default [SB X-Fi Audio [D000]]
7:AL: SB X-Fi Audio [D000]
8:AL: Generic Software on Lautsprecher (Creative SB X-Fi)
9:AL: Generic Software on SPDIF-Out (Creative SB X-Fi)
Enumerating recording devices:
0:DS: Primärer Soundaufnahmetreiber
1:DS: Mikrofon (Creative SB X-Fi)
2:DS: Line-In (Creative SB X-Fi)
3:DS: "Was Sie hören" (Creative SB X-Fi)
4:DS: Auxiliary (Creative SB X-Fi)
5:DS: Digital-In (Creative SB X-Fi)
done
Filesystem charset (ACP=1252,FSCP=28605):
 00: 0000        01: 0001        02: 0002        03: 0003       
 04: 0004        05: 0005        06: 0006        07: 0007       
 08: 0008        09: 0009        0A: 000A        0B: 000B       
 0C: 000C        0D: 000D        0E: 000E        0F: 000F       
 10: 0010        11: 0011        12: 0012        13: 0013       
 14: 0014        15: 0015        16: 0016        17: 0017       
 18: 0018        19: 0019        1A: 001A        1B: 001B       
 1C: 001C        1D: 001D        1E: 001E        1F: 001F       
 20: 0020        21: 0021        22: 0022        23: 0023       
 24: 0024        25: 0025        26: 0026        27: 0027       
 28: 0028        29: 0029        2A: 002A        2B: 002B       
 2C: 002C        2D: 002D        2E: 002E        2F: 002F       
 30: 0030        31: 0031        32: 0032        33: 0033       
 34: 0034        35: 0035        36: 0036        37: 0037       
 38: 0038        39: 0039        3A: 003A        3B: 003B       
 3C: 003C        3D: 003D        3E: 003E        3F: 003F       
 40: 0040        41: 0041        42: 0042        43: 0043       
 44: 0044        45: 0045        46: 0046        47: 0047       
 48: 0048        49: 0049        4A: 004A        4B: 004B       
 4C: 004C        4D: 004D        4E: 004E        4F: 004F       
 50: 0050        51: 0051        52: 0052        53: 0053       
 54: 0054        55: 0055        56: 0056        57: 0057       
 58: 0058        59: 0059        5A: 005A        5B: 005B       
 5C: 005C        5D: 005D        5E: 005E        5F: 005F       
 60: 0060        61: 0061        62: 0062        63: 0063       
 64: 0064        65: 0065        66: 0066        67: 0067       
 68: 0068        69: 0069        6A: 006A        6B: 006B       
 6C: 006C        6D: 006D        6E: 006E        6F: 006F       
 70: 0070        71: 0071        72: 0072        73: 0073       
 74: 0074        75: 0075        76: 0076        77: 0077       
 78: 0078        79: 0079        7A: 007A        7B: 007B       
 7C: 007C        7D: 007D        7E: 007E        7F: 007F       
 80: 20AC (0080) 81: 0081        82: 201A (0082) 83: 0192 (0083)
 84: 201E (0084) 85: 2026 (0085) 86: 2020 (0086) 87: 2021 (0087)
 88: 02C6 (0088) 89: 2030 (0089) 8A: 0160 (008A) 8B: 2039 (008B)
 8C: 0152 (008C) 8D: 008D        8E: 017D (008E) 8F: 008F       
 90: 0090        91: 2018 (0091) 92: 2019 (0092) 93: 201C (0093)
 94: 201D (0094) 95: 2022 (0095) 96: 2013 (0096) 97: 2014 (0097)
 98: 02DC (0098) 99: 2122 (0099) 9A: 0161 (009A) 9B: 203A (009B)
 9C: 0153 (009C) 9D: 009D        9E: 017E (009E) 9F: 0178 (009F)
 A0: 00A0        A1: 00A1        A2: 00A2        A3: 00A3       
 A4: 00A4 (20AC) A5: 00A5        A6: 00A6 (0160) A7: 00A7       
 A8: 00A8 (0161) A9: 00A9        AA: 00AA        AB: 00AB       
 AC: 00AC        AD: 00AD        AE: 00AE        AF: 00AF       
 B0: 00B0        B1: 00B1        B2: 00B2        B3: 00B3       
 B4: 00B4 (017D) B5: 00B5        B6: 00B6        B7: 00B7       
 B8: 00B8 (017E) B9: 00B9        BA: 00BA        BB: 00BB       
 BC: 00BC (0152) BD: 00BD (0153) BE: 00BE (0178) BF: 00BF       
 C0: 00C0        C1: 00C1        C2: 00C2        C3: 00C3       
 C4: 00C4        C5: 00C5        C6: 00C6        C7: 00C7       
 C8: 00C8        C9: 00C9        CA: 00CA        CB: 00CB       
 CC: 00CC        CD: 00CD        CE: 00CE        CF: 00CF       
 D0: 00D0        D1: 00D1        D2: 00D2        D3: 00D3       
 D4: 00D4        D5: 00D5        D6: 00D6        D7: 00D7       
 D8: 00D8        D9: 00D9        DA: 00DA        DB: 00DB       
 DC: 00DC        DD: 00DD        DE: 00DE        DF: 00DF       
 E0: 00E0        E1: 00E1        E2: 00E2        E3: 00E3       
 E4: 00E4        E5: 00E5        E6: 00E6        E7: 00E7       
 E8: 00E8        E9: 00E9        EA: 00EA        EB: 00EB       
 EC: 00EC        ED: 00ED        EE: 00EE        EF: 00EF       
 F0: 00F0        F1: 00F1        F2: 00F2        F3: 00F3       
 F4: 00F4        F5: 00F5        F6: 00F6        F7: 00F7       
 F8: 00F8        F9: 00F9        FA: 00FA        FB: 00FB       
 FC: 00FC        FD: 00FD        FE: 00FE        FF: 00FF       
End
CW: No Catweasel detected
PARAPORT: no ParaPort.dll, direct parallel port emulation disabled
IPC: Named Pipe '\\.\pipe\WinUAE_1' open
IPC: Named Pipe '\\.\pipe\WinUAE_COM_1' open
Serial port enumeration..
Serial port enumeration end
RawInput enumeration..
RAWINPUT: found 7 devices
0001003B mouse: '\\?\HID#VID_046D&PID_C001#7&20334c58&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}'
id=256 buttons=3 hw=0 rate=0
000B0039 mouse: '\\?\ACPI#PNP0F13#4&26108748&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}'
id=32 buttons=5 hw=0 rate=100
'Logitech First/Pilot Mouse+ (USB) [046D/C001]' ('\\?\HID#VID_046D&PID_C001#7&20334c58&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}')
'PS/2-kompatible Maus' ('\\?\ACPI#PNP0F13#4&26108748&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}')
DirectInput enumeration.. Keyboards..
I=6F1D2B61-D5A0-11CF-BFC7444553540000 P=6F1D2B61-D5A0-11CF-BFC7444553540000
'Tastatur' 'Tastatur' 00000413 [Keyboard]
DirectInput enumeration.. Game controllers..
I=5E5CE680-C3E4-11DE-8002444553540000 P=C218046D-0000-0000-0000504944564944
'Logitech RumblePad 2 USB' 'Logitech RumblePad 2 USB' 00010214 [Game controller]
Windowsmouse initialization..
Catweasel joymouse initialization..
wintab tablet initialization..
Tablet: no wintab32.dll
end
Logitech RumblePad 2 USB (PGUID=C218046D-0000-0000-0000504944564944):
00 000 'X-Achse' (-99,0)
04 004 'Y-Achse' (-98,0)
08 008 'Z-Achse' (-97,0)
14 020 'Z-Rotation' (-87,0)
20 032 'Mehrwegeschalter (X)' (-69,1)
20 032 'Mehrwegeschalter (Y)' (-69,2)
Logitech RumblePad 2 USB (PGUID=C218046D-0000-0000-0000504944564944):
30 048 'Taste 0' (48,-1)
31 049 'Taste 1' (49,-1)
32 050 'Taste 2' (50,-1)
33 051 'Taste 3' (51,-1)
34 052 'Taste 4' (52,-1)
35 053 'Taste 5' (53,-1)
36 054 'Taste 6' (54,-1)
37 055 'Taste 7' (55,-1)
38 056 'Taste 8' (56,-1)
39 057 'Taste 9' (57,-1)
3A 058 'Taste 10' (58,-1)
3B 059 'Taste 11' (59,-1)
00 000 'X-Achse [-]' (1000,-1)
00 000 'X-Achse [+]' (1001,-1)
04 004 'Y-Achse [-]' (1008,-1)
04 004 'Y-Achse [+]' (1009,-1)
08 008 'Z-Achse [-]' (1016,-1)
08 008 'Z-Achse [+]' (1017,-1)
14 020 'Z-Rotation [-]' (1040,-1)
14 020 'Z-Rotation [+]' (1041,-1)
20 032 'Mehrwegeschalter (X) [-]' (1066,-1)
20 032 'Mehrwegeschalter (X) [+]' (1067,-1)
20 032 'Mehrwegeschalter (Y) [-]' (1068,-1)
20 032 'Mehrwegeschalter (Y) [+]' (1069,-1)
Tastatur (PGUID=6F1D2B61-D5A0-11CF-BFC7444553540000):
01 001 'ESC' (0,-1)
02 002 '1' (0,-1)
03 003 '2' (0,-1)
04 004 '3' (0,-1)
05 005 '4' (0,-1)
06 006 '5' (0,-1)
07 007 '6' (0,-1)
08 008 '7' (0,-1)
09 009 '8' (0,-1)
0A 010 '9' (0,-1)
0B 011 '0' (0,-1)
0C 012 'ß' (0,-1)
0D 013 'AKUT' (0,-1)
0E 014 'RÜCK' (0,-1)
0F 015 'TABULATOR' (0,-1)
10 016 'Q' (0,-1)
11 017 'W' (0,-1)
12 018 'E' (0,-1)
13 019 'R' (0,-1)
14 020 'T' (0,-1)
15 021 'Z' (0,-1)
16 022 'U' (0,-1)
17 023 'I' (0,-1)
18 024 'O' (0,-1)
19 025 'P' (0,-1)
1A 026 'ü' (0,-1)
1B 027 '+' (0,-1)
1C 028 'EINGABE' (0,-1)
1D 029 'STRG' (0,-1)
1E 030 'A' (0,-1)
1F 031 'S' (0,-1)
20 032 'D' (0,-1)
21 033 'F' (0,-1)
22 034 'G' (0,-1)
23 035 'H' (0,-1)
24 036 'J' (0,-1)
25 037 'K' (0,-1)
26 038 'L' (0,-1)
27 039 'ö' (0,-1)
28 040 'ä' (0,-1)
29 041 'ZIRKUMFLEX' (0,-1)
2A 042 'UMSCHALT' (0,-1)
2B 043 '#' (0,-1)
2C 044 'Y' (0,-1)
2D 045 'X' (0,-1)
2E 046 'C' (0,-1)
2F 047 'V' (0,-1)
30 048 'B' (0,-1)
31 049 'N' (0,-1)
32 050 'M' (0,-1)
33 051 ',' (0,-1)
34 052 '.' (0,-1)
35 053 '-' (0,-1)
36 054 'UMSCHALT RECHTS' (0,-1)
37 055 '*' (0,-1)
38 056 'ALT' (0,-1)
39 057 'LEER' (0,-1)
3A 058 'FESTSTELL' (0,-1)
3B 059 'F1' (0,-1)
3C 060 'F2' (0,-1)
3D 061 'F3' (0,-1)
3E 062 'F4' (0,-1)
3F 063 'F5' (0,-1)
40 064 'F6' (0,-1)
41 065 'F7' (0,-1)
42 066 'F8' (0,-1)
43 067 'F9' (0,-1)
44 068 'F10' (0,-1)
45 069 'NUM-FESTSTELL' (0,-1)
46 070 'ROLLEN-FESTSTELL' (0,-1)
47 071 '7 (ZEHNERTASTATUR)' (0,-1)
48 072 '8 (ZEHNERTASTATUR)' (0,-1)
49 073 '9 (ZEHNERTASTATUR)' (0,-1)
4A 074 '-' (0,-1)
4B 075 '4 (ZEHNERTASTATUR)' (0,-1)
4C 076 '5 (ZEHNERTASTATUR)' (0,-1)
4D 077 '6 (ZEHNERTASTATUR)' (0,-1)
4E 078 '+' (0,-1)
4F 079 '1 (ZEHNERTASTATUR)' (0,-1)
50 080 '2 (ZEHNERTASTATUR)' (0,-1)
51 081 '3 (ZEHNERTASTATUR)' (0,-1)
52 082 '0 (ZEHNERTASTATUR)' (0,-1)
53 083 'KOMMA (ZEHNERTASTATUR)' (0,-1)
56 086 '<' (0,-1)
57 087 'F11' (0,-1)
58 088 'F12' (0,-1)
90 144 'Vorheriger Titel' (0,-1)
99 153 'Nächster Titel' (0,-1)
9C 156 'EINGABE (ZEHNERTASTATUR)' (0,-1)
9D 157 'STRG-RECHTS' (0,-1)
A0 160 'Ton aus' (0,-1)
A1 161 'Rechner' (0,-1)
A2 162 'Wiedergabe/Pause' (0,-1)
A4 164 'Medienstopp' (0,-1)
AE 174 'Lautstärke -' (0,-1)
B0 176 'Lautstärke +' (0,-1)
B2 178 'Web/Startseite' (0,-1)
B5 181 ' (ZEHNERTASTATUR)' (0,-1)
B7 183 'DRUCK' (0,-1)
B8 184 'ALT GR' (0,-1)
C5 197 'PAUSE' (0,-1)
C7 199 'POS1' (0,-1)
C8 200 'NACH-OBEN' (0,-1)
C9 201 'BILD-NACH-OBEN' (0,-1)
CB 203 'NACH-LINKS' (0,-1)
CD 205 'NACH-RECHTS' (0,-1)
CF 207 'ENDE' (0,-1)
D0 208 'NACH-UNTEN' (0,-1)
D1 209 'BILD-NACH-UNTEN' (0,-1)
D2 210 'EINFG' (0,-1)
D3 211 'ENTF' (0,-1)
DB 219 'LINKE WINDOWS' (0,-1)
DC 220 'RECHTE WINDOWS' (0,-1)
DD 221 'ANWENDUNG' (0,-1)
DE 222 'Stromversorgung' (0,-1)
DF 223 'Energie sparen' (0,-1)
E3 227 'Aktivieren' (0,-1)
E5 229 'Suchen' (0,-1)
E6 230 'Favoriten' (0,-1)
E7 231 'Aktualisieren' (0,-1)
E8 232 'Webstopp' (0,-1)
E9 233 'Vorwärts' (0,-1)
EA 234 'Zurück' (0,-1)
EB 235 'Arbeitsplatz' (0,-1)
EC 236 'Mail' (0,-1)
ED 237 'Medien' (0,-1)
Max Z3FastRAM 1536M. Total physical RAM 3326M
load config 'E:\Daten\Sonstige\Amiga\Configifurations\default.uae':0
load failed
failed to load config 'E:\Daten\Sonstige\Amiga\Configifurations\default.uae'
LCD: Logitech LCD system not detected
'E:\Daten\Sonstige\Amiga\Configifurations\configuration.cache' loaded successfully
Entering GUI idle loop
load config 'E:\Daten\Sonstige\Amiga\Configifurations\68040 Standard.uae':0
Log (enabled): 'C:\Program Files\Sonstige\WinUAE\winuaelog.txt'

Ambermoon · 31 July 2010, 15:56

winuaelog

Code:

2010-07-31 15:45:20
20-828: WinUAE 2.2.0 (2010.06.28) (6.1 [2]) 32-bit 6.F0B 4
(c) 1995-2001 Bernd Schmidt   - Core UAE concept and implementation.
(c) 1998-2010 Toni Wilen      - Win32 port, core code updates.
(c) 1996-2001 Brian King      - Win32 port, Picasso96 RTG, and GUI.
(c) 1996-1999 Mathias Ortmann - Win32 port and bsdsocket support.
(c) 2000-2001 Bernd Meyer     - JIT engine.
(c) 2000-2005 Bernd Roesch    - MIDI input, many fixes.
Press F12 to show the Settings Dialog (GUI), Alt-F4 to quit.
End+F1 changes floppy 0, End+F2 changes floppy 1, etc.
20-829: 'C:\Program Files\Sonstige\WinUAE\winuae.exe'
20-829: EXE: 'C:\Program Files\Sonstige\WinUAE\', DATA: 'C:\Program Files\Sonstige\WinUAE\', PLUGIN: 'C:\Program Files\Sonstige\WinUAE\'
20-829: NATMEM: Our special area: 0x10040000-0x20040000 (10000000 256M)
20-829: RTAREA located at 00F00000
20-829: shmget of size 65536 (64k) for rtarea
20-829: VirtualAlloc 00F00000 - 00F10000 10000 (64k) ok
20-829: uaegfx.card magic code: 00F01820-00F0195E ABI=00000000
20-831: shmget of size 8388608 (8192k) for fast
20-831: VirtualAlloc 00200000 - 00A00020 800020 (8192k) ok
20-836: shmget of size 65536 (64k) for filesys
20-837: shmget of size 524288 (512k) for kick
20-837: VirtualAlloc 00F80000 - 01000020 80020 (512k) ok
20-837: Entered action_replay_load ()
20-837: shmget of size 1048576 (1024k) for chip
20-837: VirtualAlloc 00000000 - 00100020 100020 (1024k) ok
20-837: shmget of size 524288 (512k) for bogo
20-837: VirtualAlloc 00C00000 - 00C80020 80020 (512k) ok
20-837: ROM loader..
20-843: Known ROM 'KS ROM v3.1 (A500,A600,A2000)' loaded
20-844: ROM loader end
20-844: memory init end
20-853: No disk in drive 0.
20-853: Resetting frame rate hack
20-853: Building CPU table for configuration: 68040/68040
20-875: 1879 CPU functions
20-875: Building CPU, 46224 opcodes (4 0 0)
20-875: CPU=68040, FPU=68040, MMU=0, JIT=CPU/FPU=8192.
20-875: CPUID level=10, Family=6, Model=15, Mask=11, Vendor=GenuineIntel [0]
20-875: JIT: Setting signal handler
20-875: JIT: Building Compiler function table
20-876: JIT: Supposedly 42381 compileable opcodes!
20-911: DirectDraw GUID=NULL
20-911: W=1920 H=1200 B=32 CT=9
20-915: winuae_active(0)
20-939: Direct3D: Pixel shader 2.0+ support detected, shader filters enabled.
21-093: D3D9Ex: 00000052 ALPHA DYNAMIC 
21-093: D3D9Ex: PS=3.0 VS=3.0 8192*8192*0 FS 32-bit
21-094: D3D9Ex: Attempting to load 'C:\Program Files\Sonstige\WinUAE\plugins\filtershaders\direct3d\_winuae.fx'
21-121: D3D9Ex: pixelshader filter 'C:\Program Files\Sonstige\WinUAE\plugins\filtershaders\direct3d\_winuae.fx' enabled
21-200: D3D9Ex: pixelshader filter 'C:\Program Files\Sonstige\WinUAE\plugins\filtershaders\direct3d\hq2x.fx' enabled
21-205: D3D9Ex: 376*286 texture allocated, bits per pixel 32
21-336: POS (0 0 1920 1200) - (-772 -457 -397 -171)[375,286] (772 457)
21-338: Resetting frame rate hack
21-338: clipboard: reset (00000000)
21-339: Volume E:\ FS=NTFS maxlen=255 flags=03E700FF
21-340: Volume E:\ FS=NTFS maxlen=255 flags=03E700FF
21-341: Volume E:\ FS=NTFS maxlen=255 flags=03E700FF
21-341: memory init end
21-341: Thread 'filesys' started (1076)
21-341: Thread 'filesys' started (1104)
21-341: Thread 'filesys' started (1132)
21-341: Reset at 00000000
21-341: 00000000    2048K/2 =    1024K Chip memory
21-341: 00200000    8192K/0 =    8192K <none>
21-342: 00A00000    2048K/0 =    2048K CIA
21-342: 00C00000     512K/1 =     512K Slow memory
21-342: 00C80000    1024K/0 =    1024K Custom chipset
21-342: 00D80000     256K/0 =     256K Gayle (low)
21-342: 00DC0000      64K/0 =      64K Battery backed up clock (none)
21-342: 00DD0000      64K/0 =      64K Gayle (low)
21-342: 00DE0000      64K/0 =      64K Motherboard Resources
21-342: 00DF0000      64K/0 =      64K Custom chipset
21-343: 00E00000     512K/1 =     512K Kickstart ROM (FC24AE0D)
21-343: =KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k)
21-343: 00E80000      64K/0 =      64K Autoconfig
21-343: 00E90000     448K/0 =     448K <none>
21-343: 00F00000      64K/1 =      64K UAE Boot ROM
21-343: 00F10000     448K/0 =     448K <none>
21-344: 00F80000     512K/1 =     512K Kickstart ROM (FC24AE0D)
21-344: =KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k)
21-344: 01000000    4080M/0 =    4080M <none>
21-353: P96FREQ: 312*50 = 15600 / 50 = 312
21-353: PAL mode V=50Hz H=15600Hz (227x312)
21-363: hardreset, memory cleared
21-376 [0 226x015]: SERIAL: period=372, baud=9600, hsyncs=16, bits=8, PC=f8018a
21-378 [0 226x015]: Fastcard: mapped @$200000: 8MB fast memory
21-378 [0 226x015]:    Card 1 (ZorroII) done.
21-379 [0 226x015]: Filesystem: mapped memory @$e90000.
21-379 [0 226x015]:    Card 2 (ZorroII) done.
21-379 [0 226x015]: Memory map after autoconfig:
21-379 [0 226x015]: 00000000    2048K/2 =    1024K Chip memory
21-379 [0 226x015]: 00200000    8192K/1 =    8192K Fast memory
21-379 [0 226x015]: 00A00000    2048K/0 =    2048K CIA
21-379 [0 226x015]: 00C00000     512K/1 =     512K Slow memory
21-379 [0 226x015]: 00C80000    1024K/0 =    1024K Custom chipset
21-379 [0 226x015]: 00D80000     256K/0 =     256K Gayle (low)
21-379 [0 226x015]: 00DC0000      64K/0 =      64K Battery backed up clock (RF5C01A)
21-379 [0 226x015]: 00DD0000      64K/0 =      64K Gayle (low)
21-379 [0 226x015]: 00DE0000      64K/0 =      64K Motherboard Resources
21-379 [0 226x015]: 00DF0000      64K/0 =      64K Custom chipset
21-380 [0 226x015]: 00E00000     512K/1 =     512K Kickstart ROM (FC24AE0D)
21-380 [0 226x015]: =KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k)
21-380 [0 226x015]: 00E80000      64K/0 =      64K <none>
21-380 [0 226x015]: 00E90000      64K/0 =      64K Filesystem Autoconfig Area
21-380 [0 226x015]: 00EA0000     384K/0 =     384K <none>
21-380 [0 226x015]: 00F00000      64K/1 =      64K UAE Boot ROM
21-380 [0 226x015]: 00F10000     448K/0 =     448K <none>
21-381 [0 226x015]: 00F80000     512K/1 =     512K Kickstart ROM (FC24AE0D)
21-381 [0 226x015]: =KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k)
21-381 [0 226x015]: 01000000    4080M/0 =    4080M <none>
21-422: WASAPI: '{0.0.0.00000000}.{afc64a0c-4077-49f3-8e06-93f1c99b12cc}'
WASAPI: EX=0 CH=2 FREQ=48000 BUF=512 (4096)
21-428: P96FREQ: 312*50 = 15600 / 50 = 312
21-428: PAL mode V=50Hz H=15600Hz (227x312)
21-560 [6 226x018]: Mounting uaehf.device 0 (0):
21-560 [6 226x018]: FS: mounted virtual unit DH0 (E:\Daten\Sonstige\Amiga\!HDS\wb31_standard)
21-560 [6 226x018]: Mounting uaehf.device 1 (0):
21-560 [6 226x018]: FS: mounted virtual unit DH1 (E:\Daten\Sonstige\Amiga\!HDS\programme)
21-560 [6 226x018]: Mounting uaehf.device 2 (0):
21-560 [6 226x018]: FS: mounted virtual unit DH2 (E:\Daten\Sonstige\Amiga\!HDS\spiele)
21-697 [13 226x019]: FS: WB31 (flags=00000002,E=0,ED=1,EF=0,native='E:\Daten\Sonstige\Amiga\!HDS\wb31_standard') starting..
21-818 [19 226x085]: FS: Programme (flags=00000002,E=0,ED=1,EF=0,native='E:\Daten\Sonstige\Amiga\!HDS\programme') starting..
21-819 [19 225x093]: FS: Spiele (flags=00000002,E=0,ED=1,EF=0,native='E:\Daten\Sonstige\Amiga\!HDS\spiele') starting..
21-819 [19 226x101]: clipboard task init: 00219718
21-820 [19 226x109]: clipboard process init: 00219718
21-887 [22 226x242]: FILESYS: flushing cache unit 0 (max 0 items)
22-195 [38 226x114]: FILESYS: flushing cache unit 0 (max 0 items)
22-208 [38 226x306]: FILESYS: flushing cache unit 0 (max 0 items)
22-219 [39 226x185]: FILESYS: flushing cache unit 0 (max 0 items)
22-373 [47 226x098]: FILESYS: flushing cache unit 0 (max 0 items)
22-384 [47 226x266]: FILESYS: flushing cache unit 1 (max 0 items)
22-394 [48 226x122]: FILESYS: flushing cache unit 2 (max 0 items)
23-850 [121 226x093]: clipboard initialized
43-776 [1040 000x000]: winuae_inactive(0)
50-028 [1040 000x000]: winuae_active(0)
50-263: winuae_inactive(0)

Toni Wilen · 31 July 2010, 16:08

I think I know whats wrong (if all other d3d filters work?) Try http://www.winuae.net/files/b/winuae.zip

Ambermoon · 31 July 2010, 16:33

Thanks for the superfast reply!

But unfortunately the attached exe doesn't solve the problem. Additionally I tried various other D3D filters, those weren't working correctly either. Neither with the 2.2.0 build nor with the new exe.

The image looks somewhat different (less blurry), but apart from that no change. Still very lo-res and worse than the unfiltered image.

Since I can't do more attachments I uploaded a screenshot to imageshack (config was the same as before):
http://img507.imageshack.us/img507/2...uild1image.jpg

Toni Wilen · 31 July 2010, 16:39

It is either filter panel setup issue (not 1:1 scaling) or some display card configuration setting (AA?) if even d3d null filter is blurry.

Ambermoon · 31 July 2010, 16:55

The null filter looks just fine in the newer builds, just the 'enhancing' filters show the blurry picture.

And since 2.0.1 is working flawlessly, I don't think it's a wrong display card (or monitor) configuration setting eiher, that wouldn't affect just the newer builds.

What I didn't mention before (just marked it red in the v220_filter_settings screenshot above): The combo box next to the filter selection combo box is greyed out (and not accessible) for me in the 2.1.0+ versions. Is this normal? In previous builds one can select Point/Bicubic in this combo box when D3D:hq2x is selected.

Toni Wilen · 31 July 2010, 17:23

Quote:

Originally Posted by Ambermoon

The null filter looks just fine in the newer builds, just the 'enhancing' filters show the blurry picture.

And since 2.0.1 is working flawlessly, I don't think it's a wrong display card (or monitor) configuration setting eiher, that wouldn't affect just the newer builds.

It can be display configuration (make sure you don't have any forced settings in catalyst control center) because old and new D3D does not have much in common.

Quote:

What I didn't mention before (just marked it red in the v220_filter_settings screenshot above): The combo box next to the filter selection combo box is greyed out (and not accessible) for me in the 2.1.0+ versions. Is this normal? In previous builds one can select Point/Bicubic in this combo box when D3D:hq2x is selected.

It is under filter extra settings. (read changelogs too)

Ambermoon · 31 July 2010, 17:39

Quote:

It is under filter extra settings. (read changelogs too)

That's what I thought, just wanted to be sure.

Quote:

It can be display configuration (make sure you don't have any forced settings in catalyst control center) because old and new D3D does not have much in common.

Triple checked that and tried it with and without Catalyst A.I., just to be sure. No change.

Anyway, since this does seem to happen exclusively to me, maybe it's something really weird with my system (although I can't imagine what that should be). At least I can stick to the 2.0.1 version which is working just fine.

And: thanks for your time (and of course for your hard work in general)!

Toni Wilen · 31 July 2010, 17:43

Start from scratch (move/delete default.uae too), test it step by step, first only enable d3d mode and d3d filter and so on until image becomes blurry.

Ambermoon · 31 July 2010, 18:16

Just tried 2.2.0 on my HTPC, which, as far as I can remember, never ever ran any WinUAE version before. It's also a Windows 7 machine but with an nVidia graphics card (9600GT). Same Symptoms.

I really don't want to bother, but does hq2x in 2.2.0 really look like the hq2x v2.0.1 screenshot in my first post for you when used with high resolutions?

If you want I'd be glad to send you a screen of a more common game so it's easier for you to compare the results with your own. Maybe Monkey Island or something.

Next thing I will try is setting up a new VirtualBox machine with XP and try WinUAE on it. I'm pretty curious what happens.

Toni Wilen · 31 July 2010, 18:23

I am not going to do any kind of testing without a) statefile of static screen, b) exact configuration. Other kind of comparisons are invalid.

Also d3dhq2x is worst for testing because it is the most complex and uses extra texture buffers. Something like scale2x is much better testing filter.

Ambermoon · 31 July 2010, 19:23

Fair enough.

Since the good old KS1.3 start screen is perfectly suitable for showing the effect I will use that one in conjuction with the A500 quickstart config. The upper right (diagonal) corner of the KS-diskette is an extremely good spot to show the differences. Only changes will be the display (fullscreen 1920x1200) and filter settings. This will make things pretty easy and minimizes sources of error.

Software Scale2x works normally, so I reckon you meant D3D: Scale2x. That would be fine for me, it's flawed too (for me at least). Since the effect is better noticable with the higher quality filtering algorithms I will send you d3d:h2qx (which really looks completely borked in 2.2.0) state files too, just for reference.

Additionally to the statefiles I'll send you the configs and screenshots that show how things look over here with the according settings. For both 2.0.1 and 2.2.0.

Anything special I have to be aware of when creating the statefiles?

What I'd do is this:

1. Creating the configs
2. Start WinUAE with a premade config
3. Start the emulation
4. Save a statefile (F12 -> Misc. -> Save State...)
5. Save a screenshot
6. Quit WinUAE
7. Go to 2.

Would that be an acceptable approach?

Toni Wilen · 31 July 2010, 19:44

No need for statefiles if you use standard KS "insert disk" screens. Only configuration file needed so that I can have exact same display settings.

Ambermoon · 31 July 2010, 20:50

Attached are the config files and screenshots. d3d:scale2x and d3d:hq2x at 1920x1200 for both WinUAE 2.0.1 and 2.2.0. I did a clean install for both versions.

With d3d:hq2x there is a really huge difference between the versions (see 'teaser image' below). From looking at the images I would suspect that 2.0.1 applies the filter to the full extent of the selected resolution which gives a very clean image. This is the way it works for example in DosBox builds with d3d support too. 2.2.0 on the other hand seems to apply the filter only once and seems to upscale the resulting image to 1920x1200. But that, of course, is pure speculation.

d3d:scale2x does look strange in 2.2.0 too, although it's not as easy to spot. Looks like the image simply isn't filtered at all but instead oddly scaled.

Ambermoon · 31 July 2010, 20:52

Sorry, forgot the attachment...

Toni Wilen · 01 August 2010, 16:11

http://www.winuae.net/files/b/winuae.zip should fix this problem, please confirm.

("new" d3d filter had very stupid design flaw..)

btw, I couldn't get exact same hq2x filter result using old winuae and neither exactly same as in your screenshot either. (and there was also bug in d3dhq2x table coordinates, [input_width, input_height] coordinate pair was [input_width, input_width]..)

Ambermoon · 01 August 2010, 21:58

Quote:

Originally Posted by Toni Wilen

("new" d3d filter had very stupid design flaw.

Don't all bugs look stupid once one found them?

The fixed version is working pretty well, although 2.0.1 still looks better. Something is still different than before, strange that you aren't getting the same result with 2.0.1 that I get. Especially 45°-lines aren't looking as good as they normally should. This applies to most d3d filters I tested, more noticable with the not so good ones (d3d:gs2x is a good example, the upper right corner of the 'Insert disk screen'-disk looks pretty ugly with this one).

Is the image being scaled (for example aspect ratio corrected) or prcessed in any way in the newer versions before the filter is applied? That would explain the uneven filering results pretty well.

But if you don't want to invest any more time into this, I'd say, the current results are quite OK. d3d:hq2x with bilinear scaling looks pretty nice, so I'm happy.

Thanks for fixing this!

Toni Wilen · 01 August 2010, 22:14

Quote:

Originally Posted by Ambermoon

Don't all bugs look stupid once one found them?

This was not a bug, it worked exactly as designed, unfortunately design was very stupid if filter was meant to increase original size (non-1x)

Quote:

Is the image being scaled (for example aspect ratio corrected) or prcessed in any way in the newer versions before the filter is applied? That would explain the uneven filering results pretty well.

There is extra pass in new version, it is used to overlay overlays, masks or scanlines, onscreen leds over the filter processed image, it is 1:1 copy so there should not be any quality loss (it has to be because non-filters are pixel perfect)

I'll think more about this later..

31 July 2010, 15:25	#1
Ambermoon Registered User Join Date: Jul 2010 Location: Germany Posts: 51	D3D HQ2X Filter Problem with WinUAE 2.1.0+ Since version 2.1.0 I'm completely unable to get D3D filters to work correctly. I have attached some images showing the problem and my settings, which shows the effect much better than trying to explain it here. Version 2.0.1 is the last version that works for me, the newer builds seem to do something pretty strange. Compared to the unfiltered image one can clearly see that some filtering is applied, but it's obviously not what you would expect from the hq2x filter. D3D in Misc. Tab is activated, Direct3D is the latest version, filtershaders are the latest version and I even tried to build new configurations from scratch to be sure no old settings do any harm. But that didn't help either. Maybe I'm doing something wrong, maybe this a bug. I just don't know. Main System Specs: Core2 Quad 6600, 4GB, Windows 7, ATI 4890 Thanks in advance for looking at this! Attached Thumbnails Last edited by Ambermoon; 31 July 2010 at 20:47.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problem Filter winuae 2.4.0	Viper2000	support.WinUAE	17	01 April 2012 20:40
Problem with D3D filters on netbook with Intel 945GSE	Mequa	support.WinUAE	10	24 March 2010 18:34
Defender of the crown flickering for others with D3D filter and vsync?	Xorlac	support.WinUAE	2	09 August 2009 02:23
everybody who wants hq2x winuae filter	turrican3	request.UAE Wishlist	203	10 January 2009 10:51
Winuae 1.3 direct 3d filter problem	PiCiJi	support.WinUAE	3	18 July 2006 20:11

31 July 2010, 15:50	#2
Photon Moderator Join Date: Nov 2004 Location: Eksjö / Sweden Posts: 5,647	Hmm... it finds the gfxcard, but you could also check that '4800 Series' is also in the config files you create (I think). At least I think that if the config loads some old gfxcard entry from a config there could be a mismatch. Nowadays when I upgrade hardware or WinUAE, I always rename the old WinUAE directory and install latest stable with installer to an empty folder, and then create configs from scratch. But I've broken this rule before and have had all kinds of problems with getting configs to load/save/update when I change in the UI. So try the 'clean slate' thing, start with quickstart config, set hq2x and save config. Then post here & attach the config. That would help Toni I think.

31 July 2010, 16:08	#5
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,545	I think I know whats wrong (if all other d3d filters work?) Try http://www.winuae.net/files/b/winuae.zip

31 July 2010, 16:33	#6
Ambermoon Registered User Join Date: Jul 2010 Location: Germany Posts: 51	Thanks for the superfast reply! But unfortunately the attached exe doesn't solve the problem. Additionally I tried various other D3D filters, those weren't working correctly either. Neither with the 2.2.0 build nor with the new exe. The image looks somewhat different (less blurry), but apart from that no change. Still very lo-res and worse than the unfiltered image. Since I can't do more attachments I uploaded a screenshot to imageshack (config was the same as before): http://img507.imageshack.us/img507/2...uild1image.jpg

31 July 2010, 16:39	#7
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,545	It is either filter panel setup issue (not 1:1 scaling) or some display card configuration setting (AA?) if even d3d null filter is blurry.

31 July 2010, 16:55	#8
Ambermoon Registered User Join Date: Jul 2010 Location: Germany Posts: 51	The null filter looks just fine in the newer builds, just the 'enhancing' filters show the blurry picture. And since 2.0.1 is working flawlessly, I don't think it's a wrong display card (or monitor) configuration setting eiher, that wouldn't affect just the newer builds. What I didn't mention before (just marked it red in the v220_filter_settings screenshot above): The combo box next to the filter selection combo box is greyed out (and not accessible) for me in the 2.1.0+ versions. Is this normal? In previous builds one can select Point/Bicubic in this combo box when D3D:hq2x is selected.

31 July 2010, 17:43	#11
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,545	Start from scratch (move/delete default.uae too), test it step by step, first only enable d3d mode and d3d filter and so on until image becomes blurry.

31 July 2010, 18:16	#12
Ambermoon Registered User Join Date: Jul 2010 Location: Germany Posts: 51	Just tried 2.2.0 on my HTPC, which, as far as I can remember, never ever ran any WinUAE version before. It's also a Windows 7 machine but with an nVidia graphics card (9600GT). Same Symptoms. I really don't want to bother, but does hq2x in 2.2.0 really look like the hq2x v2.0.1 screenshot in my first post for you when used with high resolutions? If you want I'd be glad to send you a screen of a more common game so it's easier for you to compare the results with your own. Maybe Monkey Island or something. Next thing I will try is setting up a new VirtualBox machine with XP and try WinUAE on it. I'm pretty curious what happens.

31 July 2010, 18:23	#13
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,545	I am not going to do any kind of testing without a) statefile of static screen, b) exact configuration. Other kind of comparisons are invalid. Also d3dhq2x is worst for testing because it is the most complex and uses extra texture buffers. Something like scale2x is much better testing filter.

31 July 2010, 19:23	#14
Ambermoon Registered User Join Date: Jul 2010 Location: Germany Posts: 51	Fair enough. Since the good old KS1.3 start screen is perfectly suitable for showing the effect I will use that one in conjuction with the A500 quickstart config. The upper right (diagonal) corner of the KS-diskette is an extremely good spot to show the differences. Only changes will be the display (fullscreen 1920x1200) and filter settings. This will make things pretty easy and minimizes sources of error. Software Scale2x works normally, so I reckon you meant D3D: Scale2x. That would be fine for me, it's flawed too (for me at least). Since the effect is better noticable with the higher quality filtering algorithms I will send you d3d:h2qx (which really looks completely borked in 2.2.0) state files too, just for reference. Additionally to the statefiles I'll send you the configs and screenshots that show how things look over here with the according settings. For both 2.0.1 and 2.2.0. Anything special I have to be aware of when creating the statefiles? What I'd do is this: 1. Creating the configs 2. Start WinUAE with a premade config 3. Start the emulation 4. Save a statefile (F12 -> Misc. -> Save State...) 5. Save a screenshot 6. Quit WinUAE 7. Go to 2. Would that be an acceptable approach?

31 July 2010, 19:44	#15
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,545	No need for statefiles if you use standard KS "insert disk" screens. Only configuration file needed so that I can have exact same display settings.

31 July 2010, 20:50	#16
Ambermoon Registered User Join Date: Jul 2010 Location: Germany Posts: 51	Attached are the config files and screenshots. d3d:scale2x and d3d:hq2x at 1920x1200 for both WinUAE 2.0.1 and 2.2.0. I did a clean install for both versions. With d3d:hq2x there is a really huge difference between the versions (see 'teaser image' below). From looking at the images I would suspect that 2.0.1 applies the filter to the full extent of the selected resolution which gives a very clean image. This is the way it works for example in DosBox builds with d3d support too. 2.2.0 on the other hand seems to apply the filter only once and seems to upscale the resulting image to 1920x1200. But that, of course, is pure speculation. d3d:scale2x does look strange in 2.2.0 too, although it's not as easy to spot. Looks like the image simply isn't filtered at all but instead oddly scaled.

01 August 2010, 16:11	#18
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,545	http://www.winuae.net/files/b/winuae.zip should fix this problem, please confirm. ("new" d3d filter had very stupid design flaw..) btw, I couldn't get exact same hq2x filter result using old winuae and neither exactly same as in your screenshot either. (and there was also bug in d3dhq2x table coordinates, [input_width, input_height] coordinate pair was [input_width, input_width]..)

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)