Started by Gryzor, 10:36, 17 October 16
0 Members and 1 Guest are viewing this topic.
Quote from: CraigsBar on 00:46, 18 October 16Looks good, but I cannot get it working on my C4CPC it crashes after the titlescreen when selecting either option
Quote from: Gryzor on 10:36, 17 October 16Looks lovely, doesn't it??
Quote from: TotO on 10:09, 18 October 16Waiting for the pretencious Jim Power PLUS version close to 5 years now, I can just laugh by seeing that skilled game at end.
Quote from: gerald on 08:12, 18 October 16Start it from a dedicated slot
Quote from: GOB on 18:54, 18 October 16Dis le à Macdeath qui n'a jamais rien branlé pour les graphismes... Pour le reste du commentaire, je n'en ferai justement pas, mais pas de doute t'es bien sur la scène demo !!!
Quote from: Gryzor on 10:36, 17 October 16http://www.cpc-power.com/index.php?page=detail&num=13363Looks lovely, doesn't it??[attachimg=1] [attachimg=2]
Quote from: roudoudou on 20:04, 29 January 17this afternoon we finish fixing the game!level selection is now ok on a real CPC and Arnoldfire effect is now OK (was disabled on previous version cause buggy)
Quote from: gerald on 20:07, 29 January 17Any detail of what was wrong ?
Quote from: roudoudou on 20:54, 29 January 17The code move some routines in memory but forgot two last bytes. As the final instruction is a JP, the JP adress is what was after in memorySurprisingly, with Winape the code jumps everywhere in the memory but luckily end in an init portion. With Arnold or a real CPC, it hangs in a HALT (so i guess INT under Winape are not accurate)For the fire effect, the 128 nops loop is doing INC (HL) to increase color index of 8 hardware spritesH is loaded from a #80 long table located in #100 (followed by #80 zeros). This table contains High bytes of HW sprites #40 to #47I guess the sinus value was supposed to be between #00 and #7A (cause there is some other increments)But not! So the code was doing some writes in #00xx -> corrupting interrupts jump then the code hangs againI fix the 128 nops loop containing H value and optimising the whole routine to gain space & stay at 128 nops
Quote from: gerald on 20:59, 29 January 17Did you manage to fix the start screen offset that happen sometimes ?
Page created in 0.116 seconds with 52 queries.