Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I was playing around with my scaling code and thought it would be cool to play the current Lufthoheit service screen on a CRT on the tripple bypassed MD2 i got recently. I've made the code a bit more efficient and added a whole scale factor so now it...

birt_shannon's profile picture

Shannon Birt

2,572 subscribers

11,643 Aufrufe • vor 1 Jahr •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

*** SEGA GENESIS/MEGADRIVE - SCALING PART 2 *** Whats better on a Friday than seeing some scaling effects on the Megadrive ? .. nothing, so read on ... In the previous part we were software scaling in either axis by a given factor, but I couldn't change the scale factor per scanline on the same frame, so I couldn't skew the base image for tilting into screen eg Mode 7 type effects. - One issue was it was scaling column by column which got wrecked for performance trying per scanline adjustments. So I converted to a row scaler rather than column, this allowed expansions and contractions on a per scanline basis. - Speed up the code significantly , now running a sprite load + music + scaling on cpu with ~50% cpu free. Relied heavily on Python scripts I wrote to generate the 68k assembly for this as it was mind numbing labourious. In doing so I got the scripts competing with each other to come up with the fastest method for each scale , I'm starting to like python ;-) - Tried all sorts to speed up the horizontal interupt - handles vertical scaling, exotic methods eg unsafe interupts / racing the beam & updating the vertical scroll every X cpu cycles, in the end the Z80 cpu (audio) stealing the 68k cpu bus intermittendly just killed these ideas as it would only be 95% stable, ended up just doing smarter interupts that saved a lot of cpu instead. - The good and the bad, spent too long on this is the bad, the good is we will need it in Lufthoheit in a few places to make up for that !! Carsten666 CYBERDEOUS - Crouzet Laurent #SGDK #SegaMegadrive #SegaGenesis
0:25

*** SEGA GENESIS/MEGADRIVE - SCALING PART 2 *** Whats better on a Friday than seeing some scaling effects on the Megadrive ? .. nothing, so read on ... In the previous part we were software scaling in either axis by a given factor, but I couldn't change the scale factor per scanline on the same frame, so I couldn't skew the base image for tilting into screen eg Mode 7 type effects. - One issue was it was scaling column by column which got wrecked for performance trying per scanline adjustments. So I converted to a row scaler rather than column, this allowed expansions and contractions on a per scanline basis. - Speed up the code significantly , now running a sprite load + music + scaling on cpu with ~50% cpu free. Relied heavily on Python scripts I wrote to generate the 68k assembly for this as it was mind numbing labourious. In doing so I got the scripts competing with each other to come up with the fastest method for each scale , I'm starting to like python ;-) - Tried all sorts to speed up the horizontal interupt - handles vertical scaling, exotic methods eg unsafe interupts / racing the beam & updating the vertical scroll every X cpu cycles, in the end the Z80 cpu (audio) stealing the 68k cpu bus intermittendly just killed these ideas as it would only be 95% stable, ended up just doing smarter interupts that saved a lot of cpu instead. - The good and the bad, spent too long on this is the bad, the good is we will need it in Lufthoheit in a few places to make up for that !! Carsten666 CYBERDEOUS - Crouzet Laurent #SGDK #SegaMegadrive #SegaGenesis

Shannon Birt

11,070 Aufrufe • vor 1 Jahr

** 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,803 Aufrufe • vor 9 Monaten

** 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

27,083 Aufrufe • vor 8 Monaten

** SEGA GENESIS / MEGADRIVE Software Scaling + Rotation *** Sega Megadrive can't scale backgrounds and rotate sprites in software at the same time ?? - hold my beer !! After Scaling I've been tinkering with Rotating sprites in software and I think it looks pretty sweet ! In the video 4 * 32x32 sprites are rotated through 64 steps at 30 FPS in software, it could be 60 FPS and more rotating objects if we were not doing the scaling at the same time but even blast processing has its limits ;-) Rotation at 30 FPS is far smoother than you typcially see in even in pre-rendered rotations anyhow ( a 64 frame 32x32 rotation is 32kb - not small ). Challenges were make it fast : very fast as this needs to work at pixel level, not double pixel like scaling. The megadrives packed pixel format (2 pixels per byte) makes that a little bit tricky . When I started the algorithm was 3x slower than now. Make it sensible : has to be usable in game , had to present a rom size reduction over pre-rendered animation. Make it flexible : so we can rotate frames in the background using up idle cycles (end of frame) and store those frames to vram for very heavy cpu scenes, so we can still have very smooth rotation with very heavy cpu demands still. Thanks to my team Carsten666 for the GFX and CYBERDEOUS - Crouzet Laurent for the marvelous tune. #SegaGenesis #SegaMegadrive #SGDK
0:32

