EdisonW1979
Second Officer
Flight distance : 1535679 ft
Canada
Offline
|
Wachtberger Posted at 2018-6-28 13:58
Hi, you might have joined this thread and others only recently and can therefore not be fully aware about the background. The truth is that this entire thread was set up in bad faith from the outset by mixing up issues that have nothing to do with what the OP and a buddy of him are claiming.
The other truth is that this thread was not set up to help any MA pilot who experiences problems with his aircraft (the persons concerned wouldn't even have either the knowledge nor experience nor willingness to help anyone here) but with the sole intention to create a mass hysteria about largely non existing or easily solvable problems which you can find when taking a closer look.
One of the main speakers here does not even own a MA and proves every day again that he has not even read its specs but tries to create the illusion that he knows all about it. The other one apparently has had a bad experience and seems now to be obsessed to convice all other MA users that they should have the same problems, just most don't have them which is the next truth in this saga. And he repeats it day after day with indeed some success with innocent new users who then ground their aircrafts for no good reason and only because they have listened to someone who very obviously has more important problems he should urgently address.
@Wachtberger,
You really just roll out the red carpet for people to come in and flame you with all the misinformation, insults, and attacks you put out there...
Let me address your false "points" (some are straight up lies) in order:
- This thread was setup to put together a comprehensive list of threads that catalouge the issues being experienced by pilots of the MA, and in some instances the MP/MPP due to shared firmware codebase, of the latest 0400 MA firmware update, thus was not setup in "bad faith"; this is something I said from the creation of this thread
- Referring to my first point, this thread HAS and continues to be HELPFUL in that it provides information to those pilots out there who ARE experiencing issues with the 0400 firmware, thus making it easier to cross-reference threads/posts of those whom have already discussed these issues in great detail, perhaps lending them clues on how to go about trying to correct the issues, or at least put their mind at ease that "no, I'm not going crazy and my MA in fact does have a problem as many others have it too", and also to put a public spotlight on the issues DJI has caused with bad software; the hysteria was brought into this thread by you and @hallmark007 refusing to shut the hell up and just let the thread serve the purpose it was intended for, which was knowledge and information about serious issues!
- I have personally gone out and spent my own time and money purchasing an additional MA to prove or disprove theories of what might be occuring, regarding issues I am experiencing (along with many others), and catalouging those tests and their results publicly... So how am I not trying to contribute here, or not shown a willingness to assist?
- The problems many are facing with the MA after 0400 are NOT easily correctable, as they require DJI to actually release FW that has bug fixes, please stop giving people false hope and leading to situations where pilots may feel OK to fly their drone after reading your misinformation only to have it crash and possibly injure innocent bystandards; even MA's who have their FW completely refreshed by DJI Assistant 2 1.2.4 have flown well for a few flights after, but the problems can re-occur, thus the "solution" you peddle is not a "solution", but a temporary fix at best until the software goes haywire againr
- The other speaker you denegrate, @HedgeTrimmer, owns a Mavic Pro, and I'm sorry, but I guess you didn't get the REPEATED memos that the MP shares a common codebase in the FW with the MA, and attacking the pilot is a very poor way to deflect from valuable feedback and insight he has brought to the table
- You and @hallmark007 repeat yourselves more times than I can even count, so please spare me that routine, because you and he are FAR MORE guilty of that crap than @HedgeTrimmer
- @HedgeTrimmer and I obviously are more concerned about the well being and safety of the public in that we actively do NOT want to fly a piece of equipment that can result in injury, and as far as common sense goes, if you have an MA that is not operating normally, YOU SHOULD GROUND IT, end of story, especially if you are a novice pilot that doesn't know what to do in situations where the MA goes crazy
- You keep using derogatory terms like "bad faith" and "obession" to describe this thread, has this thread personally injured you in any way for you to keep repeating the same mindless statements over and over like a broken record?
- The only thing revealing was all the screen caps and insults thrown around by @hallmark007 and you at people like @asaw, @HedgeTrimmer, myself, and more, just because we had different viewpoints and discovered new evidence that we brought to the table.
If anything is "revealing" is who should actually be listened to on this forum, and that is definitely not you or hallmark007. This last statement I may have cut your name out from, but the last libel you threw my way has made me lose all respect for you, and any confidence in the accuracy of the information you give out, or rather, your pro-DJI propoganda.
|
|