Failed creating render backend ошибка

So I had this problem too with both my copies of Imperator Rome and CK3. I tried fixing it the same way I fixed my Imperator and it seemed to work.

1. Go into the drive you saved your CK3 files in (the one you saved it in when you installed the game)

2. Find the «SteamLibrary» folder (or bypass steps 1-4 if you did not buy it through steam)

3. Go into «steamapps» folder

4. Go into «common» folder

5. Go into your «Crusader Kings III» folder

6. Go onto the «binaries» folder

7. Copy and paste the «d3dcompiler_47.dll» file onto your desktop

8. Delete the «d3dcompiler_47.dll» file from the «binaries» folder

9. Restart computer

10. Try launching the game

The reason I say copy and paste the «d3dcompiler_47.dll» file onto your desktop is sometimes you will get the error again (or at least I did) and the way to fix it is you have to (for an unknown reason) copy and paste it back into the «binaries» folder. If you run into the error again you have to do these steps again.

Its kind of annoying, but it did work for me.

Also, with Imperator I have not yet ran into this error again since the last update, so it could be a stability thing that will eventually be fixed through updates.

The game won’t start properly on Windows 7!
You must have the d3dcompiler_47.dll issue, hence you are missing Service Pack 1 from windows update on windows 7! (На 10-ке тоже актуально)

The game won’t start properly on Windows 10!
Microsoft released an update on April 9th so please make sure you have the latest update and see if that solves it::Войдите или зарегистрируйтесь, чтобы увидеть скрытое содержимое.

«Failed to create render background», any idea what this is about?
This is the update that is required _on top of_ Win7 SP1 (see above). It will fix any instances of the render error, or win7 crash on startup. Войдите или зарегистрируйтесь, чтобы увидеть скрытое содержимое.

The game crashes once I reach the month of November
This is an issue we’ve seen a number of reports on. We’re currently investigating it. Our apologies to those affected
UPDATE: When in main menu hit the ~ key then type Th then hit tab. It should show a command, then hit 4 and enter — this should fix the problem.

The game is «stuttering» heavily when unpaused
Please help us out by posting your CPU and GPU specs in Войдите или зарегистрируйтесь, чтобы увидеть скрытое содержимое. Also tell us if you are playing on ironman or not.

Hi there,
I’m having some some issues with GDM/gnome-shell/Nvidia, but I can’t really figure out whats going on. After a normal reboot, my system just got stuck after opening up mu LUKS crypt without any boot messages being printed. I don’t even recall having updated before or something like that. I believe it happened spontaneously.

I vaguely recall a very similar case in recent history, which was solved by switching my proprietary nvidia driver from the rolling-release to the lts version, as my graphics card rolled out of support. So I grabbed my rescue thumb drive, chroot’ed into my system and just ran a full system upgrade. After this, at least new messages appeared during boot, but the system still gets stuck at

. I also disabled all gnome extension, but that didn’t help either. There also was a similar case with the dropbox.service going rampage with resulted in gnome-shell not starting, but I disabled it and the logs show none of that kind of problem.

Maybe a few words about my system:
I’m using a Lenovo T430, which features the Optimus Technology for hybrid graphics; so I have an internal Intel graphics chip and an external Nvidia GPU. Because I need the performance and couldn’t setup bumblebee or primus correctly a few years back, I just disabled the intel chip and am running the Nvidia card all the time ever since. lspci says the following about my graphics card:

NVIDIA Cooperation GF108M [NVS 5400M]
    Subsystem Lenovo GF108M [NVS5400M]

The following packages match pacman -Qs nvidia

libvdpau 1.1.3+3
libxnvctrl 396.51-1
nvidia-390xx 390.77-14
nvidia-390xx-utils 390.77-1
nvidia-cg-toolkit 3.1-4

I also have the lib32 versions installed.
I also have the nouveau drivers installed, but I believe I’m using nvidia. Unfortunately switching ttys with ctrl-alt-f does not work in the non-booting state and I personally can’t tell from the logs, some help to get certainty here would be well appreciated. The rescue system from the thumbdrive lists nouveau as loaded.
pacman -Qs nouveau yields

plus the lib32 version.

Seeing this I added

to my

/usr/modprobe.d/nvidia-390xx.conf

, but that didn’t change anything. Previously the file only contained  the nouveau blacklist.

I also tried reinstalling the nvidia driver—to no effect. I also tried removing the nouveau blacklist entry in the nvidia modprobe config and added some xorg configuration according to the wiki to test if the nouveau driver was working. Now the system keeps creating more c2, c2, c3, … sessions for gdm and keeps crashing.

I’m really clueless at this point. I don’t know graphics card stuff, x, gdm enough to be able to debug it or find further information. Also I can only inspect the system from the rescue thumb drive, so I’m not even entirely sure which drivers are loaded etc. All I can do is look at the logs. If you have any hints, that would be great!

Here is some excerpt from my last boot log (I can’t easily post everything, since I can only look at the logs using the cli-only rescue disk and have to manually copy everything here using my roommates computer. )

...
systemd: Started Daemon for power management.
gnome-shell: Failed to create backend: Could not find a primary drm kms device
gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop
gnome-session-binary: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gdm: GdmDisplay: display lasted 1,08569 seconds
systemd-logind: Session c1 logged out. Waiting for process to exit
systemd-logind: Removed session c1
gdm: Child process -516 was already dead
gdm: Child process 439 was already dead
gdm: Unable to kill session worker process
...
/usr/lib/gdm-x-session: <config yadayada>
/usr/lib/gdm-x-session: Load Module  nvidia
/usr/lib/gdm-x-session: Loading /usr/lib/xorg/modules/drivers/nidia_drv.so
...
/usr/lib/gdm-x-session: Fatal server error:
/usr/lib/gdm-x-session: (EE) no screens found(EE)
...

this repeats a couple of times with the c1 user number increasing.
I hope this helps, if you need me to copy more gdm-x-session output, or some other parts of the log, please let me know. In the meantime I’ll look into a possibility to copy the logfile to somewhere wehre I can easily paste it. Same is true for the /var/log/Xorg.0.log file, which might be useful?

Thanks so much!

Edit:
I managed to mount another thumb drive and copy the logs. Could’ve thought about that earlier.
This is journalctl -e > journal.log. For some reason -b -0 just gives me an empty less and -b -1 the second-to-last boot. So I resided to this method. Maybe be so kind and teach me how to properly use and export with journalctl.
This is /var/log/Xorg.0.log.

Last edited by Ps0ke (2018-09-11 21:23:44)