22 replies to this topic

[Joat]

Why has this not been fixed yet?

Is there any plans on fixing this issue?

I know there is a work around......im not going to use it.

If they cant/wont fix the issue Ill just take my money els where.I just want to know if I should hold out any hope of a fix.....or should I just uninstall and move on.

let the trolling begin HAHA



I guess this is what I get for upgrading to a new BAD A&* PC - older games just wont work anymore.

[DCouch]

https://mwomercs.com...l-cpus-and-mwo/

[Joat]

Thanks for the reply DCouch.....however I did state that I have no intention of using the workaround to make the game work so I dont get why you shared the link..

I only need to know if there are plans to fix the issue or not.....If not ill just move on to the many other games that suck up my cash lol.

[John Bronco]

You should move on.

[PocketYoda]

Easy fix do what i do..

Don't upgrade.

[w0qj]

MWO works out of the box upon installation on both my two recent ThinkPad purchases (albeit both with GPU's).

Never had any problems with MWO on my computers!

[D V Devnull]

Joat, on 14 December 2021 - 08:32 PM, said:

Is there any plans on fixing this issue?

It so happens that the Player Base At-Large is not able to answer this question. Please use the following "MWO Technical Support Contact E-Mail" to inquire about this issue any further...

technical@mwomercs.com

...as nobody here knows what PGI themselves do. If they do answer you back, please let the rest of us know what they said, alright?

~D. V. "All we can really do is tell you to contact PGI directly about this matter. We simply don't know." Devnull




[Small Edit by the Post Author to correct a Major Formatting Error]

Edited by D V Devnull, 15 December 2021 - 04:49 AM.

[Meep Meep]

It says 10th and 11th gen intel cpu but my 10600k is working flawlessly with mwo. Guess its more an 11th gen issue.

[Sjorpha]

Joat, on 14 December 2021 - 08:32 PM, said:

I know there is a work around......im not going to use it.

Why not, is there a downside to using it?

Some kind of principle? Trying to force PGI to fix it?

[MrVaad]

Meep Meep, on 15 December 2021 - 07:43 PM, said:

It says 10th and 11th gen intel cpu but my 10600k is working flawlessly with mwo. Guess its more an 11th gen issue.

For 10th gen, it's the ice lake cpus (and later). Ice lake are the laptop cpus.
For 11th gen, it's the rocket lake cpus (and later).

https://en.m.wikiped..._SHA_extensions

So it could be mainly laptop cpus that are impacted for 10th gen ?

Edited by MrVaad, 16 December 2021 - 04:59 PM.

[Meep Meep]

Ah. Well since its a desktop guess I got lucky.

[Meep Meep]

Going to have to take this back. I went ahead and did this fix on a lark because I was tweaking around with the graphics files and it solved a random stuttering issue I thought was related to the gpu and not cpu.

Meep Meep, on 15 December 2021 - 07:43 PM, said:

It says 10th and 11th gen intel cpu but my 10600k is working flawlessly with mwo. Guess its more an 11th gen issue.

[LordNothing]

pgi does not fix bugs. at least not code level bugs. the game engine is an antique.

[Meep Meep]

It's not really pgi's or the game engines fault. Part of the shared openssl code developed by intel and used in the engine was buggy and this fix solves it. It didn't even have any issues until the newest cpu came out. I suppose the new owners could technically fix it by updating the openssl part of the engine but that would take money and devs whereas this fix is easy and can be done by anyone.

[MrVaad]

Meep Meep, on 05 May 2022 - 11:05 PM, said:

It's not really pgi's or the game engines fault. Part of the shared openssl code developed by intel and used in the engine was buggy and this fix solves it. It didn't even have any issues until the newest cpu came out. I suppose the new owners could technically fix it by updating the openssl part of the engine but that would take money and devs whereas this fix is easy and can be done by anyone.

Actually, it shouldn't take much time. OpenSSL released a version with only the needed fixes (in may 2017 ).
No impact on the API, no other code changed.
So PGI needs to replace their old library with that specific version. The compiler will just link the new lib (no need to recompile anything). This is assuming they are using libs from openSSL.

Here's what intel recommends :

If the application uses OpenSSL natively, Intel recommends you take one of the following steps to resolve the issue:

• Upgrade to OpenSSL version 1.0.2L. This is the first version that contains both fixes. While this will fix the issues described here there may be other security issues still remaining.
  
• Upgrade to the latest version 1.0.2. This should be a drop-in replacement and will also include many other bugs and fixes
  
• Upgrade to OpenSSL version 1.1.1. Version 1.1.1 is not a drop-in replacement for version 1.0.2, so may require more extensive development and test but will bring you up to date on all OpenSSL updates.

Edited by MrVaad, 06 May 2022 - 05:48 AM.

[Seelenlos]

MrVaad, on 06 May 2022 - 05:32 AM, said:

Actually, it shouldn't take much time. OpenSSL released a version with only the needed fixes (in may 2017 ).
No impact on the API, no other code changed.
So PGI needs to replace their old library with that specific version. The compiler will just link the new lib (no need to recompile anything).

Here's what intel recommends :

If the application uses OpenSSL natively, Intel recommends you take one of the following steps to resolve the issue:

• Upgrade to OpenSSL version 1.0.2L. This is the first version that contains both fixes. While this will fix the issues described here there may be other security issues still remaining.
  
• Upgrade to the latest version 1.0.2. This should be a drop-in replacement and will also include many other bugs and fixes
  
• Upgrade to OpenSSL version 1.1.1. Version 1.1.1 is not a drop-in replacement for version 1.0.2, so may require more extensive development and test but will bring you up to date on all OpenSSL updates.

MrVaad,

do you know by chance if it also impacts AMD Razon 3600?
(igit, would never buy that for gaming again - but for Linux, yumi)

ahhhj...

and would that set command be enough to put in an elevated cmd befire starting MWO? (or making a script)

Edited by Seelenlos, 06 May 2022 - 06:11 AM.

[MrVaad]

Seelenlos, on 06 May 2022 - 05:49 AM, said:

do you know by chance if it also impacts AMD Razon 3600?
(igit, would never buy that for gaming again - but for Linux, yumi)

and would that set command be enough to put in an elevated cmd befire starting MWO? (or making a script)

As far as i know, it's :
- intel laptop 10th gen
- all intel cpus 11th gen and later.

I don't think any ryzen owner has the problem (i have a ryzen 2600).
And yes, you can use a set command in a batch file.

Edited by MrVaad, 06 May 2022 - 06:39 AM.

[w0qj]

Does the presence (or absence) of discrete GPU matter?

I have Intel laptop, 10th gen CPU, Win10 Pro 64bit, and has a discrete GPU.
No problems installing MWO on this.

(If anyone is interested, it's a Lenovo ThinkPad X1 Extreme Gen 3,
with NVIDIA GeForce GTX 1650 Ti with Max-Q Design discrete GPU).

MrVaad, on 06 May 2022 - 06:34 AM, said:

As far as i know, it's :
- intel laptop 10th gen
- all intel cpus 11th gen and later.

I don't think any ryzen owner has the problem (i have a ryzen 2600).
And yes, you can use a set command in a batch file.

[MrVaad]

w0qj, on 06 May 2022 - 08:20 AM, said:

Does the presence (or absence) of discrete GPU matter?

I have Intel laptop, 10th gen CPU, Win10 Pro 64bit, and has a discrete GPU.
No problems installing MWO on this.

(If anyone is interested, it's a Lenovo ThinkPad X1 Extreme Gen 3,
with NVIDIA GeForce GTX 1650 Ti with Max-Q Design discrete GPU).

GPU does not matter. And the problem should make you crash on login if i'm not mistaken.

If you have this cpu (https://ark.intel.co...o-5-00-ghz.html), you have a "comet lake" cpu which is not concerned by the bug.
For 10th gen, the bug only affects "ice lake" cpus and later (if i read this correctly https://en.wikipedia...xtensions#Intel)

This would mean 10th gen mobile cpus released before "ice lake" are not affected ?

Edited by MrVaad, 06 May 2022 - 10:08 AM.

[LordNothing]

Meep Meep, on 05 May 2022 - 11:05 PM, said:

It's not really pgi's or the game engines fault. Part of the shared openssl code developed by intel and used in the engine was buggy and this fix solves it. It didn't even have any issues until the newest cpu came out. I suppose the new owners could technically fix it by updating the openssl part of the engine but that would take money and devs whereas this fix is easy and can be done by anyone.

i dont know about that. its up to the developer to keep their dependencies up to date. failure to do this usually manifests itself as these kinds of problems. they start out as minor inconveniences that require work arounds. but neglect it long enough and you will have hard incompatibility issues. this is why a lot of old games dont work on modern oses. not compatible with x hardware or y os version.

from a security standpoint forcing the game to use an old version with known security issues is also bad. this workaround essentially forces the whole system to use an old insecure version (and i totally understand the op's aversion to using it). codebases are meant to be dynamic things, but pgi has a monolithic unchanging code blob that is like a big old structure and the foundations upon which they rest are shifting and evolving. failure to adapt to the changes will cause the whole damn thing to collapse catastrophically. this is certainly no way to treat your cash cow.

Edited by LordNothing, 06 May 2022 - 10:50 AM.