• 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: July 22nd, 2023

help-circle


  • I have another answer: It’s because true innovation is hard.

    We have a ton of super-popular violent games to source ideas from for new games. We take an idea and modify it a little, and it’s fun.

    We don’t have nearly as many super-popular non-violent games to source from. They exist, but there just aren’t as many of them, and they’re generally pretty “cozy” instead of pumping the adrenaline. Sports/racing games are an exception, but “non-violent” still depends on the exact sport and implementation. Many of them aren’t non-violent.

    It’s the same reason that fantasy often still uses elves, trolls, and dwarves. They’re really easy to source from, and coming up with compelling new races that aren’t essentially the same as the tropes is hard.

    Indies are into innovation. AAAs are into money.





  • To expand upon that, I had something similar to the OP’s setup at one point, and I found things worked a lot better when the files could be moved on the same volume, rather than appearing as separate volumes (because they were mounted separately). I ended up re-engineering my whole setup for that and it’s much faster now.

    As for duplicates… I assume this is so you can continue seeding after the file has been moved? I can’t think of anything that would fit the bill for that off the top of my head. Ideally, I think you’d want QBT to just start serving from the new location instead, though I admit hard links does sound like a solution that could work.

    And after Googling, it seems like it already does hard links for torrents for this exact reason. I think if you just map /media (and drop the 2 maps you have after that) things will work like you want.






  • I could see it maybe being useful for certain large games that you only play occasionally, but…

    That’d mean redownloading right when you actually want to play, which is a pain. Also, in ability to tell it to archive or un-archive something manually makes that situation even worse.

    It feels like those “ram doublers” back in the day… Neat in theory, but just painful in reality. It puts a check mark on a sales pitch, but doesn’t actually help anyone.


  • If you’re only watching on 1 TV, I don’t think there’s any reason to keep them a separate 4k library. And if your server can handle transcoding easily, there’s still not much reason.

    If you have an often-used second (or third, etc) TV with lower resolution and your server doesn’t handle transcoding well, then it’s probably worth keeping them separate.

    I’ve also started to disagree with the guide about file size. I don’t think I can tell the difference, and I’m not trying to preserve media for the future. So long as the video has the features I want, I think just about any file size is fine.