(39) 's Extra Blueprint Nodes for You as a Plugin, No C++ Required!

[John_Alcatraz]

@;468455

Dear John,

Sounds like I need to provide a 4.11 build, though that makes my process of adding new nodes take even longer because then I have to upload an extra version on top of 1. editor 2. packaged and 3. media fire But Then I’d have to provide 3 of those for 4.11 as well!

Supporting 2 engine versions by myself for free is so much work for me, I then have to do 6 updates every I add any new nodes, as described above.

Unless I adopted 4.11 early… then anyone wanting to test my new nodes would also have to adopt 4.11 early…

Thinking about it…

Also I think 4.11 is coming out soon

Hi , thanks for your answer!

I know 4.11 is coming soon, but since I was never able to test the previews I fear there might be bugs I could have reported to Epic earlier…

I would be absolutely fine with compiling your plugin myself (I do that anyway since I use a custom build of the engine), so if you could provide only source for preview versions that would already be very helpful, if it saves you because you don’t have to compile them.

I have tried to manually compile your plugin for 4.11, but there were a few errors and I don’t know how to fix them

[Dannington]

Hi , i’m such a dummy with C++!

I’ve hijacked your blueprint function library tutorial code to try to get my machine’s local IP address with :

//Happy Message
virtual UMyBlueprintFunctionLibrary::GetHappyMessage()
{

	return GetLocalHostAddr(FOutputDevice & Out, bool & bCanBindAll);
}

But it just winds up not compiling and throwing up problems with the SocketSubsystem.h include.

The sample code from the docs is

virtual TSharedRef< FInternetAddr > GetLocalHostAddr
(
    FOutputDevice & Out,
    bool & bCanBindAll
)

Any of a nudge in the right direction? is the kind of bodgy assemblies I can return in python - I just don’t get it with C++ (But i’d love to!)

[teak421]

Hi…

Curious… I went to your github and it says that its not been updated since September. Are you still allowing access to the source? Honestly, I learn by reading other people’s code and if I do use it anyplace, you will get credit. Thanks for your work!

teak

[RhythmScript]

@;468455

Dear John,

Sounds like I need to provide a 4.11 build, though that makes my process of adding new nodes take even longer because then I have to upload an extra version on top of 1. editor 2. packaged and 3. media fire But Then I’d have to provide 3 of those for 4.11 as well!

Supporting 2 engine versions by myself for free is so much work for me, I then have to do 6 updates every I add any new nodes, as described above.

Unless I adopted 4.11 early… then anyone wanting to test my new nodes would also have to adopt 4.11 early…

Thinking about it…

Also I think 4.11 is coming out soon

Yes do send me a PM with your with consoles

I love the Victory library, but I must confess that I really do miss not being able to work with preview builds anymore. I understand the reason why, of course…

, is there usually a high labor cost associated with updating nodes to work with the newest engine versions? Obviously just the spent maintaining two branches isn’t ideal… But maybe when a new version preview release drops (just Preview 1, not updated), it would be beneficial to just quickly toss out a single compatible version of the plugin as-is? Keep updates to the main version (not the preview version) until it becomes official… But with the multi-month cycle on preview releases, even if it would mean that not EVERY new Victory node could be tested, people who are legacy-bound to Victory because they use existing nodes would be able to start testing in preview releases, even if it meant having to wait a little while for Victory to catch up.

I know for my own part 99% of what I want and need Victory for, at the moment anyway, isn’t the stuff you’re rolling out now, and I confess—sorry to say—I’d rather wait until “4.11 drops proper and Victory gets updated for it” for access to subtitles in sound cues than I would for access to the newest engine features. I (typically) only update Victory when it’s needed due to an engine update, and the extra nodes you’ve added are like a bonus at that .

And it would only literally be a single upload (the editor version) since I think the common-sense case could be made that nobody is attempting to package a game made in a preview release (certainly Epic cautions strongly against doing so). It would be a one- deal when the first version of a new preview release dropped to provide a degree of compatibility for testing projects, which is what the previews are FOR.

