I couldn't exactly pinpoint the problem by the end of the night, but it was clearly not hardware-related.
Installed the drivers and ran the NistroInside program on my desktop, and
it ran perfectly.
The "garbled mess" was from my laptop, and after hours of troubleshooting, I couldn't quite figure out what the problem was. I even went as far as copying over the two driver files from my desktop to no avail.
Update Next Day:
It appears to be a Windows issue, or something that I've downloaded is creating the issue. Slapping a new SSD into my laptop with a fairly fresh Windows install, and the capture is a lot cleaner. Not perfect, unlike my Desktop, but far fewer error frames. I hope to pivot away from the NiseTroInside software.
Got
Lorenzooone's cc3dsfs program working after spending hours figuring out how to compile the .exe (Bing AI was about as helpful as it was unhelpful), as the release is old, and it works well on my desktop. I still have issues with my laptop, but that's less important.
If you don't want to compile,
automatic nightly builds are available.
I'll have the compiling instructions below for posterity.
Update Many Days Later:
After combing through every driver and process on my Laptop, the problem turned out to be in my Laptop's BIOS, where C-states were enabled. Disabling that fixed my issue.
There was also a similar issue on both my desktop and my laptop when using a webcam on the same USB hub. For my laptop, it was due to both devices being on an external unpowered USB hub. On my Desktop, it was due to having a device plugged into a certain USB port on my case, and the other one plugged into a certain USB port on my motherboard. It is assumed they share an internal hub or bandwidth.
========================================================
Compiling the cc3dsfs program.
For the sake of posterity, for the poor soul who wants to compile the .exe but sees the terminal as an empty magician's hat, I'll post exactly what I did.
This was done on a Windows 11 PC.
Install the 3 dependencies: CMake, Git, and G++.
CMake and Git are easy enough to get. Google/Bing, and they are the first result. For
CMake, you want the Binary distributions for Windows. For
Git, just the standalone installer. Install both.
G++ is much less intuitive since it is a part of
Visual Studio 2022. What you want is the Community version, which is a free download. When you install and open Visual Studio Community 2022, in the Workloads tab, under Desktop & Mobile, select and install "Desktop Development with C++".
Create a folder, or choose a spot on your desktop to work from.
I'll be making a folder on my desktop just to work from. Going to name it "cc3dsfs".
On the Window's search bar, search and open "Git CMD"
Set the root of where you are working from using the "cd" prefix. before the filepath. So, in example, since I made a file on my desktop, my filepath is "C:\Users\MYNAME\Desktop\cc3dsfs". Putting cd before that will look like:
cd C:\Users\MYNAME\Desktop\cc3dsfs
The command line should now have that file path. If you are unsure of the filepath, you can right-click the file path at the top of the file explorer and copy the filepath as text.
Clone the Github repository.
git clone https://github.com/Lorenzooone/cc3dsfs.git
Cloning the github repository puts everything in another cc3dsfs file, so you can either move the contents out of it or add another "cc3dsfs" to the file path.
cd C:\Users\MYNAME\Desktop\cc3dsfs\cc3dsfs
Build and compile.
Now the magic happens. The command string on the github page is two commands separated by a semicolon. I wasn't able to run them both at once, so I have to run them one at a time. Note that this can take quite a bit of time.
Start with the build:
cmake -B build -DCMAKE_BUILD_TYPE=Release
Once that is done, run the other half to compile:
cmake --build build --config Release
Profit
The .exe. will poop out in the cc3sdfs file (the second one). Enjoy.
