Problematic Demos.

[SaphirJD]

http://www.pouet.net/prod.php?which=65364 - screen "shakes" also like in the video here, but more intense in Winuae and the effects especially the first balls scene get somehow distorted when watching the demo with Winuae [ Show youtube player ]

Used a quick config - A500 - 1.3 Rom OCS - 512 KB Chip and 512 Slow, Best compatibility

Normal behavior or not normal behavior?

[lordofchaos]

Anyone else experiencing trouble running "Interference" (from disc) on WinUAE using A500+ settings? The demo gets about 2 minutes in just before an effect starts, music screws up. Seems to happen with current beta and last official release.

Demo text at start claims the demo has been tested on A500+

When I get time I`ll try running it from my real A500+

[Toni Wilen]

Originally Posted by SaphirJD

http://www.pouet.net/prod.php?which=65364 - screen "shakes" also like in the video here, but more intense in Winuae and the effects especially the first balls scene get somehow distorted when watching the demo with Winuae [ Show youtube player ]

Used a quick config - A500 - 1.3 Rom OCS - 512 KB Chip and 512 Slow, Best compatibility

Normal behavior or not normal behavior?

Looks perfectly normal to me. It is 100% identical to real A500.

Never trust videos!

Originally Posted by lordofchaos

Anyone else experiencing trouble running "Interference" (from disc) on WinUAE using A500+ settings? The demo gets about 2 minutes in just before an effect starts, music screws up. Seems to happen with current beta and last official release.

Demo text at start claims the demo has been tested on A500+

When I get time I`ll try running it from my real A500+

Real A500 plus confirmed (KS 37.175). Music starts working again if you wait a bit. Same problem happens again at the very end of the demo, just before credits. (and finally it crashes when credits ends)

btw, you forgot to include group name and download link. (Fortunately this time there was no common variants)

[lordofchaos]

Originally Posted by Toni Wilen

Real A500 plus confirmed (KS 37.175). Music starts working again if you wait a bit. Same problem happens again at the very end of the demo, just before credits. (and finally it crashes when credits ends)

btw, you forgot to include group name and download link. (Fortunately this time there was no common variants)

Thanks for confirming, you beat me to it! Was in quite a rush when I made the report so apologies on the lack of detail.

[Toni Wilen]

Sushi Boyz by Ghostown: OCS Agnus scroller bug is A500 confirmed. It is switching bitplane DMA on inside DDFSTRT/DDFSTOP window. This works slightly differently on OCS vs ECS/AGA.

It looks like bug in copper list, waits for earlier position $ec/$00 but it is already $ec/$a0.

00060890: ec01 fffe [0ec 09c]  ;  Wait for vpos >= 0xec and hpos >= 0x00
                               ;  VP ec, VE 7f; HP 00, HE fe; BFD 1
00060894: 0096 8100 [0ec 0a0]  ;  DMACON := 0x8100

[Asle]

I can't seem to be able to run Jukebox 2 musicdisk by Dreamdealers (1991)
http://janeway.exotica.org.uk/release.php?id=7477

I've tried several default standard configs, to no avail. It will boot and do nothing. There's no error message, nothing. As if it waits for something. I've attached both logs files for the A500 (most common).
Not sure it will help, though.

[Toni Wilen]

Originally Posted by Asle

I can't seem to be able to run Jukebox 2 musicdisk by Dreamdealers (1991)
http://janeway.exotica.org.uk/release.php?id=7477

