Feedback

[Githubofzir]

我们尝试接入这个项目到虚幻5.7版本，但是我们使用的是源码版引擎，这样放进代码仓库，其他成员不用编译。但是我们发现源码版引擎无法正常接入这个项目，只有epic launcher发行版引擎可以。不知道作者是否已知这个问题

[softdaddy-o]

Thanks for the feedback, and thank you for reporting the issue with source-built Unreal Engine integration.

We have not tested this project against a source-built engine yet, so this compatibility problem was not previously confirmed.

If you are willing to submit a PR, we will review it positively and carefully. As long as the implementation is sound and does not break the existing Epic Launcher engine workflow, we would be happy to merge it.

[entropy622]

Hi, I am a developer of our project. I tested soft-ue-cli with a UE 5.7 project bound to a source-built engine.

This does work in the end.

What happened:

1. I followed the documented flow: soft-ue-cli setup <project>, copied the plugin, enabled it in .uproject, then rebuilt.
2. The project uses a source-built Unreal Engine, not an installed/prebuilt engine.
3. SoftUEBridge depends on ImageWrapper, and the editor module depends on several editor-side modules/plugins.
4. During rebuild, UBT pulled in engine modules that eventually required UElibPNG.
5. The build failed because the source engine tree was missing:
   • Engine/Source/ThirdParty/libPNG/libPNG-1.6.44/lib/Win64/x64/Release/libpng.lib
   • Engine/Source/ThirdParty/libPNG/libPNG-1.6.44/pnglibconf.h

Observed errors:

• fatal error C1083: Cannot open include file: 'pnglibconf.h'
• LNK1181: cannot open input file '...libpng.lib'

After restoring those missing libPNG artifacts, the project compiled successfully and soft-ue-cli check-setup passed.

So, I don't think source-built UE is unsupported. The problem is just that, enabling SoftUEBridge triggered an engine-side compile path that exposed missing ThirdParty artifacts in the source engine tree.

Thanks for building and maintaining this tool. I'm sharing this in case it helps improve the setup experience for source-built UE users.

[softdaddy-o]

Thanks for validating this with a UE 5.7 source-built engine and for documenting the root cause. I have not tested SoftUEBridge against source-built engine builds myself, so this is useful context. Based on your findings, this looks like a missing ThirdParty artifact issue in that local engine tree rather than source-built UE being unsupported. If you submit a PR to improve the setup experience or documentation for this case, I will review it positively and would be happy to merge it if the change is sound.