** SEGA GENESIS / MEGADRIVE Software Scaling + Rotation *** Sega Megadrive can't scale backgrounds and rotate sprites in software at the same time ?? - hold my beer !! After Scaling I've been tinkering with Rotating sprites in software and I think it looks pretty sweet ! In the video 4 * 32x32 sprites are rotated through 64 steps at 30 FPS in software, it could be 60 FPS and more rotating objects if we were not doing the scaling at the same time but even blast processing has its limits ;-) Rotation at 30 FPS is far smoother than you typcially see in even in pre-rendered rotations anyhow ( a 64 frame 32x32 rotation is 32kb - not small ). Challenges were make it fast : very fast as this needs to work at pixel level, not double pixel like scaling. The megadrives packed pixel format (2 pixels per byte) makes that a little bit tricky . When I started the algorithm was 3x slower than now. Make it sensible : has to be usable in game , had to present a rom size reduction over pre-rendered animation. Make it flexible : so we can rotate frames in the background using up idle cycles (end of frame) and store those frames to vram for very heavy cpu scenes, so we can still have very smooth rotation with very heavy cpu demands still. Thanks to my team Carsten666 for the GFX and CYBERDEOUS - Crouzet Laurent for the marvelous tune. #SegaGenesis #SegaMegadrive #SGDK

Shannon Birt

19,405 Aufrufe • vor 1 Jahr

** Sega Genesis 3D Engine Day 3 ** Blast Processing kicks In !! Converted the Line Drawing and Triangle drawing to 68k Assembly and gained 25% in the line drawing and 33% speedups in the triangle drawing vs C ( so far ) . The scheduler calculating the vertexs is still in C , just the drawing routines are now are in assembly . Possibly 5-10 % gains will come from the scheduler being in ASM also. The Line and Triangle drawing C code took some beating , it was surprising - particularly the line drawing to get a speed up over the C code in ASM. I guess its not too surprising as the C code was basically handling pointers and integers so I had to get exotic to find the speedups. Initially my ASM Line draw was 100% slower than the C code - the first pass conversion from C to ASM is always rough as its more about getting it working then refine later , but yeah 100% slower on first pass was brutal, after 4 hrs tweaking it was 25% faster than the C code so thats a good start - might get more yet. So added more squares and more triangles for load testing at the same frame rate. Its still not anything cohesive but right now focussing on performance in rendering to see how much can be pushed. As rendering will be the biggest cpu soak the faster that goes the better. The smaller triangles take about 1/3 the CPU time of the larger triangles at present so theres definately a fill rate limit vs the setup time to consider. The same would go for the squares been line framed - smaller ones would allow al lot more . #SGDK #SegaGenesis #SegaMegadrive
0:23

** Sega Genesis 3D Engine Day 3 ** Blast Processing kicks In !! Converted the Line Drawing and Triangle drawing to 68k Assembly and gained 25% in the line drawing and 33% speedups in the triangle drawing vs C ( so far ) . The scheduler calculating the vertexs is still in C , just the drawing routines are now are in assembly . Possibly 5-10 % gains will come from the scheduler being in ASM also. The Line and Triangle drawing C code took some beating , it was surprising - particularly the line drawing to get a speed up over the C code in ASM. I guess its not too surprising as the C code was basically handling pointers and integers so I had to get exotic to find the speedups. Initially my ASM Line draw was 100% slower than the C code - the first pass conversion from C to ASM is always rough as its more about getting it working then refine later , but yeah 100% slower on first pass was brutal, after 4 hrs tweaking it was 25% faster than the C code so thats a good start - might get more yet. So added more squares and more triangles for load testing at the same frame rate. Its still not anything cohesive but right now focussing on performance in rendering to see how much can be pushed. As rendering will be the biggest cpu soak the faster that goes the better. The smaller triangles take about 1/3 the CPU time of the larger triangles at present so theres definately a fill rate limit vs the setup time to consider. The same would go for the squares been line framed - smaller ones would allow al lot more . #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

21,354 Aufrufe • vor 6 Monaten

I love the chicken game! Only available on roobet. Use code stevewilldoit and 100% of money generated goes to the players under code . I keep zero. We are still figuring out the details on how that works but haven’t checked the code in weeks it’s all for the players . This was my idea and roobet liked it so we are doing it . :)
0:25

I love the chicken game! Only available on roobet. Use code stevewilldoit and 100% of money generated goes to the players under code . I keep zero. We are still figuring out the details on how that works but haven’t checked the code in weeks it’s all for the players . This was my idea and roobet liked it so we are doing it . :)

Steve Will Do It

