So someone is going to make a game with this? By the time it [if] ever comes to market, CD Project is going to be on the next or subsequent engine anyway --
I don't think Carmack was ever any worse for the wear after releasing the Quake engine when Quake II came to market, etc.
No one could use it since trying to release a commercial product using their engine would get the company sued in oblivion. Maybe some Chinese company that doesn't give a fuck about selling it outside of China would do it, but no existing studio would touch it. The only other reason I can think of for someone to buy it is to try to see if there's a way to backdoor some kind of malware into the game so that it spies on you or mines crypto currencies on the GPU while the game is running.
You break up the code into it's significant algorithm blocks and use those in other products. It's is not the entire code but it's elements, and how much they cost to produce and they can readily be reused. Likely coders who CD Projekt Red outsourced to but did not pay enough.
It is kind of like a bank having trouble handling it's cash and just putting that keeping of that cash to open tender, anyone who wants to handle millions of dollars and they take the cheapest tender to look after the money and they ar
Code wise, whats the point of that? You can license something like UE4 or Cryengine for a song, and its probably going to be significantly better code anyway.
All the game-specific scripting is cruft, in the scheme of things.
The whole idea of selling a product is not needed. Just sell patches to fix the defective parts. And like a virus scanner you can the code for sequences so patches can be worked into different offsets in different versions.
There is precedent. Someone created a few MS OS patches before MS did. If you have the source code, you should be able to create a signature checksum much easier.
As for rendering engines, all the tricks have already been used, which is basically not rendering bits that cant be seen. T
actually I think no existing studio would touch it even if they could do so legally. The so called 'red engine' took 8 years and its disappointing. even the engine that powers gta 3 is more impressive.
It's actually even more complex than that. After the Half-Life 2 source code was leaked there was a legitimate warning that no devs under any circumstance should look at it.
The reason being that if you wrote an algorithm in a game as a professional developer and subsequently someone working alongside you left and went to work for Valve and said "Hey, I saw this algorithm used at my last employer" then this opens the door for legal discovery against your former employer, and potentially you as an individual.
You can not get anything worthwhile done without raising a sweat.
-- The First Law Of Thermodynamics
What's the value? (Score:2)
I don't think Carmack was ever any worse for the wear after releasing the Quake engine when Quake II came to market, etc.
Re:What's the value? (Score:3)
Re: (Score:1)
You break up the code into it's significant algorithm blocks and use those in other products. It's is not the entire code but it's elements, and how much they cost to produce and they can readily be reused. Likely coders who CD Projekt Red outsourced to but did not pay enough.
It is kind of like a bank having trouble handling it's cash and just putting that keeping of that cash to open tender, anyone who wants to handle millions of dollars and they take the cheapest tender to look after the money and they ar
Re: (Score:2)
Code wise, whats the point of that? You can license something like UE4 or Cryengine for a song, and its probably going to be significantly better code anyway.
All the game-specific scripting is cruft, in the scheme of things.
Re: (Score:2)
I think your second paragraph just described most Bitcoin exchanges.
3rd party patches can be sold (Score:2)
Re: (Score:2)
Who knows? Saudi Prince's son says he wants to program videogames, dad gets him some cool source code for his birthday....
Re: What's the value? (Score:1)
Re: (Score:1)
It's actually even more complex than that. After the Half-Life 2 source code was leaked there was a legitimate warning that no devs under any circumstance should look at it.
The reason being that if you wrote an algorithm in a game as a professional developer and subsequently someone working alongside you left and went to work for Valve and said "Hey, I saw this algorithm used at my last employer" then this opens the door for legal discovery against your former employer, and potentially you as an individual.