21 May 2018, 20:18 | #401 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Here's some more info on the "debug blob" location issue I mentioned. With 16 slices, 3× scaling on 2160-line screen, so each non-interlaced Amiga scanline corresponds to 6 lines on screen.
Table of blob vertical positions: Code:
Line# Diff.from prev. 206 - 644 438 734 90 824 90 ... ... 1814 90 1904 90 The Amiga display is 574 lines so occupies 574×3 = 1722 lines on the monitor. Thus there are 2160-1722 = 438 unused lines on monitor. Is it a coincidence that 438 is exactly the number of lines between the top two blobs? |
21 May 2018, 21:32 | #402 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
http://www.winuae.net/files/b/winuae_4000b11.7z
http://www.winuae.net/files/b/winuae64_4000b11.7z Beta 11: - D3D11 fullscreen mode after alt-tab/gui was not restored properly if emulation was in paused state. - D3D9 lagless vsync partial updates (introduced in b5) used incorrect (full, D3DLOCK_DISCARD) texture update mode. - Decrease/increase emulation speed input events didn't do anything. - Power led dim config option is now integer (0 = fully off, 1 to 100 = brightness level) - Hardware emulated graphics boards didn't update properly without enabled OSD led (uaegfx was already fixed in b9) - A2410 didn't support multiple monitor mode. - Merged Aranym JIT updates. - Fixed old (since the beginning?) JIT bug: many instructions always cleared V-flag (ADDX, SUBX, NEGX, BTST/BCHG/BCLR/BSET, possibly others). Fix by Thorsten Otto. |
21 May 2018, 23:20 | #403 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
With beta 11, if you start emulation in full-screen D3D11 mode, press F12 then click Quit, WinUAE returns to full-screen mode for a moment before returning to desktop and exiting. Beta 10 was OK.
|
22 May 2018, 02:30 | #404 | ||
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,383
|
Quote:
1.) "packed decimal real format", fallback at line 67 in comemu_fpp.cpp 2.) some PC relative addressing modes at line 141: Quote:
1.) size=3 Packed-Decimal Real with Static k-Factor (P{#k}) 2.) size=7 Packed-Decimal Real with Dynamic k-Factor (P{Dn}) Maybe, Aranym or other emulators have that Jit code already implementd? Last edited by PeterK; 22 May 2018 at 12:26. |
||
22 May 2018, 14:55 | #405 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
The slice position change first occurred (or rather, seemed to get worse) with beta 5.
I took some screenshots to show the differences between b4 and b11 with 4, 8 and 16 slices. Beta 4 didn't have "debug blobs", but due to the slice position bug you can see where the slices are. Code:
http://www.media!fire.com/file/48i82v5saw9esm3/WinUAE_2018-05-22.7z Code:
static void linesync_first_last_line(int *first, int *last) { + int x, y, w, h; *first = minfirstline; *last = maxvpos_display; + get_custom_raw_limits(&w, &h, &x, &y); + if (y > 0) + *first += y; } |
22 May 2018, 20:58 | #406 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
Quote:
Anyway, no one uses packed decimal format and it still would be really slow, JIT or no JIT. Quote:
Also try other resolutions and/or filter settings. |
||
22 May 2018, 21:44 | #407 |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,262
|
Ciao Toni, i do not know if it depends on my system, with Beta 11 if you start WinUAE by default without any HD or Floppy WinUAE go to Crash (use WinUAE 32Bit Direct3D 9 and other beta do not have the problem)
|
22 May 2018, 21:48 | #408 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
Quote:
-> Not enough information. |
|
22 May 2018, 22:35 | #409 |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,262
|
Excuse me Toni i did not understand what you wrote, i attach Log and Dmp, i started WinUAE with QuickStart A1200 Basic nothing HD, nothing floppy, nothing added configuration.
I would like to clarify that if I configure Direct3D 9 in "Graphics API" nothing happens and nothing crashes. Last edited by AMIGASYSTEM; 06 June 2018 at 16:14. |
23 May 2018, 01:25 | #410 | |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,383
|
Quote:
Code:
case 3: /* (d8,PC,Xn) or (bd,PC,Xn) or ([bd,PC,Xn],od) or ([bd,PC],Xn,od) */ { uae_u32 address = start_pc + ((uae_char*) comp_pc_p - (uae_char*) start_pc_p) + m68k_pc_offset; uae_u32 dp = comp_get_iword ((m68k_pc_offset += 2) - 2); mov_l_ri (S3, address); calc_disp_ea_020 (S3, dp, S1, S2); break; } |
|
23 May 2018, 15:35 | #411 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
Quote:
Anyway, dump helped to find the problem. winuae.7z should fix it. Quote:
|
||
23 May 2018, 19:23 | #412 | ||
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,262
|
Quote:
Quote:
|
||
23 May 2018, 19:53 | #413 | |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,383
|
Quote:
Meanwhile I found another older FPU bug in ZoneXplorer as reported in the Imagine thread, but I don't know how the correct result should look like. |
|
24 May 2018, 10:21 | #414 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
I was finally able to test the Lagless VSync (Beamraced) on my CRT setup.
It works great, thanks a lot for implementing this . But there's one BIG problem, it even works flawless when using the max of 29 slices, so we need more slices! I'm curious to how many slices can be used without it causing issues. Maybe a "custom" option in the list view can be added? On my CRT setup I use a custom resolution of 744x287 for WinUAE with D3D11 (D3D9 doesn't work as well). For what it's worth, the GPU is a "modest" MSI HD6850 Cyclone with a custom bios that sets the power profile to always use max GPU clock. |
24 May 2018, 13:10 | #415 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
The usual way: edit config file manually.
|
25 May 2018, 00:23 | #416 | |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,383
|
Quote:
|
|
25 May 2018, 08:27 | #417 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
|
03 June 2018, 18:34 | #418 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
http://www.winuae.net/files/b/winuae_4000b12.7z
http://www.winuae.net/files/b/winuae64_4000b12.7z 1-2 weeks to go, some fixes remaining.. Beta 12: - Don't allow lagless vsync in normal windowed mode. - Hide lagless vsync slice count in GUI if lagless vsync is not selected. - Fixed crash if screen mode open failed and error dialog was shown. (b11) - D3D11 fullscreen mode opened in primary monitor if selected non-default monitor was connected to another GPU. - New debugger didn't load 3.1 (and probably older) amiga.lib files. - Added debugger_options config entry, currently only supported sub entry is pathprefix=x where x is string that gets appended to stabs source file paths. - Try harder to find working path for stabs source files and when working path combination is found, remember it instead of enumerating all possible variants every time source file is loaded. - uaedbg now breaks to debugger when debugged application causes unhandled exception via tc_TrapCode. |
03 June 2018, 19:58 | #419 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Quote:
Not sure if it's on your radar still, but did you have a chance to take a closer look at the synchronization / swapping method for (forced) 60hz screens we talked about earlier (see here)? It would be much appreciated if you could.. Of course nothing will beat the lagless vsync on the 50hz desktop setup, but hopefully it'll provide a decent way of enjoying WinUAE when on the road. It still irks me why those portable devices (at least the ones I used) don't allow for 50hz refresh rates. The best thing would be when the "next best" vblank swapping would not be THAT noticable on slower scrolling games, but would allow for the very low input latency... Just curious whether or not it would look any decent or not. |
|
04 June 2018, 20:42 | #420 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,567
|
I am not yet sure if it is possible without too many changes.
It is not that trivial because it would be simultaneously partially vsync and partially not vsync. At least it needs new option because vsync always means "sync emulation speed to refresh rate". ("lagless non-vsync"..) |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE 3.2.2 beta series | Toni Wilen | support.WinUAE | 21 | 20 December 2015 17:35 |
WinUAE 3.1.0 beta series | Toni Wilen | support.WinUAE | 305 | 06 June 2015 23:25 |
WinUAE 2.3.3 beta series | Toni Wilen | support.WinUAE | 124 | 17 September 2011 15:48 |
WinUAE 2.0.0 beta series | Toni Wilen | support.WinUAE | 445 | 13 December 2009 14:46 |
WinUAE 1.6.1 beta series | Toni Wilen | support.WinUAE | 54 | 18 June 2009 11:05 |
|
|