reddit: nico_is_not_a_god pokemon romhacks: Dio Vento

  • 0 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle
  • Native 4k output instead of a crappy upscaler or a RetroTink which costs more alone than this Analogue product. N64’s native composite is laggy and hideous on a flatscreen TV, you need something like this or a retrotink or a CRT to make the games look good. Even if the Analogue couldn’t play ROMs off an SD card (it can, if Analogue’s previous products are any indication), you could just stick a Summercart in it.

    I personally am a ride-or-die CRT player for my retro consoles, but big CRTs are getting rarer and living rooms less accommodating. And N64’s library has a ton of absolutely killer party games that are best experienced on a big TV with your friends, not a dark retro cave on a 20" CRT the way SNES RPGs are. If someone I knew wanted to go a “step past” emulation, I’d absolutely recommended this thing as the second shopping list priority. In order (imo):

    Real N64, Real CRT, Summercart/ED64X7 (most authentic, and also cheapest if and only if you can source a CRT that fits your needs)

    Analogue 3D, HDTV they already have

    Real N64, RetroTink, Summercart/ED64X7 (more expensive than option 2 even if they already have the console and summercart lol)

    Real N64, RetroTink or CRT, buying real copies of games at jacked-up collector prices



















  • On the flip side, I’ve been using FX file explorer for this for years with no issues, but my roommate on the latest iPhone (a year ago) encountered a pretty horrific oversight in the default Files app’s way to handle this (and no option to use third party apps).

    Whenever she tried to copy more than 2GB from the network drive to the phone via Files, the phone would completely lock up and freeze (and stop transferring, which I confirmed by looking at read operations on the home server). She had to hard reboot and copy the files over multiple operations instead of just queuing up 50GB of audiobooks once and letting it transfer in the background. It turns out the Files app handles network assets by loading them all into RAM and then writing them to the iPhone’s NAND, and if you try to perform an operation that takes more than the phone’s current available RAM it just does the Apple equivalent of a bluescreen.