[K3d-development] Possible Aqsis - ehm- axis of developpment :)
Brought to you by:
barche
Menu
▾
▴
[K3d-development] Possible Aqsis - ehm- axis of developpment :)
|
From: jerome K. <je...@op...> - 2017-06-23 00:23:26
|
Hi again all, Thanks for your warm feedback Daniel . Yes 3D Printing and CNC have somewhat same routines. Some precisions : I decided to focus on Qt>5.6 because to me this Graphical API offer currently the best choice for a limited set of dependancies over GTK or Wx. If i purposed these external librairies integration , that's because they offer a very extended set of features over a very little set of dependancies . Also, things like Inverse kinematics better not to be reinvented . DART was choosen because of links with robotics , but mainly because of the biped animation routines (who told about character animation ?) . DART and Bullet offers complentary multi physics features and tools. I've spent some time making the software jockey,i hate huge list of dependancies (for example OpenImageIO drops libjpeg,libtiff,libpng,libgif deps for an all-in-one). Also , I am not running any linux currently (not very linux-friendly,this is my extremist side), i have a W10 desktop (mostly for video games) and OpenBSD Laptops for the real stuff. I found a solution for 6 and that may help for 4 after few searches http://www.meshlab.net/ https://bitbucket.org/NeonKing/meshlab . 1, 7, 8, 16 and 17 are mostly related to UI design -> New Qt GUI proposal 2,3,11 and 12 are new tools modules to developp -> In need of infos about process to follow 5,6,9,10,13 ,14 and 15 are mostly related to external librairies interfaces - > same way , any process or doc? More i look the code and the soft structure the more i'm pleased. You really accomplished some nice work. Things sound nice to integrate easily. I had this idea i can't help no telling : 18. Add constraint-based modelling interface https://bitbucket.org/NeonKing/solvespace https://bitbucket.org/NeonKing/solvespace http://solvespace.com/index.pl and this one i forgot : 19. Developp Further Links With Quadray Real time raytracer (link already supplied before) If you have any other idea of improvement , i'll be happy to hear from anyone. If ever I can enjoy any help on any of these points , i'd be happy to be driven an to co-work with any interested peoples. As i told i wanted first to purpose few "new" organisation concepts about the UI while i'm in brainstorming mode because when coding i'd like not to be back on this for a while . I just want to not take too much on myself . We can implement these 19 points that would made K3D really up and running and fun to use for many modern 3D things. As told, any help welcome. If any core member wants to set any roadmap or scheduling i'll be happy to contribute as far as i can. Best regards, Jerome ------------------------------------------------------------------------------------------- Sounds great, I look forward to helping test the first alpha build with the new features. I guess the CNC and robotics features have a lot of overlap too. Direct CNC control from K-3D would allow tool path visualisation and many other interesting functions. On 23 June 2017 at 03:05, jerome KASPER <je...@op... mailto:je...@op... > wrote: Hi all, following Bart’s advice , i forked his repo and merged upstream branch for build fixes . I also imported aqsis as subdirectory as to me it’s a very good renderer base and very related to K3D, better not forget good old friends 😊. I have much ideas for possible improvements , all may not worth it but it might open the discussion to possible axis of developpments . 1. Developp modelling based on real drawing scans. 2. Integrate a 3-D guide system. 3. Z-painting tool ? (maybe exists) 4. Developp 3D printing compatibility with Slicing / G-code Generation https://bitbucket.org/NeonKing/camarade 5. FreeCAD is maybe good for CAD modelling , but crappy for animation . Developp further Constraint based Animation / Robotics simulation : https://bitbucket.org/NeonKing/dart https://bitbucket.org/NeonKing/ompl https://bitbucket.org/NeonKing/aikido 6. Developp further 3-scanning / reconstruction (no -best- lib suitable found yet , already found few 😊 ) 7. Developp Library System for 3D model reuse and Scene Building . Integrate a "Layers list" widget. 8. Model import from Web sources module (like https://www.thingiverse.com/ etc..) 9. Integrate aqsis as an internal developpment 10. Create an animation interface from a computer vision Library (motion capture from web cameras) https://bitbucket.org/NeonKing/microcv 11. UVW unwrapping module https://en.wikipedia.org/wiki/UVW_mapping and subsurfacing (Subsurfacing (>submesh generation from pictures , like « applied » bump mapping) 12. « Terragen » Terrain generation like module https://en.wikipedia.org/wiki/Terragen 13. Integrate Assimp https://bitbucket.org/NeonKing/assimp as a « mesh layer » 14. Integrate OpenImageIO as a « pictures » Layer https://bitbucket.org/NeonKing/openimageio https://bitbucket.org/NeonKing/openimageio 15. Integrate Bullet Physics as a physics engine https://github.com/Neonking/Bullet3 16. Developp Different UI « presets » regarding the expected use (animation , texturing , modelling ) 17. Last but not least and first one in planning order , I will draft one or 2 possible suggestions in terms of GUI by submitting pictures and associated concepts. Then Select the best and make the final UI draft on QtCreator That’s almost all what i had in mind for now :) . And yes that’s a lot . Feel free to comment anything. Best regards, Jerome ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ K3d-development mailing list K3d...@li... mailto:K3d...@li... https://lists.sourceforge.net/lists/listinfo/k3d-development |