131,809 Aufrufe • vor 2 Jahren

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."
2:04

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,073 Aufrufe • vor 4 Monaten

Jannik Sinner was asked about the changes he’s made to his serve since the U.S. Open, ‘At times I still lose it. It’s not a shot where I feel very safe with. At the same time, we are working on that’ “Can I get you to discuss the changes you made to your serve? In particular since the U.S. Open…” Jannik: “Yeah, I mean it’s not only US Open. I felt like the serve was and still is a shot where I need to improve. It’s the only shot we have where we can do everything by our self. There is a lot of room to improve. We changed the motion a little bit. The rhythm of the serve, before, it was too fast in the beginning. Now it’s a bit slower. The toss usually was a bit more in front, a bit on the right. Now it’s a bit more back and over the head. But at times I still lose it. It’s not a shot where I feel very safe with. In the same time we are working on that. It’s one of if not the most important shot we have. Let’s see how I’m gonna serve this season.” (via Australian Open Press)
1:17

Jannik Sinner was asked about the changes he’s made to his serve since the U.S. Open, ‘At times I still lose it. It’s not a shot where I feel very safe with. At the same time, we are working on that’ “Can I get you to discuss the changes you made to your serve? In particular since the U.S. Open…” Jannik: “Yeah, I mean it’s not only US Open. I felt like the serve was and still is a shot where I need to improve. It’s the only shot we have where we can do everything by our self. There is a lot of room to improve. We changed the motion a little bit. The rhythm of the serve, before, it was too fast in the beginning. Now it’s a bit slower. The toss usually was a bit more in front, a bit on the right. Now it’s a bit more back and over the head. But at times I still lose it. It’s not a shot where I feel very safe with. In the same time we are working on that. It’s one of if not the most important shot we have. Let’s see how I’m gonna serve this season.” (via Australian Open Press)

The Tennis Letter

82,301 Aufrufe • vor 8 Monaten

Here are the graphics we made at Intel. I work at Nike innovation now so don’t work on them anymore so not sure all the details for this version but basically we used cameras and computer vision to track each athlete in each lane. Because the cameras were calibrated to specific locations and each frame of video timestamped, we could get distance and time data which you can use to get speed, naturally. Feed the data to a 3D rendered stadium and overlay graphics, and voila. We chose to show speed at the end of each “phase” of the race which I based the location on the data we got from testing and common knowledge of the 100m. So stopping at 30m (drive) and 60 (maintenance) and the end was intentional. Looks like a white label indicates a leader at the end of the phase. The green thing at the front of their label looks to indicate if their are accelerating. This is a bit of a deception because you’re always either accelerating or decelerating. So what it’s actually an indication of is if you’re within a certain percentage of your top speed. The green at the end is graded based on that which is why it’s a gradient. Basically shows that Noah not only has the highest tops speed but holds it best. The final view is everyone’s top speed and where they hit it in the race. It’s freaking wild that Tobago hit his top speed so late.
0:35

Here are the graphics we made at Intel. I work at Nike innovation now so don’t work on them anymore so not sure all the details for this version but basically we used cameras and computer vision to track each athlete in each lane. Because the cameras were calibrated to specific locations and each frame of video timestamped, we could get distance and time data which you can use to get speed, naturally. Feed the data to a 3D rendered stadium and overlay graphics, and voila. We chose to show speed at the end of each “phase” of the race which I based the location on the data we got from testing and common knowledge of the 100m. So stopping at 30m (drive) and 60 (maintenance) and the end was intentional. Looks like a white label indicates a leader at the end of the phase. The green thing at the front of their label looks to indicate if their are accelerating. This is a bit of a deception because you’re always either accelerating or decelerating. So what it’s actually an indication of is if you’re within a certain percentage of your top speed. The green at the end is graded based on that which is why it’s a gradient. Basically shows that Noah not only has the highest tops speed but holds it best. The final view is everyone’s top speed and where they hit it in the race. It’s freaking wild that Tobago hit his top speed so late.

Ashton Eaton

1,164,692 Aufrufe • vor 2 Jahren

