I suggested layers way back because placing things on platforms or near other objects can become a more than a frustrating chore to accomplish. The problem is they're still poorly implemented.
I've asked for things to be fixed in them and that has fallen on deaf ears and has gone into the ether. It's more fun making new things rather than fixing things.
* When selecting the lock or the hide/unhide option, why does that become the selected layer?
* When adding to a layer, there's no way of knowing afterwards what objects are added to that layer without selecting individual objects on the route.
Clicking on the layer should have a + to expand a tree underneath to display the added objects. The ability to select assets and drag them to another layer or select and right-click to bring up options to do so would be helpful. With this, assets can be selectively hidden, unhidden, and moved much like a CAD or graphics creation program such as Illustrator, or DrawPlus.
* There's no way of group-selecting assets and moving them all to a selected layer. (This may be true in S20, but I couldn't get it to work, so I'm assuming it's still not there.)
* We don't know what layer we've selected. This is true even with Surveyor 2.0. How about a different color, or a big colored bar on the top? The layers palette while visible works only if it is visible.
* Layer meaning/terminology needs to change. Session layer vs. Session is the biggest bugaboo we have. How many people get caught out on that one?
Fixing bugs before release. What's wrong with that?
Back in the olden days of software development things were different, at least that was what I was taught when I had to take those required programming classes.
There needs to be more than a cursory check before releasing a product. This is true for all developers but unfortunately, due to clueless CEOs and S&M driving the SDLC instead of R&D, it's all about promises and less about quality. How many times have we received a flop that has required at least 4 service packs plus hotfixes to make the product worthwhile? Hint... Looking at T: ANE. A product that was rushed to market that was plagued with CTDs, smokenados, a inoperable program, poor performance, and a hopper full of other bugs too many to mention.
Gone are the days of real beta testing. Companies today create a product, put it through a cursory crash test, give it to the public to test and send the product out. The only time a product is pulled is when there's a show stopper. A C-level VP once said that part out loud at one company I worked at. If there are no show stoppers, any bugs are thrown over to tech support, now duly offshored to a low wage country, for support. N3V does have an internal helpdesk, so I'll give them credit, but most companies won't pay diddly squat for support because that's not a money-making area. In fact, most employees are considered liabilities now according to the bean counters, so if they can dispense with those, they will too. Watch out for AI doing the development next... I digressed, sorry.
We saw this with T: ANE and it's gotten worse with every version. Public beta testing is fine for the final phases of a product but not for the beginning. Many people join a beta to have the latest version for bragging rights and only a few dedicated testers will test products. Sadly, this is true for N3V as it is for Microsoft and many others.