3 New Plugins - Joystick/HOTAS Support, Blueprint Easing Functions, Saitek X52 Pro

[MC_Stryker]

@simmania;92321

Thanks Matt.
The strange thing is that the plugin is not broken after the errors. Just the Blueprint nodes in that particular BluePrint are broken. When I replace them with ‘fresh’ instances everything works again.
I’ve tried using blueprints that inherit from Pawn or Actor, but it makes no difference. It seems like the plugin is loaded after Blueprint is loaded.
I’m using UE4.2.1. The plugin is enabled. Re-enabling had no effect.

Can I reference these functions in C++ also? It would be easier and avoid the problem of using Blueprint at all.

EDIT:
Okay, the problem seems to lie in the Blueprint that inherits from a custom C++ class that inherits from Pawn. If this Blueprint has a reference to anything of your plugin, everything becomes broken.
I worked around the issue by creating another JoystickInput Blueprint and letting JoystickInput have a reference to the blueprint with parent C++ class.

EDIT2:
I’ve found another bug: if I move the Create Joystick State function to the construction script, I get the following error when saving the map:

Can't save C:/Users/simmania/Documents/Unreal Projects/Project/Content/Maps/Minimal_Default.umap: Graph is linked to object(s) in external map.
External Object(s):
JoystickState_6
/Engine/Transient
  
Try to find the chain of references to that object (may take some time)?

Sorry about the delayed response simmania. I’m curious if some of this that you are experiencing has to do that it was compiled for 4.2.0. That’s weird that re-enabling it had no effect. I believe if you were to reference these in C++, you would need the lib and header files. I haven’t messed around with the plugin lately as I’ve been trying to nail out some content for my prototype but was going to get back to it shortly. Once 4.3 is released, I will jump in and attempt to replicate some of what you are experiencing currently and see if I can get these bugs taken care of. If I have any problems replicating this, I will reach out to you directly so I setup things the way you have it going at the moment. Lets try to shoot on me having an updated version somewhere around a week following the release of 4.3. Once I get to it though, I’ll keep you all posted on the status and I’ll try to incorporate some of the feedback to make it better for you guys.

@;93942

Hey MC,

So I finally got around to testing this. Is there a way I can distribute the plugin inside the project files / working directory, as opposed to built in to the engine’s ‘Plugins’ folder? It would be easier for my artists, who also need to keep their version/plugins in line with mine, to stay up to date if we could just add the files to the project and throw it all up on our Perforce server.

I was prompted to ask this by the plugins window in the editor - one says installed, and the other ‘built in’. If we put plugins in the folder you specified, they’re in the latter category. Is the former category what I need?

Thanks!

EDIT: /Game Project/Plugins/Plugin Folder/. Got it! Shows up as expected.

Hey , droping it in the local Game plugins folder worked? I haven’t tried this yet.