Announcement

Collapse
No announcement yet.

DXGIGetDebugInterFace1 could not be located in dynamic library dxgi.dll

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    once i have my new hardware im migrating to linux ....done trying to get windows and 425 or 424.3 to work right

    Leave a comment:


  • replied
    yea were the 25% smart asses that didnt get tricked fooled or conned into windows ten phone spyware

    Leave a comment:


  • replied
    Same issue: CreateDXGIFactory2
    All users of win7 cannot lunch the game anymore. There are 25% based on statistics.

    Leave a comment:


  • replied
    Downloading .NET Framework did the trick

    Leave a comment:


  • replied
    ya i have this feeling too ....i dunno i tried that 425 engine then the control rug worked finei goto save and poof there goes the entire editor killed it
    ms needs do a serious walk back on win ten cause by time they get anywhere enar what could be used we'll all be using linux

    Leave a comment:


  • replied
    Win 7 just works. Win 10 and those plagued updates... aw man. I have win 10 installed on a laptop and it made me desire NEVER use it for game development. I'll keep developing on Win 7 and when I get near to finish my demo, I'll shift to Win10 in my new PC and cook the game there.

    Leave a comment:


  • replied
    Originally posted by Mazen IIXIS View Post
    I'm using Windows 7 and it's saying that it's missing that as well.
    For what's worth, Microsoft ended support for Windows 7 on January 22. No more patches, security fixes. Wild West for malicious software.
    I'd recommend upgrading Windows on every developer machine to Windows 10. Especially that you can get a better performance thanks to DX 12 which should be soon enabled by default.

    Leave a comment:


  • replied
    Originally posted by LowEntry View Post


    Ah thank you so much, that really helps a lot!

    That does require using the source version of the engine if I understand right?

    Do you know anything about whether Epic will fix it in future versions of the engine or whether this was intentional (as in they won't change or fix it)?

    Yes, you should use source code built version.

    I resolved this problem by read and debugged the source code. I don't known whether Epic will fix it.

    Leave a comment:


  • replied
    Originally posted by kongque View Post

    There are two solutions for resoving this problem.

    Solution 1:

    1. package your game and you got an YourGame.exe
    2. create a shortcut for YourGame.exe
    3. open shortcut property window. add -novendordevice in the target textfield.


    Solution 2:
    1. package your game, you got a folder named WindowsNoEditor
    2. Go to WindowsNoEditor\Engine\Binaries\ThirdParty\NVIDIA\NVaftermath\Win64
    3. Delete the dll named: GFSDK_Aftermath_Lib.x64.dll
    Thank you!

    Leave a comment:


  • replied
    Originally posted by kongque View Post

    You should modify the source code like below:

    1. Go to the folder: {UE4SROUCE}\Engine\Source\Runtime\D3D12RHI\Private

    2. Open D3D12Adapter.h with text editor (e.g. VS Code)

    3. Modify CreateDXGIFactory function's implementation like below:

    FORCEINLINE void CreateDXGIFactory(bool bWithDebug)
    {
    #if PLATFORM_WINDOWS || PLATFORM_HOLOLENS
    VERIFYD3D12RESULT(::CreateDXGIFactory(IID_PPV_ARGS(DxgiFactory.GetInitReference())));
    VERIFYD3D12RESULT(DxgiFactory->QueryInterface(IID_PPV_ARGS(DxgiFactory2.GetInitReference())));
    #endif
    }

    4. Recompile UE4-Editor

    That's all.

    Ah thank you so much, that really helps a lot!

    That does require using the source version of the engine if I understand right?

    Do you know anything about whether Epic will fix it in future versions of the engine or whether this was intentional (as in they won't change or fix it)?

    Leave a comment:


  • replied
    Originally posted by LowEntry View Post
    This doesn't just seem to be an inconvenient error message. When you try to run your packaged game (or when you press "Launch" in the editor), it will give the same error but with CreateDXGIFactory2, after which the game crashes. I did some digging, and apparently (if I understood correctly) it's because it needs DXGI 1.3, which is only available for windows 8+. This means that games packaged with 4.25+ will not work on windows 7 anymore.

    I don't know if this was intentional or whether it was an oversight/bug, but it currently means that the UE4 has basically dropped support for packaging to windows 7, and not in the development sense, but in the "minimum specs required to run your game" sense.


    Click image for larger version Name:	error.png Views:	0 Size:	19.8 KB ID:	1772355
    You should modify the source code like below:

    1. Go to the folder: {UE4SROUCE}\Engine\Source\Runtime\D3D12RHI\Private

    2. Open D3D12Adapter.h with text editor (e.g. VS Code)

    3. Modify CreateDXGIFactory function's implementation like below:

    FORCEINLINE void CreateDXGIFactory(bool bWithDebug)
    {
    #if PLATFORM_WINDOWS || PLATFORM_HOLOLENS
    VERIFYD3D12RESULT(::CreateDXGIFactory(IID_PPV_ARGS(DxgiFactory.GetInitReference())));
    VERIFYD3D12RESULT(DxgiFactory->QueryInterface(IID_PPV_ARGS(DxgiFactory2.GetInitReference())));
    #endif
    }

    4. Recompile UE4-Editor

    That's all.

    Leave a comment:


  • replied
    Originally posted by Amelia_P View Post

    May you tell us how to do that? Or give us a hint?
    There are two solutions for resoving this problem.

    Solution 1:

    1. package your game and you got an YourGame.exe
    2. create a shortcut for YourGame.exe
    3. open shortcut property window. add -novendordevice in the target textfield.


    Solution 2:
    1. package your game, you got a folder named WindowsNoEditor
    2. Go to WindowsNoEditor\Engine\Binaries\ThirdParty\NVIDIA\NVaftermath\Win64
    3. Delete the dll named: GFSDK_Aftermath_Lib.x64.dll

    Leave a comment:


  • replied
    Start your app with -novendordevice option can resolve this problem.
    May you tell us how to do that? Or give us a hint?

    Leave a comment:


  • replied
    Start your app with -novendordevice option can resolve this problem.

    Leave a comment:


  • replied
    This doesn't just seem to be an inconvenient error message. When you try to run your packaged game (or when you press "Launch" in the editor), it will give the same error but with CreateDXGIFactory2, after which the game crashes. I did some digging, and apparently (if I understood correctly) it's because it needs DXGI 1.3, which is only available for windows 8+. This means that games packaged with 4.25+ will not work on windows 7 anymore.

    I don't know if this was intentional or whether it was an oversight/bug, but it currently means that the UE4 has basically dropped support for packaging to windows 7, and not in the development sense, but in the "minimum specs required to run your game" sense.


    Click image for larger version  Name:	error.png Views:	0 Size:	19.8 KB ID:	1772355
    Last edited by LowEntry; 06-06-2020, 05:54 PM.

    Leave a comment:

Working...
X