$META Devansh Tandon reveals the tokens-in, engagement-out flywheel behind Meta's recommendation system, where better models lift Reels watch time 30% and the monetization pays for the next training run "These scaling curves aren't just academic research. They're driving real product impact at scale for some of the biggest consumer businesses in the world." "Here's a couple of examples I have from Meta's recent earnings reports. Instagram Reels had a strong quarter, 30% year on year watch time." "And the optimizations we made to improve the quality of recommendations included simplifying our ranking architecture to enable efficient model scaling and longer interaction histories to identify a person's interests." "We doubled the length of user interaction sequences used for training Instagram and increased the richness of each user interaction." "So these are direct parallels to the power law scaling curves for LLMs." "And I want to introduce this idea of a flywheel of tokens in engagement out, which is what's powering all of these recs models scaling." "You train a model, you then run inference on it, which is the tokens in, that recommendation model results in better content recommendations, it drives consumer engagement, daily active users' time spent, it translates to monetization and ads or subscription, which pays for the next model training run." "And so every step on the scaling curve is one loop around this flywheel, and a lot of consumer apps are spinning this core flywheel at the heart of their business. So we have a long way to scale these recommender systems." _______ For the full breakdown of the lecture on Meta's ads recommendation system:
1:29

$META Devansh Tandon reveals the tokens-in, engagement-out flywheel behind Meta's recommendation system, where better models lift Reels watch time 30% and the monetization pays for the next training run "These scaling curves aren't just academic research. They're driving real product impact at scale for some of the biggest consumer businesses in the world." "Here's a couple of examples I have from Meta's recent earnings reports. Instagram Reels had a strong quarter, 30% year on year watch time." "And the optimizations we made to improve the quality of recommendations included simplifying our ranking architecture to enable efficient model scaling and longer interaction histories to identify a person's interests." "We doubled the length of user interaction sequences used for training Instagram and increased the richness of each user interaction." "So these are direct parallels to the power law scaling curves for LLMs." "And I want to introduce this idea of a flywheel of tokens in engagement out, which is what's powering all of these recs models scaling." "You train a model, you then run inference on it, which is the tokens in, that recommendation model results in better content recommendations, it drives consumer engagement, daily active users' time spent, it translates to monetization and ads or subscription, which pays for the next model training run." "And so every step on the scaling curve is one loop around this flywheel, and a lot of consumer apps are spinning this core flywheel at the heart of their business. So we have a long way to scale these recommender systems." _______ For the full breakdown of the lecture on Meta's ads recommendation system:

Fireside Alpha

203,368 Aufrufe • vor 9 Tagen

you numbered the steps so it could not get lost it does not get lost that list was written for a model that wandered, and this one plans better than the list does, so every number you added is a place where it is no longer allowed, to be smarter than you state the goal, the constraints, and how you will know it worked keep the numbers only where exactly one sequence is safe, which is deletes, auth and compliance the procedure felt like rigour it is a cage built to the dimensions of a model that is not in the room
1:21

you numbered the steps so it could not get lost it does not get lost that list was written for a model that wandered, and this one plans better than the list does, so every number you added is a place where it is no longer allowed, to be smarter than you state the goal, the constraints, and how you will know it worked keep the numbers only where exactly one sequence is safe, which is deletes, auth and compliance the procedure felt like rigour it is a cage built to the dimensions of a model that is not in the room

Lagosaur

14,857 Aufrufe • vor 1 Monat

