Instalar o Steam
Iniciar sessão
|
Idioma
简体中文 (Chinês Simplificado)
繁體中文 (Chinês Tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Checo)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol de Espanha)
Español-Latinoamérica (Espanhol da América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polaco)
Português (Brasil)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar problema de tradução
"if something works fine on 23H2, it should work fine on 24H2 too" Thats not how it works though...
Link for submitting ticket:
https://www.ubisoft.com/en-gb/help/contact
What's needed of info:
A description of at which point in the game the bug appears
The steps needed to reproduce the issue.
Any workaround found to solve the issue.
Additional information such as images or videos.
They will maybe ask you to follow instructions posted in this link, Try these steps and make sure to include in the ticket.
https://www.ubisoft.com/en-gb/help/connectivity-and-performance/article/troubleshooting-technical-issues-on-pc/000061047
They will also most likely want you to generate the Dxdiag and MSinfo files required for further investigation.
https://www.ubisoft.com/en-gb/help/connectivity-and-performance/article/generating-a-directx-diagnostic-report/000078583
https://www.ubisoft.com/en-us/help/connectivity-and-performance/article/generating-a-microsoft-system-information-report/000078753
Please send them to Ubisoft by following the instructions in the following link: https://www.ubisoft.com/en-gb/help/connectivity-and-performance/article/submitting-files-to-ubisoft-support/000063176
Also, please include the Ubisoft Connect logs that can be found in the Ubisoft Connect installation path, in the Logs folder - launcher_log, network_info and service_log.
The default path would be:
C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\Logs
Provided Mycrasoft with all the necessary information on this problem, like it so that Mycrasoft notices this problem, link to the review (feedback center) https://aka.ms/AAt2mnd
Your link is not working
If they cared it would be done already.
Their help site is full of bots that can't help.
Sending dxdiag? It's completely useless.
They have discord. Go there, it has live people as admins. https://discord.gg/ubisoftofficial
I urge everyone still on 24H2 and is having this or similar issue to report it to Ubisoft support, as that will help get their attention more than posting on reddit/steam.
Just crazy to allow this older digital assets like Origins to die and whither. These are just as important as old books for our culture. True works of art. We need to preserve them and support them.
Eventually all of our culture will be digital and we can’t just treat it as if it’s all disposable otherwise we’ll have nothing to pass on.
Anyway sorry for rant, let’s hope some clever chap finds a solution for this. Something real under the hood must be happening that didn’t happen before this update.
I can tell you that the latest Dev builds of Windows 11 have the exact same bug. So future release candidates are also not the solution. So something active needs to be done or Origins will remain broken. Very sad. 😔
The dx file thing
borderless windows mode
source exe thing
Running the creator (not game) NVIDIA driver
Tweaking graphics settings
What is odd is the intro works, the training bit works, even the history mode worked at the start but as soon as you get into the main game it breaks and freezes after a short time. Audio plays still but all else is frozen.
As said above, I can tell you that the latest Dev builds of Windows 11 have the exact same bug. So future release candidates are also not the solution. So something active needs to be done or Origins will remain broken.