Making something USING a PC is vastly different than making something FOR a PC. Do you think people made millions of mobile apps on their phones? No, they are written on the PC and compiled/cross-compiled on the PC using a special compiler or emulator or on the target device itself. The code being written does not automatically run on PC just because it was written on it.

Kind of like a boat is not being constructed on water, but can't function outside of it.

@Serg: Not trying to be that guy but... Larger ships do tend to be finished over water. The Titanic is a perfect example.

The parts for the ship were partially constructed inland then shipped to the departing docks. From there the ship was pieced together, the dry dock gets completely filled, and you have a floating boat.

Your overall point is very spot on though.

@ Serg,

You completely missed my point. Lets not muddy the waters with cell phone architecture...

You are echoing exactly what I was saying about console games being made On Pc, but made For consoles.

I dont expect them to flick a switch on a console game an BOOM! The game works perfect.

Buuuut, you would have to think a Pc port would be easier to handle than a console port.

Rofl. I could not help but laugh my butt off at that video.

LMAO! Brilliant.

OH MY GAD!!! Everyone has to click on that video. I'm crying laughing so hard.!!!

WATCH THE VIDEO ROTFL!!!!

You gotta BUBS UP FUNNY for posting that video link!!!

Those 12 people probably weren't enough to port the game in time to meet the release date set by the publisher. Either way you're right. If there is someone to blame are the higher ups at WB.

Why would you blame the QA department on that? Sure they told them that the game doesn't work very well.

probably a typo somewhere saying Verizon instead of version

There was a typo in the title, which has been stealthily fixed.

No, No. Not at all!

What I'm saying is the base engine is made so that you can build to PC with the click of a button. Other consoles require extra code but that code sits ON TOP of the existing code. This code has nothing to do with the game and is called "Engine-level code" as it affects the engine and nothing more.

Actually, the code in question affects the "BuildTarget" - But as I said, It sits on top of the existing build target code (And doesn't replace it).

That's how it should be anyway. It sounds like they overwrite the original PC building code on the engine or some other such nonesense.

I don't understand why I'm getting dislikes for it; It's the facts. I've been a developer for just under 10 years and that's how things are with Unreal Engine - The build tools are seperate to the main engine.

Even if they had overwritten the PC build target code; It would just be a case of using an alternative build of Unreal Engine that HAD the PC Build target it and frankensteining the code together and building.

It's a process that should literally take minutes (The building would take a while though) hence why I am saying what I'm saying.

I'm not being a fanboy to any console or whatever or anything like that; I am literally just stating the facts about what Unreal Engine does on the engine level; Hence why I don't understand why it took 12 people and even then they managed to mess things up.

This is literally JUST the facts with no bias in it; But as always with N4G - Everything is your opinion and because everyone thinks you're a freakin' liar or something - It'll get "Disagreed" to poop. *Sigh*

I was only trying to shed some light on the situation from a developer point of view.

The reason I said: "Surely they wouldn't have been stupid enough to OVERWRITE the base renderer code of Unreal Engine to focus on either Playstation / Xbox" is because the code should sit on-top of each other; Not replace it. Otherwise you'd have a scenario where you'd have to have two seperate engines completely: One for Playstation and one for Xbox.

Most developers with common sense have one engine with multiple build targets (Duplicating existing build targets and editing them to their needs) but it sounds like here they only had two build targets (Xbox, PS4) which makes ZERO sense when Unreal Engine 3 COMES with a PC build target as default.

TL;DR - There's no excuse for this crappy port; I try to explain why but people think I'm a freakin' fanboy or something *Sigh*

As I said, Only trying to help shed some light on this stuff.

"Actually, the code in question affects the "BuildTarget" - But as I said, It sits on top of the existing build target code (And doesn't replace it)." Not a developer or anything but what you're talking about is exactly that; Taking code from PC, hoping to throw a little something something on there, then calling it the console version.

Again though that would mean you would be building for PC, targeting PC requirements, then doing the bare minimum to get it onto console.

You're literally flipping the scenario and calling it good that way but bad this way.

So I ask again. Why should they not be optimizing and working to get the best product possible to each platform and instead pushing PC and treating the others as an afterthought?

Not condoning what they did at all as the PC product isn't up to standards but to even insinuate a good majority should get shafted and should have a worse experience so yours can be better is just stupid. Then we really aren't talking about fixing the PC version but ways to hinder the console versions in favor of a charade.

Stories like this go to prove the point. We aren't talking about the fact that the PC version needs fixing. We're talking about hindering the console version to deliver the idea that the PC version is superior.