How to fix EOS crash on unity in GfXPluginNativeRenderer-x64 with overlay disabled

Hello, we are receiving occasional crashes for some users on our Unity integration of EOS. I expect this is something due to overlay and GfxPluginNativeRender-x64.

It is only happening on DirectX 12, (DirectX 11 works fine). And only in builds (IL2CPP)

We havent released the game, so our user base is only internal testers. From around 30 users 2 of them having crashes (not constantly, but occasionally).

It was ~50percent crash rate before, but I noticed I was not providing `EOS_PF_DISABLE_OVERLAY` and `EOS_PF_DISABLE_SOCIAL_OVERLAY` flags. Now I included them and those users crash rate reduced to ~10percent or something.

I have read this too:

https://dev.epicgames.com/community/learning/knowledge-base/DY52K/epic-online-services-why-does-my-game-crash-or-hang-when-the-overlay-is-enabled

Everything is called from main thread. Crashes still happening with overlay disabled (only providing those flags disabled the overlay, right?), but crash rate is 0 with disabled plugin entirely.

Users dont have Epic installed

I was using unlyplugin EOS version 4.1.1. Currently updating to 6.0.0 version will check if that is happening on this version as well.

Unity version 6000.0.65f1

Crashes happens always in the same place. I can tell as in non crashing case following line are always the same:

03/02/2026 10:21:43 LogEOS(Info): SDK Config Platform Update Request Successful, Time: 12.955893
03/02/2026 10:21:43 LogEOSAnalytics(Info): EOS SDK Analytics disabled for route [1].
03/02/2026 10:21:43 LogEOS(Info): Updating Product SDK Config, Time: 12.972350
03/02/2026 10:21:43 LogEOSAnalytics(Info): Start Session (User: ...)
03/02/2026 10:21:44 LogEOS(Info): SDK Config Product Update Request Successful, Time: 13.389975
03/02/2026 10:21:44 LogEOS(Info): SDK Config Data - Watermark: -287380011
03/02/2026 10:21:44 LogEOS(Info): ScheduleNextSDKConfigDataUpdate - Time: 13.389975, Update Interval: 349.502258

068QP00001Bd65EYAR.txt (46.7 KB)
https://dev.epicgames.com/community/learning/knowledge-base/DY52K/epic-online-services-why-does-my-game-crash-or-hang-when-the-overlay-is-enabled

Hi,

I attempted to reproduce a crash using the EOS Plugin sample app with the settings you provided: EOS Plugin 4.1.1, Unity 6, DX12, Disable Overlay and Disable Social Overlay. I was unable to reproduce the crash, but the sample app is very limited in what it can test. We have made bug fixes since 4.1.1 so it’s possible an issue was resolved in 6.0.0. Please let us know your results.

When you’re setting the flags, are you using the EOS Config window or are you setting it in your own code?

-Jeff

I updated plugin to 6.0.0.

It still can be reproduced, but now for different users. I was thinking maybe it had to do something with hardware or something, but after update different users started crashing. One had 100% repro case, another had only one crash with same stack trace. And confirming that this is only happening with DirectX 12 (DirectX 11 works fine, we dont have other graphics API).

C:\Users\username\Desktop\Builds\Develop\Client\Client\AMDUnityPlugin.DLL:AMDUnityPlugin.DLL (00007FFA2ACD0000), size: 8843264 (result: 0), SymType: '-exported-', PDB: 'C:\Users\username\Desktop\Builds\Develop\Client\Client\AMDUnityPlugin.DLL'
C:\Users\username\Desktop\Builds\Develop\Client\Client\NVUnityPlugin.DLL:NVUnityPlugin.DLL (00007FFA3EAB0000), size: 1638400 (result: 0), SymType: '-exported-', PDB: 'C:\Users\username\Desktop\Builds\Develop\Client\Client\NVUnityPlugin.DLL'
C:\Users\username\Desktop\Builds\Develop\Client\Client\gameName_Data\Plugins\x86_64\GfxPluginNativeRender-x64.dll:GfxPluginNativeRender-x64.dll (00007FFA4A4E0000), size: 610304 (result: 0), SymType: '-exported-', PDB: 'C:\Users\username\Desktop\Builds\Develop\Client\Client\gameName_Data\Plugins\x86_64\GfxPluginNativeRender-x64.dll'
C:\Users\username\Desktop\Builds\Develop\Client\Client\gameName_Data\Plugins\x86_64\EOSSDK-Win64-Shipping.dll:EOSSDK-Win64-Shipping.dll (00007FF99D150000), size: 20140032 (result: 0), SymType: '-exported-', PDB: 'C:\Users\username\Desktop\Builds\Develop\Client\Client\gameName_Data\Plugins\x86_64\EOSSDK-Win64-Shipping.dll', fileVersion: 1.19.0.3

Oh, and about the flags. I tried both. At first with 4.1.1 version I was setting it manually in config file, because there was some kind of editor gui error which would not show all the settings correctly, but with 6.0.0 it was fixed and I set these flags in EOS config window.

Hi Zorian,

Thanks for the updated info. If the overlay disable flag is used, the crash shouldn’t be due to the plugin native library as it’s only called when the overlay is displayed. Something that would help us with debugging this would be if you’re able to reproduce it in the sample application. Here are instructions for how to import the sample scenes: https://github.com/EOS-Contrib/eos_plugin_for_unity/blob/stable/com.playeveryware.eos/Documentation~/samples.md

Some other info that would be useful is the dxdiag from each of the machines that previously reproduced it in 4.1.1 and are reproducing it in 6.0.0.

Are all the testers using the same version of graphics drivers and is it isolated to specific video cards?

-Jeff

I didnt do sample build yet, but I am attaching dxdiag concatenated (there might be only one file attached). Was not sure how much data is needed so adding entire logs. All devices has GeForce but different models, so it is not one card. All of them are QA that mean that they test a lot more than others. So maybe all crashes are related to share amount instead than specific graphics card, not sure.

Will be trying to reproduce same with sample application next week.

So I put Sample into my game and made a build removing all other scenes and leaving only samples. So that all the environment as Unity version, rendering pipeline etc would be the same as in our build, but no custom code would be running. We tried crashing this build, but so far - everything stable. Cant be for sure yet as this crash is super rare now, but 90% sure it indicates that “something” is wrong on our end. So far couldnt find anything useful tho.

Thanks for the update Zorian. If you end up able to repro using the sample application, we can take a look at the sample project to debug it.

Hello Zorian.

On my side I tested the scene and the build and it does not crash. Also, if you disable the overlay and try to open the friends overlay, it correctly returns a “not configured” error, so that path seems to be working as expected.

Given that this only happens in your project under DX12 + IL2CPP, it likely points to a project-level integration or native interaction rather than the EOS plugin itself.

Could you please try isolating the issue by:

  • Testing your scripts in a clean project with only the EOS plugin
  • Temporarily disabling other native/rendering plugins
  • Delaying EOS initialization

Something very important is the initialization order, as this is a common source of issues:

Are you initializing EOS before the graphics device is ready?

Are you calling EOS from Awake instead of Start?

Also, in the repositoryyou will find a link.xml file, which should always be included when using IL2CPP.

This should help narrow down what combination is triggering the crash.

Thanks for advises. So far tried delaying initialization (It was on start) and now I tried waiting several frames. And then waiting until _state in EOSManager will be `running` before calling anything. Still crashing for now. Will get you posted after I will try other things as well.