we're in the process of crawling toward a final release for our Revision Demo.
Managed to shift enough data around to fit the A500 + 512 Fake Fast requirements.
Doc.K is allocating some chip mem for his 3D object which threw me off the tracks when
granting Novel another 30k for the tune - silly me.
But in this allocation there probably lies another quirk. The party version has a curious memory bug
when it's changing scenes from the hexagon-floor to the 3D object. So much so that it either completely
bugs off the Blitter and is just showing trash or it distorts the tune or the P61 replayer routine.
I've got an uncrunched executable that should run on an A500 + 512 that you can download for testing and/or debugging. I'd be glad for any hint advise to tackle this buggerremember: THIS IS NOT A FINAL ... and no official releasequintessence_a500
Any help will be highly appreciated ( ... and credited)