Just a thought.

[SudoEPM]

I’m on the latest version of the editor and I can’t see the VictoryPlugin even if I pasted the folder in the Plugins folder… Any idea?

[gozu]

Excellent work as always. I too would like a 4.11 version on Git. But i can wait, surely it wont be long now.

Good luck with Solus

[kinzua01]

Hi ,

I’ve been following thread lately and have chanced upon a project to finally utilise the awesome features of the Victory Plugin.
But i can’t get plugin to work on Mac.
Can someone please share a installation setup to get working on Mac?

And also how can one use these features for mobile? Like the instanced static mesh for iOS and android?
Any help would be grateful. I read the thread where someone else was trying to get the plugin work on mac.

Thanks a ton for the awesome work, but please share some guidelines on how i can get to work.

[anon247819]

Hi ,

I’ve got some kind of stupid question. I wanted to use your “Load Texture 2D From File” plugin and it seems to work perfectly. The example setup you pictured does its job and shows the height and the width of the image loaded in the game. But I want to actually connect the loaded image to a material and use material ingame. way I want to achieve the possibility to change the texture od the material at runtime. How can that be ?

Thanks a lot!

[John_Alcatraz]

@3Dler;470884

Hi ,

I’ve got some kind of stupid question. I wanted to use your “Load Texture 2D From File” plugin and it seems to work perfectly. The example setup you pictured does its job and shows the height and the width of the image loaded in the game. But I want to actually connect the loaded image to a material and use material ingame. way I want to achieve the possibility to change the texture od the material at runtime. How can that be ?

Thanks a lot!

If I understand your correctly, you would make the texture a parameter in the material, then reference the material somewhere in your blueprints and call “Set Texture Parameter” to set it to the texture you just loaded.

[Dannington]

Hi 3Dler,

Make your material - right click on the texture loader you’re using and change it to the parameter version. Name the parameter (in the bottom left box) as ImageTexture or something.

In you blueprint - probably off of the Begin Play node, make a create dynamic material node - and select your material as the source - promote the created texture to a variable. Set the material of your or whatever to texture using the set material node.

Now you can drag off the new dynamic material variable and choose set texture parameter and feed any new texture into it - in the parameter box you need to type ImageTexture. You can feed the loaded texture into .

Good luck!

[kleyten]

every i want to package my project i get an error… automation tool was unable to run successfully

[anon247819]

Hi ,

first of , thanks for your kind and fast answers. What I’m trying to do is:

-Loading an image from a path and make it a texture
-apply texture to a material

way I want to achieve the possibility to change the texture in the PACKAGED game by changing the image which is applied to the material. So lets say, I’ve got a cube with a bird on it. The image of the bird lays at C:\pictures\ exture01.jpg. If I swap image to a picture of a dog (of course also named “texture01”), in the packaged game there should be a dog on the cube now, as the texture for the cube is loaded from the path C:\pictures\ exture01.jpg.

I managed to load the image. But I don’t get how to say a material: “Use the image from path”. Can anybody help here?

Below there’s a screenshot which hopefully maked clear what I’m trying to achieve.

EDIT: And I also can’t package the game. First it takes extraordinarily long and than I get an unknown error.

[Dannington]

Hi 3Dler

Here is what your material should (roughly) look like:

And is the BP - Because I didn’t have 's plugin installed in project I used the async image downloader - 's loader is probably better for you, so just replace that node with 's loader.

Edit - Just to note, 's node is a pure one (green rather than blue), means it doesn’t need to be in the execution path. It’s good to understand the difference - I think of the data being dragged out of these pure nodes when the node which is asking for it is executed. You may already know or not. In your example, 's node would only be called if your ‘Set - texture2d’ node was executed (Which it isn’t in your case - it’s execution pins aren’t connected to anything).

[Rama]

@Dannington

Thanks for helping out in my thread !

[QUOTE=kinzua01;470878]
Hi ,

I've been following  thread lately and have chanced upon a project to finally utilise the awesome features of the Victory Plugin.

