Submissions open from 2024-10-31 00:00:00 to 2025-01-31 00:00:00
Submissions due in
years
months
days
hours
minutes
seconds


Amiga Demo Effect Jam 2

 Attention Amiga Beginners Coders - We are back once again!!!

Have you ever dreamed of participating in a demo party when viewing all those Amiga Demos?

Here is your chance to do so.

 This Jam is being organised with beginners in mind and for beginners that would love to participate in a demo party.

 This Jam is for Amiga OCS/ECS only 

Please Note that this is a continuation of the Demo Effect Jam that we had released a few months back.

The Jam

The aim of the Jam is that one creates an Amiga Demo Effect, and all these effects will be joined together to create a sort of an Amiga Demo. 

Technical Requirements

The demo effect needs to run on an Amiga OCS/ECS.

The Effect will be tested on a stock A500, with 512K chip and 512K slow RAM and Kickstart 1.3.

  • Source Code of the effect is necessary to the organizers to build the final Demo composition, it will not be shared unless you want to.
  • You can provide ASM or C/C++  files and eventually raw data assets.
  • The Effect will also be provided as a single executable file that does not require anything else to run (for testing and preview purposes)
    • Assigns and installation scripts are forbidden.
    • Going into the demo’s directory and starting the main executable must be the only necessary steps to watch the demo effect.
    • No other libraries or datatypes will need to be installed.
    • It needs to run in a “clean” environment, that is booting AmigaOS without startup sequence and then the demo effect executable.
  • Make sure your production works on Kickstart 1.3.
  • Pressing either the right mouse button or ESC has to end the demo effect instantly.
  • The entry must be a program with all the assets included in the form of incbin or #include and not in a compress format.
    • we suggest to provide an "initialize" and an "update" functions to simplify the integration with the rest of the demo.  Ask into the dedicated discord channel if you need help on this.
    • for testing purpose do allocate the most big blocks available of chip and slow memory, for details ask into the dedicated discord channel.
    • do not assume to have all the memory available, approximately 400k of chip should be granted while the slow memory will be used for the main demo system and the compressed assets. Ask for details into the dedicated discord channel.
    • we suggest to use compile conditions to switch from testing mode (your single executable for preview the fx) and integration mode: our demo system will handle OS on/off and the usual setup and so the transitions between effects.
  • The Demo Effect can't have any music in it. That will be dealt separately.


Some Participants From Previous Jam




Before You Submit Your Entry

  • Keep it simple.
  • Do not complicate things.
  • Read the Technical Specs more than once.
  • Deliberately breaking compatibility is not cool.

Thanks goes to Pellicus for his support and help.

You can ask for help and suggestions on the dedicated discord channel #phaze101-jams

 

Hosted and Organised by Phaze101

Phaze101 Discord


Video explaining the JAM, why we are doing it and the aim behind it