d4ddyo said:
xtonex said:
Yes DJI please rush out a fix that causes other problems in the process just so people can shut up... if your hoping dji "hurries" this along your pretty foolish... also if you have "violent tbe" its more than likely due to something else. i live in a high declination area and my tbe has never been "violent" or high speed... I'm pretty sure most of you have zero clue what it takes to code anything like this or go thru code and find problems in it! Keep your pants on
I know exactly what it takes. You keep your panties from bunching because it is what it is. Do you work for dji? If you do then listen to customers. It's all about communication which dji doesn't have. That's pretty pretentious of you to think that only you know what it takes and no one who is tired of this garbage knows what it takes.
We are customers. We are entitled to expect them to address the issue. It took them months to even acknowledge the issue.
It's taking them months to come up with a fix that's only a couple of line of code and on top of it they are putting it off this week for pressing issues ? They are making a killing on the sales so they should increase their budget on this department.
This issue goes back to last year and we are approaching mid year already!
No I do not work for DJI and DJI has been in contact with the beta testers. And you can go back in this thread and see when DJI got involved it wasnt last year and it wasnt until AFTER this thread was started. And the thread was only started 2 months ago.
I never said im the only one who knows what it takes to look thru code and find and fix a problem. I said most of the people whining about how long its taking DO NOT. If you know about coding then you know it CAN take a long time to find a issue and correct it and then test the corrections. Its obvious the naza cleans up the probem with time. Im sure its not so obvious as to why it takes so long and isnt done right off the bat. Where do you get that its only a couple lines of code to fix this problem? if you think its so easy your free to look thru the firmware and fix it yourself? Maybe apply for a job at DJI and help them...
Atleast show us your example of a few lines of code that would work or fix the problem... if not just shut up and wait for DJI to do what they need to do. All the bitching and moaning in this thread is not going to help anything.
This thread was to get a count of how many people were being effected by the issue and to get DJI's attention which is has. I think it might be time to lock it up AND BE PATIENT!