I mean I already answered his question but if neither of you want to actually follow my instructions then that’s on you. @TheShown literally said he “put the plugin into my projects plugins folder” and I straight up answered that you shouldn’t be doing that, and that the plugin needs to be in your engine plugins folder.
But if that’s too difficult for both of you to figure out, then oh well. And you people wonder why creators such as us don’t care to provide you with support because all we’re ever doing is wasting our time. You tell people a potential solution and they don’t even bother to say “yes this fixed my problem” or not so that the issue can be properly addressed.
Then you have other people like @scopesnoiper who come in and do the same thing. So did you even read my reply to him? Did you even trying compiling this as an engine plugin? Or is it in your project plugins folder? Or is that too difficult for you to figure out?
Because it would have been nice to know if that fixed the issue or not. But since both of you are incapable of providing any actual information I can assure you that absolutely no effort will go into fixing this problem.
I am sorry for not providing information and my rudeness for my expression.Actually I tried every solution that can be found in the web, but still failed to compile. SO I surely tired to put the plugin in the Engine Plugin Folder and still built error.I will tried to email you my problem in detail via gmail.Thank you for your great work!
This allows you to test WebUI 2.0 using a packaged SHIPPING build from 5.2.1 with the ability to edit anything in the web-based overlay (for testing purposes). Just open and edit the following file:
/WebInterface/Content/HTML/sample.html
You can also launch the demo application in either DirectX 11 or DirectX 12 using the command line:
I just purchased three of your plugins, but I found that they do not work on iOS as stated on your website. I then recompiled the plugins on a Mac system, but they still cannot be packaged. Can you help me identify the reason?
Unreal 5.3.2
VSCode
UATHelper: Packaging (IOS): LogWorldPartition: Display: FWorldPartitionClassDescRegistry::Initialize took 939 us
UATHelper: Packaging (IOS): LogAudio: Display: Registering Engine Module Parameter Interfaces...
UATHelper: Packaging (IOS): Failed to load the CEF framework.
UATHelper: Packaging (IOS): LogCEF3Utils: Error: Chromium loader initialization failed
UATHelper: Packaging (IOS): LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
PackagingResults: Error: Chromium loader initialization failed
Yes we can help you, but please head over to the “orders” page on our website where you can find information about contacting support. Please keep in mind, if you check my recent post from a few months ago when 5.4 released, we have officially dropped support for mobile in WebUI 2.0 for the time being. This doesn’t mean we don’t plan on supporting it in the future, but our focus recently has been on PC with these recent accelerated paint improvements. However we do intend on getting mobile support up and running again, so please contact our support via the “orders” page to help with diagnosing these issues.
The WebUI 2.0 plugin has been officially released on our website! We were originally planning to release it on the Marketplace, but since Epic Games is taking too long to get everything approved, we’ve decided to just continue releasing builds via our website. We may still move over to the Marketplace in the future (and if we do we’ll give access to anyone that purchased the plugin on our website) but we just don’t feel like waiting anymore, which is why we left the Marketplace years ago in the first place.
This includes a 3D widget example, where you can fly around in the 3D world with a “pointing device” and click on a live interactive WebUI widget. Just click the “Play” button to switch maps!
Not only does the message tell you exactly what the problem is, but instead of contacting support through our orders page, or joining our Discord, or sending an email, or any of those things…you thought this was the best way to address your issue? What would you like me to do, post your license key right here for everyone? We obviously put some protections on the plugin since so many Chinese developers kept stealing our code, and this is obviously something you need to get support on privately. So as the message literally says, either contact us to get your license key, or disable the accelerated paint feature in your project settings.
We have more exciting news! The WebUI 2.0 plugin has now been setup for Unreal Engine 4, and we are currently supporting versions 4.23-5.4 with full accelerated paint support! There’s even DirectX 12 (and DirectX 11) support on versions 4.25-4.27 along with DirectX 11 support on versions 4.23-4.24 as well.
The best part is that we’ve centralized the entire codebase. So now you only need one entire source code of the WebUI to compile all versions from 4.23-5.4 with no changes required!
Maybe that’s because you typed up the entire first half of your email in Mandarin and it went to my spam folder. In fact I’m getting quite sick of this, I think adding Chinese documentation was the worst thing I ever did. Many years ago I saw a bunch of downloads starting to happen from Chinese IP addresses, and thought “oh wow that’s great, we should expand into that market” and I paid someone to translate our documentation PDF into Mandarin. Worst. Decision. Ever. I didn’t realize just how bad the “Chinese ripoff” stereotype is 100% true, because tons of Chinese developers kept stealing my code and uploading their own versions of the WebUI (using exact custom code snippets directly stolen, because they can’t think for themselves) and it’s been a never ending DMCA nightmare ever since.
So here’s what we’re going to do, once and for all, to finally end this BS. First and foremost, the Chinese documentation is GONE. We’ve removed it from every possible download that we have. Second, if anyone approaches us that obviously doesn’t speak fluent English, they will be blocked immediately and will not receive support. These people seem to think because they have a little Google translator that it means they can speak English. Well unfortunately you can’t actually understand a thing we’re saying and we’re done trying to communicate with you (in fact, if you take note previously, I actually PAID someone to translate our documentation, cause I’m not stupid enough to think a little online translator makes someone a fluent speaker of another language). Finally, last and most important, we will be blocking all purchases and downloads from Chinese IP addresses on our website. We are 100% done with China. Period.
P.S. - This has nothing to do with region, race, ect. We love and support the Koreans, Japanese, and 100% fully support the COUNTRY of Taiwan.
There’s some exciting news! We now have the plugin completely reworked for Android and iOS too!
This new build leverages our existing mobile JavaScript interop system, but now includes all the same transparency support as PC. That means you can now use WebUI widgets on mobile with FULL TOUCH-BASED TRANSPARENCY!
We’ve also setup a URL interceptor so that all our http://game.local/ PAK file loading system (previously known as pak://) and material+texture image rendering URLs can feed custom data to the mobile browsers as well. So this means we will now have FULL MOBILE SUPPORT that is actually in FULL PARITY with the PC version of the WebUI plugin!
We’ll be uploading releases soon for UE versions 5.0-5.4 near the end of the week.
As you can see in this thread, we were first on the Marketplace in 2017. However about a year later in 2018, we decided to leave the Marketplace, because it took too long for updates, and only being able to upload the previous 3 engine versions was extremely limiting.
So we moved over to GitHub and provided all our plugins 100% FREE for many years. Then we eventually built out our website in 2021 with purchase options, and moved all our plugins to there, which is where we’ve been ever since.
However, after 6 years we are finally back on the Marketplace:
This is because we now have our own website where we can easily manage our plugins for versions 4.23+ and that means we don’t have to worry about the Marketplace limiting us to the previous 3 versions.
So if you don’t use source code builds and just use the vanilla Unreal Editor that comes with the Epic Games Launcher (and stay up-to-date with the latest engine versions) then it may be easier for you to obtain our plugins via the Marketplace instead. It’s also going to be a great way for new developers to discover our plugins, rather than having to randomly find them on the forums when searching.
We also plan to add a bunch of new plugins as well, so keep an eye on our page for future releases:
I have sent an email, but you didn’t reply.