I always found it a bit unfair that the clock would continue while the game was checking your answer. What are we supposed to do? Solve the next problem before it's even on screen???
There are definitely improvements that can be made. It shouldn't take multiple seconds for an algorithm to find these solutions, and I'm definitely concerned that your solution is affected by "similar" images or performance is so drastically affected by the images being in colour versus greyscale. This is cool but a video optimising these and going into detail on algorithms would be much more interesting.
it's python, it's just slow, he probably used pyautogui which is not the fastest in my experience but I think it's not bad at all how he implemented it
Great video, personally I'd love to see the explanations for how you fixed each problem within the code. You do a great job of identifying what the problems are, but then suddenly they're just fixed
Does Pathfinder really need a whole-ass computer vision solution? The vertical lines and horizontal connections are in the same place every time, and they're recognizable because of black pixels. Then to find the horizontal lines, you just look between the vertical lines for black pixels. Keep your x position between 2 lanes and look downwards and where you see an RGB(0,0,0) that's either a skull or a horizontal line. You distinguish between them by continuing to look downwards; if you see an RGB(255,255,255) it's a skull. You stay on the skull until you see a pixel that's neither black nor white. Once you know how many vertical lines there are, you know exactly where the animals might be. Like at a 3-line puzzle, you know the animals' x-coordinates are gonna be at a, b, and c (they have the same y coordinate every time). If you see a gray pixel at a+10,y+30 it's a koala. If you see a brown pixel at a+14, y+20 it's a bear. etc.
I'd have loved to see how far you can go on hard mode. It feels like 1000g are just in reach (if that's even possible). And from this goal onwards, you could show, how you improve the existing algorithm, showing the areas where it performs too slow. Still a cool video though :)
for matchmaker you could instead go through each image in the grid and store it's position in a hash table and when there's already something in the hash table you click on the current position and the position in the hash table at that index
I always found it a bit unfair that the clock would continue while the game was checking your answer. What are we supposed to do? Solve the next problem before it's even on screen???
I love seeing people destroy the point system of games.
Awesome video. I’d love to see Rythm Paradise if that’s possible. It drove me nuts as a child
There are definitely improvements that can be made. It shouldn't take multiple seconds for an algorithm to find these solutions, and I'm definitely concerned that your solution is affected by "similar" images or performance is so drastically affected by the images being in colour versus greyscale. This is cool but a video optimising these and going into detail on algorithms would be much more interesting.
it's python, it's just slow, he probably used pyautogui which is not the fastest in my experience but I think it's not bad at all how he implemented it
Fun video! I love watching people break games 😂 Can't wait to see what DS games you destroy next, haha
Great video, personally I'd love to see the explanations for how you fixed each problem within the code. You do a great job of identifying what the problems are, but then suddenly they're just fixed
Does Pathfinder really need a whole-ass computer vision solution? The vertical lines and horizontal connections are in the same place every time, and they're recognizable because of black pixels. Then to find the horizontal lines, you just look between the vertical lines for black pixels. Keep your x position between 2 lanes and look downwards and where you see an RGB(0,0,0) that's either a skull or a horizontal line. You distinguish between them by continuing to look downwards; if you see an RGB(255,255,255) it's a skull. You stay on the skull until you see a pixel that's neither black nor white.
Once you know how many vertical lines there are, you know exactly where the animals might be. Like at a 3-line puzzle, you know the animals' x-coordinates are gonna be at a, b, and c (they have the same y coordinate every time). If you see a gray pixel at a+10,y+30 it's a koala. If you see a brown pixel at a+14, y+20 it's a bear. etc.
Great video! Congratulations on reaching your sub goal :D
Hope you reach your sub goal!
W UA-cam recommendation
A tutorial on how you achieve this would be amazing for people who want to do their own image processing gaming!
Watching this is so nostalgic....
I'd have loved to see how far you can go on hard mode. It feels like 1000g are just in reach (if that's even possible). And from this goal onwards, you could show, how you improve the existing algorithm, showing the areas where it performs too slow. Still a cool video though :)
Honestly loved the video! But the repeated game sound effects were really annoying at points
for matchmaker you could instead go through each image in the grid and store it's position in a hash table and when there's already something in the hash table you click on the current position and the position in the hash table at that index
So cool man, keep it up
You are very underrated
Do Flash Focus next
Great stuff! But I can't help but notice mouth clicks and sounds all over the voice over.
Maybe adjust the mic position a little bit?
Bro for your work you deserve more subscrive4
i was cracked at this game
part 2 please
Let's goooo
Train the switch version and try to get a perfect score multitask AI
Hi there!
Damn, only 700 subs, as underrated as my meme channel
HOW DO YOU NOT HAVE A BILLION SUBS
Wait this is DS
1 away from 1K
I am 999 sub
tetris please
its still very slow
pathfinder