I just copied my 4.8 version over to a project I converted from 4.7 today and it worked right away. Delete the intermediate and binary folders in the plugin folder and try again.
Yeah, was a Problem on my Side. For some reason the Application.ico in the Build Folder was not on my SVN and that was the reason it couldn't compile
I've been getting an error that i'm not sure to fix that says
Plugin 'AdvancedSessions' failed to load because module 'AdvancedSessions' does not appear to be compatible with the current version of the engine. The plugin may need to be recompiled
while initializing the project.
I'm using the 4.8 version and engine and i've extracted it to the projectfolder/plugins. Any idea why this isnt working?
↓ Thanks, solved the problem c:
I've been getting an error that i'm not sure to fix that says while initializing the project.
I'm using the 4.8 version and engine and i've extracted it to the projectfolder/plugins. Any idea why this isnt working?
Sorry, I never re-uploaded 4.8 after it officially released and blueprint only projects can't use the old binaries. I'll re-upload with all of the binaries built now that blueprint only projects work with plugins.
*Edit*: New version of the 4.8 is up, should work with blueprint only projects now.
It was a wrong post. But that's okay I took advantage to give an entry. Because I found it interesting. I'll take a look at the blueprints. I can to enable steam api with this?
Yes if you have the steam subsystem active and working then the blueprint nodes will work just fine. Epic made their backend subsystems so that they can be used pretty much the same no matter which one is active.
hi, I have a problem with this plugin.
I can t package my project.
I get this errors: *snip*
Sorry man, this didn't show up on my feed, in fact quite a few questions in here didn't show up for some reason.
I tested the newest version of it with all of the binaries required to run as a blueprint only project and had it working fine for me, however I did not test packaging that BP only project.
I just remade the test project and tried to package it and the engine RECOMPILED the binaries for packaging even though I have already compiled the shipped versions of all binaries. You will need to install a compatible compiler even if you don't touch any C++ for the engine to package it seems.
Honestly it is probably better to have a compiler installed along side it anyway, if you ever want to touch c++ you just can then and the engine obviously wasn't intended to be fully standalone. You don't have to compile or edit any code with an installed compiler, it just gives the engine the ability to do so when it needs to. The engine setup/installation page will have information for download VS Express for free and that will solve your problem.
It might be able to package without a compiler with the intermediate file structure included, but I really don't want to bloat the download to 4 gigs instead of 37mb.
Comment