I Built a 37.0 Profit Factor Bot by Cracking Every TradingView Source Code tradingview is a gold mine hiding in plain sight and i just found the master key to unlock every single secret hidden within its community scripts. most traders spend their entire lives staring at candles and hoping for a miracle while the actual alpha is buried in the open source code that nobody bothers to look at. i used to be that guy who sat there getting liquidated at three in the morning because i thought i could outplay the market with my gut feeling and some drawings on a screen. it turns out that the game is completely rigged against you if you are trading manually but there is a specific way to flip the script. i am going to show you how to stop guessing and start knowing exactly what works across every possible market condition before you ever risk a single dollar. i spent years losing money and thousands on developers because i thought i was not smart enough to code the systems myself but i was wrong. the first step to cracking the market is realizing that every indicator on the super charts has a source code section that is completely open to the public. you can literally scroll through the community scripts and pull the exact logic for thousands of different strategies that people claim are the holy grail of trading. but the secret is not just having the code because most of these indicators are actually garbage that will blow your account up in a week. this is where the real loop opens because you need a way to test these ideas across twenty five different data sets in seconds rather than months. i use a custom setup with ai agents specifically a sub agent i call the backtest architect to handle the heavy lifting of turning pine script into python code. the goal is to create a factory where you can feed in a raw indicator and get back a full report on its expectancy and profit factor without lifting a finger. most people find one strategy and marry it for life but a real data dog knows that you have to iterate to success or you will get left behind. i am running eighty one different backtests right now because i know that ninety percent of what i find will be trash but that remaining ten percent is where the wealth is made. the backtest architect knows exactly how to structure the folders and data paths so that we are testing everything from the base indicator to complex versions with filters. you might think that popular tools like fibonacci or order blocks are the way to go because everyone on social media talks about them like they are law. but when i actually ran the numbers through the machine the results were embarrassing and most of those strategies just resulted in negative expectancy. it is a dangerous trap to follow the crowd into a trade just because some guru said a certain level was important when the data shows it is a coin flip at best. the dynamic swing indicator was one of the few that actually held its weight during the recent massive testing sessions we ran. it was pulling in profit factors of over thirty seven with annualized returns that look too good to be true until you see the trade list. we combined it with filters like the adx and the money flow index to see if we could refine the signals and the results were absolutely staggering. when you have a system that can run through forty data sets while you are drinking tea you realize that manual trading is a form of self harm. i realized this after spending hundreds of thousands on apps and devs only to find out that i could just learn to build these bots myself live on the internet. the speed of iteration is the only thing that matters in this game because the faster you can fail the faster you can find the one strategy that actually prints. one of the biggest hurdles i faced was thinking that i needed to be a math genius or a senior engineer to automate my trading systems. the truth is that code is the great equalizer because it allows a regular person to compete with massive hedge funds by using the same logic and speed. i decided to learn everything in public because i wanted people to see the process of losing money with liquidations and then finally finding a path to automation. the reality of the market is that it moves in cycles and what worked yesterday will almost certainly fail tomorrow unless you are constantly testing. that is why i built the agents to automatically look through the results folder and rank the top performers based on a composite score. it takes all the emotion out of the process because i am no longer looking for a reason to enter a trade i am just looking at a csv file that tells me the truth. if you are still drawing lines on a chart and hoping for the best you are basically playing a game of chance against a high speed casino. the transition from a manual trader to a systems builder is the single most important pivot you will ever make in your life. it is not about being right or wrong it is about having a positive expectancy that has been proven across thousands of trades and multiple years of history. i had to fix a few errors in the short selling logic where the agents were getting confused between maximum and minimum values for take profit levels. these tiny bugs are the difference between a winning system and a blown account so you have to be willing to dive into the code and refine the machine. but once the system is tuned and the sub agents are running it becomes a beautiful workflow that functions entirely without your input. we are currently moving through the editors picks and the trending indicators one by one because i want to have a database of every single strategy on the platform. being a data dog means you never stop searching for that edge and you never settle for a strategy that just looks okay on a single chart. you have to demand excellence from your code because the market will not give you a single inch of mercy if you are lazy with your research. the ultimate goal is to have fully automated systems trading for you so you can focus on scaling rather than staring at a screen for ten hours a day. i am already up to over eighty backtests in this single session and i plan on hitting hundreds more by the end of the week. once you realize that you can crack the code of any indicator you see on the internet you will never look at a chart the same way again. this is the power of using agents to bridge the gap between a raw idea and a finished trading bot that actually works in the real world. i am done with getting liquidated and i am done with the stress of over trading because the code handles everything with cold precision. the path to success is paved with data and if you are not willing to automate your process you are just waiting for your next liquidation to happen
49:49