But i can't get  plugin to work on Mac. 
Can someone please share a installation setup to get  working on Mac? :)

And also how can one use these features for mobile? Like the instanced static mesh  for iOS and android?

Thanks a ton for the awesome work, but please share some guidelines on how i can get  to work.
[/QUOTE]


Someone in the community needs to help me out with a Mac version as I dont have a Mac so I can't reliably test for it :)

Regarding mobile, Epic is very careful that the features they release work with mobile, I believe instancd static meshes should work yes :)

@gozu;470708

Excellent work as always. I too would like a 4.11 version on Git. But i can wait, surely it wont be long now.

Good luck with Solus

Thanks!

[QUOTE=SudoEPM;470593]
I'm on the latest version of the editor and I can't see the VictoryPlugin even if I pasted the folder in the Plugins folder... Any idea?
[/QUOTE]


The "latest" version of the engine is a pre-release build not an official build, something that does seem to confuse a lot of people the way it is currently presented.

But a message clearly indicates that you should not be working on your main projects in 4.11 yet as it is not an official release.

The last official release is 4.10, that is what my plugin is still working with.


I wonder how Epic is going to handle everyone wanting their marketplace plugins updated to the pre-release engine builds... :)

[Rama]

Supporting Pre-Release Engine Builds

@John Alcatraz;468711

I would be absolutely fine with compiling your plugin myself (I do that anyway since I use a custom build of the engine), so if you could provide only source for preview versions that would already be very helpful, if it saves you because you don’t have to compile them.

I have tried to manually compile your plugin for 4.11, but there were a few errors and I don’t know how to fix them

Compiling is not the, constantly adding to and updating two engine versions worth of updates every I want to add a node:

1. victory plugin editor version
2. victory plugin packaged binaries
3. victory plugin editor + packaged on media fire

is what takes the

It is the distribution of the software that is taking me the , not the software itself

@RhythmScript;469466

, is there usually a high labor cost associated with updating nodes to work with the newest engine versions?

The labor is in having to maintain two versions of updates. And I really am not getting very many donations at , so maintaining Victory Plugin for two engine versions is just beyond my capacity when offering whole plugin for free to the community.

Epic really needs to think about when it comes for marketplace plugins, because if everyone is so impatient to be on the not-entirely-stable-supposed-to-be-test branch, rather than the stable tested branch, it is going to bother everyone if plugin makers dont always upload for the test branch.

But as I said, having to maintain two versions of the plugin becomes ridiculous.

I wonder why everyone wants the unstable-declared-to-be-test branch more than the official release?

The point of a test branch is for testing, not mainline development!

Yet everyone seems to move over to the latest and supposedly greatest, even though it is just a test branch.

What to do?

Perhaps for certain pre-release builds that are highly preferred, I would simply stop supporting the previous engine version and move on to the pre-release version.

I am under the presumption that discussion will become a moot point within a few days, when 4.11 is released, but if it seems to be taking too long I will do the upgrade.

[Rama]

Victory Plugin Source Code

@teak421;469223

Hi …

Curious… I went to your github and it says that its not been updated since September. Are you still allowing access to the source? Honestly, I learn by reading other people’s code and if I do use it anyplace, you will get credit. Thanks for your work!

teak

The latest source code is included in every download of my plugin from the links I include in my posts!

I have not had to update the Git in addition to every other step involved in releasing a new victory plugin version.

You can always find the latest source code in the plugin download itself!

[Rama]

@Dannington;468782

Hi , i’m such a dummy with C++!

I’ve hijacked your blueprint function library tutorial code to try to get my machine’s local IP address with :

//Happy Message
virtual UMyBlueprintFunctionLibrary::GetHappyMessage()
{

	return GetLocalHostAddr(FOutputDevice & Out, bool & bCanBindAll);
}

But it just winds up not compiling and throwing up problems with the SocketSubsystem.h include.

The sample code from the docs is

virtual TSharedRef< FInternetAddr > GetLocalHostAddr
(
    FOutputDevice & Out,
    bool & bCanBindAll
)

