WinUAE 2.3.0 beta series (was 2.2.1) - Page 6

UncleSpam · 27 July 2010, 18:00

DirectDraw display buffer is disabled when switching from DirectX prior to running the emulation.

Then, no display, except for the on-screen LED status bar.

- Bogdan

UncleSpam · 27 July 2010, 18:19

Another issue, this time when using DirectX. Notice the two glitches in the scanline mode display (indicated by the red arrows). Logs and config file included.

- Bogdan

Toni Wilen · 27 July 2010, 18:28

Quote:

Originally Posted by UncleSpam

Another issue, this time when using DirectX. Notice the two glitches in the scanline mode display (indicated by the red arrows). Logs and config file included.

- Bogdan

I am not so sure that this and above one are specific to this beta series..

UncleSpam · 27 July 2010, 18:56

Quote:

Originally Posted by Toni Wilen

I am not so sure that this and above one are specific to this beta series..

The first issue works 100% correctly in 2.2.

The second issue shows the middle line glitch in 2.2 but not the bottom glitch.

Toni Wilen · 27 July 2010, 19:16

Quote:

Originally Posted by UncleSpam

The first issue works 100% correctly in 2.2.

Quote:

DirectDraw display buffer is disabled when switching from DirectX prior to running the emulation.

This is old.

What do you mean by DirectX? There is DirectDraw and Direct3D. There is no "DirectX" display mode.

EDIT: winuaelog.txt missing.

Quote:

The second issue shows the middle line glitch in 2.2 but not the bottom glitch.

I didn't notice the bottom part (and it was already fixed). Again, what mode?

UncleSpam · 27 July 2010, 19:59

Sorry, I meant Direct3D.

Here's the missing winuaelog.txt file.

As far as the bottom display glitch is concerned, it shows up when booting (prior to LoadWB command). I can't seem to get it in any screenmode once WB is loaded.

It also happens in NTSC emulation, but not under PAL emulation (Direct3D only).

Hope this helps.

Toni Wilen · 27 July 2010, 20:20

Quote:

Originally Posted by UncleSpam

As far as the bottom display glitch is concerned

I meant it is ("should be") fixed in post-beta6 alpha winuae.zip versions.

Extra line in the middle is some kind of rounding error in filtering code. Will be fixed later.

Quote:

Then, no display, except for the on-screen LED status bar.

What do you exactly mean by this? My currently blurry crystal balls says that you can try adjusting position using filter panel (D3D and DD modes can work very differently)

UncleSpam · 27 July 2010, 20:43

Quote:

Originally Posted by Toni Wilen

What do you exactly mean by this? My currently blurry crystal balls says that you can try adjusting position using filter panel (D3D and DD modes can work very differently)

Basically, the display is blank, there is no image being displayed besides the status LEDs.

Turning the Filter off and Display centering (H/V) off restores the display in the upper left, but causes very slow updates (F12 takes a long time to activate the settings screen).

Again, this is for DirectDraw only.

Cosmos · 28 July 2010, 19:33

Don't know if it's an old or a new bug, but Quake crash WinUAE :

Launch Quake...
Wait until you climb under the water...
Crash all the time here...

Toni Wilen · 28 July 2010, 20:44

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

Beta 7:

- reverted b5 audio hack, it breaks other programs and also it does not seem to be audio.device bug after all but application calling CMD_WRITE with interrupts disabled..
- zipped iso was unnecessarily unpacked completely during scanning if cue was found later
- some drives/driver/Windows versions don't seem to like IOCTL_CDROM_RAW_READ, returns ERROR_INVALID_FUNCTION (XP returned ERROR_INVALID_PARAMETER). Falls back to SPTI SCSI passthrough in this situation and uses SCSI READ CD command
- improved default ROM path handling
- ccd and mds CDA was silent (b5)
- higher CPU usage, display emulation debugging stuff.. (b5)
- initial rom scan didn't load AF key files correctly
- updated VPOSW fake 60hz support sometimes selected bogus 314 line timing for sound sync (not really much difference, might have caused some extra SND% changes)
- CD32 audio play status code was unreliable if new CDA play command was send without stopping previous play state (Fightin' Spirit CD32)
- CD32 state restore ignored statefile embedded CD image path (if included)
- CD32 state save saved wrong command fifo offset, restoring state can send some random commands to drive (old bug)
- new CDTV state file support was quite unusable
- state restore didn't initialize audio completely, samples playing while state was restored could play incorrectly until sample (on any channel) ended or new sample was started (old bug)
- printscreen key saves screenshot when button is released (was when pressed) quick workaround for Windows built-in screenshot not getting overridden in rawinput keyboard mode (perhaps there is better way..)
- "highend" quickstart mode was not in KS2.0+ check list
- fullscreen 8-bit RTG and "match depth" RTG setting enabled and 32-bit display mode selected in Display panel: 16-bit mode was selected with 32-bit mode color settings.

"Portable mode" updates: (and no stupid registry related comments again or..)

- added -portable command line parameter which is same as "-ini winuae.ini", creates ini in temp directory if winuae.exe directory is write protected
- /<command line parameter name> also accepted
- official support for relative paths added, checkbox in Paths panel, automatically enabled when ini mode is started (ini missing or empty), all paths that are inside of winuae directory are kept relative. Report all possible side-effects or paths that are not in correct format. Currently all relative paths have .\ prefix, this may disappear in future
- do not set apppath in registry in ini-mode
- real harddrive configuration path is now ":<name of device>" (was "HD_<name of device>") (to prevent relative/absolute path conversion conflicts, field is unfortunately shared with hdf paths), this is automatically converted when old config is loaded

thomas · 28 July 2010, 21:12

Confirmed that all of "my" issues are fixed except one:

The print key now creates a good screenshot in Windows clipboard but gives the attached mungwall hit in AmigaOS.

Edit: happened only once when I tried it for the first time. Cannot reproduce it again.

yaqube · 28 July 2010, 22:56

Works correctly with 32-bit host colour depth. With 16-bit host screen the colours are not correct in 8-bit modes (regardless of match host and RTG colour depth).

29 July 2010, 02:33

I can't get the new version 2300B7 to work on my pc's.
The problem is when i click configirations the app crashes.
It crashes also when i click Hardware Or Host.
Here is my crashdump...

freddy · 29 July 2010, 07:00

Quote:

Originally Posted by Lemmingsbeest

I can't get the new version 2300B7 to work on my pc's.
The problem is when i click configirations the app crashes.
It crashes also when i click Hardware Or Host.
Here is my crashdump...

The same thing for me under Vista SP2 32Bits.

Toni Wilen · 29 July 2010, 08:03

Quote:

Originally Posted by yaqube

Works correctly with 32-bit host colour depth. With 16-bit host screen the colours are not correct in 8-bit modes (regardless of match host and RTG colour depth).

Worked for me when I tested it. It rarely is that simple -> logs. Always.

Retroplay · 29 July 2010, 14:09

Beta 7 crashes immediately after I execute WinUAE.

WinXP SP3 x86 + DirectX Jun2010.

Mclane · 29 July 2010, 15:57

Working fine here on Windows 7 X64 Enterprise..

June DirectX

2gig ram, Nvidia7800 card...

P4 3.2

FreakyDan · 29 July 2010, 16:36

Beta 7 crashes immediatley if i install it in a previuos winuae directory. If install it in a new directory it runs fine.

Toni Wilen · 29 July 2010, 16:39

http://www.winuae.net/files/b/winuae.zip should fix the crash?

FreakyDan · 29 July 2010, 16:40

Yes... crash fixed

28 July 2010, 21:12	#111
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,034	Confirmed that all of "my" issues are fixed except one: The print key now creates a good screenshot in Windows clipboard but gives the attached mungwall hit in AmigaOS. Edit: happened only once when I tried it for the first time. Cannot reproduce it again. Attached Thumbnails

29 July 2010, 14:09	#116
Retroplay Lemon Curry ? Join Date: Sep 2004 Location: Denmark Age: 49 Posts: 4,142	Beta 7 crashes immediately after I execute WinUAE. WinXP SP3 x86 + DirectX Jun2010. Last edited by prowler; 10 September 2016 at 23:12. Reason: Removed attachment.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE 2.5.1 beta series	Toni Wilen	support.WinUAE	69	22 December 2012 10:22
WinUAE 2.3.3 beta series	Toni Wilen	support.WinUAE	124	17 September 2011 15:48
WinUAE 2.3.2 beta series	Toni Wilen	support.WinUAE	79	31 May 2011 19:39
WinUAE 1.5.3 beta series	Toni Wilen	support.WinUAE	58	09 November 2008 13:46

28 July 2010, 20:44	#110
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,574	http://www.winuae.net/files/b/winuae_2300b7.zip Beta 7: - reverted b5 audio hack, it breaks other programs and also it does not seem to be audio.device bug after all but application calling CMD_WRITE with interrupts disabled.. - zipped iso was unnecessarily unpacked completely during scanning if cue was found later - some drives/driver/Windows versions don't seem to like IOCTL_CDROM_RAW_READ, returns ERROR_INVALID_FUNCTION (XP returned ERROR_INVALID_PARAMETER). Falls back to SPTI SCSI passthrough in this situation and uses SCSI READ CD command - improved default ROM path handling - ccd and mds CDA was silent (b5) - higher CPU usage, display emulation debugging stuff.. (b5) - initial rom scan didn't load AF key files correctly - updated VPOSW fake 60hz support sometimes selected bogus 314 line timing for sound sync (not really much difference, might have caused some extra SND% changes) - CD32 audio play status code was unreliable if new CDA play command was send without stopping previous play state (Fightin' Spirit CD32) - CD32 state restore ignored statefile embedded CD image path (if included) - CD32 state save saved wrong command fifo offset, restoring state can send some random commands to drive (old bug) - new CDTV state file support was quite unusable - state restore didn't initialize audio completely, samples playing while state was restored could play incorrectly until sample (on any channel) ended or new sample was started (old bug) - printscreen key saves screenshot when button is released (was when pressed) quick workaround for Windows built-in screenshot not getting overridden in rawinput keyboard mode (perhaps there is better way..) - "highend" quickstart mode was not in KS2.0+ check list - fullscreen 8-bit RTG and "match depth" RTG setting enabled and 32-bit display mode selected in Display panel: 16-bit mode was selected with 32-bit mode color settings. "Portable mode" updates: (and no stupid registry related comments again or..) - added -portable command line parameter which is same as "-ini winuae.ini", creates ini in temp directory if winuae.exe directory is write protected - /<command line parameter name> also accepted - official support for relative paths added, checkbox in Paths panel, automatically enabled when ini mode is started (ini missing or empty), all paths that are inside of winuae directory are kept relative. Report all possible side-effects or paths that are not in correct format. Currently all relative paths have .\ prefix, this may disappear in future - do not set apppath in registry in ini-mode - real harddrive configuration path is now ":<name of device>" (was "HD_<name of device>") (to prevent relative/absolute path conversion conflicts, field is unfortunately shared with hdf paths), this is automatically converted when old config is loaded

28 July 2010, 22:56	#112
yaqube Registered User Join Date: Mar 2008 Location: Poland Posts: 159	Works correctly with 32-bit host colour depth. With 16-bit host screen the colours are not correct in 8-bit modes (regardless of match host and RTG colour depth).

29 July 2010, 15:57	#117
Mclane Old retro god. Join Date: Apr 2002 Location: Northolt, West London Age: 63 Posts: 861	Working fine here on Windows 7 X64 Enterprise.. June DirectX 2gig ram, Nvidia7800 card... P4 3.2

29 July 2010, 16:36	#118
FreakyDan Freaky Dan Join Date: Dec 2001 Location: Sweden Age: 49 Posts: 97	Beta 7 crashes immediatley if i install it in a previuos winuae directory. If install it in a new directory it runs fine.

29 July 2010, 16:39	#119
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,574	http://www.winuae.net/files/b/winuae.zip should fix the crash?

29 July 2010, 16:40	#120
FreakyDan Freaky Dan Join Date: Dec 2001 Location: Sweden Age: 49 Posts: 97	Yes... crash fixed

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