SuperMario64 Technical Runtime Observer and Object Processor
This is a fork from SM64-TAS-ABC/STROOP designed to be faster, less memory intensive and more extensible. The feature set and code structure may differ severely from the baseline.
STROOP is a diagnostic tool for Super Mario 64 that displays and allows for simple editing of various game values and information. It can connect to a running emulator and update values in real time. Some core features include views of loaded/unloaded objects, Mario structure variables, camera + HUD values, an overhead map display, and many more.
This reworked version aims to reduce the memory load and improve the real-time performance of STROOP by reevaluating the underlying structure of what STROOP does and what I believe it is meant to be. By generalizing some of its core features and entirely refactoring the map tab, this version is able to handle complex TASing workloads even on relatively weak machines.
You can even create sick ghost comparisons like this one with relative ease.
If you wish to stay connected with the most recent developments, I recommend that you build STROOP yourself as described under the Building section.
You can download (somewhat) recent binaries of the Refactor here.
If this updated feature set doesn't suit your needs, you can of course still get the releases from the original main branch.
As of the current build, STROOP has the following system requirements:
Requirements:
OpenTK is a prerequisite for building STROOP. This is easiest installed by using the NuGet package manager. STROOP can be easily built from the source code by opening up the solution file in Visual Studio and performing a build.
Yes, I fully expect you to know your way around git and Github for now. Clone the repository and double click the file and build and whatnot, it's not that difficult, but I'm aware that this is really incomplete right now. Also, this is just copy-pasted from the main repository, so don't blame me for being unspecific!
The repository is currently a hot mess and I shall update it to reflect a more structured approach to develop this version of STROOP in the coming weeks (as of 2024/08/18).
This refactor is ongoing and has diverged severely from the main branch in order to rework the structure of the project and implement new complex features, such as a fully redesigned (3D) map tab and the "ghost hack" used to display and compare runs within the game, as well as a work-in-progress brute-forcing Tab.
Features from the main branch are partially missing or work in different ways.
I hope to eventually get STROOP back onto a single track again, whether that be the main branch or this fork remains to be seen however. If you are capable and willing to take a heavy load, I'd invite you to discuss details with me on how that should happen on this barebones Discord server (will adjust as the needs arise).
I'd love to develop this version of STROOP into something that everyone involved with SM64 TASing and beyond can get great value from.
If you are a user of this STROOP version in any capacity, all of your suggestions for improvements will be appreciated (and ideally eventually implemented).
You may submit your feedback either via an issue or just speak your mind in this barebones Discord server.
Unfortunately, the source code is a hot mess right now and in dire need of a big cleanup. If you are crazy enough to dive into a big project with little to no documentation and are willing to improve this state, hit this repository with a pull request or an issue, be it documentation, new features, repairing broken ones (there are a lot), structural changes on the core or any other feature, or even the general direction this project should be going to.