I Built a 37.0 Profit Factor Bot by Cracking Every TradingView Source Code tradingview is a gold mine hiding in plain sight and i just found the master key to unlock every single secret hidden within its community scripts. most traders spend their entire lives staring at candles and hoping for a miracle while the actual alpha is buried in the open source code that nobody bothers to look at. i used to be that guy who sat there getting liquidated at three in the morning because i thought i could outplay the market with my gut feeling and some drawings on a screen. it turns out that the game is completely rigged against you if you are trading manually but there is a specific way to flip the script. i am going to show you how to stop guessing and start knowing exactly what works across every possible market condition before you ever risk a single dollar. i spent years losing money and thousands on developers because i thought i was not smart enough to code the systems myself but i was wrong. the first step to cracking the market is realizing that every indicator on the super charts has a source code section that is completely open to the public. you can literally scroll through the community scripts and pull the exact logic for thousands of different strategies that people claim are the holy grail of trading. but the secret is not just having the code because most of these indicators are actually garbage that will blow your account up in a week. this is where the real loop opens because you need a way to test these ideas across twenty five different data sets in seconds rather than months. i use a custom setup with ai agents specifically a sub agent i call the backtest architect to handle the heavy lifting of turning pine script into python code. the goal is to create a factory where you can feed in a raw indicator and get back a full report on its expectancy and profit factor without lifting a finger. most people find one strategy and marry it for life but a real data dog knows that you have to iterate to success or you will get left behind. i am running eighty one different backtests right now because i know that ninety percent of what i find will be trash but that remaining ten percent is where the wealth is made. the backtest architect knows exactly how to structure the folders and data paths so that we are testing everything from the base indicator to complex versions with filters. you might think that popular tools like fibonacci or order blocks are the way to go because everyone on social media talks about them like they are law. but when i actually ran the numbers through the machine the results were embarrassing and most of those strategies just resulted in negative expectancy. it is a dangerous trap to follow the crowd into a trade just because some guru said a certain level was important when the data shows it is a coin flip at best. the dynamic swing indicator was one of the few that actually held its weight during the recent massive testing sessions we ran. it was pulling in profit factors of over thirty seven with annualized returns that look too good to be true until you see the trade list. we combined it with filters like the adx and the money flow index to see if we could refine the signals and the results were absolutely staggering. when you have a system that can run through forty data sets while you are drinking tea you realize that manual trading is a form of self harm. i realized this after spending hundreds of thousands on apps and devs only to find out that i could just learn to build these bots myself live on the internet. the speed of iteration is the only thing that matters in this game because the faster you can fail the faster you can find the one strategy that actually prints. one of the biggest hurdles i faced was thinking that i needed to be a math genius or a senior engineer to automate my trading systems. the truth is that code is the great equalizer because it allows a regular person to compete with massive hedge funds by using the same logic and speed. i decided to learn everything in public because i wanted people to see the process of losing money with liquidations and then finally finding a path to automation. the reality of the market is that it moves in cycles and what worked yesterday will almost certainly fail tomorrow unless you are constantly testing. that is why i built the agents to automatically look through the results folder and rank the top performers based on a composite score. it takes all the emotion out of the process because i am no longer looking for a reason to enter a trade i am just looking at a csv file that tells me the truth. if you are still drawing lines on a chart and hoping for the best you are basically playing a game of chance against a high speed casino. the transition from a manual trader to a systems builder is the single most important pivot you will ever make in your life. it is not about being right or wrong it is about having a positive expectancy that has been proven across thousands of trades and multiple years of history. i had to fix a few errors in the short selling logic where the agents were getting confused between maximum and minimum values for take profit levels. these tiny bugs are the difference between a winning system and a blown account so you have to be willing to dive into the code and refine the machine. but once the system is tuned and the sub agents are running it becomes a beautiful workflow that functions entirely without your input. we are currently moving through the editors picks and the trending indicators one by one because i want to have a database of every single strategy on the platform. being a data dog means you never stop searching for that edge and you never settle for a strategy that just looks okay on a single chart. you have to demand excellence from your code because the market will not give you a single inch of mercy if you are lazy with your research. the ultimate goal is to have fully automated systems trading for you so you can focus on scaling rather than staring at a screen for ten hours a day. i am already up to over eighty backtests in this single session and i plan on hitting hundreds more by the end of the week. once you realize that you can crack the code of any indicator you see on the internet you will never look at a chart the same way again. this is the power of using agents to bridge the gap between a raw idea and a finished trading bot that actually works in the real world. i am done with getting liquidated and i am done with the stress of over trading because the code handles everything with cold precision. the path to success is paved with data and if you are not willing to automate your process you are just waiting for your next liquidation to happen

Moon Dev

26,242 Aufrufe • vor 7 Monaten

Now that I am home and have access to my files I decided to do a quick test with one of my Vtubing avatars. It works way better with my larger iPad Pro (less crashing/more memory and more screen space) compared to the mini so I did want to bring that up. Importing the file over as GLB was more stable than just OBJ plus it kept the color info from the previous texture. I texture all my avatars on substance painter but have been looking at an alternative when I am out and about that is not on the computer and this actually hits all the right "wants". Adding a quick video of the way the app works for me. I like that it has layers, I can alter my brushes and even add stabilization when I am drawing (which I use that extensively on procreate so that was a huge plus). The stamp tools will come in handy as well but did not show it on this video. The file itself is imported as "one mesh" but each part is treated as their own separate piece which I show in the video. I do the same thing on substance painter making it really easy for me to texture. The app then exports the texture out for each object which is the same way I do so on substance. Overall I am extremely impressed with the work Sparseal has done on this application and see how useful this will be for my current work flow of texturing. I for one love the ability to be "portable" which is a big reason I sculpt so much with Nomad Sculpt on the iPad. Having the freedom to do your work away from a desk and if you feel like doing it outside is probable why I yearn for iPad apps so much like so. Give this app a look, it is free to try on the App Store (It is $19 to be able to export, but a one time buy). It is called "Wafer" for the iPad. I already use CozyBlanket from the same creator to do re topology so I expected this level of fantastic with this current app.
2:44

