MLB 15 The Show Screenshots (High Resolution)

[WaitTilNextYear]

Quote: Originally Posted by ShowTyme15

Yeah I'm just confused. I'm curious how it's going to work. What if the Tanaka I'm using was created and the SCEA version wasn't the base for him?

[A_Quiet_Pro]

Quote: Originally Posted by WaitTilNextYear

They could program it to save over a given player's name but that would be really tricky for 2+ guys with the same name (Chris Young, ahem). I am sure that each SCEA player has a unique identifier so I am also not sure how the game would pick up CAP Tanaka and replace him with SCEA Tanaka. That I don't understand it doesn't mean it can't happen though.

I'm thinking each individual player has their own digital thumbprint in game, so the game knows it's them (even if they're traded or whatever)... I'd have to say that SCEA's engineers would code the game to have the game overwrite SCEA's face over the CG face for that particular digital thumbprint. (Once a player is created, it creates a digital thumbprint the game can read... it becomes part of the roster file and once the SCEA face is introduced, it becomes part of the created file). If that makes sense. (My programming skills are only VERY basic, and understanding of it only slightly better.)

[ShowTyme15]

Quote: Originally Posted by WaitTilNextYear

I edited my post.

[ShowTyme15]

Quote: Originally Posted by A_Quiet_Pro

I'm thinking each individual player has their own digital thumbprint in game, so the game knows it's them (even if they're traded or whatever)... I'd have to say that SCEA's engineers would code the game to have the game overwrite SCEA's face over the CG face for that particular digital thumbprint. (Once a player is created, it creates a digital thumbprint the game can read... it becomes part of the roster file and once the SCEA face is introduced, it becomes part of the created file). If that makes sense. (My programming skills are only VERY basic, and understanding of it only slightly better.)

That makes sense if it does work that way I guess.

[WaitTilNextYear]

Quote: Originally Posted by A_Quiet_Pro

I'm thinking each individual player has their own digital thumbprint in game, so the game knows it's them (even if they're traded or whatever)... I'd have to say that SCEA's engineers would code the game to have the game overwrite SCEA's face over the CG face for that particular digital thumbprint. (Once a player is created, it creates a digital thumbprint the game can read... it becomes part of the roster file and once the SCEA face is introduced, it becomes part of the created file). If that makes sense. (My programming skills are only VERY basic, and understanding of it only slightly better.)

Sounds simple enough, but the problem is the digital thumbprint. If you are bored one day and create 17 Masahiro Tanaka CAPs, then transfer your save to '15, how does the game know which one of the 17 Tanakas to replace? It might not recognize the thumbprint of a CAP for that reason.

[A_Quiet_Pro]

I think what we need is to have Russell or a roster dev through Russell explain how that happens and lay down the law.

[WaitTilNextYear]

Quote: Originally Posted by A_Quiet_Pro

I think what we need is to have Russell or a roster dev through Russell explain how that happens and lay down the law.

This sounds like a job for....

Spoiler

B Ma

[A_Quiet_Pro]

Quote: Originally Posted by WaitTilNextYear

Sounds simple enough, but the problem is the digital thumbprint. If you are bored one day and create 17 Masahiro Tanaka CAPs, then transfer your save to '15, how does the game know which one of the 17 Tanakas to replace? It might not recognize the thumbprint of a CAP for that reason.

I understand your problem, but to quote the Rock.. Why in the Blue Hell would you create 17 different entries of the same dude? LOL (However.... I Imagine the game would create them if you did with it's entry name it uses for the thumbprint then like name.1, name.2 or name_1, name _2. And the game would probably overwrite the original file automatically. (The files with the .1 or _1 wouldn't be touched)