msev wrote:I really don't know whats the problem that all classic multiwii devs also don't collaborate with baseflight/forks developement directly, because price surely isn't a factor...
Because TC's "STM32 Development Board" which is sort of a STM32 32-bit variant of the Arduino Pro-mini, is only 6$ more expensive than arduino pro-mini. So even for the budget minded I don't see any problem. Even Elm who is a very budget minded person used a similair board .
I'm sure TC+users of naze32 would be happy if useful, properly formatted contributions would be made to baseflight.
Because if you look at the number of pages in the Naze32 threads on various forums (rcgroups,mwii,fpvlab) you see that naze32 is the most popular variant of multiwii derived firmware.
Also why wait for Eosbandi if he log's in just once in a few months , why doesn't one of the lead-devs iron out the very few remaining bugs, and credit Eosbandi properly? So 2.4 could be released
Just a few thoughts.
We have already Baseflight for STM32 ... this is already MultiWii running on STM32 ... at least in my book
STM32 environment is a bit different then MultiWii, so some people familiar on Arduino may not like to move on Baseflight ... also ... for properly compile Beseflight it is need a software that cost around 2000$ in licenses
The question that I have not got a clear answer is: does MultiWii still have a future after 2.4 ... or the mission of the original developer group has been accomplish ?
PS:I think it is fair to wait for EOS, 2.4 sound more a blessing of a work already available in the download page.
PPS: I think that MultiWii on Atmega8bit still make sense and it can still evolve ...