Now that I am home and have access to my files I decided to do a quick test with one of my Vtubing avatars. It works way better with my larger iPad Pro (less crashing/more memory and more screen space) compared to the mini so I did want to bring that up. Importing the file over as GLB was more stable than just OBJ plus it kept the color info from the previous texture. I texture all my avatars on substance painter but have been looking at an alternative when I am out and about that is not on the computer and this actually hits all the right "wants". Adding a quick video of the way the app works for me. I like that it has layers, I can alter my brushes and even add stabilization when I am drawing (which I use that extensively on procreate so that was a huge plus). The stamp tools will come in handy as well but did not show it on this video. The file itself is imported as "one mesh" but each part is treated as their own separate piece which I show in the video. I do the same thing on substance painter making it really easy for me to texture. The app then exports the texture out for each object which is the same way I do so on substance. Overall I am extremely impressed with the work Sparseal has done on this application and see how useful this will be for my current work flow of texturing. I for one love the ability to be "portable" which is a big reason I sculpt so much with Nomad Sculpt on the iPad. Having the freedom to do your work away from a desk and if you feel like doing it outside is probable why I yearn for iPad apps so much like so. Give this app a look, it is free to try on the App Store (It is $19 to be able to export, but a one time buy). It is called "Wafer" for the iPad. I already use CozyBlanket from the same creator to do re topology so I expected this level of fantastic with this current app.

Val / LatinVixen ➡️ Megaplex

17,469 Aufrufe • vor 7 Monaten

I stood on the steps of the Supreme Court Monday . Donald Trump has done real things for MAHA. I believe that. But when the Department of Justice shows up to defend Bayer and Monsanto against the American people, against the health of our children, I have to say: you got this one wrong. Liability protection for corporations that poison people is not a conservative value. It is not a Republican value. It is not a Democratic value. It is not an American value. It is the opposite of a free market. It is the government putting its thumb on the scale for corporations that are losing in court because their products are causing cancer. Every child in this country deserves to be healthy. That is not a political statement. That is the only statement that matters. So in the words of the President himself: we are going to fight, fight.
0:43

I stood on the steps of the Supreme Court Monday . Donald Trump has done real things for MAHA. I believe that. But when the Department of Justice shows up to defend Bayer and Monsanto against the American people, against the health of our children, I have to say: you got this one wrong. Liability protection for corporations that poison people is not a conservative value. It is not a Republican value. It is not a Democratic value. It is not an American value. It is the opposite of a free market. It is the government putting its thumb on the scale for corporations that are losing in court because their products are causing cancer. Every child in this country deserves to be healthy. That is not a political statement. That is the only statement that matters. So in the words of the President himself: we are going to fight, fight.

Del Bigtree

147,561 Aufrufe • vor 5 Monaten

Most people still aren't using AI. (I know, we're in a bubble on X.) But for the majority that are, they're still in chat mode. And they're only using about 5-10% of what's actually there. In this video, I teach you how to use the other 90%. To be honest, I was hating on chat for a while. Then I took the time to really learn it. And in the process, I found that chat mode has 2 features that are world class and not available in the other modes. I break down what those are, how to use them, and the rest of the features you're probably sleeping on. This video is for you if: → You're a beginner looking to do more with AI → You're already in chat / Cowork / Claude Code and want to learn best practices, token efficiency, and which chat features are genuinely GOATED → You have colleagues who need to be doing more with AI but don't know where to start That last one is the real reason I made this. This is the video you send to your team. I'm doing the same with my network right now. Uncle J, Freddie, Genny, this is coming your way. Hope it helps (if so, show some 💙)
42:20

Most people still aren't using AI. (I know, we're in a bubble on X.) But for the majority that are, they're still in chat mode. And they're only using about 5-10% of what's actually there. In this video, I teach you how to use the other 90%. To be honest, I was hating on chat for a while. Then I took the time to really learn it. And in the process, I found that chat mode has 2 features that are world class and not available in the other modes. I break down what those are, how to use them, and the rest of the features you're probably sleeping on. This video is for you if: → You're a beginner looking to do more with AI → You're already in chat / Cowork / Claude Code and want to learn best practices, token efficiency, and which chat features are genuinely GOATED → You have colleagues who need to be doing more with AI but don't know where to start That last one is the real reason I made this. This is the video you send to your team. I'm doing the same with my network right now. Uncle J, Freddie, Genny, this is coming your way. Hope it helps (if so, show some 💙)

JJ Englert

30,447 Aufrufe • vor 4 Monaten

The way Carlos was so invested on the relationship topic is cracking me up lmao. “You need to be chased. Men are chasers. We need to go after it.” “But if you give him 700 hints and still didn't go for it...Don't worry. You're not going to marry this guy. And he's not the man of your life.” “You're P14 (on the list) because you believe you're P14. Who says you're P14?… You might not be P14. You might be the guy to the girl.” “And women love a self-confident man.” “I got a bit emotional there.”
4:32

