Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The link is from 2022, is the same problem back in 24H2 ?
https://www.bleepingcomputer.com/news/microsoft/ubisoft-fixes-windows-11-24h2-conflicts-causing-game-crashes/
```Microsoft now says it lifted the upgrade blocks for devices with Star Wars Outlaws and Avatar: Frontiers of Pandora last Thursday after Ubisoft released temporary hotfixes that mitigate the crashes (although those affected might still experience some performance issues).```
These references are letting folks know this isn't a problem on our end but one that is from the Windows 11 issue. Our team is monitoring it and seeing if there is anything we can do at all since it wasn't something we did that caused this.
Waiting for a Microsoft fix isn't a solution.
I know this has also effected a bunch of other game such as Ubisoft titles, but they put a patch out to fix their games immediately as well as some other studios. MS haven't put out a hotfix and its been over a month. Maybe time to start taking action your end.? Being the fact that its your software It's sort of your responsibility to all of the people who bought your game to get it working on modern systems. OMD1 is pretty old now and I'd excuse that as being more of a compatibility thing. But OMD3 you latest working title and your just going to sit on your hands??
I implore you to re-read what I said that you quoted.
"There isn't a solution at the moment" - meaning, there isn't a solution with us. We have been looking into it regardless. It just wasn't our fault this happened in the first place.
We've even put this on our website as well - https://robotentertainment.com/omdsteamtechfaq
We will be continuing to work on a solution, but we're a small team shipping our newest game next month. OMD3 hasn't really seen this issue either - it seems to be only affecting OMD1. Again, we're not letting is go, we will get a fix here eventually.
I hope you can understand. Thank you.
So no fix?
Thank you for confirming you are investigating. I am looking forward to finishing OMD1 before picking up deathtrap.
Thank you.