[=Tzulanfall;424313]
To me whole business of updates to the engine making big chunks of the marketplace content unusable, is surly a really bad thing for the future of the marketplace.
Sure a content creator will be happy to upload their stuff and maybe update it once or maybe twice. But eventually they are just going to say “well is old content so will not be updated” And who would blame them.
[/]
I would. Update != new content or bugfixing session, it just updating compatibility to next version and in most cases it takes less then a couple of minutes. Some blueprints may require change to the new API(And these deprecated functions are highlighted in Blueprint Editor so it was easy to update them) or could be affected by the bug( is, however, Epic problem and not the content creator), by is minor cases. You can’t build a policy based on minor cases
[]
So eventually the market place will be full of dead content for any serious developer.
[/]
In my perspective, serious developer is the one who make sure his project is working in the latest version of engine and the one who abandoned project.
[]
The problem with is that most indi game development or content creation takes many months if not a year or so to get finished and these people do not have time to keep updating large sections of content every month or so.
[/]
As I said - it takes a couple of minutes and now you have an option just to check on your side if everything working and send message to Epic update it automatically on their side.
[]
I half wonder if much of is to do with the nature of Blueprints and might not be such a problem if C++ were used, I stand to be corrected.
[/]
You have to recompile C++ plugins for new versions of Engine and recompile your code for new version of Engine. It’s not C++ or BP nature, it’s sort of security nature - just to be sure that everything will work correctly.
[]
Anyway my suggestion is to at least attempt to make updates backward compatible at least for the life of a version 4,0 4,1 4,2 etc. (Ok its a pipe dream:)
[/]
I’ve made my Marketplace project backward compatible by changing meta data and recompiling in custom UE4 in order to get it working on outdated Unreal Tournament Editor and it worked correctly, but it could be worse if not tested. Try to make same trick and import 4.10 into 4.5 - a tons of stuff in 4.10 simply does not exist in 4.5 and you will crash immediately and maybe corrupt the project. I mean you can do it, but stability is more important. And you have to maintain stability.
[]
And if not then please can we have the compatibility indicator next to the pic on the market place page, instead of having to open each individual item to find out if it is compatible or not, which is pointless and souls destroying when just the item you need is dead.
[/]
Well, people will think EVERYTHING IS DEAD all the time whenever Engine update hits, because updates applied in time window(1-10 days) after Engine update. It will do only harm and won’t help to understand if project is getting updates or not.