Remote Play Controller 2 Not Working - Steam
My gf and I were playing through Split Fiction with Remote Play Together. Recently however when we connect, her controller does not get recognized by the game. This is the only game that has this issue, as we can successfully play any other Remote Play Together game and her computer recognizes the controller just fine. Are there any known fixes for this? We are about halfway through the game now so it doesn't make sense why it would break all of a sudden.
Lost in Random - "Origin is not installed"
So after letting the game sti for 2 years in my STEAM library I decided to give it a go. Thought that'd go without a hitch. Sadly the game is refusing to launch, telling me that "Origin is not installed". I tried everything. Reinstalling, deleting all cache files from the EA App and Origin, restarting in between steps, running the game from the EA App, installing the EA App from online, disabling my antivirus. There's absolutely no reason for this to not work, how do I even go about solving this when having tried all the solutions from every past posts about that issue on various forums didn't work.The Game is Crashed in the only one placed
the game crashed when Leo & Vincent arrive amirca by plane and the police man waiting them. LowLevelFatalError [File:E:\Haze1\Main\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 815] Rendering thread exception: LowLevelFatalError [File:E:\Haze1\Main\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 182] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG') KERNELBASE.dll!0x0000000067EC5369 AWayOut.exe!0x00000000CED1A76B AWayOut.exe!0x00000000CECEA228 AWayOut.exe!0x00000000CF157F41 AWayOut.exe!0x00000000CF158E0A AWayOut.exe!0x00000000CF146769 AWayOut.exe!0x00000000CF1510A8 AWayOut.exe!0x00000000CF43F9F4 AWayOut.exe!0x00000000CF464D0F AWayOut.exe!0x00000000CF47F099 AWayOut.exe!0x00000000CF4712AA AWayOut.exe!0x00000000CF43F353 AWayOut.exe!0x00000000CF43F1BE AWayOut.exe!0x00000000CF20EEC8 AWayOut.exe!0x00000000CF447641 AWayOut.exe!0x00000000CF43AAD8 AWayOut.exe!0x00000000CEC79E2E AWayOut.exe!0x00000000CEC79FEC AWayOut.exe!0x00000000CF537436 AWayOut.exe!0x00000000CF5374C8 AWayOut.exe!0x00000000CED6B647 AWayOut.exe!0x00000000CED66BA7 KERNEL32.DLL!0x00000000688F7374 ntdll.dll!0x000000006A85CC91 ntdll.dll!0x000000006A85CC91Fatal crash - Access violation (0xC0000005) in SplitFiction.exe v5.4.4.0
Description: - Game: Split Fiction (SplitFiction.exe) version 5.4.4.0 - Platform: Steam (installed at D:\steam\steamapps\common\Split Fiction\Split\Binaries\Win64\) - OS: Windows 10 (Build 26100.1) - GPU: NVIDIA GeForce 4060ti 16G, driver version 581.80 - Local time of crash: 2025.11.6 19:17 - Repro rate: always Error details (from Windows Event Viewer): - Faulting application name: SplitFiction.exe, version: 5.4.4.0 - Faulting module name: ntdll.dll, version: 10.0.26100.6899 - Exception code: 0xc0000005 - Fault offset: 0x000000000000aa83 - Faulting process id: 0xB90 - Faulting application path: D:\steam\steamapps\common\Split Fiction\Split\Binaries\Win64\SplitFiction.exe - Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll - Report ID: 460323ae-7a03-49a9-a953-9c4eb8e547d8 Additional analysis (from local !analyze dumps): - Multiple dumps show INVALID_POINTER_READ (Attempt to read from ffffffffffffffff). - Stack frames reference: AK::ReadBytesSkip::Count, AK::WriteBytesBuffer::GetPos, ffxFrameInterpolationResourceIsNull (Wwise/frame interpolation related functions). - Suggestion: the crash appears to originate from buffer read/write or frame-interpolation logic (possible invalid pointer or incorrect size/offset used). Steps already tried: - Verified integrity (Steam) - Full reinstall (uninstalled + deleted residual AppData folder) — still crashes - Disabled overlays (GeForce Experience) - Ran sfc /scannow and DISM RestoreHealth (no system corruption found)
Split Fiction 108-0 error
Purchased the game a couple hours ago after reading a bunch of great reviews, only to find that there is some persistent error where cross play is concerned. I'm on PC (win 10, current in most respects, but going to try 11 as a 'just in case'), partner is on PS5 (also up to date in all the ways), and we haven't been able to find any combination of network settings, account unpair/re-pair, file validation, firewall settings, uninstall/re-install and a few other things besides, that have gotten the game to work. We're on the same network, and we can see each others in game status change through the game, but keep running into the same issue of 'other person left the session.' Is there something else we should try? Incredibly disappointed in this whole experience.Split Fiction – Accessibility issue: no Russian subtitles for over 200M players
Hello EA team and players, I’ve already seen a thread requesting Russian subtitles, but I’d like to emphasize this not just as a language request — it’s an accessibility problem. Russian is spoken by over 200 million people across multiple countries (Russia, Ukraine, Belarus, Kazakhstan, Latvia, etc.). Split Fiction is a story-driven game, and without subtitles or interface translation, millions of players cannot follow the plot at all. This goes beyond localization — it’s about equal access for everyone. Please, forward this issue to the Localization and Publishing teams. Thank you for understanding.
Split Fiction - Suggestions
Subtitles size adjustment: I'd be great to have control over subtitles size. At least playing on 4K, I found it really small and difficult to read. Camera auto rotation: "camera assistance" feature doesn't seems to make any difference when turned on. My partner isn't really a gamer person and she struggles a lot trying to adjust the camera with the joystick every time she walks. It would be really great if we had some improvements in this aspect too. DLSS: is a really missing feature and currently better than FSR. Any future plans for having it available? I hope this is the right place to put this kind of suggestion/feedback. We are loving the game even with all the things mentioned above, and despite not having pt-BR voice (our native language).
