Started by Overflow, 00:43, 19 March 14
0 Members and 1 Guest are viewing this topic.
Quote from: arnoldemuHave you come out of retirement to make another demo/intro?
Quote from: arnoldemuThe events list is a nice way to synchronise the actions in the demo, and I like the way that instead of a if event=0 do thisif event=1 do thisyou turned it into a poke the ram to redirect the demo to perform the action.
Quote from: arnoldemuThe synchro by resetting the interrupt counter is a good method where you can have used all the screen time.Interesting that you wanted to make a demo 19968 cycles long, is this more for programmer satisfaction or because you need to use all cycles?
Quote from: arnoldemuI think what made the demo for me:- overscan- nice effect with various differences shown through the demo and the effect is done well- short- fast- great music
Quote from: Overflow on 00:43, 19 March 14A few days ago, I felt like writing down some thougts about YAP!Might be as a therapy to cure myself from retirement. Disclaimer: I do not intend anything else than sharing,
Quote from: Overflow on 20:42, 19 March 14Quote from: arnoldemu on 19:42, 19 March 14you turned it into a poke the ram to redirect the demo to perform the action.I am also wondering if this is something "new";
Quote from: arnoldemu on 19:42, 19 March 14you turned it into a poke the ram to redirect the demo to perform the action.
#38 contains JP intsyncintsync: ld b,#f5 in a,(c) rrca jr c, intvec0 ; when we detect the first vsync since start, rejoin at intvec0... retintvec0: ld hl,intvec1 ld (#39),hl...intvec1: ld hl,intvec2 ld (#39),hl...intvec5: ld hl,intvec0 ld (#39),hl...
Quote from: MacDeathWe made a few palette tests (...)
Quote from: MacDeaththe "classic overused" blue-to-cyan and red-to-yellow are not overused for nothing. those are the only 2 smooth long palettes possible.May be cool, if possible to get this with not 2 long palettes gradiants but perhaps 3 shorter ones...
events_list db 25 : dw event1 ; 0.5 second is 25 frames to wait for db 50 : dw event2 ; 1 second is 50 frames to wait for; called eventsevent1 ld hl,new_palette:ld (adr_palette+1),hl:retevent2 ld a,#2B: ld (adr_incdec),a:ret;somewhere in codeadr_palette ld hl,old_palette;somewhere elseadr_incdev inc hl ; ==#23 while #2B== dec hl
pokes_list db 25+#80 : dw adr_palette+1 : dw new_palette ; +#80 stands for: pokes 2 bytes db 50+#40 : dw adr_incdec : db #2B ; +#40 stands for: pokes 1 byte;somewhere in codeadr_palette ld hl,old_palette;somewhere elseadr_incdev inc hl ; ==#23 while #2B== dec hl
Quote from: GryzorThanks for doing that; didn't understand half of it, but very interesting read!
Quote from: OverflowAbout the curves (...)I am assuming that the curve is continuous, and its slope does not change much.Briefly? ddV is from [-1,0,1] , 5 ddV are stored in 1 byte (3^5=243 <256)One loop to get a new V value for the curve is: read ddV from stored data dV = dV + ddV V = V + dV
Quote from: ralferoo on 11:37, 22 March 14(...) looks a lot like a copperlist for the Amiga...
QuoteYou still have the dsk with basic launcher to test palettes, don't you?
Page created in 0.095 seconds with 43 queries.