This is a weeks worth of work in designing the Mavic Pro in A3CD (3D CAD program used to create a 3D design). Then another week to program it to fly in the ClearView Simulator.
It still needs some work but so far the results are not too bad.
AntDX316 Posted at 5-8 18:38
lmao the mavic does not fly like this. If you want I can film it so you can try to copy the proper dynamics.
Thanks for the offer.
It took a week to get it to take off . I used an V-22 Osprey program code to get it to fly. Still working on a code to make the Mavic Fly properly.
houdini Posted at 5-9 04:29
Thanks for the offer.
It took a week to get it to take off . I used an V-22 Osprey program code to get it to fly. Still working on a code to make the Mavic Fly properly.
It won't really make sense to code if it can't accurately simulate the flight characteristics in the air. Putting cinematic mode turns the brakes off. Sport mode is quick but if you are flying low, the input lag will make it crash. Tripod mode is customizable and it can fly slower than a Spark with everything on. Also normal mode w/ different expo and rate settings will also make it change in handling. The brake gain setting also exist. Winds will also change it. The random altitude deviations and other things also cannot be truly simulated w/o a lot of work. The standing out in the field while looking at a slightly dim screen due to day light is something that isn't really simulated. Basically it would take a lot more work over the amount of work you have done and going to do that I don't think it's worth doing to make it work correctly.
AntDX316 Posted at 5-9 06:57
It won't really make sense to code if it can't accurately simulate the flight characteristics in the air. Putting cinematic mode turns the brakes off. Sport mode is quick but if you are flying low, the input lag will make it crash. Tripod mode is customizable and it can fly slower than a Spark with everything on. Also normal mode w/ different expo and rate settings will also make it change in handling. The brake gain setting also exist. Winds will also change it. The random altitude deviations and other things also cannot be truly simulated w/o a lot of work. The standing out in the field while looking at a slightly dim screen due to day light is something that isn't really simulated. Basically it would take a lot more work over the amount of work you have done and going to do that I don't think it's worth doing to make it work correctly.
I think we should just use this.
Thanks again for the advise.
The main reason I tried creating the Mavic was just to see if I could design it in a CAD program and make it respond to the controls. I don't think I will go much farther with it to make it actually respond as the Mavic actually does..
I tried the DJI Sim. Works well.
Thanks again for watching my video.
If you didn't see my post of the V-22 Osprey I posted on the forum, here it is again. I used some of its code to make the Mavic fly.