![Possibly Retarded](/forums/smiles/titles/possibly_retarded.png)
They have developers from the OG company that made Baldurs Gate they don't need to contaminate the game with some Belgian garbage.
Like in Congo, so in California Belgian rule might be the least evil.They have developers from the OG company that made Baldurs Gate they don't need to contaminate the game with some Belgian garbage.
$$$$$Why should Larian license out their engine?
It's basically free cash given they have to maintain internal staff to manage/develop it for their own projects who could probably support external devs remotely given they'll already be doing it for Larian's studios spread across multiple continents, so if someone else wants to use it and pay for the privilege why not?
Yeah. But I'll explain it from a perspective of a licensee (who receives the license).$$$$$Why should Larian license out their engine?
It's basically free cash given they have to maintain internal staff to manage/develop it for their own projects who could probably support external devs remotely given they'll already be doing it for Larian's studios spread across multiple continents, so if someone else wants to use it and pay for the privilege why not?
It's cash if people use your engine. No one will use your engine if you don't invest a lot into customer support and giving them the features they want. Which like I said means it only makes sense for Larian to license out their engine if they want to turn into Epic Games and hire 4K people.
After they forced him to add the bear sex...I don't think he gives a fuck at this point. He liked the opportunity to work on BG3 because he likes BG, but from everything he said he never wants to work with WotC again.Lets see what our Swen has to say about this lol.
Sounds like what I've been hearing about it.A friend of mine worked at CD Projekt Red as a programmer. He's seen a lot of engines, but he said their engine was the best, the most sophisticated, most elegant thing he's ever seen. And over time, CDPR lost their engineers and all they could hire were "ue4 monkeys" who couldn't work with it. They ended up having to ditch it for UE5.
Bioware licensed out their engines to Black Isle, Obsidian, and CD Projekt. Bethesda did the same with Obsidian. It is really not such a big deal when you're making a sequel (and in CDP's case it was an original game).$$$$$Why should Larian license out their engine?
It's basically free cash given they have to maintain internal staff to manage/develop it for their own projects who could probably support external devs remotely given they'll already be doing it for Larian's studios spread across multiple continents, so if someone else wants to use it and pay for the privilege why not?
It's cash if people use your engine. No one will use your engine if you don't invest a lot into customer support and giving them the features they want. Which like I said means it only makes sense for Larian to license out their engine if they want to turn into Epic Games and hire 4K people.
It might if the game they make with your engine competes with your own game in the engine.Bioware licensed out their engines to Black Isle, Obsidian, and CD Projekt. Bethesda did the same with Obsidian. It is really not such a big deal when you're making a sequel (and in CDP's case it was an original game).
For a while there they had Logic Artists doing that trpg Divinity 2 spin-off, but LA messed that up on their own by missing their milestones and having to meet other obligations instead.It might if the game they make with your engine competes with your own game in the engine.
Look at Bethesda's reaction to New Vegas. They clearly didn't like that someone else made a better game with their egine, and that people started comparing Fallout 3 to NV in a negative light. So what did they do? They stopped licensing their engine.
It's a bit different in the case of Bioware, because there must have been a mutually beneficial deal between Bioware and Interplay: Bioware would license its Infinity engine to Interplay and Interplay would share its D&D license. In the case of NWN's Aurora engine, I think they only licensed it to Obsidian and CD Projekt because they were done with it. By then they had updated it for KotOR and named it Odyssey.
So I'm not so sure Larian would license their prized engine.
True, forgot about it.For a while there they had Logic Artists doing that trpg Divinity 2 spin-off
CDPR has access to a near limitless amount of skilled engineers, who would love nothing more than work for them. I find it hard to believe all they could find on the job market were "ue4 monkeys". Unless, you know.. the hiring process included some other variablesYeah. But I'll explain it from a perspective of a licensee (who receives the license).$$$$$Why should Larian license out their engine?
It's basically free cash given they have to maintain internal staff to manage/develop it for their own projects who could probably support external devs remotely given they'll already be doing it for Larian's studios spread across multiple continents, so if someone else wants to use it and pay for the privilege why not?
It's cash if people use your engine. No one will use your engine if you don't invest a lot into customer support and giving them the features they want. Which like I said means it only makes sense for Larian to license out their engine if they want to turn into Epic Games and hire 4K people.
Custom engines require good engineers. A friend of mine worked at CD Projekt Red as a programmer. He's seen a lot of engines, but he said their engine was the best, the most sophisticated, most elegant thing he's ever seen. And over time, CDPR lost their engineers and all they could hire were "ue4 monkeys" who couldn't work with it. They ended up having to ditch it for UE5.
UE monkeys wouldn't know what to do with Larian's engine even if they got it for free. Nobody's interested.