Помогите с Unreal Engine 4
Привет ребята. При экспорте игры из unreal engine 4 происходит следующее: Все идет нормально потом начинается компиляция шейдеров и через минут 20 ком зависает намертво. Когда он отвисает я получаю оповещение о том что unreal engine крашнулся.
Кто знает в чем проблема?
Fatal error: [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Util.cpp] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 — ‘INTERNAL_ERROR’)
UE4Editor_D3D11RHI!TerminateOnDeviceRemoved() [d:\build\++ue4\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:208]
UE4Editor_D3D11RHI!VerifyD3D11Result() [d:\build\++ue4\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:256]
UE4Editor_D3D11RHI!FD3D11Viewport::PresentChecked() [d:\build\++ue4\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11viewport.cpp:390]
UE4Editor_D3D11RHI!FD3D11Viewport::Present() [d:\build\++ue4\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11viewport.cpp:570]
UE4Editor_D3D11RHI!FD3D11DynamicRHI::RHIEndDrawingViewport() [d:\build\++ue4\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11viewport.cpp:716]
UE4Editor_RHI!FRHICommand ::ExecuteAndDestruct() [d:\build\++ue4\sync\engine\source\runtime\rhi\public\rhicommandlist.h:726]
UE4Editor_RHI!FRHICommandListExecutor::ExecuteInner_DoExecute() [d:\build\++ue4\sync\engine\source\runtime\rhi\private\rhicommandlist.cpp:351]
UE4Editor_RHI!FRHICommandListExecutor::ExecuteInner() [d:\build\++ue4\sync\engine\source\runtime\rhi\private\rhicommandlist.cpp:622]
UE4Editor_RHI!FRHICommandListExecutor::ExecuteList() [d:\build\++ue4\sync\engine\source\runtime\rhi\private\rhicommandlist.cpp:672]
UE4Editor_RHI!FRHICommandList::EndDrawingViewport() [d:\build\++ue4\sync\engine\source\runtime\rhi\private\rhicommandlist.cpp:1585]
UE4Editor_SlateRHIRenderer!FSlateRHIRenderer::DrawWindow_RenderThread() [d:\build\++ue4\sync\engine\source\runtime\slaterhirenderer\private\slaterhirenderer.cpp:1111]
UE4Editor_SlateRHIRenderer!TEnqueueUniqueRenderCommandType >::DoTask() [d:\build\++ue4\sync\engine\source\runtime\rendercore\public\renderingthread.h:198]
UE4Editor_SlateRHIRenderer!TGraphTask > >::ExecuteTask() [d:\build\++ue4\sync\engine\source\runtime\core\public\async\taskgraphinterfaces.h:847]
UE4Editor_Core!FNamedTaskThread::ProcessTasksNamedThread() [d:\build\++ue4\sync\engine\source\runtime\core\private\async\taskgraph.cpp:686]
UE4Editor_Core!FNamedTaskThread::ProcessTasksUntilQuit() [d:\build\++ue4\sync\engine\source\runtime\core\private\async\taskgraph.cpp:583]
UE4Editor_RenderCore!RenderingThreadMain() [d:\build\++ue4\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:340]
UE4Editor_RenderCore!FRenderingThread::Run() [d:\build\++ue4\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:471]
UE4Editor_Core!FRunnableThreadWin::Run() [d:\build\++ue4\sync\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:96]
когда рассекретят спеки твоего компа тогда приходи
телепаты в отпуске
Engine source runtime windows d3d11rhi private d3d11util cpp
LowlevelfatalError [File:D:\ArkSVN-Gen1Develipmenet\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line:201] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 — ‘INTERNAL_ERROR’)
I have already verify the files, only 2 files was missing, and still didn’t work.
Using this as my launch settings «-USEALLAVAILABLECORES -sm4 -d3d10» of course without the «».
I was playing the game just fine. After this update, it crashes every time.
Giving me that link doesn’t help, already tried all of those and can’t do settings when can’t even load Ark. instant get error.
There should be an option to reset your graphics settings, on the little window that pop’s up when Ark Launches.
Also for some people more recently, driver updates and turning off image sharpening (NVidia Control Panel -> Manage 3D Settings), seem to help mitigate the problem.
Also might be worth trying to remove the launch options, and see if that removes the crash, it might not even be related but might as well try to rule out possible problems right ?
PS:
«-USEALLAVAILABLECORES» — Is no longer needed for as far as i know.
«-sm4» — Forces DirectX 10 shaders/lighting
«-d3d10» — Simply forces everything to DirectX 10.
So technically speaking you only need «-d3d10», as it will already do what ever «-sm4» does.
Not sure why some FPS guides keep recommending to mix and match, but i recon you just copy and pasted those from one.
Giving me that link doesn’t help, already tried all of those and can’t do settings when can’t even load Ark. instant get error.
There should be an option to reset your graphics settings, on the little window that pop’s up when Ark Launches.
Also for some people more recently, driver updates and turning off image sharpening (NVidia Control Panel -> Manage 3D Settings), seem to help mitigate the problem.
Also might be worth trying to remove the launch options, and see if that removes the crash, it might not even be related but might as well try to rule out possible problems right ?
PS:
«-USEALLAVAILABLECORES» — Is no longer needed for as far as i know.
«-sm4» — Forces DirectX 10 shaders/lighting
«-d3d10» — Simply forces everything to DirectX 10.
So technically speaking you only need «-d3d10», as it will already do what ever «-sm4» does.
Not sure why some FPS guides keep recommending to mix and match, but i recon you just copy and pasted those from one.
Engine source runtime windows d3d11rhi private d3d11util cpp
LowLevelFatalError [File:D:\ArkSVN-Gen1Development\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 201]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 — ‘INTERNAL_ERROR’)
VERSION: 309.4
KERNELBASE.dll!UnknownFunction (0x00007ffb9153a859) + 0 bytes [UnknownFile:0]
ShooterGame.exe!FError::LowLevelFatal() (0x00007ff7381b6b75) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\core\private\misc\outputdevice.cpp:354]
ShooterGame.exe!TerminateOnDeviceRemoved() (0x00007ff73858a370) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:214]
ShooterGame.exe!VerifyD3D11Result() (0x00007ff73858a57c) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:250]
ShooterGame.exe!FD3D11EventQuery::WaitForCompletion() (0x00007ff73857a019) + 313 bytes [d:\arksvn-gen1development\engine\source\runtime\windows\d3d11rhi\private\d3d11query.cpp:168]
ShooterGame.exe!FD3D11DynamicRHI::RHIEndDrawingViewport() (0x00007ff73858df0e) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\windows\d3d11rhi\private\d3d11viewport.cpp:619]
ShooterGame.exe!FRHICommandListExecutor::ExecuteInner_DoExecute() (0x00007ff7385ec7e8) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\rhi\private\rhicommandlist.cpp:249]
ShooterGame.exe!TGraphTask ::ExecuteTask() (0x00007ff7385f2f64) + 32 bytes [d:\arksvn-gen1development\engine\source\runtime\core\public\async\taskgraphinterfaces.h:871]
ShooterGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff7381257f8) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\core\private\async\taskgraph.cpp:939]
ShooterGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff7381249ad) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\core\private\async\taskgraph.cpp:680]
ShooterGame.exe!FRHIThread::Run() (0x00007ff7385f7b72) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\rendercore\private\renderingthread.cpp:226]
ShooterGame.exe!FRunnableThreadWin::Run() (0x00007ff738207636) + 0 bytes [d:\arksvn-gen1development\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff7382074f8) + 8 bytes [d:\arksvn-gen1development\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007ffb91ca7bd4) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ffb937eced1) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ffb937eced1) + 0 bytes [UnknownFile:0]
Specs:
i7 8700k
RTX 2060
32 GB 3000MHZ RAM
Steam is the only application open when trying to play. Uninstalled the game a couple months ago and it was fine. Now, it is completely unplayable. Any help would be greatly appreciated
D3D errors are pretty common errors with any Unreal Engine games.
We need your actual specs from what Steam detects — but you can start with the obvious:
1. Ensure your drivers are up to date. Like. really.
2. Check your in-game settings. RTX cards had issues with Shadows on Higher settings — might be fixed. or not, but generally, leave those on Low — they’re FPS hogs anyhow.
3. Do make sure it’s not running on the iGPU if you have one. it does happen more than you’d think.
Anyways, start with these steps — try again — then come back with more details if things keep getting messy.
Engine source runtime windows d3d11rhi private d3d11util cpp
Games that crash, won’t launch or suffer from stability issues are undoubtedly the most frustrating part of PC gaming. Although we strive to deliver a flawless gaming experience in the depths of Hoxxes IV, we can’t guarantee you won’t encounter a crash or stability issue at some point during your employment at Deep Rock Galactic. This is in part due to the iterative nature of game development in an early access stage but also because everyone has different hardware and PC specifications.
If you find yourself in an annoying predicament where the game crashes frequently, don’t panic! Take a deep breath and follow the steps below. More often than not we know a reliable solution to your problem.
Restart your PC and ensure the crashes are consistent. This tried-and-true method for fixing things does sometimes work, as it’s possible you’re running into memory problems and just need to clean house. If it doesn’t work, at least you’ve ruled out the easiest fix.
If you’re overclocking your CPU or GPU, stop it, at least for now. Even if every other game runs fine, it’s best to rule out overclocking as a cause. You can always reinstate the overclock later.
Copy the crash report, provided in the Ghost Ship Games Crash Reporter that appears when the game terminates. Paste it in a document and save it on your PC. Send and close the crash report. (Screenshot here!) [i.imgur.com]
Take note of the first couple of lines in the crash report and look for its reference below. From a troubleshooting standpoint, these are the most important pieces of information you can gather in relation to your crash.
Troubleshoot the issue using the most common workarounds detailed beneath the respective crash report. If the workarounds described here don’t work, head back to the Bugs + Crashes subforum and search for your crash there.
If you encounter a crash that prevents the game from launching entirely, restart your PC. If that doesn’t resolve it, verify the integrity of the game files by right-clicking the game in your Steam Library > Properties > Local Files > Verify Integrity of Game Files. If that doesn’t resolve it, run UE4PrereqSetup_x64.exe as Administrator located in steamapps\common\Deep Rock Galactic\Engine\Extras\Redist\en-us.
As a last resort, you can try to add «-dx12» to the launch options by right-clicking the game in your Steam Library > Properties > Set Launch Options. Beware that forcing DirectX12 with this method is known to cause graphical oddities throughout the game.
The crashes described below are the most common crashes reported by the Deep Rock Galactic community. Work your way through the steps beneath your respective crash and see if that restores your game to a playable state. If you are still experiencing crashes afterward, feel free to leave a reply on this topic and we’ll assist you to the best of our ability.
Please be advised that some crashes may be related to Unreal Engine and thus not exclusive to Deep Rock Galactic. As such, it may be worth trying to boot up another game built on Unreal Engine (e.g. Fortnite, Mordhau) and see if your issue also occurs there.
This crash is one of the most frequent crashes we’re seeing and relates to an Intel Integrated HD graphics drivers issue, presumably inflicted by a faulty Windows update.
- Step 1
First of all update your Intel HD graphics drivers, directly from Intel [downloadcenter.intel.com] . If you find that the versions of the latest driver on the website and that of the driver installed on the computer are the same, I would suggest you uninstall and reinstall the current version of display driver to try and fix the issue.
Step 2
Restart your PC and boot up the game again. Are the crashes still occurring? If not; fantastic! If the crashes have not been resolved, resume with step 3.
Uninstall Intel HD graphics drivers and use normal drivers instead.
This crash log indicates GPU issues, often related to overheating.
- Step 1
Head into the in-game Options and try to limit your FPS in the 60 — 120 range or enable Vsync. Some players have reported that allowing the FPS of the game to spool into higher ranges can cause crashes for some GPUs.
Step 2
Update your graphics drivers if Step 1 yields no success. Still crashing? Proceed to step 3.
Step 3
Perform a clean uninstall of the game and delete all residual files and folders related to Deep Rock Galactic on your PC.
This crash has many manifestations but is most commonly related to your graphics card drivers.
- Step 1
Perform a clean uninstallation of your GPU drivers. We recommend this tool [www.guru3d.com] as long as the guidelines for recommended usage are followed.
Reinstall the latest GPU driver for your graphics card.
This crash log relates to the game engine Deep Rock Galactic runs on.
- Step 1
Install the Epic Games Launcher
Step 2
Open up the Epic Games Launcher
Step 3
Click on the yellow and black downward arrow beside Launch
Step 4
Click on Options
Make sure that there is a check-mark beside ‘Editor symbols for debugging’ and press Apply
Occasionally, a connection issue between Steam and the game may be preventing you from playing. This is indicated by a loading screen with the text «Waiting for Steam to load». [i.imgur.com]
First of all; try to restart your PC. If that doesn’t resolve it, end all Steam related processes via the Task Manager and restart Steam. Ensure Steam isn’t at fault by messaging someone on your friends list. Did your friend receive your chat message? Perfect. You have a connection to Steam. Boot up the game and see if your issue has been fixed.
If that doesn’t resolve it head into the quarantine settings of your anti-virus and restore all DRG-related files that may have been caught in the quarantine. Closing your anti-virus or adding an exception for the game in the settings is rarely sufficient. You must ensure that no DRG related files have already been isolated in the quarantine.
Last but not least, running dedicated servers for other games can be the cause of a connection conflict. Close any dedicated servers that may be running in the background and see if that fixes your issue. This has for instance been the case for players running Mordhau servers and Conan Exiles servers.
Some players report unusual connection issues that manifest themselves by preventing players from joining or hosting servers on the server list, causing random, unexplainable loss of connection to games mid-mission or weird in-game behavior like no weapons, the inability to jump, clipping into terrain, etc.
If you are a victim to these symptoms, forcing your PC to reset your IP stack/network adapter can alleviate the problem:
- Step 1
Right-click your network adapter and select ‘Properties’. Disable ‘IPv6’.
Step 2
Run Command Prompt as administrator. Command Prompt is most easily be located by searching for ‘cmd’ in the Windows Start Menu.
Step 3
Enter the following commands in the Command Prompt.
Type netsh int ip reset then press Enter.
Type netsh winsock reset then press Enter.
- Nvidia Ansel is notorious in the community for causing performance issues. Try to update Nvidia Ansel. If that doesn’t work, disable it completely.
If you are running a PC configuration with AMD FX Series components and/or Realtek Audio, refer to the following Steam Topic for help:
https://steamcommunity.com/app/548430/discussions/2/1729827777339086202/
Disable ‘Anti-Lag’ in the AMD Radeon™ Software
If your game refuses to launch entirely even after reinstalling and downloading DirectX, try to add «-dx12» to the launch options by right-clicking the game in your Steam Library > Properties > Set Launch Options.
If the game crashes on startup, try to add «-regenerateinis» to the launch options by right-clicking the game in your Steam Library > Properties > Set Launch Options. Beware that this launch option will reset all options to their defaults.
Are you suffering from unresponsive mouse clicks? Change your game to fullscreen and your native resolution. That should do the trick.
