Backwards compatibility of Blueprints (uasset hidden when moving back to 4.4)
I was working on Blueprints in 4.5 (migrated these to another project which was 4.4) and the assets no longer show up when moving back to 4.4 I cannot recompile them either simply because they aren't available in the Content Browser anymore.
asked Oct 05 '14 at 03:57 PM in Bug Reports
I assume that what you are describing would be forward compatibility. Using BluePrints from a higher version in a lower one could break them, they are serialized and the size of the properties is very important. I had the same problem moving a BP from 4..4 to 4.3, the issue was that in 4.4 one of the parent code classes had a new property, a user defined struct in my case. The engine told me that the code is incomplete (check your log) and they never loaded. To fix the issue I just got rid of the code that prevents the assets from loading and commented a whole bunch of checks (you will have lots of crashes until you get it working!), and change some serialization to null or default values by hand.
I guess there is no easy way for you to use you BP in a lower version automatically, you can still copy&past the BP code over and recreate it in 4.3, this was my first attempt too but it took longer then fixing the serialization for my classes.
answered Oct 06 '14 at 09:52 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here