Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question - Fusion360 STL File Access #15

Open
danlohman opened this issue Jun 14, 2023 · 12 comments
Open

Question - Fusion360 STL File Access #15

danlohman opened this issue Jun 14, 2023 · 12 comments
Assignees
Labels
good first issue Good for newcomers hardware question Further information is requested

Comments

@danlohman
Copy link
Collaborator

I'm trying to download current STL files for each hardware component as well as groupings of assembled components. On some of the groupings I get the error that "This assembly uses files in other projects. To share this assembly, you need Editor access to all those projects." In the attached example it looks like the problem is that I need access to some sub-components used in the Head v1.7 component. I just requested access but wanted to post this as well.
image
image
image

@danlohman danlohman added the question Further information is requested label Jun 14, 2023
@realsnick
Copy link
Contributor

@RichardGHopf can you help with access?

@realsnick
Copy link
Contributor

realsnick commented Jun 15, 2023

btw, @danlohman @RichardGHopf @fcbarros will it be valuable to move the STL files to git? one version control? google folder isn't really for version control and hard to follow changes. Further, now, github support 3d file rendering even in markup

https://docs.github.com/en/repositories/working-with-files/using-files/working-with-non-code-files#diffs

@danlohman
Copy link
Collaborator Author

I agree that it would be a great idea to maintain a current version of the STL file (and any others that are needed) for each hardware component in Github. It may make sense to maintain the main website (sky360.org) code in Github as well if you want to reduce the number of places where update need to be made.

@Sky360Admin
Copy link
Member

yes, we can host STLs on Git.

hosting them on Drive was just a means of provision for downloads, not for version control. this happens in A360, where all CAD files are hosted.
@danlohman you need access to A360?

the request for access to Joe Webers private folder is, hmmm, a bit problematic. but his sources are all in public folders.
@danlohman dm me what you need.

@realsnick realsnick added documentation Improvements or additions to documentation good first issue Good for newcomers and removed documentation Improvements or additions to documentation labels Jun 20, 2023
@realsnick realsnick self-assigned this Jun 20, 2023
@realsnick
Copy link
Contributor

i'll take on moving the STL files to the git repo

@Sky360Admin
Copy link
Member

just for everyone to know - STL files are meshes, only useful for 3D printing, not for further modelling. that's why you find here only 3D printable STLs:
https://drive.google.com/drive/folders/1neKtp0gZ_70_DP4wMYcA_6emzVf_1uGb

@danlohman
Copy link
Collaborator Author

I was interested in the STL files per hardware component because that file format is usable in 3D web renderings. If we have already done the hard work to design/build/pull them together, it opens up the ability of showing parts of stations in 3D in tutorials, guides, interactive demos, within the GUI, and much more. I'd love to visualize how a station is assembled in 3D with the parts coming together in a 3D animation. Its also a great way to get someone comfortable with design and parts before buying. In addition, It opens up viewing 3D parts outside of programs with limited access and steep learning curves by allowing for simply viewing on a webpage. Just a few thoughts behind why I asked. I realize I did not give any explanation for my request.

@realsnick
Copy link
Contributor

@RichardGHopf can you help with locations for what @danlohman is asking for , i'll move it all to STL.

@Sky360Admin
Copy link
Member

Dan, please go away from STLs - they are huge single meshes.
every renderer would suffer calculating each triangle.
they are just meant for production.
what you need is a lightweight 3D model like STEP, or even OBJ (quadrilateral mesh), FBX (with materials) - the latter are supported by three.js

@danlohman
Copy link
Collaborator Author

No problem. If the file format can be loaded in three.js, then I totally agree that the smaller the file, the better. Can you direct me to the most current version of the complete station in Fusion360? If there isn't a 3D model of a completely assembled station, no worries, we can work from the hardware component list being created to guide the gathering of the 3D models.

@Sky360Admin
Copy link
Member

there is a complete assembly (still without the Pi5 - because we're not 100% settled on it) and this assembly contains tons of referenced components. if you export an assembly to a mesh, you end up with a huge single mesh, you can't work with. so, it's better to export every component into FBX - which is certainly a month work.

@realsnick
Copy link
Contributor

is there a way to automate it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers hardware question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants