Chapter 7 "Activate the Launch Tubes" PS5 game-breaking bug!
So after completing chapter 6 I went to do a side-mission "You Are Not Authorized" and used the tram. A cut scene was triggered where the tram seemed like it crashed into something, and now it says the Mining area is "locked". It only takes me to Engineering. The current main objective is in the mines and I no longer can access that area. THIS IS SO FRUSTRATING. A $70 GAME SHOULD NOT HAVE THIS MANY GAME-BREAKING BUGS. Has anyone else run into this?
Dead Space
bonjour, je 'arrive pas à lancer Dead Space sur mon PC. Ca me dit qu'une erreur vient du coté de EA et de réessayer plus tard. Or ça fait 10 jours que l'on réessaye plus tard et ça ne fonctionne toujours pas, et bien évidement l'assistance n'est pas disponible sur ce jeu. Nous l'avons désinstallé et réinstallé plusieurs fois et utilisé aussi la réparation, mais rien n'y fait... Pour info : voici ma configuration Stockage 9,10 TB Memoire RAM installee 64,0 Go Carte graphique 12 GB NVIDIA GeForce RTX 4070 Vitesse : 4200 MT/s Processeur 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz Une idée de comment faire ?
I can't properly launch Dead Space 3. The game won't start
I can't properly launch Dead Space 3. The game won't start, and an error message appears. This message "A problem on our end caused the launch to fail. Please try again later." I was able to play Dead Space 3 before, but recently it won’t start. I have followed all the troubleshooting steps provided by EA customer support, but the problem still persists. Please advise me on how to resolve this issue, as I purchased a game that may become unplayable at any moment. I have three EA games that I can’t play, including Star Wars Battlefront II, Mirror’s Edge, and Dead Space 3. None of them are working. I paid for these games, but now I can't play them, and the issues still haven't been resolved. Should I be asking for a refund? I bought the game through Steam.
Traversal stutter appears CPU-bound during streaming events
Hi Motive team, Traversal stutter during area transitions is still consistently reproducible. The game otherwise maintains high and stable FPS, but frametime spikes occur when moving between sections of the Ishimura. Based on testing, this does not appear to be GPU-limited. Average framerate remains high, and the issue persists on fast SSD/NVMe storage. The behavior feels more CPU-bound during streaming events, as if workload spikes occur when new assets are loaded. Interestingly, reducing storage throughput (via a community workaround) lessens the severity of the spikes, which suggests the issue may be related to how aggressively assets are streamed and processed rather than raw hardware limits. I understand that large engine-level changes may not be feasible at this stage. However, if there are any adjustments that could smooth CPU workload during traversal (such as streaming pacing or buffering changes), even partial mitigation would significantly improve smoothness. Dead Space Remake is otherwise an outstanding experience, and this remains one of the only technical issues affecting immersion. Thank you for your time.Dead Space Remake: DLSS 3.5/4.5 + FSR Update with Frame Generation
Dead Space Remake is one of the most visually impressive and well-crafted AAA titles in recent years. Its atmosphere, lighting, and technical presentation make it a standout experience on PC. To keep the PC version aligned with modern hardware, I would like to request an update to DLSS 3.5/4.5 (including Ray Reconstruction) and the latest FSR, along with Frame Generation support for both technologies. These improvements would boost performance and maintain stable, high-quality visuals in ray-traced areas. Implementing these changes could extend the game's lifecycle, encouraging both returning and new players. Thank you for considering this request.
error: Invalid license !?!
Hello, I'm writing my third letter, no one is answering me or fixing the problem . On February 4th I bought the game Dead Space 3 from EA through my account: danko2142 Order date: 04/02/26 Order number: 1005662992512 The game was downloaded, but when I wanted to start it, it did not start, a window appeared with the following error: Invalid license. Reason code=Missing DLL d3dx9_43.dll Error 0x000000c1 Please help me solve the problem!
Potential fix for your (PC) controller not working in Dead Space (2023)/Remake
I have a Keychron K2 HE keyboard that causes problems in a handful of games (Dead Space (2023)/Remake and Sekiro are the ones that I know of so far), where this keyboard is recognised as the primary gaming controller and renders my Xbox wireless controller completely unusable in these games. No input from my Xbox controller registers in these games whatsoever - with or without Steam Input enabled - unless I unplug the keyboard, which is far from ideal, so I wanted a better solution. After a lot of research, I found the best solution for me was to use "HID hide" (https://github.com/nefarius/HidHide) to hide my Keychron Keyboard from the affected games. It was very simple to implement the fix, and here are the steps required: -Download HID Hide -Install it and reboot when prompted -After the reboot, open the newly-installed "HID Hide Configuration Client" -Go to the "Devices" tab and find your Keychron K2 HE (or similar device causing the issue) -Click on the device and tick the "Enable device hiding" box -Unplug the device and replug the device -Load your game and test it If your problem was caused by the same issue mine was, this will work. If it doesn't work, your problem may be caused by something else. Thanks to "nefarius" for creating and sharing "HID Hide"! Additional info: "HID Hide" runs as a Windows service in the background, and, upon installation, is set to start automatically, so after you have configured it, you don't have to revisit it unless you change devices or reinstall Windows. I think the reason the Keychron K2 HE is recognised by Windows 11 as a gaming controller is because it can be confirgured as a "controller" in the keyboard's management software. It's a pretty unique feature which I'd never come across before and therefore never experienced loss of controller functionality due to this specific issue.
