Why am i getting a compiler error when all my blueprints check out?
I built 2 blueprints and both of them tested out fine, they was with custom meshes i built in blender, and they worked fine. When i build the 3rd blueprint using the static mesh sm_door in the starter content i got the error stating that one of the blueprints has a compiling error do I still want to play in the editor. I clicked yes and the door blueprint worked fine. So I was trying to find the error in the blueprint I went through every blue print that is in my project weather i am using it or not looking for an error to fix it. Nothing.... So I restarted the editor thinking it was a glitch. It's still pulling up. next i removed the blueprints along with the static meshes involved, and still I am getting this error. I have searched every where I can think of online and have found similar situations tested them out and the error is still there.
I even recreated the blueprints and they work in game but the error will not go away. I do not know what to do.
the link to the blueprint i used down to the exact placement on all three doors i used is below. Each time I tested the blueprint after completion and noticed that didnt have the error till I used the mesh from the started content. https://www.youtube.com/watch?v=hlwh_EO1JG0
asked May 06 '16 at 08:29 AM in Blueprint Scripting
Ok no need to answer this question i figured it out while trying to think of more information i provided. I am leaving this up here to help any one that has a similar problem. I fixed the problem cause i was setting up my class blueprints on static meshes that i had used in matinee sequences, and when i deleted them to replace them with the new class blueprints i made, it popped up the error that i came across. since i used it in a level blueprint to set it up with matinee and then deleted the mesh is what caused the error.
remember a couple of things fellow developers. 1. think of every possible source of anything you delete, if it is possibly connected it probably is. 2. if you can not seem to fix a problem think. this program is well known and it most likely is not a bug, dont say i am not saying there is not bugs because there is, but think of everything you did prior to the error all the way from starting up the program, and just retrace your steps and think of what you did that you may not realized what effects it has had. you all know the saying be smarter than what you are working with. the problem i posted was because i thought i hit a wall and not going to lie was starting to face the possibility that i may have to delete my past 2 months worth of work, but sit back relax and think. that will help you stand apart from all the other designers out there is to be able to diagnose and think in tough and stressful situations.
Remember every one that has read this post. Your thoughts control your world, dont let your world control your thoughts.
answered May 06 '16 at 09:00 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here