FAB-Plugin does not work with EOS SDK plugins

Summary

Hi there…

I think, many people currently encounter the same problem.

The FAB-Plugin is using the Engine internal EOS SDK implementation to authentificate Users.

My Problem (especially with f.e. the Redpoint EOS Subsystem Plugin) is, that this uses its own SDK implementation, to allow more up-2-date versions of the SDK.
Now, the FAB-Plugin stops those plugins from working, since it overrides the SDK implementation.

Can you update the FAB plugin to work with such custom SDK implementations, please?
Maybe so it just uses the internal SDK, of no external is available?

Cause right now, we need to disable the FAB-Plugin, to go on with developing.

What type of bug are you experiencing?

Plugins

URL where the bug was encountered

https://www.fab.com/listings/b900b244-0ff6-49e3-8562-5fc630ba9515

Steps to Reproduce

Have f.e. Redpoint Games EOS Online Subsystem running.
Try to open Project with FAB plugin enabled.

Expected Result

Have FAB-Plugin not cancel out EOS Online Subsystems with external SDK support.

Observed Result

The Redpoint EOS Online Subsystem will not work until you disable these plugins and restart the editor.

Platform

Windows

Operating System

Win 11 pro

Additional Notes

disabling the "EOS Shared " and “Online Subsystem EOS” does not work, since the FAB-Plugin activates them again.

+1

Kinda difficult now to make custom stuff because inbuilt SDK is older and is not available for all platforms, so using Custom SDK is the only choice which Fab Plugin messes up completely, thanks to not using a custom sdk but the Shared one.

1 Like

Just noting here that I have flagged this with Epic and am still waiting on a resolution.

The only practical solution is for Fab to have it’s own, completely separate version of the EOS SDK DLL, otherwise any developer using a version of the engine from the Epic Games Launcher will be locked into old EOS SDK versions.

3 Likes

Just leaving my +1 here for the issue.

The status of EMP-14190 incident has been moved from ‘New’ to ‘Blocked’.

+1

I guess this won’t be solved with 5.5 release. Sad…