#Thread
1 messages ยท Page 1 of 1 (latest)
Can you try using the command line argument "--vulkan-device-index 1" in your steam settings for the game? (it would be better to find the setting in your driver though)
can you upload the log again?
ok.. that should work - it doesn't list your 4070 in the log file at all - that is why the command line argument doesn't work
so now what can i try?
So the game did work before the update?
we have to convince windows (and your amd driver) to let us use the 4070 ๐
I'm looking for a way to do that right now
did you try to disable the amd device in your device manager?
(assuming you don't need that for anything)
not sure but i can look
i disabled
ok. that should help enshrouded to find the nvidia gpu
should i take out the command i put in?
yes please
same graphics error popped up
[E 00:00:00,095] [graphics] vkCreateInstance failed with error 'VK_ERROR_INCOMPATIBLE_DRIVER'
[E 00:00:00,095] [graphics] Could not create vulkan instance! error=wrong version
ok.. very interesting
do you have current nvidia drivers installed?
yes, that was one of the first things i tried to update
very strange
i agree with that
I'm not on a nvidia gpu right now - but isn't there a list of 3d settings in the nvidia control panel?
can you check if there is a setting for enshrouded?
in the program settings tab
is there a setting for vulkan rendering gpu or something?
not that i can see
Did you update your amd graphics drivers lately?
Because I found someone having a similar problem - and it was solved by installing a current amd driver (for the gpu we don't want to use) - so you could try that - probably good idea to enable the device again before you do that
i don't think so unless it does it automatically with windows
probably - it's windows ๐
yeah
crashed. should i disable the amd again in device manager?
can you give me the log file first please?
no change unfortunately
so now what?
[I 00:00:00,119] [graphics] - driver info: 24.12.1 (AMD proprietary shader compiler)
ok.. you got the new am driver - that worked
so do i let the system choose?
can you please open up the amd driver ui ?
right click on the desktop -> amd radeon settings
system -> switchable graphics
ok.. there is a third way: https://www.amd.com/en/resources/support-articles/faqs/GPU-110.html
sorry, not seeing the switchable graphics
yeah.. it seems the link I posted is the new way
(sorry - don't have my amd in right now)
trying to follow the instructions
i try to launch and it gives me the doesn't meet minimum requirements error
what did you set it to?
nvidia should be correct
i disabled the amd
ok
should i upload it?
not necessary now - i just need the log
no .. it's still using the wrong one
ok.. another thing we can try
do you know how to edit environment variables on windows?
been a while but i think i can find it
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1 = 1
that should disable the amd layer that tries to force the amd gpu to be picked
ok. should i re-enble the amd
that shouldn't matter at this point
or just try again?
just try it
log file please ๐
and you are sure the environment variable is set correctly?
copy and pasted
can you post a screenshot please ?
ok.. do you start the game through steam?
yes
can you please restart steam?
sure
the ini looks correct to me but it still lists the VK_LAYER_AMD_switchable_graphics in the log
that shouldn't happen
did you restart the steam application?
no.. once is fine
it's just that the environment variables are copied when a process starts
i can't imagine i'm the only one having this issue
either that or i'm just that special
no - but I'm not the best customer supporter - sorry
๐
can you please try starting enshrouded with the command line argument "--keep-vulkan-layers" ?
no
just checking
yeah - good idea
ok.. do you know how to use the registry editor? ๐
(pulling out the big guns now)
yes
"Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ImplicitLayers"
this is a list of so called implicit vulkan layers
these are 'plugins' for vulkan and loaded automatically
i'm there
there should be an entry for the VK_LAYER_AMD_switchable_graphics
can you show me the list? i don't know the exact name unfortunately
oh.. interesting - these two are fine - can you check "HKEY_CURRENT_USER\Software\Khronos\Vulkan\ImplicitLayers" then?
that is the other place
no Khronos entry?
no - it's fine that means there are non
ok
ok.. another thing we can try is to install the newest vulkan runtime from https://vulkan.lunarg.com/sdk/home#windows
there is the Runtime Installer here https://sdk.lunarg.com/sdk/download/1.4.304.0/windows/VulkanRT-1.4.304.0-Installer.exe
that installs the newest vulkan 'loader' - and the handy vulkaninfo.exe
you should be able to run vulkaninfo.exe now from the start menu
it looks a bit like this..
long list of text
there is a section called device properties and extensions
that should list your nvidia 4070
WARNING: [Loader Message] Code 0 : windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_AMD_switchable_graphics uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD C:\Windows\System32\DriverStore\FileRepository\u0410212.inf_amd64_daae2c8b5eb35aaa\B409877.\amdvlk64.dll. Skipping this driver.
ERROR: [Loader Message] Code 0 : terminator_CreateInstance: Found no drivers!
Cannot create Vulkan instance.
This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan.
ERROR at C:\j\msdk3\build\Khronos-Tools\repo\vulkaninfo\vulkaninfo.h:456:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVER
ok.. interesting - pretty much the same error we get in the game
but the install completed successfully
ok.. do you now the program called DDU ?
Display Driver Uninstaller (DDU) is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store). The AMD/NVIDIA/INTEL video drivers can normally be uninstalled from the Windows Contro...
it's a tool to completely remove an existing gpu driver - which windows sometimes doesn't manage to do
so the plan would be to use that tool to completely uninstall the amd driver - and then we can install it again (the newest one) - because it looks like there is some remains from an old amd driver in your system
https://www.wagnardsoft.com/forums/viewtopic.php?t=5191 that is the link to the download
yes
you can select which driver it should remove
alternatively we could try a normal 'clean' install of the amd driver first
it looks like this
on the rigth side you select GPU + AMD
and leave the other settings as is
then press clean and restart on the top
yes
that doesn't look correct - did you get an error message?
nope
can you check if the file c:\windows\SysWow64\vulkaninfo.exe exists?
got it to run
different output than before?
ideally there would be your nvidia gpu in the list of devices ๐
in the "device properties and extensions" section
the section lookl like this
you probably have to scroll up quite a bit
not seeing the nvidia just the amd
that is sad
but you don't get the error that you got before?
so did you install the amd driver? Or did windows do that automatically?
GPU0:
VkPhysicalDeviceProperties:
apiVersion = 1.3.280 (4206872)
driverVersion = 2.0.302 (8388910)
vendorID = 0x1002
deviceID = 0x164e
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = AMD Radeon(TM) Graphics
pipelineCacheUUID = a0bf0c9a-559e-5522-bccf-038566bafc98
looks like windows did it on it's own
ok.. can you upload the log again please?
no, that is sign that it didn't find your nvidia
ok.. VK_LAYER_AMD_switchable_graphics is still there
is that good or bad
that is unfortunate - because that is the thing preventing us from seeing the nvidia gpu and you from playing the game
certainly bad then
it's a bid strange - because enshrouded by default automatically sets the environment variable we talked about before - but it's still listed in the active layers - which shouldn't be the case
so how do we make it play nice?
do you have a folder c:\amd on your pc?
that is the place the amd driver is installed in
yes
there should be a folder in that with the name of the driver
says chipset driver
sorr chipset software
is there a clean install option in the amd driver installer?
i can reinstall the adrenalin package i downloaded
yes - and check if there is a checkbox in the installer to do a 'clean' or 'full' install
not sure how it's called for amd
ok
ok.. lets try again
launching the game, right?
yes
that's not good
I'll send an email to an amd contact - maybe they have an idea. I do have to go now though - it's 1:39am here and I really have to sleep
sorry for keeping you so late. get some rest
sorry that I wasn't able to fix your issue (yet)
i know you will figure it out. i will check back tomorrow
Hi! I'm Florian another graphics engineer at Keen ๐
Could you please try to cleanly remove the Nvidia driver and reinstall that? If that does not work it would be great to set this environment Variable VK_LOADER_DEBUG=all
that would possibly tell us why the vulkan loader is declining your Nvidia driver in the first place
should i try to disable the intgreated GPU first?
sorry for the delay, just got home from work
where do i put the variable? in the steam settings?
'
there was not an option to disable in the bios that i could find. only priority, which in my nvidia
Okay, @strange lynx - so you already have the "big guns" looking into your issue. They are on German time there, so their office hours are a bit weird for us who are elsewhere in the world.
The only suggestion I would maybe have that I don't think they have touched on is to either reinstall Vulkan (you already have the latest version) or since that version of Vulkan is relatively new, maybe try installing the 1.3.296.0 version of it instead. It's kind of a "Hail Mary" idea, though.
But frankly, the two people that have helped you already know way more about this than I do - so you are in good hands there, and I would continue to try and work with them on the issue.
thank you very much.
i just tried the fresh install and that did not work either
of the graphics drivers
i will just try and be patient and hopefully they can find a fix
Did you use DDU to uninstall your current drivers, or just the fresh install through your GPU software?
yeah sorry, then I would wait for them to get back in the office, and hopefully they'll have more insight after talking to their contact at AMD.
i don't get home till 530pm eastern time
thank you for trying
and i just got the pc in december too
I just looked at the log you posted and I am not seeing the AMD GPU stuff in there at all anymore. (though I can't read it like they can).
You should probably toss it in here so that they have it when they come on - to keep the information all in one place.
i dont know if it matters, but this is the first time i have seen Vulkan 1.4 in a log. Is it possible the game has a compatibility issue with the new Vulkan version? i dont know how backwards compatible Vulkan is on major releases. Trying an older driver might be a useful test if you haven't already tried it.
thank you
Alright, the log says that enshrouded was now able to find your RTX 4070 SUPER and selected it for rendering. Progress! ๐
From the looks of it there is something going awry in the creation of the rendersystem but the log won't tell what that is
is there an enshrouded.dmp file next to the log? I would be very interested in that
The crash dumps will be located in a folder named "crash_dumps' in the same directory you have been getting your log from. Each crash is organized into it's own directory when you click on it. The part before the underscore is the YYMMDD of the crash itself.
It will have a .log file, .info file, and sometimes a .dmp file, which is what they are asking for.
it should be here: SteamLibrary\steamapps\common\Enshrouded\crash_dumps
SteamLibrary is just the place where you have installed steam, for me that is C:\Program Files (x86)\Steam\
just did a file integrity check and tried to launch the game again. I was able to click play and choose hosted game and then screen went black and computer locked up
no new crash dump file though
i was so excited that it at least launched
There is progress!
Let's try and go through the rest of the minidump steps to at least see if we can't get it more stable, while they look into your .dmp file
Liandry's tool would be next:
- Type
Powershellin your window's search bar - Right click on the "Windows Powershell" program that comes up and click "Run as Administrator"
- Type the following command in the window that pops up:
irm "https://raw.githubusercontent.com/LiaNdrY/Enshrouded-Tool-Fix/main/Enshrouded_Tool_Fix.ps1" | iex - Restart your computer after it's complete.
then check your game and lets see if that had any impact.
Okay. (sorry about the delay, getting ready to head to a doctor's appointment) The next step is to rename the the enshrouded_user.json located in your enshrouded game folder.
You can access the file by opening up your Steam library and right clicking on "Enshrouded" in the list. Click on "Properties" and then "Installed Files" in the main box, click "Browse" and this will open up your game folder.
It doesn't matter what you rename it to, as long as it's not the same as the name it is currently.
Alright, and If I recall, you have already used DDU and reinstalled your drivers?
yes, ma'am
Okay. So those steps just went through the "obvious" and since we already have WaitForPresent looking into the issue, I'd say that's probably the best bet.
I would probably include the latest dmp file in here just to make sure they have the latestinformation with the few fixes we just tried.
i will check to see i there is a new dump file now
just the one from the 29th, nothing new
Okay, thanks. Hopefully that can help them find out the issue.
hope so. really do enjoy the game. was making great progress
Thanks for the data! I looked at it and they are two different issues one of which is a device loss (which means your GPU did not respond back within a 2 second time window). We currently only have limited tooling to debug this on user PCs. One thing you could try is to launch the game with the command line argument "--enable-gpu-breadcrumbs" that will make the game run slightly slower on the gpu but will hopefully report back in which part of the code the device loss happened.
Could you also please always upload the .log and the .dmp file together? That helps alot with analyzing what is going on ๐
there isn't always a dump file
the only .dmp file in the folder is the one from 1-29
I'm really wanting to get back to playing the game.
any more thoughts on what to try?
another attempt to lauch. I reenabled amd onboard graphics. game got to the point of chosing type of game. tried to chose hosted and that is when it crashed.
still no crash dump data
could you maybe try to launch with --disable-ioring?
it's a stretch but the logs really don't tell us anything here which is really surprising ๐ค
crashed my pc again
The log does say though that the game is using the ioring api which is supposed to be only available on windows 11
You do have windows 10 right?
Your OS reports to us as Windows 10 Home ๐ค
What I mean is that at game launch, we ask for the OS version and put that in the log file and your OS seems to report itself as windows 10 Home. Which is super strange ๐ค
seems to be my luck.
hopefully we can get it figured out. I really want to get back to playing. The pc is not that old, I got it back in December
yeah no the pc specs themselves are more than enough to run the game
did you run the game before on this pc? Or on a different one?
same pc. it worked great up until the update
ok, i revalidated the files and was actually able to get into the game and play for a brief time. maybe 5 minutes.
still no crash dump files
this is getting weirder and weirder not gonna lie ๐
I'll prep a special version for you to run a test on. This might take a day or two though
Often times people will set the game to run in compatibility mode for an older version of windows because various copy+paste articles on the web say to do that for every game. That changes what gets reported when the game asks. If you have done this, please undo it. The advice is only relevant for old games and may cause issues in newer games. The AI bots writing the articles do not understand the difference.
sounds good to me. so long as i can play
did not set to run in capatiblity mode as it was working prior to the update. didn't even occur to me to try that honestly
thank you very much
I sent you an access code to a beta branch. Please try it and see if you can launch the game in that version.
Ideally do not use your old character/world because they might become incompatible when saved in this branch
will do. thank you. I will let you know how it goes