is getting a bit silly…but… simply go to issues and click on FIXED and then sort by VOTES. You will see a TON of things fixed that were highly voted on. But, that also works the other way, there are also highly voted on items that are backlogged. Again, its a bummer things are backlogged, but to say Epic doesn’t fix highly voted items is not fair. Could they do better? Sure… We all could. But, with limited resources they do have to make some choices. Anyway… Hopefully your issues gets worked on.
Epic doesn’t pay me to defend them nor do they need to be defended, but these posts of certain individuals here are just bizarre. UE4 is designed as general purpose engine to suit needs of Epic and partners as far as I understand the concept. Unlike Unity, which is tailored to the likes of all kind of devs, UE is tailored to serve Epic’s projects first. So, if you happened to be making something along the lines of what Epic is working on, you should have a way less issues and missing features.
If you have enough money, like Oculus, you could probably partner with Epic to make a project that will encompass all the features you need. Otherwise learn how to enjoy what you are offered for free or use another engine.
I need some features that UE4 doesn’t have (or they are half-a$$ or broken). It seems common sense for UE4 to have those features, but it doesn’t and it won’t until Epic or partners need it. I was bitter about it when I started with UE4. Now it just seems obvious why things the way they are and I simply either avoid using those broken/half-a$$ed features, or find a way to live without missing features. Welcome to f#$king real life. Make peace with it and move on.
We can sit here and argue bug fix priorities all day. At the end of the day, some highly requested things will be skipped, others will be implemented. People need to realize that while the community is great and all, the VAST majority of the community will not do anything worthwhile with the engine and simply want features because they’re shiny. Epic will prioritize the needs of huge studios and their own internal teams due to the simple fact that those are much more experienced developers who actually help keep the company alive.
HOWEVER, I do want to contribute on something else. Seeing the posts about “not being able to get Epic to recognize issues” I remembered that I had a very frustrating experience of that same nature too. It went something like :
“Scaling the landscape even by 0.01 in any direction would cause the generated foliage instance count to increase hundredfold, causing extreme performance drops. was regardless of foliage layers, material setup, anything.”
It was that simple. Yet it took a long time going back and forth and the was never acknowledged. Digging back through AnswerHub I noticed that of course, it was AndrewHurley with whom I had the exchange with:
questions/313894/bug-landscape-grass-takes-forever-to-load.html
I don’t know if bug is still in the engine as I’ve stopped scaling my landscapes, but the whole exchange has been frustrating beyond belief. It was very clear that didn’t understand the and didn’t properly follow the reproduction steps, trying to shift blame on me due to something completely unrelated to the bug I was reporting (“You should sample layers, not have foliage on the whole terrain!”).
[=teak421;701658]
Did you click on any of the issues I linked? The first one had 37 votes… While the one you linked had 44, its not too far off. Plus, I only went through about 2 pages worth of links…I could have done more, but I thought it was a waste of time. Bottom line, Epic does indeed fix bugs that are highly voted on…do they always fix highly voted, well…no. But, to say they do not fix highly voted on issues is unfair as indicted by the links I gave above.
Yes I clicked on them. 37 votes is 7 votes less than 44. Obviously votes number doesn’t help with the sorting. Also your 33 votes report was created on Dec 9, 2014 and fixed on Mar 2, 2017, even if it was fixed just for the sake of votes, 2.5 year wait is how much a highly voted bug report was valued… I’m not sure if I’d still be here by the time the one with 44 votes gets fixed.
[=;701666]
It was that simple. Yet it took a long time going back and forth and the was never acknowledged. Digging back through AnswerHub I noticed that of course, it was AndrewHurley with whom I had the exchange with:
questions/313894/bug-landscape-grass-takes-forever-to-load.html
I don’t know if bug is still in the engine as I’ve stopped scaling my landscapes, but the whole exchange has been frustrating beyond belief. It was very clear that didn’t understand the and didn’t properly follow the reproduction steps, trying to shift blame on me due to something completely unrelated to the bug I was reporting (“You should sample layers, not have foliage on the whole terrain!”).
strikes again!
[=;701677]
Yes I clicked on them. 37 votes is 7 votes less than 44. Obviously votes number doesn’t help with the sorting. Also your 33 votes report was created on Dec 9, 2014 and fixed on Mar 2, 2017, even if it was fixed just for the sake of votes, 2.5 year wait is how much a highly voted bug report was valued… I’m not sure if I’d still be here by the time the one with 44 votes gets fixed.
That the point! They do get to them… Also, yes… sorting does help… Here’s a screen shot…
@teak421, To be fair what’s happening is :
We report bugs, bugs go in two separate categories based on random selection. To-do and Backlogged.
To-do bugs get fixed, sometimes the one with more votes is fixed before the one with less votes.
The backlogged ones get votes. They stay backlogged for sometimes even a year, the number of votes grow even more than a highly voted report that’s on the to-do list, yet the backlogged bug doesn’t get the slightest attention, not even clear why it’s backlogged.
Anyone reading my posts thinks I’m being negative and looking at the empty half of glass but that’s just honestly what we are experiencing.
It’s not fair to blame the shortage of manpower if it’s a billion dollar company and there’s been 8 months, sometimes 2 years passed since a bug report that’s highly voted on.
.
.
.
Edit: “You” sorted the view based on votes, they don’t sort the bugs like that and start fixing from top to bottom.
[=;701690]
@teak421, To be fair what’s happening is :
We report bugs, bugs go in two separate categories based on random selection. To-do and Backlogged.
To-do bugs get fixed, sometimes the one with more votes is fixed before the one with less votes.
The backlogged ones get votes. They stay backlogged for sometimes even a year, the number of votes grow even more than a highly voted report that’s on the to-do list, yet the backlogged bug doesn’t get the slightest attention, not even clear why it’s backlogged.
Anyone reading my posts thinks I’m being negative and looking at the empty half of glass but that’s just honestly what we are experiencing.
It’s not fair to blame the shortage of manpower if it’s a billion dollar company and there’s been 8 months, sometimes 2 years passed since a bug report that’s highly voted on.
Edit: “You” sorted the view based on votes, they don’t sort the bugs like that and start fixing from top to bottom.
Random selection…? They flip a coin to determine which bugs they work on? Really!? Uh… How do you know ?
I’m going to jet… is getting a bit silly and I’m not helping…
[=teak421;701693]
Random selection…? They flip a coin to determine which bugs they work on? Really!? Uh… How do you know ?
You are being silly. What he means is obviously that there’s no way for us to tell which bugs will be fixed and which will be doomed to the eternal limbo of the backlog. We don’t know the criteria nor the selection process. is reading comprehension 101 and you seem to misunderstand his post on purpose.
Well yes it’s quite random that sometimes your report get’s a “solved” 3-4 times because they didn’t understand the, and then after days/weeks of back and fourth and providing evidence the problem is there, “in only a matter of seconds” you see a bug report created with it reading “Backlogged” without any evaluation.
[=;701698]
You are being silly. What he means is obviously that there’s no way for us to tell which bugs will be fixed and which will be doomed to the eternal limbo of the backlog. We don’t know the criteria nor the selection process. is reading comprehension 101 and you seem to misunderstand his post on purpose.
Ok, true dat… I’ll admit, silly. I’ve tried to be a bit light-hearted here and it doesn’t look like it worked.
SO,
I didn’t do a search of the forums for , maybe its there and so it wouldn’t be random…but…for clarification: Epic, can you explain how you select which bugs to work on and which ones to backlog? And, once put out there, have people weigh in on it to determine if the team needs to make changes. I’m going to start a new thread, since is for the road map.
I think the staff needs to realize they are directly responsible for the livelihood of others, and I don’t think many DO necessarily recognize that. They think that they’re working on something cool or that someone complaining is just being mean to them. But you have to look at it from our perspective in that if you imagine that said he wasn’t going to pay you guys, how quickly you get angry because that hurts your livelihood.
That’s the same position you’re putting us in in that you’re hurting our livelihoods. It’s a hurtful move to leave people in the dark for months, to lie to them about when a roadmap is coming, or to blow off their problems and concerns. It doesn’t cost you a dime to come here and post regular updates for us. Weeks, months, and years later, we’re at a point where that frustration is manifesting itself here on the forums. Saying you’re listening is different than talking back. “We hear you” is meaningless without a meaningful back and forth.
The Engineers who feel like they’re being unfairly derided, or ridiculed, need to come to grips with the fact that you are literally making people’s lives harder for them. is what being in a position of responsibility is like because when you put out product called Unreal Engine 4, your company told , “is going to be able to let you live the life you always dreamed of being able to live” and you accepted that you would be responsible for making that happen.
Then when you don’t follow through on those promises, patronize people who request help, lie to others about when a roadmap is coming up, you’re obviously going to get treated with ridicule because, again, you accepted that responsibility. The engineers may think they’re just doing their own thing and they’re collecting their paycheck and going home. But people like need to remember that you are DIRECTLY responsible for other people’s lives and when you ignore their calls for help, you are being absolutely unprofessional and do not deserve the paycheck you collect. At minimum, who blew off deserves their problems reviewed. At best, the Epic staff understands the seriousness of the responsibility your executives took when they accepted being responsibile for people’s livelihoods.
[=;701726]
I think the staff needs to realize they are directly responsible for the livelihood of others, and I don’t think many DO necessarily recognize that. They think that they’re working on something cool or that someone is just complaining and being mean to them. But you have to look at it from our perspective in that if you imagine that said he wasn’t going to pay you guys, how quickly you get angry because that hurts your livelihood.
That’s the same position you’re putting us in in that you’re hurting our livelihoods. It’s a hurtful move to leave people in the dark for months, to lie to them about when a roadmap is coming, or to blow off their problems and concerns. It doesn’t cost you a dime to come here and post regular updates for us. Weeks, months, and years later, we’re at a point where that frustration is manifesting itself here on the forums. Saying you’re listening is different than talking back. “We hear you” is meaningless without a meaningful back and forth.
The Engineers who feel like they’re being unfairly derided, or ridiculed, need to come to grips with the fact that you are literally making people’s lives harder for them. is what being in a position of responsibility is like because when you put out product called Unreal Engine 4, your company told , “is going to be able to let you live the life you always dreamed of being able to live” and we accepted that you would be responsible for making that happen.
Then when you don’t follow through on those promises, patronize people who request help, lie to others about when a roadmap is coming up, you’re obviously going to get treated with ridicule because, again, you accepted that responsibility. The engineers may think they’re just doing their own thing and they’re collecting their paycheck and going home. But people like need to remember that you are DIRECTLY responsible for other people’s lives and when you ignore their calls for help, you are being absolutely unprofessional and do not deserve the paycheck you collect. At minimum, who blew off deserves their problems reviewed. At best, the Epic staff understands the seriousness of the responsibility your executives took when they accepted being responsibile for people’s livelihoods.
I can feel your pain.
The only tip i can give you is to learn using unity,even when its not super hot at the moment.
Workflow and Level Editor are already now better in unity , some other stuff is not.
But im under the impression at the moment that the unity team is more hungry to give the users cool new features then the unreal devs are.
So hopefully unity catches up on the graphics site enough to consider it as engine soon.
You should really get a second leg to stand on because the Situation with unreal will not get any better, trust me.
You can extrapolate from the last years.
Communication got worst every year and you will not be here when it reaches bottom line.
[=emeraldcoast;701814]
But im under the impression at the moment that the unity team is more hungry to give the users cool new features then the unreal devs are.
I can’t even start to care about new features until the basics like collision detection actually work.
[=emeraldcoast;701814]
I can feel your pain.
The only tip i can give you is to learn using unity,even when its not super hot at the moment.
Workflow and Level Editor are already now better in unity , some other stuff is not.
But im under the impression at the moment that the unity team is more hungry to give the users cool new features then the unreal devs are.
So hopefully unity catches up on the graphics site enough to consider it as engine soon.
You should really get a second leg to stand on because the Situation with unreal will not get any better, trust me.
You can extrapolate from the last years.
Communication got worst every year and you will not be here when it reaches bottom line.
Every single “serious” game made with Unity suffers from extreme performance issues. That alone is reason enough to steer around it in a very large circle.
[=;701677]
Yes I clicked on them. 37 votes is 7 votes less than 44. Obviously votes number doesn’t help with the sorting. Also your 33 votes report was created on Dec 9, 2014 and fixed on Mar 2, 2017, even if it was fixed just for the sake of votes, 2.5 year wait is how much a highly voted bug report was valued… I’m not sure if I’d still be here by the time the one with 44 votes gets fixed.
Actually 4.15 and 4.16 are the first releases that actually fix some of most voted issues!
Now… some of you gonna complain “oh no, why it took so long?”. But others could see hope here, i.e. some annoying and “basic” bugs in blueprint system are finally fixed 
Number of votes can’t be never the only deciding factor for single reason. Different teams and people are responsible for different parts of engine.
So often issues with no votes at all are fixed faster because given team is “free” for few days. Or they refactor some tool so it’s easy and quick to address many issues at once.
Once “blueprint guys” started to work on most voted issues, they fixed few of them.
But I agree with you - producers should minimize situation in which a lot of important issues wait over 2 years to be fixed. And then decrease " waiting period" with every release.
[=emeraldcoast;701814]
I can feel your pain.
The only tip i can give you is to learn using unity,even when its not super hot at the moment.
Workflow and Level Editor are already now better in unity , some other stuff is not.
But im under the impression at the moment that the unity team is more hungry to give the users cool new features then the unreal devs are.
So hopefully unity catches up on the graphics site enough to consider it as engine soon.
You should really get a second leg to stand on because the Situation with unreal will not get any better, trust me.
You can extrapolate from the last years.
Communication got worst every year and you will not be here when it reaches bottom line.
The thing is using any engine is an investment. In many ways its like buying a house and building a life around the location of that house. You can’t just pick up the codebase we invested to make for platform and move to another engine. And so early on many of us had to make a decision whether we would trust Epic and build our life in ecosystem. Whether we would invest thousands of dollars to get a project made that would earn a living for all of us (and in turn share 5% of the wealth we accumulated with Epic Games for giving us that platform).
In many ways our decision to settle into ecosystem now feels like its being taken for granted and that is hurtful. You might have the most qualified engineers in the industry working at Epic, but might as well have hired robots if they can’t begin to care about our needs and concerns, and talk to us with a sense of decency and duty. It’s a genuine betrayal of the trust we placed in platform when we first moved in. You can’t make people wait three years for a bugfix. You can’t tell people a roadmap is going up in early April and then go radio silent as that time comes and goes. It takes 10 minutes to throw up a forum post. In that time if we check out 's Twitter, he’s tweeting about playing Persona 5.
, how are you going to play Persona 5, when your team promised that we’d get an update for the roadmap in Early April? Don’t you see how screwed up that is? People are waiting with their livelihood in their hands and you’re busy playing Persona 5 instead of following through on your word. That doesn’t mean you’re listening. It might as well mean you’re not even here. You’re hurting us.
[=;701985]
The thing is using any engine is an investment. In many ways its like buying a house and building a life around the location of that house. You can’t just pick up the codebase we invested to make for platform and move to another engine. And so early on many of us had to make a decision whether we would trust Epic and build our life in ecosystem. Whether we would invest thousands of dollars to get a project made that would earn a living for all of us (and in turn share 5% of the wealth we accumulated with Epic Games for giving us that platform).
In many ways our decision to settle into ecosystem now feels like its being taken for granted and that is hurtful. You might have the most qualified engineers in the industry working at Epic, but might as well have hired robots if they can’t begin to care about our needs and concerns, and talk to us with a sense of decency and duty. It’s a genuine betrayal of the trust we placed in platform when we first moved in. You can’t make people wait three years for a bugfix. You can’t tell people a roadmap is going up in early April and then go radio silent as that time comes and goes. It takes 10 minutes to throw up a forum post. In that time if we check out 's Twitter, he’s tweeting about playing Persona 5.
, how are you going to play Persona 5, when your team promised that we’d get an update for the roadmap in Early April? Don’t you see how screwed up that is? People are waiting with their livelihood in their hands and you’re busy playing Persona 5 instead of following through on your word. That doesn’t mean you’re listening. It might as well mean you’re not even here. You’re hurting us.
You know they take Saturday and Sunday off.
[=Themanwithideas;701994]
You know they take Saturday and Sunday off.
Was just gonna say that… it’s Sunday.