The way Carlos was so invested on the relationship topic is cracking me up lmao. “You need to be chased. Men are chasers. We need to go after it.” “But if you give him 700 hints and still didn't go for it...Don't worry. You're not going to marry this guy. And he's not the man of your life.” “You're P14 (on the list) because you believe you're P14. Who says you're P14?… You might not be P14. You might be the guy to the girl.” “And women love a self-confident man.” “I got a bit emotional there.”

WIO🦄

466,363 Aufrufe • vor 6 Monaten

hockeystick moments are the biggest opportunity of your career. It's exciting and kinda scary. Everything changes! I wrote Scaling Fast: Software Engineering Through the Hockeystick as your guide. 16 years of startup experience condensed into 240 pages Scaling Fast is based on startup war stories, academic research papers, talking to my mentors, and reading industry insights. It shows you what it takes to survive and thrive through the hockeystick. You'll learn about scaling teams and scaling code, how they influence each other, and why none of it matters if the business is bad. Scaling Fast: Software Engineering Through the Hockeystick is organized in 3 sections: - Scaling the Business - Scaling the Team - Scaling the Tech The business part, that's to help you evaluate the companies you join, this isn't a business book. The team part, that's key to shaping your everyday. We talk about delegating decisions, empowering engineers, working smooth instead of fast, finishing things all the way to done, good code review culture, and shipping incrementally without risky big bang releases. The tech part, that's my favorite. We talk about good abstractions, architectural complexity, observing your systems break, making steady improvements to your code without huge refactoring sprints, why tests don't solve everything, what's even worth testing, how your team structure impacts what you can do with the code, and why solving today's problem is more important than building for an imagined future. None of it is about numerical scaling [name|]. That's easy in 2025. Computers are fast. The challenge is building complex systems that don't fit in any one person's brain without breaking the business. oftware engineering when your whole company changes every 6 months is the fun part of this gig. And that's what Scaling Fast is about. 👉
3:35

hockeystick moments are the biggest opportunity of your career. It's exciting and kinda scary. Everything changes! I wrote Scaling Fast: Software Engineering Through the Hockeystick as your guide. 16 years of startup experience condensed into 240 pages Scaling Fast is based on startup war stories, academic research papers, talking to my mentors, and reading industry insights. It shows you what it takes to survive and thrive through the hockeystick. You'll learn about scaling teams and scaling code, how they influence each other, and why none of it matters if the business is bad. Scaling Fast: Software Engineering Through the Hockeystick is organized in 3 sections: - Scaling the Business - Scaling the Team - Scaling the Tech The business part, that's to help you evaluate the companies you join, this isn't a business book. The team part, that's key to shaping your everyday. We talk about delegating decisions, empowering engineers, working smooth instead of fast, finishing things all the way to done, good code review culture, and shipping incrementally without risky big bang releases. The tech part, that's my favorite. We talk about good abstractions, architectural complexity, observing your systems break, making steady improvements to your code without huge refactoring sprints, why tests don't solve everything, what's even worth testing, how your team structure impacts what you can do with the code, and why solving today's problem is more important than building for an imagined future. None of it is about numerical scaling [name|]. That's easy in 2025. Computers are fast. The challenge is building complex systems that don't fit in any one person's brain without breaking the business. oftware engineering when your whole company changes every 6 months is the fun part of this gig. And that's what Scaling Fast is about. 👉

Swizec Teller

59,335 Aufrufe • vor 10 Monaten

DON'T SHORT $BTC YET The channel is broken and $59k is gone But the next leg down doesn't start from here There is a FVG at $68k that needs to be filled first! Last time this happened was before the drop from $82k Price climbed into the FVG, filled it, then collapsed to where we are now The script is identical - just one level lower So, here is my read: Touch FVG ($67-68k), then the final leg to bottom zone ($47k) I called the $BTC crash from $126k before it happened - publicly, on this page This is my next major call - and I'm putting the same conviction behind it Follow now to not miss the update - turn on notifications to see it first
0:34

DON'T SHORT $BTC YET The channel is broken and $59k is gone But the next leg down doesn't start from here There is a FVG at $68k that needs to be filled first! Last time this happened was before the drop from $82k Price climbed into the FVG, filled it, then collapsed to where we are now The script is identical - just one level lower So, here is my read: Touch FVG ($67-68k), then the final leg to bottom zone ($47k) I called the $BTC crash from $126k before it happened - publicly, on this page This is my next major call - and I'm putting the same conviction behind it Follow now to not miss the update - turn on notifications to see it first

bee🐝

95,699 Aufrufe • vor 4 Monaten

*** 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,259 Aufrufe • vor 10 Monaten