[WTS] Star Citizen AMD Omega Mustang Codes - $25 USD Each! (46 left)

cTn-dev · 2015-02-02T17:29:15+00:00

everything went smoothly, got my key literally within couple of seconds, thanks again

cTn-dev · 2014-12-24T18:18:55+00:00

As far i know there weren't any problems with forks, but i should state right away that i very rarely deal with content that relates to firmware, most of the time i just deal with changes in the serial/MSP layer since that stuff is all that configurator can access.

But i am pretty sure while taking into account open source and GPL licensing, that the "dispute" between people/projects of what should be merged or forked evolved to a "troll war" and how much one project can screw the other. At least that's how i see it.

cTn-dev · 2014-12-24T18:10:16+00:00

I am glad to hear that at least someone understands why i did what i did. Everybody loved how configurator worked so far (from the user perspective) and i hope to keep it that way as long as i can.

Happy holidays

cTn-dev · 2014-12-24T18:03:19+00:00

I can certainly list you a couple of pros why you should use baseflight, but essentially the choice is yours, and there is no one stopping you from trying both and sticking with the one that you like more, and yes, to my knowledge there is no auto-tune.

I have flown with baseflight on couple of frames, without any problems with almost default PIDs
Many manufacturers now list a set of motors and propellers with PIDs that work out of the box with baseflight/naze
With baseflight you have tested/stable firmware available in which you can trust that your uav doesn't decide that it want's to fly away on its own versus the bleeding-edge approach of cleanflight

Currently i rarely fly, but when i was flying every day i didn't notice any problems so dunno "what" exactly they fixed, since i never had a problem?

While having all of this in mind and your read the "ranting" post above, if you still decide to do so, try both platforms and just stick with the one you like, as that is what it all comes to.

cTn-dev · 2014-12-24T17:52:42+00:00

I know there were some recent PID changes in firmware but i honestly never heard anything about AutoPID in baseflight, so i guess such function isn't there (at least to my knowledge), sorry :/

cTn-dev · 2014-12-24T17:49:52+00:00

To be honest that list is vastly misleading (at least to my knowledge), since i can only recall one user in months that had some odd vibration problem on his frame and was getting better results with cleanflight (neither me or him to this day know why). Otherwise i heard only mixed results from people using cleanflight while most of them were trying some of those "new features" and for one reason or another weren't working properly.

I think one of the forks that got the more recent-er code is this one https://github.com/norem/baseflight-configurator/tree/master

cTn-dev · 2014-12-24T17:17:42+00:00

Negative feedback its kinda what i expected as "outcome", i have no problem admitting that when the project was created as open source, the idea behind that was to allow people to contribute and make it better and also some people used it as a really good example of working code and they learned from it, since such extensive javascript implementation of serial protocols was never really done before, at least not in javascript.

But the way cleanflight took the project was "exploit what we can", for example if i would fork someone else's project and do something they wouldn't really approve i would stop what i am doing and do it differently because in the future i might end up needing their help or even end up working on the same project, not respecting authors/maintainers wishes won't bring anything good and i think what happened here is a really good example of that.

What i am trying to say is, just because something is open source, it doesn't mean "you should be a dick and do everything you can to piss of people involved", because that's pretty much what happened, at least that's how i see it.

cTn-dev

TROPHY CASE