Last updated: 10/11/2017 (v0.85b) - Added hardware acceleration, NFC patching, presets and more features! Yep, Snickerstream's back from the dead and is better than ever, bringing much better performance when streaming, lots of new features, bugfixes and more - all in a proper release this time instead of a mere PoC! (Also, the only reason I'm calling this a beta is because I still want to code in some more stuff, but I feel that this version is stable enough for everyday use!) If you don't know what Snickerstream is, here's a quote from the readme: Warning: Spoilers inside! Snickerstream is a completely new streaming client for NTR CFW. It aims to become a complete NTRViewer replacement with lots of extra features, including stuff such as better netcode, more screen layouts and less RAM usage. This is different than kit-kat/NitroStream as the formers still uses NTRViewer as its internal streaming client while Snickerstream has been completely written from scratch, making it the first real NTR streaming client alternative (also, if you've tried UWPStreamer or cuteNTR then you can say you've already tried Snickerstream in a way, as they used or have previously used part of its code internally!) Now, I hear you ask, why reinvent the wheel? Why make this if there's already something that does a very similiar thing? The reason is simple: I wanted to add some functions to NTRViewer, but some of the stuff I had in mind simply wouldn't be possible without altering its source code, and considering that NTRViewer wasn't properly updated in a while I took the opportunity of making this complete rewrite. So, you may ask, what does Snickerstream bring to the table compared to other alternatives? Well, here's list of improvements over NTRViewer: Warning: Spoilers inside! Real time screen scaling Pixel interpolation, which improves the image quality if the window has been scaled Two rendering libraries are supported: Direct2D (hardware accelerated if available) and GDI+ (software only) Way less resource usage under Direct2D Better netcode, it will automatically try to recover any lost frames if needed No DLL files needed, as it uses the Windows API to draw the GUI and GDI+ to draw the screens (keep in mind that kit-kat still uses DLLs, they just get extracted to a temporary directory) Native x64 version for better performance on x64 computers MANY more screen layouts, such borderless fullscreen and inverted layouts More options that will make Snickerstream work better on crappy computers or networks Better default settings that will make streaming smoother on most networks Built-in screenshot function (press S while streaming to create a screenshot) Built in NFC patching 7 different remoteplay presets are available Amutomatic remoteplay init, so you only need to click connect and Snickerstream will care about everything else And this is this version's full changelog, highlighting what has been added, modified and fixed! Snickerstream now supports Direct2D as its rendering library. Direct2D is hardware accelerated if your GPU supports it (if not, it uses to software mode). This means much less CPU usage, more constant RAM usage, less tearing and less dropped frames due to slow hardware, while still requiring no external DLLs and being Wine-friendly. Thanks to it, Snickerstream now works on many more hardware configurations and fullscreen works properly (it isn't an experimental feature anymore!) This means that, as both now support hardware acceleration, Snickerstream should perform at just as good as NTRViewer! In order to use Direct2D in hardware accelerated mode you need a GPU that supports at least Direct3D feature level 9 and has WDDM 1.1 drivers (read: any GPU made during or past 2006 should support it). The minimum requirements to use Direct2D rendering are Windows Vista SP2 (or later) and a graphics card with 128 MB of VRAM (256+ recommended). Although it's not recommended (because Direct2D is better than it in basically every way), it's possible to choose between Direct2D and GDI+ rendering. Pressing ENTER will now go back to the connection window. The Init Remoteplay and Connect buttons have been merged togheter. Snickerstream will automatically detect if Remoteplay has been started and send the appropriate packet if it isn't. In case you want to edit how much time it will wait before sending the packet, you can edit the WaitRemoteplayInit value in the INI (in milliseconds) NFC patching has been added for firmwares <=11.3 and >=11.4. Presets have been added. There are a total of 7 presets ranging from best quality to best performance. Packet errors will now be logged at loglevel 2, making this loglevel a bit more useful without producing giant logfiles. CPU model and frequency, GPU model and OS version are now logged at loglevel 3. (Bugfix) Key presses are only recieved if the GUI is active. (Bugfix) The GUI buttons get disabled when one of them gets clicked on to avoid function calling related bugs. If you want a quick tutorial, there's one included in the readme file. Also, if you have any problems, check the "troubleshooting" section of the readme and, if you don't resolve your issue this way, feel free to ask help in this thread! (Be sure to include a log with a loglevel of 3! You can change Loglevel to 3 in settings.ini and Snickerstream will start logging to log.txt when you open it.) There's also a list of FAQs now. And now the good stuff: download links! Releases / Source (GitHub) Happy streaming!