So, what’s next guys?
Sometime ago you commented something like publishing a roadmap. Have you changed mind?
Anyway, are you going to open a new forum group for the next release, like you did with 5.1 beta?
I think there is a small roadmap session next week at Unite so maybe they will put something on the web after that (finally). If not, then it’s starting be as big joke as the UI was and we need a roadmap for the roadmap 
1 Like
I would peg 5.2 release around unite US, or maybe the beta at least. So far features that have been mentioned and are likely candidates have been hinted at in various tweets and forum posts.
A new UI rendering batch algorithm for improved UI rendering performance. A big issue since the UI was released.
They teased some improved 2d toolset features. Including a tile map terrain builder.
Aras was also working on some CPU rendering improvements (somewhere around 10% savings). I am not sure if those made it into 5.1.
I figure a roadmap for them is hard because there is so much R&D going on and the time might be reappropriated based on ever-changing priorities. Which means there will be a lot of broken promises going beyond a patch or two into the future. Having a rigid roadmap is dangerous in the fast-paced area of technology where support for the latest rendering API or the latest piece of hardware might need to take priority over another feature that patch.
Yes, I completely agree that publishing a roadmap with a reference timetable could be dangerous. But at least a prioritized list of demanded features, like SSR and many others so we can stop requesting over and over the same things.
I would say that WebGL should be prioritized, so the “preview” label can be removed ASAP.
The requesting will not stop with a roadmap in place, that’s for sure. People still would have the possibility to complain about the priorities and if something goes wrong they will criticize that and will ask why feature X is already done which had a lower priority than feature Y which is still missing, though it is without question the most important feature ever. The amount of requests would likely stay, but the discussion would shift into a slightly different direction.
Regarding WebGL, it already seems to have a high priority as it is frequently mentioned in the release notes. Removing the preview most likely depends more on the browser vendors and other external forces than Unity itself.
WebGL preview tag isn’t going away for quite some time AFAIK. It’s not only about Unity priorities but also about browser vendors, emscripten team etc.
For roadmap there could at least be a list what is being worked on without timeframes or with rough ones. Now the info is only in random blog post, dev posts on the forum etc.
Someone should write a bot that collects posts from people with the black unity tag, could give lots of hints about whats being worked on without searching for it.
1 Like
Yeah some forum system have own dev tracker threads and/or all threads with dev answers marked with custom symbol.
I have most devs followed here with the forum feature so it provides good stalker feed too
4 Likes
A dev post tracker for the forums is actually a pretty good idea! Although I’d want to ignore some dev’s postings, like all of the lockable topics that Aurore and Andy Touch needs to post in for example.
I already have created the “isthenewguioutyet.com” and I swear… if they’re not publishing the roadmap, I’ll grab the “istheroadmapoutyet.com”…
1 Like
Well why not use dynamic task system, where the most wanted features are tracked and colour coded to indicate their state and with what release they will arrive. And as it’s a dynamic system so nothing is fixed in stone.
Let’s hope that cool temporal antialiasing will be possible in 5.2.
Lets hope some of the bugs the community is complaining about are fixed in 5.2, no new features even needed.
UI issues priority + Performance fixes are a must for mobile development 4x + 5x
Android related issues to low FPS 5x + BlackScreen reports on 5.1
Mostly mobile performance fixes in 5x builds + common bugs.
1 Like
Definitely need features…
- Option for 32-bit vertex indices.
- Option to cap mip-map levels.
- GI that can work on procedurally generated terrain.
- Metal support on OS X.
- IL2CPP on desktops.
- Better multithreading support.
I think that sums up my list of wishes. Granted, maybe those aren’t needed in 5.2. Hopefully soon though!
1)Okay I agreed with Metal Support on OSX and Retina Support - both confirmed to be coming (doubt in 5.2)
2)What do you mean better multithreading support? For mobile development I see this option but currently no one has been able to confirm what exactly happens when this tick box is checked (in my experiance nothing)
3)IL2CPP Desktop, its taking them long time to even finish iOS but progress is being made each week, so I think this would take some time, maybe months. I not sure if they plan to do Android next?
I find myself quite annoyed at the “so and so function can only be called on the main thread” even when I’m doing perfectly thread safe things that (at least in my mind) have no possible way of messing up any internal systems, and then always having to work around it by using slower and more obnoxious code.
Can i haz dis please? O_O
Would you mind providing an example?
I think it’s pretty hard to say that something shouldn’t cause problems without knowing how Unity manages the underlying datastructures.
Here’s the roadmap: Whats Unity roadmap look like? - Industries - News & General Discussion - Unity Discussions
Not going to reply to all the speculation but:
There’ll be a new beta forum once 5.2. hits beta (currently in alpha).
The preview label on WebGL will indeed be with us for a while. Like @Ostwind mentioned we depend a lot on browser vendors and JS itself to move forward.
The Unite talk will have more details as to what is coming down the line as the name implies 