Why not just remove the trello completely? The current one just adds work to your personnel without any real benefit to community.
Here are some examples of your competition understanding that a roadmap is supposed to show the future, not the past:
[=Zeblote;703442]
Here are some examples of your competition understanding that a roadmap is supposed to show the future, not the past:
https://unity3d.com/unity/roadmap
For a company as broke as Crytek, that roadmap… what are you doing epic?
Wow so many toxic people in forum.
The engine’s open source for god’s sake, do you want to help? Go help, learn to code, implement whatever the hell you’re dreaming about.
Want your own ? Go write your own .
Whining and complaining will not make anything better, on the contrary it will only demotivate the devs and others.
So far I think UE devs did a pretty amazing job with all these updates and if they changed their roadmap system, it’s probably because the new one is easier to manage for them.
[=;703458]
For a company as broke as Crytek, that roadmap… what are you doing epic?
You’re forgetting the fact that they delayed all these “on time” features for 2-3 months already, not to forget that they only do 2 major updates per year.
**Anyhow, here’s a request for UE forums/community: **
How about a reputation system, or even better, temporarily banning people from certain boards so that they stop with these stupid pointless rants ( I’m looking at you ).
It simply hurts to read these replies
I prefer the new roadmap because it’s way easier to see what’s done and being worked on. The one before had 's niche features they wanted and it was hard to know what was being worked on. It was easier seeing that by looking at commits. The most useful of the roadmap for me was the “DONE” tag when features were done for certain engine versions so that’s why the new one is basically just as good for me.
That being said it’s a bit… sparse at the moment with only 3 features tagged for 4.17 (unless 4.17 is only releasing with those 3) and I also think it could be good to list more longer term features in another category. For example I’m very interested in stuff like Niagara and things like that could be on the roadmap even if they’re not targeted for the next version. Another thing that was good with the old roadmap was the information updates in features that were being worked on. should be a part of the new roadmap too so people who don’t read commits have a way to find out what’s happening with the more long term features.
<reply to 's deleted comment>
I went through the thread, and I think you and others pretty much got the point across.
However, I agree with RicarDog, roadmaps work better when they don’t allow long-term discussions.
[=Zeblote;703442]
Here are some examples of your competition understanding that a roadmap is supposed to show the future, not the past:
https://unity3d.com/unity/roadmap
I think the organization of these roadmaps are by far better than what we just got. Unity is Alphabetical. CryEngine is by system type.
But I think there’s a bigger here that Epic as a company doesn’t trust other developers to give it feedback during development which is why things like voting have been removed. But voting, showcasing regular WIP progress on the roadmap + update notes, would help us feel way more involved and personally invested in seeing thing succeed. We don’t want anything bad to happen to Epic or Unreal Engine 4. We want to nurture ecosystem.
But when we have back and forth’s like the ones between and Dev where Max-Dev pointed out that SSS (subsurface scattering wasn’t working as intended) and argued that was the point as SSS couldn’t be properly replicated anyway. I think conflicts like those are regressive and could have been addressed with regular twitter like updates added to the Trello roadmaps regarding the limitations Epic Staff are working with. Ultimately, both sides end up feeling salty. Max-Dev feels like Epic doesn’t care about him. The Epic staff meanwhile feel like they are being unfairly criticized for technical limitations beyond their control.
More communication is the answer. Not less. The engine is open source anyway so I don’t see the problem with additional notes being added to the roadmap as to how things are coming together. Trust us, we’ll appreciate it and the community will be healthier for it.
[=;703539]
But I think there’s a bigger here that Epic as a company doesn’t trust other developers to give it feedback during development which is why things like voting have been removed.
So, they do not trust you to give feedback… Interesting, you are on a FEEDBACK FORUM! There are other ways besides VOTING to give your feedback and help determine the future of the engine… You are doing it now, albeit in an annoying way…
[=Zeblote;703442]
Here are some examples of your competition understanding that a roadmap is supposed to show the future, not the past:
https://unity3d.com/unity/roadmap
Visual scripting has been on the Unity map for years… How will a roadmap help you in terms of the games / projects you are working on now? Would you slow development until a certain is released? Are you just curious? Why is a long term roadmap (in the case of Unity, YEARS for Visual Scripting) important?
[=teak421;703550]
So, they do not trust you to give feedback… Interesting, you are on a FEEDBACK FORUM! There are other ways besides VOTING to give your feedback and help determine the future of the engine… You are doing it now, albeit in an annoying way…
My apologies for not being clear enough. Requesting feedback, AFTER Epic is finished with a system, instead of during development is what my post addresses.
For example they have a new audio system in 4.16. We knew nothing about how that was going to be implemented. If one of us comes up with a much better way of going about audio, but it means Epic has to start over from scratch, that’s going to be difficult for Epic to justify and we’ll be stuck for years with something that could better implemented.
A great example is the current way UE4 does roads. Implementing Spline Decals requires in some capacity trashing the work that came before it. Epic doesn’t want to feel like they wasted resources of course and so it becomes much more difficult to justify adding such a set. But if we’d been in the conversation early on when was being discussed for UE4 maybe Spline Decals would have made it in from the start. In the case of my personal project, would be something that would undoubtedly help speed up development of my project by months.
[=;703562]
My apologies for not being clear enough. Requesting feedback, AFTER Epic is finished with a system, instead of during development is what my post addresses.
For example they have a new audio system in 4.16. We knew nothing about how that was going to be implemented. If one of us comes up with a much better way of going about audio, but it means Epic has to start over from scratch, that’s going to be difficult for Epic to justify and we’ll be stuck for years with something that could better implemented.
A great example is the current way UE4 does roads. Implementing Spline Decals requires in some capacity trashing the work that came before it. Epic doesn’t want to feel like they wasted resources of course and so it becomes much more difficult to justify adding such a set. But if we’d been in the conversation early on when was being discussed for UE4 maybe Spline Decals would have made it in from the start.
4.16 is not out yet and its May 3rd. There was a stream about the new audio engine back in early Feb. Did you watch that presentation? Did you come to the feedback forum and suggest changes? I know there is a robust discussion about the new audio engine now. Are you contributing to that discussion?
[=;703562]
A great example is the current way UE4 does roads. Implementing Spline Decals requires in some capacity trashing the work that came before it. Epic doesn’t want to feel like they wasted resources of course and so it becomes much more difficult to justify adding such a set. But if we’d been in the conversation early on when was being discussed for UE4 maybe Spline Decals would have made it in from the start. In the case of my personal project, would be something that would undoubtedly help speed up development of my project by months.
Could you point me to the feedback post you created on the feedback forum? Would like to review and maybe add my 2 cents…
[=]
Could you point me to the feedback post you created on the feedback forum? Would like to review and maybe add my 2 cents…
You can see the issues with mesh decals and why Spline Decals should be implemented. Because Epic implemented Mesh Decals, which to be fair was a long time ago, my own personal project is hampered by the number of roads I in my project, and the time investment needed afterwards for the terrain touchups needed to make the look nice.
In the future if the inclusion of such features were more transparent, wouldn’t have been as big of an. That transparency could be easily communicated through the roadmap as the features are being created rather than as development winds down. We could weigh the pros and cons of how similar systems in other engines is handled, like how does in that thread, comparing CryEngine and Unreal. The alternative is like I discussed before. We’re stuck with Mesh Decals with no clue when Spline Decals will be implemented. Roadmap voting would let us get that figured out sooner as well.
If you’re looking to discuss how affects me personally, please send me a PM. After 's last couple of messages about fighting, I’m not looking to derail the thread.
[=;703581]
You can see the issues with mesh decals and why Spline Decals should be implemented. Because Epic implemented Mesh Decals, which to be fair was a long time ago, my own personal project is hampered by the number of roads I in my project, and the time investment needed afterwards for the terrain touchups needed to make the look nice.
In the future if the inclusion of such features were more transparent, wouldn’t have been as big of an. That transparency could be easily communicated through the roadmap as the features are being created rather than as development winds down. We could weigh the pros and cons of how similar systems in other engines is handled, like how does in that thread, comparing CryEngine and Unreal. The alternative is like I discussed before. We’re stuck with Mesh Decals with no clue when Spline Decals will be implemented. Roadmap voting would let us get that figured out sooner as well.
If you’re looking to discuss how affects me personally, please send me a PM. After 's last couple of messages about fighting, I’m not looking to derail the thread.
The Epic engineer responded to that thread and has been transparent. The outcome wasn’t what you and others wanted, but they did respond. Did you read the post suggested by the engineer about why certain features might not make it into the engine? What more do you want Epic to do? Other than implementing the , what additional communication could they have done in addition to the posts already on that thread? is transparency… No? You may not like the method of communication…forum responses as opposed to a road map, and that’s made perfectly clear. The end result though is the same…communication.
You didn’t answer my audio question and how Epic failed to be transparent about a that was introduced back in early Feb. What else could they have done that would have satisfied your transparency needs?
[=teak421;703627]
The Epic engineer responded to that thread and has been transparent. The outcome wasn’t what you and others wanted, but they did respond. Did you read the post suggested by the engineer about why certain features might not make it into the engine? What more do you want Epic to do? Other than implementing the , what additional communication could they have done in addition to the posts already on that thread? is transparency… No? You may not like the method of communication…forum responses as opposed to a road map, and that’s made perfectly clear. The end result though is the same…communication.
You didn’t answer my audio question and how Epic failed to be transparent about a that was introduced back in early Feb. What else could they have done that would have satisfied your transparency needs?
Communication and clear communication are two different things. There was clearly a failure to communicate clearly which is what my post addresses. Like I mentioned, conflicts like those are regressive and could have been addressed with regular twitter like updates added to the Trello roadmaps regarding the limitations Epic Staff are working with. Ultimately, both sides end up feeling salty. Max-Dev feels like Epic doesn’t care about him. The Epic staff meanwhile feel like they are being unfairly criticized for technical limitations beyond their control. What you’re arguing is that bad communication is okay as long as the attempt is made. I disagree with that assertion. I’m sure many others will as well.
Regarding the audio, send me a PM regarding my discussion of the audio system. I fear there’s a few things that have gone over your head. But if you want to post a full history of how the new audio system was introduced for us, the methods placed for us to review it, and how both reveal and review were in correlation with the roadmap, I think the entire thread will be happy to go through the process with you, myself included.
[=;703633]
Communication and clear communication are two different things. There was clearly a failure to communicate clearly which is what my post addresses. Like I mentioned, conflicts like those are regressive and could have been addressed with regular twitter like updates added to the Trello roadmaps regarding the limitations Epic Staff are working with. Ultimately, both sides end up feeling salty. Max-Dev feels like Epic doesn’t care about him. The Epic staff meanwhile feel like they are being unfairly criticized for technical limitations beyond their control.
Regarding the audio, send me a PM regarding my discussion of the audio system. I fear there’s a few things that have gone over your head. But if you want to post a full history of how the new audio system was introduced for us, the methods placed for us to review it, and how both reveal and review were in correlation with the roadmap, I think the entire thread will be happy to go through the process with you, myself included.
PM is not necessary… The feedback provided by you about how the audio changes were introduced (and discussed on a current forum thread) back in early Feb would be important for all to see…most importantly, Epic.
[=teak421;703627]
The Epic engineer responded to that thread and has been transparent. The outcome wasn’t what you and others wanted, but they did respond. Did you read the post suggested by the engineer about why certain features might not make it into the engine?
It was actually 's post on the thread not an Epic engineer. And what did was linking an engineer’s external article on why some features might not be implemented. It didn’t necessarily mean spline decals aren’t in because of something related to that article. creates confusion. mentioned if there’s enough audience for it, it’ll be looked into. Spline decals are a tool with wide use and large audience. I asked how many votes are needed and we’ll literally spread the news so anyone who needs the tool will vote for it. Of course if don’t, only 5-10 people will vote for it since others aren’t aware such ticket exists. I didn’t get a response from on that. And more over, none of the engineers have actually responded to the thread to let us know if they have seen the thread or not, if there is a barricade in the way or not, if they’re going to add it sometime later or not. That’s where transparency is lacking.
If any of the engineers step in and say look, despite tool having a large audience, despite most of you being harmed because of absence of tool, we’re not able to implement it for X reason, I’d say alright thanks for getting back to us. That’s how simple it is.
Edit: Like said, I don’t like to be banned either so please post in related thread if you want to leave a reply.
Looking forward to reviewing how Epic could have improved the rollout of the audio changes… Until then, have a great one…
[=;702472]
Hey all, thank you for all of your feedback on the roadmap, our bug list and other pieces of our offerings. It seems that more heads up on the roadmap alterations would have been welcomed. is on us, and we’ll do our best to provide more runway for conversation to happen before we make wide changes to how we present information going forward. Thanks for your patience with us while we work through the change and apologies for any pain felt. We’re parsing a lot of the feedback here in hopes to continue to evolve our offerings based on it. A couple ways you can help us hear you better in thread:
BUGFIXES: We understand that a number of you have been looking for specific bug fixes to be implemented. The best place to continue those conversations is somewhere outside of roadmap thread. The roadmap is a place to discuss forward facing features and issues should be taken up on their answerhub thread or in the parent forum - Feedback for Epic. As a few others have pointed out, has a great follow up regarding some of the questions that have been brought up in thread over here.
ARGUING / FIGHTING: is hopefully the last time I’ll mention , but please keep the fighting and attacks to a minimum in thread and on these boards. Taking shots at each-other is not constructive for anyone involved, and we’ll have to take action if it continues.
There’s a ton of great discussion regarding the Unreal Engine roadmap happening here that we’re thankful for (and heading!), I fear a lot of it is being lost in arguing and off-topic discussion. Thanks for helping us make a productive conversation and keeping things on track while we pursue ways to better serve you all.
How is the parsing of the feedback going?
Also:
- When can we get a conversation going on what will happen with 4.17? Or is that never going to happen?
- Why can’t you post more than once every 24 hours in regards to the road map (or on the forums in general)?
- Why did you go the whole month without telling us about the changes to the road map?
- When is the next update to the roadmap coming?
- Are any of the the upcoming features in 4.17 debatable?
- How are decisions made on what to work on next? Does each team work on whatever they feel like? Or is there overall directive and goal going from version to version?
- What is the reason bugfixes can’t be on the Roadmap? It seems like otherwise they get forgotten for literally years on end? How do you intend to address otherwise?
- Should we continue to expect a culture of prioritizing new features at the cost of bugfixes in the Roadmap?
- What spurred on the decision to prioritize the Audio System for 4.16?
- Does the Roadmap take into account other games generating revenue for Epic that could use specific features? If not, what could spur that on?
- Instead of a voting system like before, why not set up a bracket system organized by Epic for the community, where we can vote for specific features? We start with 64 potential features. The top 32 voted features move to the next voting bracket. We vote again and the top 16 features move up. Eventually when we have our top 4 features, that’s how you know what the community wants the most. Services like Brackify: https://brackify.com/product/pricing - will let you do that for free. Winners get added to the road map (along with a time frame for how long they’ll take to be implemented, meaning that a might get put on the agenda today to be completed by 4.19).