[22 Jan 2010] Known Bug in FX transition effects?

Contains all messages from the Hollywood mailing list between 01/2006 and 08/2012
Locked
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[22 Jan 2010] Known Bug in FX transition effects?

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Fri, 22 Jan 2010 19:24:24 +0100

Hi all

after resuming my "project" on Hollywood 4.0, I found a 2 bugs. One is harmless, the other one kills hollywood and sometimes even entire AmigaOS (-- on AmigaForever's Aos3.1 (e-uae in linux) and AOS4.1 on SAM and Peg2, too).

1) Some transition effects where objects are moved to its final position doesn't work correctly. So the finaly coordinate is not reached. This bug appears with ShowLayerFX() on TextObjects with bullets (done with "Circle()") in front of it. Sometimes, the text is quite far away from it's destination. I can't exactly say which effect causes the error. There are too many to test ;-) I choosed "#RANDOMEFFECT" and then, sometimes it happens :-)

2) The second one is worse but seems also to be related to some (one special?) transitioin effect. I used ShowLayerFX(..,(async=True) on a group of (maybe 20?) layers which all are displayed in with "AsyncDrawFrame()" afterwards within a loop. The transition effect is chosen randamly again.

If i repeat that loop often enough (-- I display the result and press a key to hide the group and then to display it again with the next random effect), first my application breaks, then Hollywood and finally AOS. On AmigaOS3.1 I get an Guru Meditation which forces a reboot. On AmigaOS4.1 (update 1), I got on my Peg2 a system freeze without a GrimReaper. And on Sam440ep, AmigaOS4.1 just Hollywood froze without GR, but AmigaOS4.1 was still alive.

Even if i had programmed stupid things in HW, it shouldn't crash HW or AOS itself, right? And most of the transitioin effects seem to work without a problem. But sometimes, after 1, 10 or more times hiding/showing of the same group of layers with AsyncDrawFrame() and without having them modified in any way, it causes the dead of my system -- thats of course not nice ;-) ) If the crash happen's then only small parts of the group of layers are shown.

Are these Bugs already known and maybe even fixed in HS4.5?

thanks! nexus
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[22 Jan 2010] Re: Known Bug in FX transition effects?

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Fri, 22 Jan 2010 19:33:18 +0100

I accidently found this type:

type=#HOPENGATE

which causes Hollywood to freeze on Sam440ep without crashing AmigaOS, but it's not possible to close HW's window anymore or anything else. HW is simply dead.
User avatar
airsoftsoftwair
Posts: 5943
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[23 Jan 2010] Re: Known Bug in FX transition effects?

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 23 Jan 2010 15:14:21 +0100
Are these Bugs already known and maybe even fixed in HS4.5?
The transition effect library received huge changes in 4.5, including many bug fixes. So I'd suppose that these problems are gone now...
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[23 Jan 2010] Re: Known Bug in FX transition effects?

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 23 Jan 2010 16:36:18 +0100
The transition effect library received huge changes in 4.5, including many bug fixes. So I'd suppose that these problems are gone now...
yes, meanwhile i've found out, that this bug is related to the "text wrappign bug". The crash does not happen, if there's no textobject which needs to be wrapped to the next line.

So, I guess HW4.5 works just fine :-) That means, I need to get it sooner :-)

I think in February, I will place my order!

Thanks, nexus

P.S. regarding the API change. Yes, it's nice that you stay compatible to older Hollywood releases. However, from a programmer point of view it's ugly to use older API versions :-D
Locked