Alright, so I got this game yesterday evening. Clean install, no mods whatsoever.
But it won’t start… I’ve followed a few guides on Youtube. Made an exception for Windows Defender and a boat load of other stuff, but I can’t get the damn game to work.
I now have re-installed the game, fresh, for the 4th time and I’m unsure how to proceed.
What am I missing or doing wrong?
Again, no mods installed of any kind and it was a clean install.
Which I did 3 times now… Please help?
Welcome to the game - hopefully it gets better for you 
Hopefully someone more knowledgeable will have some good suggestions - but my current ‘first stop’ for loading issues on PC would be to try CodeMage’s BUGLE (see link below) - it’s a useful launcher with a bunch of features, but more relevantly, if the problem turns out to be related to the standard Funcom Launcher rather than the game itself, it might help you get in.
Assuming that doesn’t work, I’d also suggest providing any details you can think of - how far is the loading process getting, any error messages etc - as that may help someone with more knowledge than me to diagnose the problem.
I hope that helps
Thanks for the reply. It crashes at start-up.
Even if I circumvent the launcher by starting it through the executable in the Binaries folder.
I will try BUGLE first, but I have my reservations as to it having to do with the launcher.
Even with Bugle I get the same error.
Is this d3d or renderthread? If so and you are using an nvidia card, run the mpo disable registry edit provided by nvidia:
https://nvidia.custhelp.com/app/answers/detail/a_id/5157
Hope that helps. Even if no error, if using nvidia, I would do this (I do).
I think it says sometimes it has to with D3D but I’m not sure. I use a Radeon RX 6700XT.
So I don’t think Nvidia settings will help me.
I think with radeon it may be solved by switching your docp (?) setting, or so I’ve read.
Also check here and elsewhere similar:
https://www.partitionwizard.com/partitionmanager/failed-to-create-d3d-device.html?amp
It’s an Unreal thing independent of CE so the fix is hardware dependent.
Sorry, dude. This didn’t help either. Getting a bit frustrated at this point.
I’ve been trying to get it to work for 3 days now…
A bit of extra information.
I have the following setup:
CPU: Intel® Core™ i9-12900KF - 16 Cores
Motherboard: MSI MAG Z690 TOMAHAWK WIFI
RAM: Corsair Vengeance RGB Pro 64GB DDR4-3200
GPU: AMD Radeon RX 6700XT 12GB
SSD M.2 1000GB Kingston NV1 (1x)
Samgsung EVO 1000GB (2x)
PSU: 1050 Watt Cooler Master
I run a Samsung curved monitor through the display port output of my GPU.
I am running Windows 11.
The exact message is: The UE4-ConanSandbox Game has crashed and will close. With a sub-message saying: Fatal error!
This is all I get from the error itself.
And here are the most recent logs:
ConanSandbox-backup-2024.04.25-23.47.41.log (9.3 KB)
ConanSandbox-backup-2024.04.25-23.48.45.log (10.9 KB)
ConanSandbox-backup-2024.04.25-23.55.17.log (23.7 KB)
ConanSandbox-backup-2024.04.26-00.23.20.log (9.7 KB)
ConanSandbox.log (9.4 KB)
Delete your logs folder altogether and try again (the one you got those from, ConanSandbox\Saved\Logs)
Alright, then here is the new one.
ConanSandbox.log (9.7 KB)
Edit: The GPU driver has been updated 9 days ago and since I haven’t been prompted by either Windows or AMD’s Adrenaline to update it, I assume it is up to date. (I added this, since the log couldn’t get the information about the GPU driver. No clue if this is of any concern to this problem).
There wasn’t supposed to be a new one
The reason I told you to delete them is because one of the potential causes of a crash that looks exactly like yours is certain data ending up in one of the files in that folder. It will cause the same crash on load with the same message that lacks any info and the same log that’s cut very short.
Obviously if you in fact deleted the entire folder and got a crash even after, then that’s not the cause in your case.
Your game crashes very early btw, the log hasn’t really got any usable information.
Make sure you have the latest driver from AMDs website installed. I know this might be obvious and maybe you tried it first, but you haven’t mentioned it in this thread and you’d be surprised at the amount of people trying to play with stock windows drivers or jank downloaded by “driver finder” apps etc.
Also try disabling any form of overclocking, or if you’re handy with that stuff, then you might try a temporary downclock by about 25 mhz on the GPU to see if that helps.
Oh, you mentioned it while I was typing
It’s weird though. I open the launcher, start the game and I do get the intro cinematic in windowed version of the game while receiving the UE4 crash… But as long as I don’t click on the error prompt… The game keeps booting…
That is yet again the exact symptoms of the issue I described… maybe try deleting the folder a couple of more times for good measure…
Like close down the game the launcher… delete the whole Logs folder… and then restart
I deleted the entire log folder. And I did not have any overclock settings going at all when I downloaded the game. I now do have a CPU XMP going, but not on the GPU.
I will reboot now and try to downclock it in the BIOS. BRB. (Once the game re-installed… again. On a different SSD this time.)
Yea, alright.
It’s weird though, cuz with that last piece of information that your game doesn’t actually crash till you hit the button… that’s textbook silent event problems. When you have an actual crash, the game window instantly disappears, when you get this “fake crash” it stays… but so far for every single person, deleting the logs let them start the game after 
You might have an unstable xmp profile going. Sometimes you have several ram speed options to choose from.
Yeah, I don’t know dude… My brother and I both bought the game on the same day. And his is working… and mine isn’t. xD
Out of curiosity, how much power does your PSU supply and is your PC fairly clean? If you run close to the max of your power supply, every ounce of heat dissipation can matter.
Nvm 1050 I see it. I’d still check for lint.
I don’t know if that’s the issue, though. Because I just set-up that XMP (EZ mode memory and CPU XMP default OC-profiles).
But I only just turned those on.
I had this problem before turning them on as well. 
Thanks for trying though, I do appreciate it. Because I don’t have the slightest clue about fixing this kind of stuff…