Any of a nudge in the right direction? is the kind of bodgy assemblies I can return in python - I just don’t get it with C++ (But i’d love to!)

In your build cs (either plugin or project level depending where you wrote your code), you have to add a public dependency to “HTTP”,

Then that code should compile fine

[Rama]

Animated Vertex Locations

Dear Community,

node lets you obtain the actual animated positions of a character, taking frame rate and physics/visual update into account!

**Latest plugin download on the UE4 Wiki: (7.16 mb) **
https://wiki.unrealengine.com/File:VictoryPlugin.zip

**Plugin Release Dates and UE4 Engine Versions**
https://wiki.unrealengine.com/%27s_Vertex_Snap_Editor_Plugin#Plugin_Release_Dates_and_UE4_Engine_Versions

Victory Plugin Binaries for Packaged Games

A new, community-hosted Unreal Engine Wiki

**Donations**

Donations can be sent to me via:
http://lightningfitness.org/donate/

Enjoy!

:)



![AnimatedVertexLocations.jpg|1280x960](upload://xif0tb713gyoLicF4HX0LQGUChw.jpeg)

![AnimatedVertexLocations2.jpg|1280x960](upload://7R9xFuIwIbZiD46nmLHl54K8r57.jpeg)

![AnimatedVertexLocations3.jpg|1280x960](upload://cfEH9JuoDvsoTKEtoJEj4XuyR2L.jpeg)

[John_Alcatraz]

@;472174

Compiling is not the, constantly adding to and updating two engine versions worth of updates every I want to add a node:

1. victory plugin editor version
2. victory plugin packaged binaries
3. victory plugin editor + packaged on media fire

is what takes the

It is the distribution of the software that is taking me the , not the software itself :)a

What if you would only update your plugin once for a preview and only upload the editor version or only the source? You would add new nodes only to the stable one, and never touch the preview version again (unless Epic changes some C++ functions in a new preview that would make your plugin not compile). So you would only have to upload one single version once when Preview 1 is released.

@;472174

Epic really needs to think about when it comes for marketplace plugins, because if everyone is so impatient to be on the not-entirely-stable-supposed-to-be-test branch, rather than the stable tested branch, it is going to bother everyone if plugin makers dont always upload for the test branch.

But as I said, having to maintain two versions of the plugin becomes ridiculous.

I wonder why everyone wants the unstable-declared-to-be-test branch more than the official release?

The point of a test branch is for testing, not mainline development!

Yet everyone seems to move over to the latest and supposedly greatest, even though it is just a test branch.

What to do?

Have you ever seen anyone who wants to do serious development on a Preview release? I think I made very clear that I only need your plugin to work with the Preview to be able to test the preview with a copy of my project and report new bugs to Epic so that they are fixed once I switch my real project to the new stable version. And I think is how everyone handles it, since is what previews should be used for

@;472174

Perhaps for certain pre-release builds that are highly preferred, I would simply stop supporting the previous engine version and move on to the pre-release version.

I am under the presumption that discussion will become a moot point within a few days, when 4.11 is released, but if it seems to be taking too long I will do the upgrade.

Epic said 4.11 will be released in March, so its still quite a while, way more than a few days

[Dannington]

I can get Victory running fine on my mac - with a little adjustment. probably won’t like solution but…

There are a couple of functions where there’s an error about a class not being allowed to return a ‘False’ bool - I think it’s some node which finds sockets on a character or something. My solution - because I never use these nodes - is to just comment out the class from the .h and the .cpp files.

also applies to compiling for 4.11 For my purposes I just commented out the functions which didn’t work - it’s a bit of a nasty hack, but it works perfectly for me as I don’t use these character based nodes.

Get your hands a bit dirty is my suggestion! I keep tinkering hoping I’ll suddenly understand C++ (It hasn’t happened yet)

What would probably help is a copy of the error messages from X-code. I think it’s only about 3 classes which return error about bools (for Mac 4.10).