27 replies to this topic

[EldrenOfTheMist]

Ghost Paladin117, on 31 December 2018 - 11:11 AM, said:

I'm not too sure about the level of work involved but PGI said they weren't doing anything major to MWO until MW5 is done

Then that means they are thinking of doing some thing Major after MW5. right?

[Svarti713]

EldrenOfTheMist, on 01 January 2019 - 06:17 PM, said:

Then that means they are thinking of doing some thing Major after MW5. right?

You are correct! Hopefully it will be a Tech Update

[KursedVixen]

On what grounds Can Crytek sue for people changing engines? that seems a little illegal if you ask me.

[Alreech]

KursedVixen, on 02 January 2019 - 03:03 AM, said:

On what grounds Can Crytek sue for people changing engines? that seems a little illegal if you ask me.

CryTek and CIG made a Game License Agrement, a contract about money, copy rights and support.
CryTek sued CIG in California for breaking parts of that contract.

CryTek claimed that GIG has only the right to make one Game (Star Citizen) with their Engine, and selling Squadron 42 without Star Citizen on it's own is using the License for two games.
CryTek also claimed that CIG promised to deliver all Bugs they found and Engine improvements to them, but didn't
CryTek claimed a lot of other stuff (as usual in such lawsuites).

CIG told the Judge to dismiss the lawsuite, but only a part of the claims haven been dismissed.
CIG added the Game License Agrement to their motion to dismiss, so it became public.

CryTek also told in their lawsuite that they created the Kickstarter Promo Video for Star Citizen and gave CIG the CryEngine License for a reduced price, so they are probably enraged that CIG switched the engine without terminating the license (that would CIG force to remove all CryEngine code from Star Citizen & Squadron 42) or fullfilling the promise to deliver engine improvments.
Chris Roberts Partner and CoFounder of CIG is also a former Lawyer of CryTek...
IMHO the whole thing is more a personal problem than a grab for money (CryTek gave Amazon a License for the CryEngine for a lot of money).
CryTek is a German Company founded by the sons of turkish imigrants, and if you do business with Germans or Turks that kind of action (getting the license for a reduced price and a lot of support, than breaking the contract) is an insult.

I doubt that PGI got the kind of support / license terms from CryTek that CIG have got. And I doubt that PGI didn't have fullfilled their obligations to CryTek.

[Fyrwulf]

The whole "will it run Crysis" meme is because the basic engine was, and remains, an unoptimized pile of garbage. When CryTek did their DX12 update, performance actually decreased with AMD hardware, when the basic DX12 code was heavily based off Mantle and was implemented with a great deal of AMD help. So CryTek managed what should have been impossible.

IMO, the best engine to migrate to would be Nitrous. Oxide would help PGI with the switch over and has great documentation. However, with work already being done with MW5 on UE4, I think it would be cheaper to continue on with that engine.

[MitchellAvellar]

I for one would be whole-heartedly in favor of a port of MWO over to UE based on what i've seen so far of Mercs5. It plays so very much better on a joystick than MWO. I mean, i was finally able to get the right stick (T16000) and enough practice with it that my aim isn't complete crap anymore in MWO, but i was aiming sweet day one with it in Mercs5. And the whole entire feel of the mechs is just way better. No more FPS (ish) garbage. I might even have to go get the rest of the gear (pedels and throttle) if they actually end up porting MWO over to that platform.

Note: the assumption being they wouldn't keep all the mech customization limitations from mercs5 lol. That would be just plain horrible.

[McHoshi]

Koniving, on 29 December 2018 - 09:25 AM, said:

How i miss that old heat vision. Why was it changed? Because of performance Problems? Should be reimplemented asap.

[Koniving]

McHoshi, on 30 December 2019 - 03:45 AM, said:

How i miss that old heat vision. Why was it changed? Because of performance Problems? Should be reimplemented asap.

Combination. Gameplay issue and laziness.

Gameplay issue:
The colored heat vision was only colored on mechs, which made it easier to just murder them. There was no reason not to have it on.

Laziness:
In order for the maps to be able to show proper thermographic vision would require considerable effort dedicated to setting the temperature of every asset, and modifying this for every map. Something that was apparently too daunting, or that they flat out never thought of doing as you'd often end up on a map that's pitch black with the earliest thermal camera after the complaints sending out a "sonar" pulse effect on at your feet to help you see the building 6 meters in front of you that's otherwise invisible. Eventually, they just blanketed everything with a bluish shade, and finally just said **** it.

Proper thermals
FLIR style


or traditional


(Thermal for the City of Ghent)


Thermal of a home.
(Note that one home is leaking all kinds of heat... but the larger home is really cold despite some windows showing there is heat inside [this happens a lot for occupied homes that are well insulated]. This is important because the reason why lasers and PPCs don't generate heat to the target while literally melting the armor into molten metals is according to TechManual 2007 and Battlemech manual 1990s, and BattleTechnology magazine 1987, mechs are well insulated and dissipate heat rapidly off the surface such that internal heat would barely register aside from recently fired weapons, with one of them mentioning that mechs over 25% heat tend to start to stand out, being "noticeable" over 46.67% heat, and impossible not to be seen at 70%. Meanwhile fire a laser and you'd start changing colors in the old thermals of MWO.)


Military thermals (most mechs would appear closer to black or whatever color the environment is until they heat up, except for at the weapons which would spike with heat after every firing until cooled down)

Edited by Koniving, 30 December 2019 - 12:35 PM.