This seems suspiciously like a “save game” feature. Many games even auto-save which functions suspiciously like what they are describing as a “trigger point”.
While I am sure this is new and innovative, it still reminds me of when pyramid schemes mostly converted to MLM terminology. I had a friend that tried to convince me that MLM wasn’t a pyramid. So, I had him draw their sales hierarchy on a sheet of paper for me…
Yes. And this description gives me Alone in the Dark (2007) vibes: they explicitly stylized chapters and subchapters as episodes on dvd. Would they make something original to build a game around this idea? Would it be linear-only, for games like TLOU with limited choices? Or it’s just about patenting everything that’s not nailed down?
I think it would only stand out if you would be able to rewind and passively watch the in-engine recording of your whole previous gameplay (like in cybersports, or clip editors in some games), with an option to jump in at some sections. But it’s a little too much to implement smoothly, having no reason.
By pure chance, I am watching Edge of Tomorrow as we type. (It’s a Tom Cruise time loop movie, if you haven’t seen it.)
A game with a story line built around that concept would be very interesting, for sure. However, the old Sierra adventure games came to mind, specifically Space Quest and Leisure Suit Larry, where you just had to keep trying different things until you didn’t die. It was fun back in the day, but it got old really quick.
Implemention in a sports game is a cool idea, though.
yeah this can only work if implemented by the devs. The only reason this can be done for some older emulated games is that there is only a megabyte or two needed to capture the state of the entire system. Not several gigabytes.
I was under the assumption the collections that utilize this system do it by just saving the inputs and timestamps and simulate them as such rather than understanding the entire whole state. I’m not sure how it works with non-seeded elements
I do agree with you about the dev focus. It would be way more complex even though if feasible if you can simulate without it graphically but you I can’t imagine it just being a system similar to recording or achievements
that only really works with deterministic systems though. You could do that with a 6502 or simple systems because you could perfectly predict what the state of the system would be in just by replaying inputs. everything up to predicting all cache misses.
consider a badly written game on a modern console (remember that save states should work for any game) in which physics is tied to framerate. Follow the chain… framerate depends on system speed… which, indirectly depends on the ambient temperature (a console running in a hot climate would throttle earlier than one running in an air conditioned cool room). And because modern systems execute more than one process, it also depends on what else is running (were you downloading a game in the background, slowing down the game ever so slightly?) or unpredictable things such as interrupts on certain system timers. And the list goes on and on. Even if the game didn’t have physics depending on framerate, differing deltaTime on each frame means different floating point rounding errors happen, which could accumulate over time.
So in this case, replaying inputs does not get you the exact state. you were in. there are just too many variables.
No game should save gigabytes. Even megabytes can be too much. If the game is very linear a save could mean a single number. Even if it has character cosmetic customization and a convoluted plot with lots of choices it’s still usually in the kilobyte range. The larger saves (overall) would be sports games like rally racing where the game needs to be able to provide a thorough replay of every race.
system state is not the same as a save file. System state is the cpu registers, the process’ entire memory space (because you don’t know what the game might do at any point) gpu context, etc.
edit: example: the save file for older games was measured in bytes. System state is much larger han that. It contains everything not just what the developer decided to allow you to save.
Many emulators have been doing something like this for quite a while. Its called a “saved state.” In some cases, a saved state can introduce bugs into the game play and mess up your progression, but that is just in emulation.
Hell, Nintendo has this on their Switch online emulator. Are they going to have to remove that from NSO because Sony patented it?
They did, but that isn’t really relevant to the discussion. The Wii Virtual Console is discontinued and technically doesn’t have live support from Nintendo like the Switch and NSO currently. If Sony somehow did get a patent for save states in games, I don’t think it would retroactively apply to the Wii.
And? Sony has patented their way of doing it, big deal if it’s been done elsewhere. It isn’t something PlayStation games can do easily so they’re building a solution.
This article isn’t saying this is some groundbreaking discovery of technology or something, nor is it a press release/announcement.
The points you make are the exact reason why people are looking at this patent in a funny way.
What they are describing in the patent is basically a save game or checkpoints for subchapters in a game. This is not innovative or new and that is the problem. You can’t patent something that can already be considered public domain or common practice.
It’s very much a big deal if this has been done somewhere else. The patent is obscure enough to look unique but it common enough to start years long legal battles.
On reading the patent, it is specifically referencing streamed game checkpoints. That is, believe it or not, very different than save games stored locally. Still, I find it hard to believe that NVidia, Google or Nintendo wouldn’t have a patent for that already. If not, it may still be considered common use.
The devil is in the details for this issue. Is it really a new thing or is it “reverse” patent trolling?
I just had a revolutionary idea: what if every time you reach a new point in a game, it showed you a certain sequence of icons related to that point in the game. Then, if you ever want to play that part of the game again you can just insert that same sequence of icons into an option of the game and it’ll play from there.
Then people could also share the sequences they discover with their friends, allowing said friends to skip part of the game if they want to.
That’s how our games worked in the 80’s. Most of them used passwords. I remember one that used a tic-tac-toe looking thing where you entered a combination of dots to load your game. I think it may have been Mega Man. Zelda was the first one I remember that actually saved your game. There was a battery in the cartridge.
Another software patent that no one should respect because it does something that was done 30 years ago.
