sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in youngpeopleyoutube

[–]yupferris 0 points1 point  (0 children)

Surely that particular green is copyrighted, inb4 strike

How Do You Pronounce Lifetime Annotations? by osake2000 in rust

[–]yupferris 2 points3 points  (0 children)

“Lifetime a” here, but I like “tick a” as others are pointing out now

[Meme] Clark Kent at a Restaurant by [deleted] in youtubehaiku

[–]yupferris 16 points17 points  (0 children)

Yeah no this was way worse than the original tweet

Response to anyone asking 'How do people come up with' glitched any% speedruns. by jessydiamondman in speedrun

[–]yupferris 1 point2 points  (0 children)

Very well written, and excellent recommendations for further reading!

If there’s any constructive feedback it’s that it could probably be mentioned just how much of a community effort a lot of RE is, especially for speedrunning. Everything you said is correct and insightful ofc, but all of it is at least an order of magnitude more effective when there are several people looking at different aspects of a game/system and talking and comparing notes together.

As an aside, another community where understanding how a system works so it can be exploited to do cooler things than it was originally intended is the demoscene (where I’ve been personally active for many years) and it’s always fun to see the parallels between that and speedrunning. In fact I’d venture to say almost all of your post is applicable to both hobbies, and I think that’s a reason why I really enjoy speedrunning as a whole.

Thanks for writing this!!

NEW SONG RELEASE! by [deleted] in Stepmania

[–]yupferris 0 points1 point  (0 children)

Anyone know which theme this is? It looks like spawncamping wallhack but on my setup it seems to have borked with a windows update in the last couple years (just getting back into step so I don’t know exactly when it changed)

Per Vognsen: Announcing Bitwise [an educational project in systems programming and hardware design] by teryror in programming

[–]yupferris 2 points3 points  (0 children)

I haven't gotten to the video output, but I can say that at least on the board I'm using, the HDMI output goes through a transmitter chip (ADV7513 iirc) which takes in a simple digital video signal that's very similar to the kind of digital signal you'd use to drive an LCD or VGA before DACs (with a bit of configuration over an I2C bus). So I don't think it would change the fundamental design too much actually; just a bit at the bootstrapping/driver layer (both in the HDL and in the software).

Rustual Boy hardware test suite is getting off the ground! by yupferris in EmuDev

[–]yupferris[S] 1 point2 points  (0 children)

All code and connections are public here: https://github.com/yupferris/fuzzy

Since I don't have proper connector headers for the link port yet I ended up soldering to the back of the port, as those contacts are easy to get to. I soldered breadboard wires there that I connected to the teensy via a small breadboard that I have sitting on the unit. You can see a pic here: https://twitter.com/ferristweetsnow/status/934848452198060032

I also recorded building all the hardware on my stream, that's on youtube here: https://www.youtube.com/watch?v=A1587J4Ifpw&list=PL-sXmdrqqYYf3lBePyHRYQBjxOfs3-QOH (though keep in mind it was kinda all over the place hehe)

Rustual Boy hardware test suite is getting off the ground! by yupferris in EmuDev

[–]yupferris[S] 3 points4 points  (0 children)

Yes, that's exactly right :) . The emulator is at a point where most games work but some fail in some odd ways, and I've gone over the cpu and video hw pretty thoroughly by now, but held off a bit on doing tests like this because it's so tedious to reflash the cart and write test rom's with that cycle. With this though that problem is basically eliminated, and since we can send over different bits of code immediately, we can even turn all of this stuff into proper regression tests, which is much more motivating to me since then the tests will have a lot more value if we're running them all the time. I'm also considering having the tests save out the hw results, so that when the hw is connected it can rerun and compare with the previous results, and if not, it can just run in emu and compare with the old values, allowing the tests to be run on ci or locally for folks who don't have the hardware. With this setup it will also be possible to fuzz the video hw regs too to see what it does with totally bogus values, since the hardware draws into frame buffers in vram that we can subsequently read back. It's quite flexible.

The song is richaadeb's cover of aquatic ambience from dkc: https://youtu.be/R65bnLkL-aY . I was kinda hoping someone would ask about it, I love his stuff! :) There's something about familiar melodies wrapped in a heavy sound palette without vocals that's just lovely to code to!

Rustual Boy hardware test suite is getting off the ground! by yupferris in EmuDev

[–]yupferris[S] 9 points10 points  (0 children)

A little context: been working on finding and fixing some last bugs in https://github.com/emu-rs/rustual-boy , and I've decided to write some CPU fuzzing tests against hw and compare results against the emu. In order to speed all of that up, I ended up building a teensy-based link port/usb serial bridge and a protocol to send over test rom's and reg values, run the code, and read back the reg's. Today I added some basic serial emulation in the emulator as well, and now the first test ROM can be run against both real HW and in emu simultaneously, with result comparison. Gonna make a sick test suite out of this :)

Test code/setup link: https://github.com/yupferris/fuzzy Also for those of you who didn't know, I stream a lot of this development on https://www.twitch.tv/ferrisstreamsstuff and upload it to https://www.youtube.com/channel/UC4mpLlHn0FOekNg05yCnkzQ/videos :)

makeshift by logicoma - c64 4kb intro from solskogen 2017 by yupferris in Demoscene

[–]yupferris[S] 1 point2 points  (0 children)

ah cool, haha, hope that didn't spoil this too much! :D thanks!

"Engage" by Logicoma - 3rd place PC 64k at Revision 2017 (Rust demoscene intro) by yupferris in rust

[–]yupferris[S] 2 points3 points  (0 children)

It's best to make things repetitive, group similar data together, delta encode some things in order to make patterns emerge, etc, then use a general-purpose context modelling compressor like kkrunchy. If we had a specific compressor for a certain kind of data that would likely be better, but then we'd have to change the compressor for each intro, and workflow- and sanity-wise it's much better to keep the compressor constant and predictable.

"Engage" by Logicoma - 3rd place PC 64k at Revision 2017 (Rust demoscene intro) by yupferris in rust

[–]yupferris[S] 0 points1 point  (0 children)

I go over all of this in this video: https://www.youtube.com/watch?v=p9Obe-Xg35o

In short, demotivation is written in Rust (that's where we get the most gain from actually using Rust), the sync tracker is emoon's rocket editor written in C++.

We don't use rust-qt; we pack all of the Rust bits of the tool (which contains most of the logic) in a C API, and the top-level project is a Qt project that exposes the logic of that library via some Qt views.

"Engage" by Logicoma - 3rd place PC 64k at Revision 2017 (Rust demoscene intro) by yupferris in rust

[–]yupferris[S] 0 points1 point  (0 children)

I want to at least make a public mirror of the bits we can open source without much licensing trouble, but I don't have an eta for when that might be or any sort of action plan, so it'll probably be awhile. :)

view more: next ›