Another "works only accidentally".. It tries to check if INTREQR has COPER interrupt request bit set but it actually checks DSKSYN bit. (btst #4,INTREQR vs btst #4,INTREQR+1)

It already works if KS is 2.0+ because it uses disk wordsync feature but on real hardware it also works under older versions because wordsync contains zero value after power up that causes hardware to detect wordsync condition immeditely when disk dma has been started. (Currently emulation ignores this condition).

hi toni
Thank you very much for WinUAE program works.I'm programming with C language on Amiga. But i use cross compiler vbcc for windows.Building software after doing tests on WinUAE.

i want to ask a quesiton.
I encountered two problems.

first , WinUAE correctly working on the my intro coded . intro have got virtual sprites .but When tested on real hardware crashes.

second , i coded x fighter animation dual playfield mode and 8 color mode each for playfield.this animation for ecs chipset.Fighter made it bob image.WinUAE correctly working . When tested on real hardware fighter bob image problem shows ,you can see below videos. Thanks again

real hardware config A1200 ,apollo 1240 32mb , dce scan magic / flicker free ,4gb cf card ,OS 3.9

winuae config A1200 , 68040 cpu with fp and mmu , 32 mb fast ram ,aga chipset , Os 3.1

Test on winuae emu.

[ Show youtube player ]


Test on Real hardware

[ Show youtube player ]

[Toni Wilen]

Originally Posted by seko

Thank you very much for WinUAE program works.I'm programming with C language on Amiga. But i use cross compiler vbcc for windows.Building software after doing tests on WinUAE.

First, I don't think this is correct thread, this is not how to fix/adjust something topic and this is also OCS/ECS topic only and especially: unexpanded only!. Probably should be in Coders.* forums.

Anyway: probably CPU speed difference, especially chip ram speed is totally different unless you use cycle exact mode. Do not attempt to match non-expanded 68020+ modes' _speed_ (anything else can work) with real hardware, it is not going to work, even different real hardware accelerator boards can have totally different memory speeds that can make a difference.

[SaphirJD]

http://janeway.exotica.org.uk/release.php?id=9696

Tested with OCS/ECS quickstart configs, not sure if this belongs to the demo or not, during this scene the screen starts to flash in a rather crazy way.

[Toni Wilen]

Originally Posted by SaphirJD

http://janeway.exotica.org.uk/release.php?id=9696

Tested with OCS/ECS quickstart configs, not sure if this belongs to the demo or not, during this scene the screen starts to flash in a rather crazy way.

Flashing is correct (A500 + Philips CM8833-II confirmed). Note that it looks very different if (LCD) TV tries to do interlace to progressive conversion. (Same result as Display panel, Line mode -> Double, fields)

[SaphirJD]

http://janeway.exotica.org.uk/release.php?id=30674

Some strange white line appears during that change of scenes on the left. Posted 3 pics when the line enters the scene. It happens when the Straff font fades out and also visible for short time when the scene in picture 3 starts (was not able to make a screen cap of that as i constantly miss it) - Anyway, this line seems not to appear on real Amiga video captures of that demo on Youtube.

Tested with usual Quickstart OCS/ECS configurations.

[Toni Wilen]

Originally Posted by SaphirJD

http://janeway.exotica.org.uk/release.php?id=30674

Some strange white line appears during that change of scenes on the left. Posted 3 pics when the line enters the scene. It happens when the Straff font fades out and also visible for short time when the scene in picture 3 starts (was not able to make a screen cap of that as i constantly miss it) - Anyway, this line seems not to appear on real Amiga video captures of that demo on Youtube.

A500 confirmed. Possibly that white line is slightly in overscan region and was cut from the video. Never trust videos

[Moved from beta thread]

Can anyone check this demo (Was released at flashback just recently)

The animation part just after the "onslaught" logo at the beginning has some visible sprites on the right edge side on A500 machine (when all screen is visible) but on winuae even at maximum border width setting, the glitch is not visible

link to demo here.

http://www.pouet.net/prod.php?which=65736

[Toni Wilen]

Originally Posted by algorithm

The animation part just after the "onslaught" logo at the beginning has some visible sprites on the right edge side on A500 machine (when all screen is visible) but on winuae even at maximum border width setting, the glitch is not visible

Confirmed. Probably same "problem" as background color changes appearing in right border when horizontal position is less than 9 or so.

I had posted this in the wrong section yesterday (Apologies, 40 hours of no sleep can cause this..)

I had created a demo where one of the parts use non-dma sprites (for credits) the sprites are sloppily hidden initially via offset $1e4. On Winuae even on maximum overscan setting, there is no sign of the sprite on the screen.

On the A500 however, (Not sure about the other amiga systems) this sprite is partially showing on the far right. See screenshot as an example.



Just before the compo (flashback 2015) I modified it quickly by displaying the sprite black and then changing it to the desired colors after a while. (Not a good way as I found out that as the text credits move from left to right, the artifacts still appear in this area)

Disk image for testing can be downloaded from here

http://www.pouet.net/prod.php?which=65736

[Toni Wilen]

Check 2 previous posts

Apologies, I should have looked at this first. :-|

[Toni Wilen]

Originally Posted by algorithm

I had created a demo where one of the parts use non-dma sprites (for credits) the sprites are sloppily hidden initially via offset $1e4. On Winuae even on maximum overscan setting, there is no sign of the sprite on the screen.

A500 tested.

It was caused by chipset hpos=0 offset. (As I guessed). If sprite start hpos is >=2 and <=9, it will appear in right overscan border. Not non-DMA mode related, also happens in DMA mode. Will be emulated in next version.

(If you fix this, fix also right overscan background color copper waits )

Great. Should have really coded the demo using full border mode via winuae. Once the whole demo was finished, I noticed the right hand side issues in several of the parts, but did not fix them (as I assume most CRT displays do not display the extreme edges) - On a Projector however, may be a different story :-|

The border changes could have been fixed with something such as xx07 instead of xx01 (where xx =line position)