• 0 Posts
  • 17 Comments
Joined 10 months ago
cake
Cake day: November 19th, 2023

help-circle


  • I actually have experience porting games and engines to consoles. If it runs on a development PC (likely Windows), they have the build system and platform layer implemented, which is the hardest part. Porting the content is also an important step, but really only for consoles, which usually have limited memory and power.

    Typically the only problem with “PC ports” today is when the game wasn’t designed around mouse/keyboard, or when the devs didn’t make an effort to optimize it on consumer specs (although nowadays console architecture isn’t too different from PCs so there are more optimizations that work across platforms). Another potential problem is when the game gets a lot of last minute hacks to fix bugs in order to ship on a console and those hacks don’t survive a platform transition, then the publisher just tells them to ship as is since there’s no certification process on PC. Basically, the problems are almost always logistical/business decisions due to a lazy/cheap publisher.

    None of that is going to apply to this game. Rockstar has always intended to ship and fully support PC from the beginning. They had the technology, the talent, the incentive, and the time to do it. The most realistic explanation (IMO) for the PC delay is that they’re trying to double-dip.




  • Sure, but GTA 6 is 100% already working on PC. Not just because they develop the game on PC, or because they’re building on top of the RDR2 engine (which is already ported to PC), but because they planned to support PC from the beginning, and that type of engine work usually gets ironed out early during development or in pre-production.

    I was just pointing out the flaw in your tire analogy though. TBH I’m not saying they should give free copies to people who bought it on other platforms. That’s unprecedented for giant publishers like this. But I am pissed that they’re delaying the PC version since you can be sure it’s a calculated plan to ensure PC gamers buy the game twice. They collected enough analytics and surveys to know that a significant amount of GTA5 PC gamers also own a next-gen console. It’s all very nefarious.


  • Unless it’s either PS5 or Xbox exclusive (not both), I don’t think that’s true. Sony and Microsoft wouldn’t collude to prevent launch on PC. That’s extremely illegal, even for companies that are masters of dodging antitrust laws.

    The most realistic explanation (IMO) is that Rockstar did their research and found that most PC players also own a console, and will very likely buy the game twice in the long run.

    Or if we’re being charitable, maybe the game needs more optimization work before it can run well on the Steam deck, and they want that working before launching on PC.





  • And since it’s GPL that any additions are compatible with the GPL, which the ad / tracking stuff they’re likely to add likely isn’t.

    That’s a good point, although I wonder if there are any ad SDKs that are GPL compatible? There’s no reason that couldn’t exist AFAIK.

    However, there’s also the much simpler scenario where they straight up replace the apps with something completely different. This company buys apps all the time, so I’m sure they have at least a few calendar, gallery, file browser, etc apps lying around that they can reuse.


  • I’m not a lawyer either, but the GPL doesn’t say anything about commercial use. Zipo can sell the code in the apps without having to ask permission from contributors. The only restriction is that they have to keep their modifications open source (which that Github response says).

    But the main point is that the Zipo people bought out the Google Play listing, giving them access to the millions of users who have those apps installed on their phones. They likely don’t give a shit about features/keeping the apps closed source. It’s just a purchase of the userbase, likely for shady reasons.

    This also means that forking the Simple Mobile repos isn’t even likely to accomplish much. Sure, it’ll put control of the repo in the hands of a more trusted party (which is significant), but since it’s open source anyways, it’d be easy to catch any attempts to sneak malware into the apps. And if all development effort moves to the fork, Zipo can still take that fork and redistribute it under the “Simple Mobile Tools” name.

    Ultimately, the fucked up thing here is that the original developer, Tibor Kaputa, sold out millions of users. Forking isn’t going fix that. Fuck him. The only thing that will fix this situation is if Google takes down their store listing, but that’s not going to happen. Hopefully F-droid does.