Closed Matlauk closed 4 years ago
Those functions add a lot of clutter, they should probably be added somewhere else where they can be directly accessed by BP instead of needing a wrapper function for it. Putting them here will require a BP function library to even work with BP.
The purpose of this PR was to add more "clutter" to code to remove "clutter" from blueprint scripting where more "clutter" is more difficult to deal with. I haven't had the the time to develop this further. I'm not even sure I want to. But I am confused by your comment. I'm not even sure it's meant for this pull request. Mostly because I did things in the same manner that was already done, I added new functions to the relevant sections that already existed and it's all accessible via the already existing blueprint library that is already used to access and modify the streams.
Anyway, I am closing this because I wont have time to develop this further for quite some time. That is, if I chose I even want to move forward with it.
Oh wait, i'm dumb, I thought you added these somewhere else. These could be merged in but it's up to Koderz to decide whether to merge or not.
I haven't had the opportunity to test any of this yet. I'd love to work on it through the weekend but I'm out for vacation in the morning. I plan on implementing a lot of the same for the collision stuff as well when I get back.
FRuntimeMeshVertexTexCoordStream::AddRange is probably wrong