I don’t have the exact date, but this project has been using it since at least April. Never had this issue before.
Behaviour is certainly unexpected. Can you by the way disable collisions on your Volumes and see what happens?
Hello,
It seems that either rotation doesn’t work anymore or I am doing it wrong, with all ProInstances shapes with 4.26.2 and 4.27.1.
No matter what values I put here, the objects are never rotated.
What can I do?
Thank you for your help!
Hey, please check out that inside “Instances” array “Instance Local Settings” are unchecked - only in this case “Instance Global Settings” are gonna work.
That was it! I should have looked harder… Thank you for your help!
Hey everybody, I’m having an Issue where the meshes of spline dissappear at a certain height? How can I fix this? Thanks!
Usually #1 reason behind this is that ProInstances are colliding with Volumes on your level. You can add them in ignore list inside ProInstance Main Settings.
Yellow error is reported when packing. Please solve it
Errors are marked as red, yellow are warnings and they can be very different. What exactly did you get?
A question about the plugin on mobile platforms. Do I need to build this package for the specific mobile project and have it included, if I want to have instances with HISM and culling in a map?
Hi there,
This plugin is fantastic. Is there any way to point the instances to a separate, centralised array? I am hoping to have a centralised array instead of per spline BP so it can be updated without updating multiple spline arrays. The array seems to be handled by the ProInstanceToolsParent - is that correct? Is it possible to change / and a big task? Sorry I’m very inexperienced with coding.
@bad_locality1 plugin does support mobile so you should be good without additional hassle.
@meat_helmet can you please explain it a little bit more? Sorry, I didn’t quite understand the question.
Hi, I was wondering if you could kindly help?
I was just testing your instanced static meshes with the Grid to create roof tiles and I set the start and end cull to 1500, for this test, but noticed that the mesh appears to be still there… or is it? Sorry to ask but can you explain what I’m looking at here? When I set other static mesh cull states they don’t appear in the wire frame but your grid meshes do?!
Then look at this mesh…
it disappears as expected.
I just want to confirm that the culling works on this tool. I love this tool, I use it all the time but this has confused me. Thanks.
sorry if this is a stupid question, I just want to understand what I’m looking at.
Hello! No, it’s fine.
Not quite sure what’s going on though! It should be culling on both view modes. Try switching to HISM maybe, instead of ISM. Or if you’re using Cull Distance Volume it probably can interfere with each other, depending on its settings.
Be amazing if you could fix these warnings, thanks!
LogPython: Warning: 'ProInstanceInstance.bOverwriteMaterials' and 'ProInstanceInstance.OverwriteMaterials' have the same name (overwrite_materials) when exposed to Python. Rename one of them using 'ScriptName' meta-data (or 'ScriptMethod' or 'ScriptConstant' for extension functions).
LogPython: Warning: 'ProInstanceInstance.bInstanceSettings' and 'ProInstanceInstance.InstanceSettings' have the same name (instance_settings) when exposed to Python. Rename one of them using 'ScriptName' meta-data (or 'ScriptMethod' or 'ScriptConstant' for extension functions).
LogClass: Warning: ObjectProperty FProInstanceInstance::Mesh is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
LogClass: Warning: ObjectProperty FProInstanceRotation::RotateToActor is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
LogClass: Warning: ObjectProperty FProInstanceCurrentInstanceContainer::StaticMesh is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
LogClass: Warning: ObjectProperty FProInstanceCurrentInstanceContainer::ISM is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
LogClass: Warning: ObjectProperty FProInstanceCurrentInstanceContainer::HISM is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
1 Like
Yeah, aware of these. Thankfully it’s just warnings and actually it was totally ok in earlier versions of Unreal. But have to fix it nonetheless.
1 Like
A hotfix update 1.25 is up:
- Fixed “not initialized properly” variables inside structs
It should now compile for UE5 with much less warnings. Remember that warnings are not equal errors! And also that proper support for UE5.0 is coming only when UE5.0 will be finally released.
1 Like
In the UE5 version, your warnings and errors are cluttering my log, can you please clean these up?
Warning LogPython 'ProInstanceInstance.bOverwriteMaterials' and 'ProInstanceInstance.OverwriteMaterials' have the same name (overwrite_materials) when exposed to Python. Rename one of them using 'ScriptName' meta-data (or 'ScriptMethod' or 'ScriptConstant' for extension functions).
Warning LogPython 'ProInstanceInstance.bInstanceSettings' and 'ProInstanceInstance.InstanceSettings' have the same name (instance_settings) when exposed to Python. Rename one of them using 'ScriptName' meta-data (or 'ScriptMethod' or 'ScriptConstant' for extension functions).
Error LogClass ByteProperty FProInstanceRotation::RotateToActorByAxes is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
Display LogClass 1 Uninitialized script struct members found including 0 object properties
Error LogAutomationTest UObject.Class AttemptToFindUninitializedScriptStructMembers will be marked as failing due to errors being logged
Error LogAutomationTest ByteProperty FProInstanceRotation::RotateToActorByAxes is not initialized properly. Module:ProInstanceToolsPlugin File:Private/ProInstanceToolsParent.h
Yes, you can expect in a few days. Dang it it’s just one enum variable wasn’t initialized.
Sorry I’m just short of time to test UE5 properly. I still develop plugins in UE4 and then porting them to UE5.
On the other hand these warnings are bothering me on different reasons (this wasn’t there in UE4 before 4.25), it’s expecting me to just rename variables to get rid of it. But that will break variable serialization and user settings a lot. I don’t think a lot of ProInstance users use Python at all?