Obviously the new prefab system is having a lot of problems and people are concerned right now. Two big general issues:
Backward compatibility. I wasn’t able to convert any existing project to the new prefab system in the 2017.2 special build (and still the same case with the 2018.3 beta build). A lot of it were due to editor-crashing bugs. New projects work wonderfully ofc.
Workflow Overhead. New workflow adds a bit of cognitive overhead on editing simple prefabs. The old prefab system was simple and predictable, albeit more restricted.
Both of these problems can be mitigated if the new improved prefab system does not replace the old system, but exists as something standalone.
Because Prefabs are such integral part of the engine, I feel that the old system should be preserved as a whole. Otherwise I’m afraid, a lot of people will stay on 2018.2 for quite sometime.
I know it’s probably too late for Unity to do anything drastic now… but still want to vent this one out.
I don’t know how many times it has to be said. The new prefab system is a change to the core of Unity, it’s not a C# library you can download through package manager or a git repo.
Even if Unity decided to write and maintain two separate ways of creating prefabs, how to communicate that through the Editor? With all the different icons, colors and inspector changes required it would be a bloated mess.
I think a more constructive approach to feedback regarding the new prefab system is to suggest improvements, rather than “I don’t like it, please revert”. This is a beta after all, things are bound to be buggy, especially with upgrading old projects. But that’s the point, find the bug and report it. Then we all get a stable editor at the end.
I don’t know how many times it has to be said, all the major grievances against the Improved Prefabs were aired during the 2018.2 beta of them, and they were all said to be either impossible to be fixed, by design or inextricably linked to this supposed core modification.
ergo, the only options left, for those reliant on the 10+ year old way of using Prefabs, are:
stay with 2018.2
hope Unity splits off Improved Prefabs to a package, somehow.
because option 3, them getting Improved Prefabs to be a true improvement on existing prefabs, isn’t going to happen.
Not long ago I had to go through my project and revamp a years worth of custom Shaders, it was painful, but we put our heads down and after a week of hard work we had a new shader system migrated from shader forge to Amplify shader.
At the time i was incredibly frustrated, doing work i thought was unnecessary. Looking back it was a godsend, the new, better shader editor has greatly expanded our ability to modify and upgrade shaders and we have no worries of the system suddenly becoming obsolete.
Prefab variants and nested prefabs are the future, I actually shifted dev of my personal project in a huge way in anticipation of them and can’t wait to go from having 6 core fish prefabs in my game to 5,000 now that we can confidently make prefab variants and update all content across the board very easily.
You may find prefab migration is easier than you thought, maybe you can make a scene, add all your current prefabs to it, break the connections, make them bare bones game objects, open 2018.3 and simply convert them to prefabs? I can’t imagine this process would be that gating to your project…
The fact that any prefabs migrate at all to the new one shows a lot of extra work on Unity’s part, I’m kinda kicking myself for not upgrading earlier but was playing it safe. This is kinda how gamedev is, you run into new features and you have to manage upgrading the project, we’ve known for a long time there would be hiccups, all things considered I’m really impressed by how well Unity has managed the transition to new and improved prefabs.
Gamedevs are spoiled and have gone soft these days :P. Horrific catastrophic failure is par for the course, if gamedev was hard everyone would do it…
Initial testing shows yes, but if I had not we would be able to reset our project very easily as we anticipated more issues and kept our current content very low.
TBH
The we fear change does no apply. I see this attitude enforced with the prefabs change to a point that makes me nervous.
new prefab system breaks projects. Ive updated a 5 years of work project from 4.7 with less broken feel. Its still a beta, fine. Still it renders the beta unusable for serious testing.
new system makes common operations way bulkier.
I’ve 0 complaints for the rest of additions same as pretty much it happened with other iterations latelly.
If you think people is ranting on this prefab system by chance and not other additions you can move on with it and pretend as if nothing happened
edit: forgot how much I dislike the new icons in hyerarchy.
It was meant to be a bit tongue in cheek. The new system can be improved, its footprint feels a little big right now, but give it time, feedback begets improvements, and tertiary elements will change, the core of the system works now and that’s what matters.
Variants and nested prefabs are amazing. Unity did a great job. No arguing about that.
I’ll be a happy man if 3 months from now, I can convert my old projects painlessly to 2018.3 and be not too annoyed by not being able to edit prefabs in project panel.
I’ve sent in my fair share of bug reports and took a risk posting in a beta.1 forum. The 2 issues in the OP are legitimate concerns. Hope Unity can take them into consideration.
One issue with new system is that it was stated that BY DESIGN it won´t allow multiple prefab editing at a time, aswells as surfing with arrow keys trough prefabs and checking properties won´t be possible for same reason, this features are gone pretty much forever, anyways, I just whant/need the current breaking issues be fixed, sure that helps change my modd to an extent, and NOT by 2018.3+ BUT 2018.2, current project upgrade status is broken so badly that this should be at the very top of the priorities, releasing .2 without a fix for this would be like enough to abandon beta evaluation after all we’re prodiding free (somewhat skilled) labour, I would expect som kindness in return.
You have mentioned the update in another thread, what doesn’t work for you?
I have a rather big project folder and it crashed after a day, but unity continued where it stopped once I restarted it.
These were discussed in the preview and someone mentioned an editor script could restore inspector on prefab root. Which means UT can implement that. so what happened since then? ( a.k.a source)
Sad to hear, cause I can tell you that you are missing out on some amazing features… the only pain I found with the new prefab system was rewriting all the prefab tooling we have and when I ran into some issues for 1 particular script that was breaking every intention of prefab (old and new) I came on forum and started to ask questions and took about 1 week of talking with Unity DEVs here and got it working and the result is somewhere in a thread here for all to use
what if you need to edit the prefab on the scene?
Often happen stat you need to edit the prefab directly on the current sene, and create a cascading (prefab inside a prefab) and keep all inside the scene 'cause you need reference and stuff… and just you can’t!
'cause it ask you to edit the prefab from the damned prefab editor?
which can be useful, but not always, and when it’s not, it irritating as hell!
I’m talking about this…
imagine to have edit a fence prefab which you are nested. You have to scale just the fence to make it fix beetween 2 other object (not the entire prefab just the fence). You have to go inside the prefab editor.
So the only solution to see what is going on is to have 2 windows, one with the prefab editor and one with the scene.
Yes, it’s a particular case, but it happens so often to me, that I decide to stick with 2018.2
As far as I see it there are two fundamental issues:
You cannot edit common components across multiple prefabs
You cannot immediately edit a component of a prefab without clicking ‘open prefab’
Unity NEEDS TO FIX THIS
(and to an extent the problem that you cannot edit a prefab in the context of a scene, though this seems to be an education issue)
Not just saying ‘we will maybe add it to our backlog’. We need concrete information that we can plan around.
So far we have received no confimation on what is being worked on, and over what timeline. Even worse, since 2018.3 basically morphs into 2018.4 LTS, we could be left with this system for a long time.
I hate to be blunt, but if Unity doesn’t fix these workflow issues by 2019.1, I am switching to Unreal Engine for any future projects.
Workflow-breaking changes like this should be introduced in the 20xx.1 versions of releases, not in 20xx.3
