Support NeoGAF

[Sega Orphan]

I'm not sure if there are any game devs on here, but I was wondering just how much resources it takes to port a game from one system to another.
Say when Sony ported GOW to PC, they had GOW on a Sony exclusive game engine, and using Sony's own API, how much work was involved?
Are we talking like a dozen people working for three months, or are we talking 100 people working for 12 months?
I saw Sony buying the PC porting studios recently, and I was wondering if they would be able to do all the Sony porting work alone, or would they still need to use other companies to do it as well.

 

[MrFunSocks]

Consoles these days are basically just low-mid spec PCs, x86 and using hardware abstraction layers. Porting is basically as simple as it can ever be. If you make a game for the Series S/X you've basically made it for PC and the other console already, same with PS5.

 

[SlimeGooGoo]

.

 

[ReBurn]

Just change the target and recompile it. Then when that doesn't work you do it the hard way.

 

[kingfey]

God of war took 2 years to port it to pc. Small games takes less time to port it to pc.

 

[hemo memo]

Depends on the dev and the level of care they give.

 

[Sega Orphan]

God of war took 2 years to port it to pc. Small games takes less time to port it to pc.

But was it two years because it was a part time project, or because it's really involved?
Nixxes has around 60 employees and were bought by Sony to port their games to PC.
I wonder how many games a year a studio of that Size can port to PC.

 

[kingfey]

But was it two years because it was a part time project, or because it's really involved?
Nixxes has around 60 employees and were bought by Sony to port their games to PC.
I wonder how many games a year a studio of that Size can port to PC.

You actually need the original developers to port the game. Nixxes is great. but they still need SIE studios support to port those games. If you are have multiple projects, its hard to finish it fast.

 

[AllBizness]

Why cant porting games be as simple as burning a CD?

 

[Griffon]

Just put your PS5 disc in an Xbox and bam: instant port.

 

[Dream-Knife]

Xbox one and PS4 were moved to PC architecture to simplify ports (from pc to console). The reverse works easily enough.

Everything but the Switch (ARM) is made with x86 in mind.

 

[MrFunSocks]

You actually need the original developers to port the game. Nixxes is great. but they still need SIE studios support to port those games. If you are have multiple projects, its hard to finish it fast.

No you don’t, especially if you’ve got the source code.

 

[mhirano]

I just want proper ports of Kingdom Hearts 1.5 and 2.5 for the Switch (not shitty cloud versions).

 

[mhirano]

Just change the target and recompile it. Then when that doesn't work you do it the hard way.

It only works that way if you have an engine with multiple platform support.

 

[Kataploom]

Just change the target and recompile it. Then when that doesn't work you do it the hard way.

Yeah, basically Unity is like this, when something doesn't work, you target a fix for that specific platform if it works well in the other. Tho that's with modern public engines, those engine creators will have to do it the hard way anyway first to bring it to us the honey way

 

[RoadHazard]

You just check the "build for PS5" checkbox, optimization per platform isn't a thing that exists. At least that's what VFXVeteran told me.

 

[MrFunSocks]

You just check the "build for PS5" checkbox, optimization per platform isn't a thing that exists. At least that's what VFXVeteran told me.

He must work for FromSoft.

 

[Clintizzle]

You just rename the .psx file to a .exe or .xbx and make sure you run with administrator priviledges.

Easy $60.

 

[Stooky]

Consoles these days are basically just low-mid spec PCs, x86 and using hardware abstraction layers. Porting is basically as simple as it can ever be. If you make a game for the Series S/X you've basically made it for PC and the other console already, same with PS5.

lol hope you are joking.

 

[FloatingIslands]

It depends on a lot of factors like the nature of dealing with a legacy system, the design of the code, the tools that were used to develop the game, etc.

 

[kingfey]

No you don’t, especially if you’ve got the source code.

You still need the key people who are familiar with it.

 

[RoboFu]

Easier than in the past but still not simple.

Usually the biggest issue is if you use a third party lib that’s not on another platform. Like when you start up a WB games like Batman and see a ton of logos on screen like oodle, monotype, speed tree..etc. any platform you port to have to at least have versions of those as well.

Plus now we have lower level graphics apis like Vulkan and dx12 that’s a bit of pain for smaller devs who don’t have the resources to spend. Which is why Unreal and Unity are so great.

 

[MrFunSocks]

You still need the key people who are familiar with it.

If you’ve got the source code then no, you don’t.

 

[Sean Mirrsen]

The reason it takes a lot of effort to port a game right is because you first have to flip the ship upside down.

But also, it just differs greatly depending on too many things to count. Could be as easy as changing a setting and compiling code for another platform. Could be whatever magic it took to port No Man's Sky to the Switch.

 

[EverydayBeast]

*Porters show up and instantly reveals porting methods*

 

[Deft Beck]

I just want proper ports of Kingdom Hearts 1.5 and 2.5 for the Switch (not shitty cloud versions).

It's possible for everything except KH3. Square-Enix is just cheap and doesn't want to pay for cartridges.