PDA

View Full Version : Super Frog Bug? Is it known?


Unregistered
08 December 2001, 09:11
Hi,

Don't want to be one of those people who demand/want/request for all/some/one game. However, I have to ask this question to discover the situation and what causes the problem.

I've just installed

winfellow_alpha_v0.4.3_build_1_directx3_snapshot_2001_11_15

and have been blown away by its ability to emulate. Playing games at full rate with pure quality sound (ie, Pinball Fantasy, Starglider2, Virus etc). I then put in Superfrog (my all time favourite game) and it all looked pretty good. Running the intro at full sound/speed etc. However, when the game runs, the main frog sprite is transparent! I assume there is some type of sprite bug that is causing it! The game plays perfectly other than for this problem.

Is anybody aware of this? Will there be a fix? Can somebody reply to late me know..

Thanks in advance...

Carl

P.S. Thanks again for such a brilliant product. WinUAE manages to run things perfectly (ie Superfrog) but it really is the pits when it comes to perfect Sound/Speed.

TikTok
08 December 2001, 09:35
You're right, WinFellow is great :). I'm sure this problem will be fixed eventually. I think there are a few sprite related issues that are mentioned on the website. Zool and quite a few other games dont show the main sprites, for example.

Drake1009
08 December 2001, 09:37
Another bug which can be a little annoying is the missing collisions such as in Blood money. Apart from that and a minor bug with disk loading (Which might be fixed now) it's the best emulator. Well in my opinion anyway.

P-J
08 December 2001, 19:35
Originally posted by Drake1009
Another bug which can be a little annoying is the missing collisions such as in Blood money. Apart from that and a minor bug with disk loading (Which might be fixed now) it's the best emulator. Well in my opinion anyway.


Too right! For games, WinFellow rules ;)

Worfje
09 December 2001, 21:43
Is anybody aware of this? Will there be a fix? Can somebody reply to late me know..
We are and were aware of this bug. :D