Thanks you!!
EDIT: @Aemony SK injection to Jedi FO works but I can’t move mouse, SK took control over it and i only have cursor.
Can’t find a way to “disable” that.
That’s weird it doesn’t on me at all. I was able to play almost 5 to 6 hrs straight. Though I always end task the crash handler.exe since that was causing my game to stutter a lot worse and cause crashes every so often. I mean the one that boots up with the game.
Uh did you accidentally go into the Input settings and disable mouse? That would disable the mouse ingame. This would be in SK GUI or did you do option to hide mouse icon?
Maybe I explained it wrong.
With SK activated, once I turn in-game UI on with Ctrl+Shift+Backspace, I can’t mouselook at all - that is, even with the UI off, moving the mouse does nothing - all I see is the cursor moving side to side and the game recognizes my input (left/right mouse buttons), the game even recognizes the mouse in menus, but I can’t look around with the character with the mouse.
It’s like SK has some overlay and doesn’t relinquish the mouse movement in favor of the camera when needed.
Hold down TAB, I think.
I believe that is used to change the input between exclusively SK or the game.
Hold down TAB, I think.
Doesn’t work, still can’t mouselook and I see the cursor.
Did you redo ctrl shift backspace to turn off Overlay? Can’t leave it on. Plus why would you do that with Horizon? It doesn’t come up at all due to game being dx12.
Yes and I am talking about Jedi FO:(
Probably best to do it the easiest way – configure Special K correctly and then close the game and restart it, and after that don’t bother with the in-game control panel 
Fallen Order is a weird one due to its dual-overlays, so it’s probably a weird conflict somewhere in-between those.
You could see if disabling Steam enhancements of Special K also fix the issue.
1 Like
Thanks, will try 
Yup, almost certainly Meridian causing it. If I’m outside of it, I can usually run around just fine for a while, but after I had re-entered it I crashed within some 10 minutes again 
I really really hope they sort the D3D12 calls out soon.
That’s weird that is happening to you Aemony even without SK. Odd b/c on my end with AMD GPU I haven’t had any crashes while inside Meridian. Have you tried end tasking the Crash Handler.exe that runs alongside Horizon exe?
SK disables the game’s own crash handler and that have no effect on the issue.
Erebus (whom uses AMD hardware as well) also mentioned how he didn’t experience any crashes related to Meridian.
Right now one of my thoughts are that it might be related to the oversaturation of the PCIe lane that the game is famous for, but it’s too early to say for certain.
Well If I am not mistaken Erebus runs an AMD GPU as well. Might be something to do with Nvidia Users right now.
In the update thread itself I have seen posts about how ppl are crashing even more often with latest update. Don’t know yet if they are Nvidia or AMD.
Got everything working and using the local injection method with the latest SpecialK64.dll Kaldaien posted in this thread.
Only problem I have now is the Steam Overlay is no longer working and as such the controller no longer connects. Anyone have any suggestions on how to fix this? I tried disabling all other overlays I could think of (RTSS and Geforce Overlay) yet it’s still not working. Is there as specific configuration I should try changing under the Steam.System section of the ini?
Locate the below section and set Silent to true. This will disable Special K’s Steam enhancements and related features:
[Steam.Log]
Silent=true
That didn’t end up working for me but I got it working by simply rerunning Steam as administrator. Thank you for the suggestion though!
Oddly enough i reached Meridian yesterday and everything fine so far. Besides some crashes at launch that are solved launching the game a again, it has been a smooth experience for me.
I’m running Win10 2004 (GPU scheduling enabled), GTX 1070, Latest nVidia Hotfix driver. Using Special k to limit fps and RTSS for osd.
So is there no way to run this in exclusive fullscreen? I feel I’ve tried everything so far.
Sounds like it’s not needed but it also sounds like Kaldaien overrode the behavior so the game is windowed or borderless and the settings normally used to define display and window behavior in SpecialK don’t affect this though being D3D12 I was under the impression flip model was required instead and Microsoft has been pushing to have borderless mode as the standard including overrides like the full-screen optimization setting also outside of the DirectX 12 API.
Assuming it’s accurate NVIDIA might also have a new driver update for next week but nothing specific was mentioned just fixes and some non-title specific crash condition fixes.
EDIT: The older SpecialK64.dll embeds in this topic might still work in fullscreen exclusive as might the main download itself with the 64-bit .dll dated August 9th instead of the last two - three versions this last week and some further updates and changes so that could be a way to get exclusive full-screen display capability back for the game.