-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
various issues with the generated files for oddish project #50
Comments
Thanks for checking out the project! [1] is due to invalid footprint setup most likely, the solder joints get created based per Pad, based on it's type (you probably got it set to THT). [2] looks like one of these pad types: pcb2blender/pcb2blender_importer/importer.py Lines 540 to 542 in bfcc0f7
which are not supported for generating solder joints automatically (you should get that warning in the console). [3] atleast for that subboard on the right, it seems like KiCads WRL exporter only exports that part. So there's not much I can do about that I think.
They are exported at the correct scale. They are just really small because by default Blender is zoomed out somewhere in the meters range. If you want to scales things up (which I'd generally not recommend) you can just select everything [Ctrl + A] and scale it up [S 100] (for example). |
|
That doesn't make any sense. If your footprints pads are set to the wrong type, I'd suggest you to fix that.
Not sure what that's supposed to mean exactly, but you can always just add the few missing solder joints if you really care. (Realisticly, nobody is probably going to notice if you don't).
Once again, not sure what that's supposed to mean. Your board will be as big ... as your board is supposed to be. If your board is 20cm long, it'll be 20cm long in Blender. (Not sure how "printing" that would help). |
I don't understand what you are trying to say ...
It doesn't really matter what option is chosen there, because things will be rescaled on import anyways, so that the scale is correct in Blender. How would printing that information be any help to you?
Probably an issue with KiCads WRL exporter then. Will see if I can reproduce it. |
the plugin in general work great, better than the native export
few issues i noticed
this is the full kicad render

[1]


[2]
[3]
the full repo is of the project is https://gitlab.com/m-lego/m65
exported file:
a.zip
The text was updated successfully, but these errors were encountered: