Loading video...

Video Failed to Load

Go Home

** 3D Engine Update 6 ** New Buffer System. 15-20% Faster !! Using Planes A and B interleaved horizontally we can get the best of all worlds with a near continuous frame buffer for fast Triangle & Quad writes and still use DMA for fast sending of the RAM...

birt_shannon's profile picture

Shannon Birt

2,500 subscribers

12,052 views • 1 month ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

** Sega Genesis 3D engine update 4 ** Never can leave a good rabbit hole undug ! .. updates since last update : Changed frame buffer from a VDP tile friendly buffer to a linear buffer which needs CPU translation , which speedup drawing a LOT not having to worry about tile boundaries albiet slows buffer sending to VRAM. The interior filling of triangles now is running at 1.5c ( 68k cycles ) per pixel ! however sending the buffer is twice as slow per byte as we need the CPU to send the buffer to VRAM to write to the tile format the VDP needs, rather than DMA directly to VRAM . Overall speedup 25% + as the drawing speedup is much greater than the frame buffer slow down. Optimised Line drawing and Triangle filling -near optimal now for the linear frame buffer. Triangle drawing might get a little bit more yet. Quad drawing is next on the list as that will speedup drawing quads. Some gains will come from been smart about partial clearing of RAM buffers and partial sending to VRAM buffers, rather than send the whole buffer. Vertice rotation and projection needs a lot of optimising .. i expect good gains to come from this - this is all in C at present and all calced in real time. Line and Triangle drawing are in assembly but all vertex manipulation is in C. #SGDK #MegaDrive #SegaGenesis
0:24

** Sega Genesis 3D engine update 4 ** Never can leave a good rabbit hole undug ! .. updates since last update : Changed frame buffer from a VDP tile friendly buffer to a linear buffer which needs CPU translation , which speedup drawing a LOT not having to worry about tile boundaries albiet slows buffer sending to VRAM. The interior filling of triangles now is running at 1.5c ( 68k cycles ) per pixel ! however sending the buffer is twice as slow per byte as we need the CPU to send the buffer to VRAM to write to the tile format the VDP needs, rather than DMA directly to VRAM . Overall speedup 25% + as the drawing speedup is much greater than the frame buffer slow down. Optimised Line drawing and Triangle filling -near optimal now for the linear frame buffer. Triangle drawing might get a little bit more yet. Quad drawing is next on the list as that will speedup drawing quads. Some gains will come from been smart about partial clearing of RAM buffers and partial sending to VRAM buffers, rather than send the whole buffer. Vertice rotation and projection needs a lot of optimising .. i expect good gains to come from this - this is all in C at present and all calced in real time. Line and Triangle drawing are in assembly but all vertex manipulation is in C. #SGDK #MegaDrive #SegaGenesis

Shannon Birt

15,092 views • 2 months ago

** Sega Genesis 3D engine Update 5 ** Added support for Quads - quads are faster than triangles for drawing 4 sided objects ( vs 2 triangles ) as theres larger filling runs before edges. Made multiple enhancements to Triangle and Quad drawing for speed. 27% faster than last Video for triangle drawing. Changed back to Non linear frame buffer + DMA for speed of frame buffer (fb) transfer. The two buffer systems ( Linear FB + CPU blit Vs Non Linear FB + DMA transfer ) I have competing and porting optimisations back to either for the meantime. Triangle drawing vertex calculation done in Assembly . Triangle and Quad functions now loop in Assembly saving stack calls from C. Next tasks, H40 mode for Faster DMA with centered screen , more optimisations in setup , more optimisations in cullling and more detail in general. #SGDK #SegaGenesis #SegaMegadrive
0:22

** Sega Genesis 3D engine Update 5 ** Added support for Quads - quads are faster than triangles for drawing 4 sided objects ( vs 2 triangles ) as theres larger filling runs before edges. Made multiple enhancements to Triangle and Quad drawing for speed. 27% faster than last Video for triangle drawing. Changed back to Non linear frame buffer + DMA for speed of frame buffer (fb) transfer. The two buffer systems ( Linear FB + CPU blit Vs Non Linear FB + DMA transfer ) I have competing and porting optimisations back to either for the meantime. Triangle drawing vertex calculation done in Assembly . Triangle and Quad functions now loop in Assembly saving stack calls from C. Next tasks, H40 mode for Faster DMA with centered screen , more optimisations in setup , more optimisations in cullling and more detail in general. #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

17,044 views • 1 month ago

*** Parodius Update - LAZERS !! *** How many sprites do we have to use on the Sega Genesis to make 4 x 160 pixel wide lazers ?? 10 ? 20 ? ZERO !! Which is really great as when the options overlap all with Lazers using sprites would have lead to sprite severe overload / dropout otherwise. So yes we have some raster trickery going on . I think this might take the cake for the most exotic effect Ive added just for a power up type haha. Breaking down the effect. 1.) Lazer tile rows ( the tile rows the lazers are currently on ) are copied to an offscreen area of the plane . I used the DMA VRAM to VRAM copy mode for this. You can see these offscreen rows just above the Game Videos window in the Plane A tilemap view. 2.) Then a solid block of Lazer colored tiles is drawn at the position of the Lazer horizontally in the offscreen buffer we just copied too - these are 8x8 tiles. 3.) Then onscreen when as the display is being drawn we change to the Lazers row at the correct pixel line offset for exactly 1 scanline then change back to the normal screens next row. I'm using the Horizontal interupt system developed in SOTA for handling the interupts for this. The technique used has been done before on the NES ( Salamander tech demo ) , as usual some of the best techniques come from the 8 bit systems , still it presented challenges getting it working on the MD. These irregular spaced interupts on the Genesis are a little bit of a problem too . All the height sorting has to be done on the frame before. Whats very interesting about the VRAM to VRAM copy DMA (Copy DMA) is it runs asynchronous to the CPU. Normally ROM/RAM to VRAM write DMA (Write DMA) halts the CPU during the send operation but with a Copy DMA I can pipeline one Copy DMA setup while the previous one is copying still . So even though the Copy DMA is 1/2 the speed of a Write DMA with the pipelining and no stalling its probably on par or better in some cases , where a copy makes sense to use. Theres still need some fine tuning , might make smaller lazers with more breaks etc. The Lazers can be full screen width , or narrow as we want so bit of fine tuning here to come. Pyron Vector Orbitex #Parodius #SegaMegadrive #SegaGenesis #SGDK
0:34

*** Parodius Update - LAZERS !! *** How many sprites do we have to use on the Sega Genesis to make 4 x 160 pixel wide lazers ?? 10 ? 20 ? ZERO !! Which is really great as when the options overlap all with Lazers using sprites would have lead to sprite severe overload / dropout otherwise. So yes we have some raster trickery going on . I think this might take the cake for the most exotic effect Ive added just for a power up type haha. Breaking down the effect. 1.) Lazer tile rows ( the tile rows the lazers are currently on ) are copied to an offscreen area of the plane . I used the DMA VRAM to VRAM copy mode for this. You can see these offscreen rows just above the Game Videos window in the Plane A tilemap view. 2.) Then a solid block of Lazer colored tiles is drawn at the position of the Lazer horizontally in the offscreen buffer we just copied too - these are 8x8 tiles. 3.) Then onscreen when as the display is being drawn we change to the Lazers row at the correct pixel line offset for exactly 1 scanline then change back to the normal screens next row. I'm using the Horizontal interupt system developed in SOTA for handling the interupts for this. The technique used has been done before on the NES ( Salamander tech demo ) , as usual some of the best techniques come from the 8 bit systems , still it presented challenges getting it working on the MD. These irregular spaced interupts on the Genesis are a little bit of a problem too . All the height sorting has to be done on the frame before. Whats very interesting about the VRAM to VRAM copy DMA (Copy DMA) is it runs asynchronous to the CPU. Normally ROM/RAM to VRAM write DMA (Write DMA) halts the CPU during the send operation but with a Copy DMA I can pipeline one Copy DMA setup while the previous one is copying still . So even though the Copy DMA is 1/2 the speed of a Write DMA with the pipelining and no stalling its probably on par or better in some cases , where a copy makes sense to use. Theres still need some fine tuning , might make smaller lazers with more breaks etc. The Lazers can be full screen width , or narrow as we want so bit of fine tuning here to come. Pyron Vector Orbitex #Parodius #SegaMegadrive #SegaGenesis #SGDK

Shannon Birt

16,162 views • 9 months ago

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius
0:30

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius

Shannon Birt

25,495 views • 5 months ago

** Mega Parodius Update ( MegaDrive / Genesis ) ** 2 vid updates - In the first the Vic Viper players ship is heavily damaged .. only the bomb bay is operational ... so the viper goes on a bomb *blast* processing rampage !! ... This shows enemy destruction and some polishing of the bomb effect. The 2nd vid shows VRAM handling of objects with the tile viewer opened below the gameplay window. You can see objects load in , then as only the burning chests remain those animations are shifted live to maximise free object buffer. Progress since last progress vid : All collisions now implemented : Enemy to Player added , Bomb to Enemy added, Enemy Destruction added. Auto Defragging VRAM system implemented for Enemy Objects. Supports variable slot size also to maximise tile space . Fixed slot sizes wouldn't allow enough slots as they would need to be too large to cover all objects. Without defragging the VRAM would become like swiss cheese after a few screens of enemies also making larger slots difficult to allocate. Vram was getting tight due to things like the Blue Bell Bomb / White Bell text needing a reserved amount of vram ( as they can occur anywhere in the level via powerups ) . Theres also theres quite a bit of variety in Level 1 with warmup enemies , bottle enemies, chickens, crabs, orcas, chests, bees, penguin bathes, walking penguins, bouncing heads etc. We are also using all the arcade assets without trying to cut frames. It can't be loaded all at once so a dynamic system is needed. The enemy object buffer is 444 tiles presently for Level 1 , but the Catboss for example takes 308 when he's onscreen so things can get squeezed. For Mega versions of levels I wanted to ramp things up so that might mean we need more diversity in places than for the arcade accurate option , this system will help that also. The system can stream animation or utilise static animation if vram allows. Seems a mundane thing but sloppy vram management is the achiles heal of GFX diversity in a retro game . To help reduce the Bell effects VRAM buffer , Blue Bomb tiles required reduced to 120 tiles Max ( was 172 ) with no loss of quality . I've also reduced the sprite count by 6 sprites overall - down to 46 sprites used at max frame size. Lots more action / enemies to add yet but particularly the VRAM handling had to be improved before we can implement everything so glad thats in place now. Pyron and Vector Orbitex have been busy with upcoming GFX / Audion for the port , as always I'm very gratefull to have these Masters working with me on the port . #SGDK #Parodius #SegaMegadrive #SegaGenesis
0:26

** Mega Parodius Update ( MegaDrive / Genesis ) ** 2 vid updates - In the first the Vic Viper players ship is heavily damaged .. only the bomb bay is operational ... so the viper goes on a bomb *blast* processing rampage !! ... This shows enemy destruction and some polishing of the bomb effect. The 2nd vid shows VRAM handling of objects with the tile viewer opened below the gameplay window. You can see objects load in , then as only the burning chests remain those animations are shifted live to maximise free object buffer. Progress since last progress vid : All collisions now implemented : Enemy to Player added , Bomb to Enemy added, Enemy Destruction added. Auto Defragging VRAM system implemented for Enemy Objects. Supports variable slot size also to maximise tile space . Fixed slot sizes wouldn't allow enough slots as they would need to be too large to cover all objects. Without defragging the VRAM would become like swiss cheese after a few screens of enemies also making larger slots difficult to allocate. Vram was getting tight due to things like the Blue Bell Bomb / White Bell text needing a reserved amount of vram ( as they can occur anywhere in the level via powerups ) . Theres also theres quite a bit of variety in Level 1 with warmup enemies , bottle enemies, chickens, crabs, orcas, chests, bees, penguin bathes, walking penguins, bouncing heads etc. We are also using all the arcade assets without trying to cut frames. It can't be loaded all at once so a dynamic system is needed. The enemy object buffer is 444 tiles presently for Level 1 , but the Catboss for example takes 308 when he's onscreen so things can get squeezed. For Mega versions of levels I wanted to ramp things up so that might mean we need more diversity in places than for the arcade accurate option , this system will help that also. The system can stream animation or utilise static animation if vram allows. Seems a mundane thing but sloppy vram management is the achiles heal of GFX diversity in a retro game . To help reduce the Bell effects VRAM buffer , Blue Bomb tiles required reduced to 120 tiles Max ( was 172 ) with no loss of quality . I've also reduced the sprite count by 6 sprites overall - down to 46 sprites used at max frame size. Lots more action / enemies to add yet but particularly the VRAM handling had to be improved before we can implement everything so glad thats in place now. Pyron and Vector Orbitex have been busy with upcoming GFX / Audion for the port , as always I'm very gratefull to have these Masters working with me on the port . #SGDK #Parodius #SegaMegadrive #SegaGenesis

Shannon Birt

12,721 views • 5 months ago

** Sega Genesis 3D engine Day 2 ** Added solid filled triangles. Added colors ( full 15 color buffer ) . All code in C so far apart form the buffer clear and DMA buffer sending so should be some good speedups to come yet once line / triangle routines are ported to 68k Assembly. I've done basic filling optimisations in C such as where we can write longs eg fill 8 pixels at once for interior parts of the triangle the function will utilise that. Still using 3 divisions per triangle setup , I think i will see if I can use a cheaper reciprical multiplication instead. All rotations vertices are calculated live , in 2d space at present. #SGDK #SegaGenesis #SegaMegadrive
0:26

** Sega Genesis 3D engine Day 2 ** Added solid filled triangles. Added colors ( full 15 color buffer ) . All code in C so far apart form the buffer clear and DMA buffer sending so should be some good speedups to come yet once line / triangle routines are ported to 68k Assembly. I've done basic filling optimisations in C such as where we can write longs eg fill 8 pixels at once for interior parts of the triangle the function will utilise that. Still using 3 divisions per triangle setup , I think i will see if I can use a cheaper reciprical multiplication instead. All rotations vertices are calculated live , in 2d space at present. #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

17,379 views • 2 months ago

*** SOTA RETROCON S.O.T.A UPDATE *** Whilst the Versao LTDA team is busy at Retrocon showing off our latest Sega Genesis SOTA update, here is a small snippet of how the game is progressing. This video has 3 parts, our menu screen, rain - wind sub section of level 1, then the boss. Everything is still wip including my gameplay skill lol ( and i thought the controller would help .. ) Some challenges overcome : The Menu screen uses shadow and highlight transparency modes in two ways, the background mode for the light rays and then the sprite mode for the mist - it has a nice overlapping effect too, due to using the forground plane for the light rays (s & h background mode) the entire forground is made up of sprites - all the words are sprites . SaviorMarks sent me a screenshot of an issue with boss leftover Mist sprites affecting the menu screen and I thought that looks really cool - lets do that haha . Sometimes bugs are keepers !! The rain section uses more than 80 sprites, a sprite multiplexor handles the rain whilst normal non plexed sprites make up the moon / clouds in the far background , the lamp posts and lamp light in the mid forground and Fences in the front forground . Without the multiplexor there was too much drop out on the rain at times. The rain is still blinked in alternating X positions due to the pixels per line limit , but it gives a great result still. The lamp lights use Shaded Active Dither as S&H here would not overlap the enemies / player . The Boss was a challenge with its size and full frame updates, up to 650 tiles are changed per animation frame into vram. Custom Dual priority DMA routines and extended DMA timings are used (still NTSC 224 pixels tall screen size but most of the vblank was used for updating tiles ) . These methods were used to update the bosses dual display buffers. I needed to have dual priority DMA buffers as the player / waterfall etc had to update their frames whilst the boss is constantly streaming tiles. There are also S&H transparent Mist sprites used for the boss sequence. It seems if you want everything to break at once target a demo for a retrocon event haha, we had lots of issues mainly with vram getting stomped and as all animating sprites need to be DMA streamed to fit into VRAM as the forgrounds and backgrounds take up a lot of tiles. Some new tools which show the VRAM allocation for the sprite engine on a frame by frame basis helped and a self defragging VRAM system helped quite a bit also. Thankfully things are in a good state now apart from a couple of small bugs that persist. Thanks to SaviorMarks and GamesCare for putting up with and testing all the bugged updates haha !! #SegaGenesis #SGDK GamesCare SaviorMarks #VersaoLTDA
1:25

*** SOTA RETROCON S.O.T.A UPDATE *** Whilst the Versao LTDA team is busy at Retrocon showing off our latest Sega Genesis SOTA update, here is a small snippet of how the game is progressing. This video has 3 parts, our menu screen, rain - wind sub section of level 1, then the boss. Everything is still wip including my gameplay skill lol ( and i thought the controller would help .. ) Some challenges overcome : The Menu screen uses shadow and highlight transparency modes in two ways, the background mode for the light rays and then the sprite mode for the mist - it has a nice overlapping effect too, due to using the forground plane for the light rays (s & h background mode) the entire forground is made up of sprites - all the words are sprites . SaviorMarks sent me a screenshot of an issue with boss leftover Mist sprites affecting the menu screen and I thought that looks really cool - lets do that haha . Sometimes bugs are keepers !! The rain section uses more than 80 sprites, a sprite multiplexor handles the rain whilst normal non plexed sprites make up the moon / clouds in the far background , the lamp posts and lamp light in the mid forground and Fences in the front forground . Without the multiplexor there was too much drop out on the rain at times. The rain is still blinked in alternating X positions due to the pixels per line limit , but it gives a great result still. The lamp lights use Shaded Active Dither as S&H here would not overlap the enemies / player . The Boss was a challenge with its size and full frame updates, up to 650 tiles are changed per animation frame into vram. Custom Dual priority DMA routines and extended DMA timings are used (still NTSC 224 pixels tall screen size but most of the vblank was used for updating tiles ) . These methods were used to update the bosses dual display buffers. I needed to have dual priority DMA buffers as the player / waterfall etc had to update their frames whilst the boss is constantly streaming tiles. There are also S&H transparent Mist sprites used for the boss sequence. It seems if you want everything to break at once target a demo for a retrocon event haha, we had lots of issues mainly with vram getting stomped and as all animating sprites need to be DMA streamed to fit into VRAM as the forgrounds and backgrounds take up a lot of tiles. Some new tools which show the VRAM allocation for the sprite engine on a frame by frame basis helped and a self defragging VRAM system helped quite a bit also. Thankfully things are in a good state now apart from a couple of small bugs that persist. Thanks to SaviorMarks and GamesCare for putting up with and testing all the bugged updates haha !! #SegaGenesis #SGDK GamesCare SaviorMarks #VersaoLTDA

Shannon Birt

10,243 views • 10 months ago

YO ADRIAN! I DID IT! Update on my TMNT SNES port. This is the most extensive OAM overhaul I've ever done with a port, and I'm damn proud of myself! Lot of reverse engineering with the OG OAM engine, and I was finally able to incorporate a new method of writing to the buffer. This game does some heavy ADC/TAX for OAM buffer rotation to try to work around the sprite flicker. But that ADC/TAX rotation was complicating things for me when I was trying to incorporate a 16-bit index engine. What is also tricky, is that this game uses 8x16 sprites, and what is special on the NES, its hardware creates the bottom 8x8 sprite tile, without the need of the OAM to have it present. You can't do that on the SNES, you have to create that 2nd 8x8 sprite tile within code. The reason this is such a big deal, is before with 8x16 titles i've worked on, I would first simply copy the games original oam buffer to my snes buffer, but that addded alot of extra cpu time, this is present in my Legend of Zelda SNES port. Later ports I've done, I don't do that anymore, I modify the games original storage of OAM values, and send them directly to my custom snes OAM buffer, eliminating extra cpu cycles. So what's the big deal? My method of doing 8x16 sprites, is using my first 256 byte oam buffer for the top 8x8 tile, and my second 256 byte oam buffer for the bottom 8x8 tile. The issue I was having, was errors with sprite priority when sprites overlap each other. I noticed this right away during the dam sequence where the turtles have to disarm the bombs. Here is a before and after my port. Now I can finally move on with the port! 🙂
1:16

YO ADRIAN! I DID IT! Update on my TMNT SNES port. This is the most extensive OAM overhaul I've ever done with a port, and I'm damn proud of myself! Lot of reverse engineering with the OG OAM engine, and I was finally able to incorporate a new method of writing to the buffer. This game does some heavy ADC/TAX for OAM buffer rotation to try to work around the sprite flicker. But that ADC/TAX rotation was complicating things for me when I was trying to incorporate a 16-bit index engine. What is also tricky, is that this game uses 8x16 sprites, and what is special on the NES, its hardware creates the bottom 8x8 sprite tile, without the need of the OAM to have it present. You can't do that on the SNES, you have to create that 2nd 8x8 sprite tile within code. The reason this is such a big deal, is before with 8x16 titles i've worked on, I would first simply copy the games original oam buffer to my snes buffer, but that addded alot of extra cpu time, this is present in my Legend of Zelda SNES port. Later ports I've done, I don't do that anymore, I modify the games original storage of OAM values, and send them directly to my custom snes OAM buffer, eliminating extra cpu cycles. So what's the big deal? My method of doing 8x16 sprites, is using my first 256 byte oam buffer for the top 8x8 tile, and my second 256 byte oam buffer for the bottom 8x8 tile. The issue I was having, was errors with sprite priority when sprites overlap each other. I noticed this right away during the dam sequence where the turtles have to disarm the bombs. Here is a before and after my port. Now I can finally move on with the port! 🙂

infidelity

13,377 views • 9 months ago

** Mega Parodius Update ** The team have been busy over last couple of weeks , implementing more of the games engine. WIP since last update : White Bell power up ( this is the text attack ) Blue Bell power up ( full screen explosion ) Catboss & animating Trees Updated Lazers to work on the BGB layer ( Plane A updated to 64x64 tilemap ) . Pyron has been doing excellent work on Blue bell Explosion, Whitebell power up text gfx - the slogans are great !! Arcade quality tree animations have been added. Feeding me a lot of videos so we can replicate the arcade port more accurately. Vector Orbitex has updated the music to mark IV for stage 1 making it smaller yet again , he's also added the Orchestra Hit in , potentially more samples can be added back in now also as the song now is a miniscule 57 kb. I keep telling him its 2025 - not 1990 for rom sizes haha , a professional is always a professional though !! The Blue Bell power up uses the static large sprite class I made for SOTA where it supports unlimited amount of sprites per object and detects all the reverses / flips & uses the same tile pointers where it can and crunches it down into single sprite object. We use up to 40 sprites in the Explosion but only 147 tiles needed in vram thanks to clever use of mirroring. The Catboss is easily the hardest enemy in the level for a few reasons - we also had to free up Plane A so the boss could shift upwards onscreen, so lazer effects were shifted to Plane B. The bit that caused me the most issues was when he sits in the water line between the two islands. He is quite wide and also has overlapping palettes and animating parts , to do it solely with sprites would have lead to severe dropout at times. At the waterline we have to simulate 3 background planes and sprites at that point and we only have 2 background planes. Luckily the MD sprite engine is very flexible and we were able to recreate the arcade look at this point with some sprite trickery, the water-line is now sprites . So we use Plane A + sprites to recreate him and use a lot of plane animation to reduce the amount of sprites needed. For example the face, the tail the propeller are all plane A animations . I analysed the SNES/PCE versions and we use less sprites than those versions for him so that will help reduce the chance of sprite dropout when attacking. The Catboss is only about 1/2 done , all damage states, the onboard penguin factory, bullets from Cannons yet to added etc. He wraps around at the end of the vid as theres no destruction routine in for him yet . No extra enemies in at this stage , tackling the hard parts first etc. We took the arcade GFX for the Trees that sway around under the Catboss, all the animations are in. There were some DMA bandwidth issues originally I had to sort out as the Catboss has several animating parts + swaying Trees was leading to overload so after some load balancing it all is playing nicely !! We still have loads of stuff to add , collisions are not in - normal enemy waves etc but yeah a lot of future issues were sorting out just getting this far. So the team is very happy with the progress !! #SGDK #Parodius #SegaGenesis #SegaMegadrive #indiegame
0:47

** Mega Parodius Update ** The team have been busy over last couple of weeks , implementing more of the games engine. WIP since last update : White Bell power up ( this is the text attack ) Blue Bell power up ( full screen explosion ) Catboss & animating Trees Updated Lazers to work on the BGB layer ( Plane A updated to 64x64 tilemap ) . Pyron has been doing excellent work on Blue bell Explosion, Whitebell power up text gfx - the slogans are great !! Arcade quality tree animations have been added. Feeding me a lot of videos so we can replicate the arcade port more accurately. Vector Orbitex has updated the music to mark IV for stage 1 making it smaller yet again , he's also added the Orchestra Hit in , potentially more samples can be added back in now also as the song now is a miniscule 57 kb. I keep telling him its 2025 - not 1990 for rom sizes haha , a professional is always a professional though !! The Blue Bell power up uses the static large sprite class I made for SOTA where it supports unlimited amount of sprites per object and detects all the reverses / flips & uses the same tile pointers where it can and crunches it down into single sprite object. We use up to 40 sprites in the Explosion but only 147 tiles needed in vram thanks to clever use of mirroring. The Catboss is easily the hardest enemy in the level for a few reasons - we also had to free up Plane A so the boss could shift upwards onscreen, so lazer effects were shifted to Plane B. The bit that caused me the most issues was when he sits in the water line between the two islands. He is quite wide and also has overlapping palettes and animating parts , to do it solely with sprites would have lead to severe dropout at times. At the waterline we have to simulate 3 background planes and sprites at that point and we only have 2 background planes. Luckily the MD sprite engine is very flexible and we were able to recreate the arcade look at this point with some sprite trickery, the water-line is now sprites . So we use Plane A + sprites to recreate him and use a lot of plane animation to reduce the amount of sprites needed. For example the face, the tail the propeller are all plane A animations . I analysed the SNES/PCE versions and we use less sprites than those versions for him so that will help reduce the chance of sprite dropout when attacking. The Catboss is only about 1/2 done , all damage states, the onboard penguin factory, bullets from Cannons yet to added etc. He wraps around at the end of the vid as theres no destruction routine in for him yet . No extra enemies in at this stage , tackling the hard parts first etc. We took the arcade GFX for the Trees that sway around under the Catboss, all the animations are in. There were some DMA bandwidth issues originally I had to sort out as the Catboss has several animating parts + swaying Trees was leading to overload so after some load balancing it all is playing nicely !! We still have loads of stuff to add , collisions are not in - normal enemy waves etc but yeah a lot of future issues were sorting out just getting this far. So the team is very happy with the progress !! #SGDK #Parodius #SegaGenesis #SegaMegadrive #indiegame

Shannon Birt

19,194 views • 8 months ago

Anyone with 8GB or 12GB VRAM setups needs to understand that "-ncmoe" is the key flag to boost performance on llama.cpp Here are my results for Qwen3.6 35B A3B, with 64k q8_0 context on a 8GB RTX 3070Ti: ⚪️ no flag → 8.7 tok/s RAM: 13.6GB & VRAM: 7.8GB 🔴 -ncmoe 35 → 27.5 tok/s RAM: 12.1GB & VRAM: 4.3GB 🟢 -ncmoe 30 → 32.5 tok/s RAM: 12GB & VRAM: 5.6GB 🔵 -ncmoe 25 → 40.9 tok/s RAM: 12GB & VRAM: 6.9GB Please note the ram and vram usage you see are total usage of a windows pc, with the model running. My friend's setup: 8GB VRAM and 16GB RAM. You can boost performance by switching to Linux, just something to keep in mind. Basically, this flag keeps the MoE experts in the first X layers on your CPU + RAM, instead of eating all your VRAM straight away. This is a smart hybrid offload way that lets you run bigger models without OOM while keeping the rest on your GPU for speed. As we can see on the data, there's a sweet spot. When we lower it from 35 to 25, speed bumps +50% because there are more layers on your GPU (look at the VRAM usage). The key here is to play around with the number and fit as much as possible on your VRAM, goal is to have 1GB/800MB headroom to avoid stress. ↓ server flags below
0:37

Anyone with 8GB or 12GB VRAM setups needs to understand that "-ncmoe" is the key flag to boost performance on llama.cpp Here are my results for Qwen3.6 35B A3B, with 64k q8_0 context on a 8GB RTX 3070Ti: ⚪️ no flag → 8.7 tok/s RAM: 13.6GB & VRAM: 7.8GB 🔴 -ncmoe 35 → 27.5 tok/s RAM: 12.1GB & VRAM: 4.3GB 🟢 -ncmoe 30 → 32.5 tok/s RAM: 12GB & VRAM: 5.6GB 🔵 -ncmoe 25 → 40.9 tok/s RAM: 12GB & VRAM: 6.9GB Please note the ram and vram usage you see are total usage of a windows pc, with the model running. My friend's setup: 8GB VRAM and 16GB RAM. You can boost performance by switching to Linux, just something to keep in mind. Basically, this flag keeps the MoE experts in the first X layers on your CPU + RAM, instead of eating all your VRAM straight away. This is a smart hybrid offload way that lets you run bigger models without OOM while keeping the rest on your GPU for speed. As we can see on the data, there's a sweet spot. When we lower it from 35 to 25, speed bumps +50% because there are more layers on your GPU (look at the VRAM usage). The key here is to play around with the number and fit as much as possible on your VRAM, goal is to have 1GB/800MB headroom to avoid stress. ↓ server flags below

left curve dev

165,327 views • 1 month ago

*** Parodius Demo Update *** After seeing my good friend Pyron amazing Parodius artwork , I could not let that go to waste. Its a crying shame Konami's shooters did not make it to MD at the time , time to rectify that (in time). The video shows some of the progress so far. Stage 1 scrolling using the streaming scroller from lufthoheit to automatically manage the tile management for the scrolling rather than using different sets etc. Its great when I can grab bits of code and apply them to new projects, it speeds things up !! Lufthoheits new stage is coming along well also and has its first enemies in , hopefully show something of that soon. The VRAM view is to the right , we will have plenty of vram left for objects without resorting to much manual management it seems. ~ 1/2 vram left. It looks like the biggest challenge for this level is the Cat Ship mid boss - the end boss seems easier in comparison for a few reasons. I've analysed the way it was done on PCE and SNES and will come up with the best option for MD. More to come on that soon. At present we will target mainly assembly , so performance won't be an issue . I'm not sure we need a sprite multiplexor for > 80 sprites , but we will use one anyway just to not have regrets/changes later on and for the Hint color effects the multiplexor can do also. We have an A level musician volunteering also for those concerned about the audio side of things - it wont dissapoint I'm sure. As this is now my 3rd / 4th project it will be done as time permits so no gaurantees on timelines sorry - we are all hoping to do well by the community however. #SGDK #Konami #Parodius #MegaDrive #SegaGenesis
0:45

*** Parodius Demo Update *** After seeing my good friend Pyron amazing Parodius artwork , I could not let that go to waste. Its a crying shame Konami's shooters did not make it to MD at the time , time to rectify that (in time). The video shows some of the progress so far. Stage 1 scrolling using the streaming scroller from lufthoheit to automatically manage the tile management for the scrolling rather than using different sets etc. Its great when I can grab bits of code and apply them to new projects, it speeds things up !! Lufthoheits new stage is coming along well also and has its first enemies in , hopefully show something of that soon. The VRAM view is to the right , we will have plenty of vram left for objects without resorting to much manual management it seems. ~ 1/2 vram left. It looks like the biggest challenge for this level is the Cat Ship mid boss - the end boss seems easier in comparison for a few reasons. I've analysed the way it was done on PCE and SNES and will come up with the best option for MD. More to come on that soon. At present we will target mainly assembly , so performance won't be an issue . I'm not sure we need a sprite multiplexor for > 80 sprites , but we will use one anyway just to not have regrets/changes later on and for the Hint color effects the multiplexor can do also. We have an A level musician volunteering also for those concerned about the audio side of things - it wont dissapoint I'm sure. As this is now my 3rd / 4th project it will be done as time permits so no gaurantees on timelines sorry - we are all hoping to do well by the community however. #SGDK #Konami #Parodius #MegaDrive #SegaGenesis

Shannon Birt

12,526 views • 10 months ago

I know some bros want to see what happens when we push the value even further, so here we go: ⚪️ -ncmoe 25 → 41.8 tok/s RAM: 12GB & VRAM: 6.9GB 🔴 -ncmoe 23 → 43.8 tok/s RAM: 12.2GB & VRAM: 7.4GB 🟢 -ncmoe 21 → 38.6 tok/s RAM: 12.4GB & VRAM: 7.8GB 🔵 -ncmoe 19 → 19.8 tok/s RAM: 13.8GB & VRAM: 7.8GB As you can see, there's a sweet spot with the VRAM usage. Play around and monitor to find the right value for your setup, you can use llama.cpp web ui to monitor speeds easily Sweet spot seems to be 25-23 for 8GB VRAM ✅ +40tok/s for Qwen3.6 35B with 64k q8_0 context on a 8GB card is very impressive just by using base llama.cpp, and we didn't even try Turboquant, MTP or Dflash yet! I'll focus on these next 👀 (Server flags and setup in the quoted tweet)
0:29

I know some bros want to see what happens when we push the value even further, so here we go: ⚪️ -ncmoe 25 → 41.8 tok/s RAM: 12GB & VRAM: 6.9GB 🔴 -ncmoe 23 → 43.8 tok/s RAM: 12.2GB & VRAM: 7.4GB 🟢 -ncmoe 21 → 38.6 tok/s RAM: 12.4GB & VRAM: 7.8GB 🔵 -ncmoe 19 → 19.8 tok/s RAM: 13.8GB & VRAM: 7.8GB As you can see, there's a sweet spot with the VRAM usage. Play around and monitor to find the right value for your setup, you can use llama.cpp web ui to monitor speeds easily Sweet spot seems to be 25-23 for 8GB VRAM ✅ +40tok/s for Qwen3.6 35B with 64k q8_0 context on a 8GB card is very impressive just by using base llama.cpp, and we didn't even try Turboquant, MTP or Dflash yet! I'll focus on these next 👀 (Server flags and setup in the quoted tweet)

left curve dev

18,049 views • 1 month ago

*** Mega Parodius Sega Megadrive Update *** Lately I've been having some fun seeing how far we can push the Parodius game engine . This is not arcade accurate - just for testing, decreased bullet timers and upped the bullet count to see what would happen re cpu usage when things are made a lot busier ! Maybe something like this could be insane mode in the options etc. Since last update we are a lot more optimised under the hood . The C based sprite engine, particularly visibility checking was speedup , overall 25 % faster. Then re-wrote the sprite engine completely in 68k assembly , 30% faster again. It took about 3 days and 1500 lines of assembly , thankfully the gains were worth it. All these gains will be back ported to S.O.T.A also as its using the same sprite engine. Usage is around 19% of cpu per frame with a full sprite load - 33 % cpu left in the busiest frame currently . Parodius is using a write the sprite list every frame type engine , so priority and meta-sprite objects can be handled with ease albiet its still a bit slower than static allocation sprite engines such as the one in lufthoheit but this is a bit easier to code for in the long run. All collision checks are been done , we are using a spatial grid system to get the collision checks done faster than a brute force approach . To get to maximum sprite count destruction is disabled in the video. We hit 80 sprites onscreen in this sequence , the sprite counter is one the Left side. We use about 16 sprites in the top hud and water line , about 21 for player attacks / missiles / shots / options . Up to 35 bullets + enemies . No lazer usage here as the Lazers use zero sprites thanks to the raster tricks , this video is all about the sprites ! Improved the water line when the Catboss is active , as he is Sprites + Forground we are doing some tile rotation tricks eg bit scrolling to give the impression of parrallax at that point . Vector Orbitex has updated the stage 1 music again and has made things even higher quality , hes mixed pcm and fm channels together to create higher quality orchestral hits for example . Pyron has started converting assets from stage 2/3 , some amazing work there . Hes well ahead of me at present which is a good thing. Still lots of incomplete animations missing logic etc , its slow going with RL getting in the way haha and 2 other projects !! Still its fun !! #SGDK #SegaMegadrive #SegaGenesis #Parodius
0:41

*** Mega Parodius Sega Megadrive Update *** Lately I've been having some fun seeing how far we can push the Parodius game engine . This is not arcade accurate - just for testing, decreased bullet timers and upped the bullet count to see what would happen re cpu usage when things are made a lot busier ! Maybe something like this could be insane mode in the options etc. Since last update we are a lot more optimised under the hood . The C based sprite engine, particularly visibility checking was speedup , overall 25 % faster. Then re-wrote the sprite engine completely in 68k assembly , 30% faster again. It took about 3 days and 1500 lines of assembly , thankfully the gains were worth it. All these gains will be back ported to S.O.T.A also as its using the same sprite engine. Usage is around 19% of cpu per frame with a full sprite load - 33 % cpu left in the busiest frame currently . Parodius is using a write the sprite list every frame type engine , so priority and meta-sprite objects can be handled with ease albiet its still a bit slower than static allocation sprite engines such as the one in lufthoheit but this is a bit easier to code for in the long run. All collision checks are been done , we are using a spatial grid system to get the collision checks done faster than a brute force approach . To get to maximum sprite count destruction is disabled in the video. We hit 80 sprites onscreen in this sequence , the sprite counter is one the Left side. We use about 16 sprites in the top hud and water line , about 21 for player attacks / missiles / shots / options . Up to 35 bullets + enemies . No lazer usage here as the Lazers use zero sprites thanks to the raster tricks , this video is all about the sprites ! Improved the water line when the Catboss is active , as he is Sprites + Forground we are doing some tile rotation tricks eg bit scrolling to give the impression of parrallax at that point . Vector Orbitex has updated the stage 1 music again and has made things even higher quality , hes mixed pcm and fm channels together to create higher quality orchestral hits for example . Pyron has started converting assets from stage 2/3 , some amazing work there . Hes well ahead of me at present which is a good thing. Still lots of incomplete animations missing logic etc , its slow going with RL getting in the way haha and 2 other projects !! Still its fun !! #SGDK #SegaMegadrive #SegaGenesis #Parodius

Shannon Birt

16,084 views • 6 months ago

Jesus Christ, jnmartin has officially implemented his first big improvement over the N64 original for the Sega Dreamcast port of Mario Kart 64! Now the jumpotron monitor screens in Wario Stadium and and Luigi Raceway are updating at a full 30FPS, or 6x the framerate of the N64! ...and he's doing this entirely in software with the DC's SH4 CPU performing slow, direct VRAM reads from the framebuffer into a temporary buffer in system RAM which is later passed to OpenGL which transfers it back into VRAM to update the jumpotron texture with... and the freaking Dreamcast doesn't drop a frame doing all this shit! Might want to keep that in mind, as a community... That accessing texture memory or the framebuffer directly from the SH4 via the "uint16_t vram_s[]" symbol that the video API within KallistiOS exposes, while comparatively slow, is not actually so slow as to be unrealistic for a well-optimized game to do anything useful with... very interesting!
0:26

Jesus Christ, jnmartin has officially implemented his first big improvement over the N64 original for the Sega Dreamcast port of Mario Kart 64! Now the jumpotron monitor screens in Wario Stadium and and Luigi Raceway are updating at a full 30FPS, or 6x the framerate of the N64! ...and he's doing this entirely in software with the DC's SH4 CPU performing slow, direct VRAM reads from the framebuffer into a temporary buffer in system RAM which is later passed to OpenGL which transfers it back into VRAM to update the jumpotron texture with... and the freaking Dreamcast doesn't drop a frame doing all this shit! Might want to keep that in mind, as a community... That accessing texture memory or the framebuffer directly from the SH4 via the "uint16_t vram_s[]" symbol that the video API within KallistiOS exposes, while comparatively slow, is not actually so slow as to be unrealistic for a well-optimized game to do anything useful with... very interesting!

Falco Girgis

24,032 views • 1 year ago

I think really the best solution is Ukrainian membership in NATO and the idea of creating security in Europe by having Ukraine as a kind of buffer zone between Russia and nato countries. It just failed. That is the reality. It failed. So we don't need to have such a buffer. We need Ukraine to be inside NATO. Unfortunately, now we see that nato leaders and, first of all, the United States are not ready for this. But I think that will come CNN
3:49

I think really the best solution is Ukrainian membership in NATO and the idea of creating security in Europe by having Ukraine as a kind of buffer zone between Russia and nato countries. It just failed. That is the reality. It failed. So we don't need to have such a buffer. We need Ukraine to be inside NATO. Unfortunately, now we see that nato leaders and, first of all, the United States are not ready for this. But I think that will come CNN

Oleksiy Goncharenko

11,685 views • 11 months ago

** MEGA Parodius Scaling Effects Part 2 ** Well - this is the BIG one - literally !! Huge thanks to my team Pyron & Vector Orbitex for their efforts. Pyron has provided all the source frames for Puyon and his spikes / explosion and a lot of analysis video on how the spikes behave / move which was really helpful. Pyron also used his CRT setup for this video as we felt an emulator video would not do it justice - running on 100% real MD hardware FTW. Vector has provided the catchy boss music and its sounding great - as always ! The coding on this has been a bit insane - things done since part 1 post previous: Implemented dual buffering - Last video was single buffered - so VRAM is very tight now , we only have about 40/2048 tiles free. For the longest time I didn't think it would fit - I found a vram jigsaw puzzle that made it work in the end. Double buffering has cleaned up the stability of the animation and matches the arcade scaling effect now albiet costing 2x more VRAM . Vertical Scaling Implemented - the vertical scaler was taken from Lufthoheit ( my other shooter ) and its heavily optimised to reduce cpu usage. During the scaling the vertical scaler partitions the 68k processor registers into 2 sets, 4 registers are allocated to feeding the fast horizontal interrupt (h-int) that drives the vertical scaling , remaining 12 registers are for the horizontal scaler running in the background. This setup is much faster than normal backup / restore register methods, as we do not need to backup / restore registers in the h-int which would double CPU costs. The catch is the momment any background routine tries to use the H-ints registers it would break things so it has to be carefully timed. Added the spike projectiles - this was very tricky to get close to the arcade, they are semi heat seeking missiles basically and hence needed code that worked out angle differences to player at speed theres no time for arc-tan or similar so it uses faster lookup tables to work out the angles . They speed up over time and get larger and whats more we can't keep all the scales in VRAM - we have room for 2 spike buffers only. Also what was a real pain was working out scaled coordinates for the circular launch of the spikes . Added Fish Damage - Shock frame and Explosion frames from Arcade . Very proud of the fact we have the full arcade quality explosion is which is fully scaled also. Added Temporal Masking - which is fancy wording for don't draw nothing to buffer if nothing is there already there for the scaling . So empty Corners and edges can be optimised out to lower cpu costs and rom costs. I had to make some scripting for this and work out what areas did not need drawing at all in the frame, which should be force cleared by cpu and which areas should just be copied from rom. This reduced rom size by 30 kb and with a bit more work we could extend that to 60 kb & get a bit more speedup even doing so. Added a frame limiter . In the last video update we let the 68k burn hot and just pump out frames as fast as it could - here we match the arcade animation rate which does leave the cpu idling at times , particularly in the smaller frames - even at large though we could be running the animation 25 % faster , issue is though that would speed up the game logic and make it less arcade accurate. We had some real bullet / Spike hell simulations going without the limiter but yeah we had to tone it down a bit. Maybe in a hardcore mode we could let it run wild though ! Code is 95% 68k assembly with about 5% C code (v-int as its cold path ) driving things . This sort of thing needs all the speed it can get !! Well now after all that I can return to finish off Level 1 haha - just a wee sidetrack there . No doubt we will polish stage 8 boss some more in time too !! #SegaMegadrive #SegaGenesis #Parodius #SGDK
0:58

** MEGA Parodius Scaling Effects Part 2 ** Well - this is the BIG one - literally !! Huge thanks to my team Pyron & Vector Orbitex for their efforts. Pyron has provided all the source frames for Puyon and his spikes / explosion and a lot of analysis video on how the spikes behave / move which was really helpful. Pyron also used his CRT setup for this video as we felt an emulator video would not do it justice - running on 100% real MD hardware FTW. Vector has provided the catchy boss music and its sounding great - as always ! The coding on this has been a bit insane - things done since part 1 post previous: Implemented dual buffering - Last video was single buffered - so VRAM is very tight now , we only have about 40/2048 tiles free. For the longest time I didn't think it would fit - I found a vram jigsaw puzzle that made it work in the end. Double buffering has cleaned up the stability of the animation and matches the arcade scaling effect now albiet costing 2x more VRAM . Vertical Scaling Implemented - the vertical scaler was taken from Lufthoheit ( my other shooter ) and its heavily optimised to reduce cpu usage. During the scaling the vertical scaler partitions the 68k processor registers into 2 sets, 4 registers are allocated to feeding the fast horizontal interrupt (h-int) that drives the vertical scaling , remaining 12 registers are for the horizontal scaler running in the background. This setup is much faster than normal backup / restore register methods, as we do not need to backup / restore registers in the h-int which would double CPU costs. The catch is the momment any background routine tries to use the H-ints registers it would break things so it has to be carefully timed. Added the spike projectiles - this was very tricky to get close to the arcade, they are semi heat seeking missiles basically and hence needed code that worked out angle differences to player at speed theres no time for arc-tan or similar so it uses faster lookup tables to work out the angles . They speed up over time and get larger and whats more we can't keep all the scales in VRAM - we have room for 2 spike buffers only. Also what was a real pain was working out scaled coordinates for the circular launch of the spikes . Added Fish Damage - Shock frame and Explosion frames from Arcade . Very proud of the fact we have the full arcade quality explosion is which is fully scaled also. Added Temporal Masking - which is fancy wording for don't draw nothing to buffer if nothing is there already there for the scaling . So empty Corners and edges can be optimised out to lower cpu costs and rom costs. I had to make some scripting for this and work out what areas did not need drawing at all in the frame, which should be force cleared by cpu and which areas should just be copied from rom. This reduced rom size by 30 kb and with a bit more work we could extend that to 60 kb & get a bit more speedup even doing so. Added a frame limiter . In the last video update we let the 68k burn hot and just pump out frames as fast as it could - here we match the arcade animation rate which does leave the cpu idling at times , particularly in the smaller frames - even at large though we could be running the animation 25 % faster , issue is though that would speed up the game logic and make it less arcade accurate. We had some real bullet / Spike hell simulations going without the limiter but yeah we had to tone it down a bit. Maybe in a hardcore mode we could let it run wild though ! Code is 95% 68k assembly with about 5% C code (v-int as its cold path ) driving things . This sort of thing needs all the speed it can get !! Well now after all that I can return to finish off Level 1 haha - just a wee sidetrack there . No doubt we will polish stage 8 boss some more in time too !! #SegaMegadrive #SegaGenesis #Parodius #SGDK

Shannon Birt

26,344 views • 4 months ago

Hello everyone. I've been working every day on my port of Mega Man II SNES 16-BIT. I'd like to showcase the following video, what I have to do in order for the giant BG fish in Bubble Man's stage, to disappear in 16-BIT mode. I like how in Mega Man X, a defeated enemy will have it's image fluctuate from being present on the screen, to not being present on the screen during it's destruction, this happens every other frame. I needed to do something like that in my situation, since I'm using multiple BG layers, and if I simply do what the original 1988 version does, a simple palette fade to blue like the water, the bg image of the fish will still be present. So I've had to create alot of custom asm for the destruction, and non drawing, of the defeated giant bg fish. 1: create new death sequence by modifying the tilemap where the giant fish is located, and alternate it's tileset via a DMA buffer with it's tiles in 1 frame, and blank tiles in another frame 2: at the end of the death sequence, create a flag in ram indicating one of the bg giant fish (there are 2) has been defeated 3: modify the games level construction engine, to read against defeated fish flag to see if it's set, if not, allow the original 16x16 blocks to be drawn, it set, bypass the original 16x16 blocks for bg giant fish and replace with a blank 16x16 block 4: clear defeated bg fish flags when you get a game over, or when bubble man is defeated All of that I've had to code, just for that, heh.
1:37

Hello everyone. I've been working every day on my port of Mega Man II SNES 16-BIT. I'd like to showcase the following video, what I have to do in order for the giant BG fish in Bubble Man's stage, to disappear in 16-BIT mode. I like how in Mega Man X, a defeated enemy will have it's image fluctuate from being present on the screen, to not being present on the screen during it's destruction, this happens every other frame. I needed to do something like that in my situation, since I'm using multiple BG layers, and if I simply do what the original 1988 version does, a simple palette fade to blue like the water, the bg image of the fish will still be present. So I've had to create alot of custom asm for the destruction, and non drawing, of the defeated giant bg fish. 1: create new death sequence by modifying the tilemap where the giant fish is located, and alternate it's tileset via a DMA buffer with it's tiles in 1 frame, and blank tiles in another frame 2: at the end of the death sequence, create a flag in ram indicating one of the bg giant fish (there are 2) has been defeated 3: modify the games level construction engine, to read against defeated fish flag to see if it's set, if not, allow the original 16x16 blocks to be drawn, it set, bypass the original 16x16 blocks for bg giant fish and replace with a blank 16x16 block 4: clear defeated bg fish flags when you get a game over, or when bubble man is defeated All of that I've had to code, just for that, heh.

infidelity

23,162 views • 12 days ago

you can't tell me AI isn't a game changer for programming it's connecting over webrtc the screen is made of 16 by 16 regions each region is 256 by 256 ive come up with a custom encoding I spam UDP packets for each reigion for each client each region is designed to fit in a single packet the next state of the simulation is computed in my GPU using cuda the cuda is linked to golang the program manages a double buffer this is so that the network broadcastloop doesn't contend with the cuda update for the object when you write it sends a udp packet for every mouse event i manage a stream to update it on my gpu the client takes each packet and has custom webgl to update the regions and render everything in a single pass. texture 3d
0:22

you can't tell me AI isn't a game changer for programming it's connecting over webrtc the screen is made of 16 by 16 regions each region is 256 by 256 ive come up with a custom encoding I spam UDP packets for each reigion for each client each region is designed to fit in a single packet the next state of the simulation is computed in my GPU using cuda the cuda is linked to golang the program manages a double buffer this is so that the network broadcastloop doesn't contend with the cuda update for the object when you write it sends a udp packet for every mouse event i manage a stream to update it on my gpu the client takes each packet and has custom webgl to update the regions and render everything in a single pass. texture 3d

kache

97,819 views • 1 year ago

"Assassin’s Creed: Odyssey" map of Greece on a single 32,768 x 32,768 texture in the Browser. Virtual Texture tech in WebGL 2.0 The source is a 804 Mb PNG. Without Virtual Texture tech you'd need to download that and wait for a few seconds for your browser to decode it before you could use it. Your browser would then crash when it tries to upload it to the GPU :) If we imagine that the upload to the GPU would succeed - it would take 4Gb of VRAM. Virtual Texture loads immediately, because the image is split into small fixed-sized tiles with full LoD chain (mips) and uses 2048x2048, which is just 16 Mb of VRAM. Article:
1:30

"Assassin’s Creed: Odyssey" map of Greece on a single 32,768 x 32,768 texture in the Browser. Virtual Texture tech in WebGL 2.0 The source is a 804 Mb PNG. Without Virtual Texture tech you'd need to download that and wait for a few seconds for your browser to decode it before you could use it. Your browser would then crash when it tries to upload it to the GPU :) If we imagine that the upload to the GPU would succeed - it would take 4Gb of VRAM. Virtual Texture loads immediately, because the image is split into small fixed-sized tiles with full LoD chain (mips) and uses 2048x2048, which is just 16 Mb of VRAM. Article:

Alex Goldring

188,343 views • 5 months ago

🇺🇦🇷🇺 NO BUFFER ZONE: “If Russia wants to have a greater distance from us, they can withdraw deeper into the temporarily occupied territories of Ukraine” – Zelensky rejects a "buffer zone" "Only those who do not understand the current state, the technological state, in which the war is taking place today, propose a buffer zone of 40, 50, 60, I have even heard proposals for 100 kilometers. This is a completely different story. Today, heavy weapons are already located more than 10 kilometers apart from each other, because everything is targeted by drones. This buffer zone, I call it a dead zone, some call it a gray zone – it already exists”
1:55

🇺🇦🇷🇺 NO BUFFER ZONE: “If Russia wants to have a greater distance from us, they can withdraw deeper into the temporarily occupied territories of Ukraine” – Zelensky rejects a "buffer zone" "Only those who do not understand the current state, the technological state, in which the war is taking place today, propose a buffer zone of 40, 50, 60, I have even heard proposals for 100 kilometers. This is a completely different story. Today, heavy weapons are already located more than 10 kilometers apart from each other, because everything is targeted by drones. This buffer zone, I call it a dead zone, some call it a gray zone – it already exists”

Lord Bebo

82,116 views • 9 months ago