View Single Post
Old 17 May 2016, 22:25   #1
michaljarz
Registered User

 
Join Date: Jul 2014
Location: Katowice/Poland
Posts: 44
"Fastest possible" since 2.4.0 beta 21...

Hello.

Last time I load clean config A500 with kick 1.3. Use:
- 68000,
- 24bit addr,
- more compatible,
- full ecs,
- immediate blitter and wait for blitter unticked.
I set "fastest possible" and "start"... Boot image is corrupted ("workbench" word).

It's only OK when ticked "Immediate blitter" or "Approximate/cycle-exact".

Last working version - 2.4.0 beta 20.
This image corruption since 2.4.0 b21.

This if from changes below?
Code:
- Huge improvement in fastest possible CPU (with or without JIT) + low latency vsync performance.
(...)
NOTE: Above changes WILL break some games/demos that (accidentally) worked previously. It is 100% guaranteed!
Image grab from last beta 3.3.0b13 17.05.2016

(PS. sorry for my english)
Attached Thumbnails
Click image for larger version

Name:	ok.png
Views:	103
Size:	5.1 KB
ID:	48461   Click image for larger version

Name:	not_ok.png
Views:	106
Size:	5.0 KB
ID:	48462  
Attached Files
File Type: zip winuae_debug_3.3.0.zip (12.7 KB, 35 views)
michaljarz is offline  
AdSense AdSense  
 
Page generated in 0.05247 seconds with 10 queries