Hi all,
Istill need a way to assign 3D models to existing Footprints.
BTW: why is the notation in libaray.io and eagle not consistent?
In Eagel you have 'Device', 'Package', '3D Package' and 'Symbol',
in library.io you have 'Components', 'Symbols', 'Package' and 'Footprint'
Kind regards, Paul

Hi Jorge ,
thanks for your anser. It looks like you guys are working on your cloud service... thats good. But only if it works better than before.
If I try to login with firefox on library.io the site is in a kind of reload loop. With Chrome login works. So why using firefox...
@jorge_garcia wrote:
Currently, the only way to assign 3D models to existing packages is through library.io as you have noted.
Well, if I open my lib at library.io it says:
To edit this library, launch the Library Manager in EAGLE, ensure the library is downloaded and in use, and open it in the Library Editor.
So ok I ignore this. Go with Chrome to Packges and click on the package I'd like to add the step model. But nothing happend, just this little dots are hopping. The same happens when I click on edit.
And now I use eagle (my normal browser is firefox) right click on the 3D Package and select "see in web". Then Firefox opens and after a few seconds I can edit the 3D model. What the... And Chorme is the suggested browser?!
This is realy annoying and time consuming, especially when the test periode for fusion is running out.
Kind regards,
Paul
PS: Video are a nice additional feature but please consider to write a documentaion or how-to. Scrolling and searching thru a paper is even better than press pause or shift the slider in a video!

Thanks, Jorge. I had been having the same problem and that did resolve it for me. I want to take this moment to point out a few broken steps in the process of assigning a 3D model:
1. There's no reason why a user should need to make a change to a footprint in order to upload a new .STEP file to its package.
2. It should be possible to assign any package that is already in the library to any footprint.
3. Selecting a local .STEP file to become a new package should be independent of assigning that package to a footprint.
4. Selecting a local .STEP file shouldn't pull up a list of libraries but rather should pop up a question dialog box asking whether to look within the EAGLE libraries (currently the only option) or have the user select one using a file select dialog box. Alternatively, the upload option could be part of the EAGLE library selection dialog box.
5. There's no reason that a new version of a library should be needed in order to upload a .STEP file if that work is taking place, at least from the user's perspective, within the EAGLE application and not on libraries.io.
6. If a feature is unavailable (like uploading a .STEP file), leaving the controls visible but grayed out helps the user to see that they at least were looking in the correct place and that there's an issue that they need to resolve rather than have them keep looking.
If you can get the developers to cross these six issues off, I think that it will make a lot of users very happy.
Also, to whoever else may be lurking here, I want to tell you that although EAGLE has a ways to go to fully implement their vision, Jorge's been truly phenomenal at customer support in the interim. I drafted a list of 45 bugs/missing features that I'd identified in EAGLE and Jorge went through every single one of them with a suggested workaround, an acknowledgement that the problem had been added to the queue for repair, or a request for additional information to isolate the issue. Because of this level of engagement, although EAGLE has some issues now, it's obvious that it's already pulling away from the competing design applications and will become far superior to them over the next few months or years.
I hesitate to mention this because I worry that now Jorge will be buried in bug reporting but wanted to point out how happy I am with EAGLE's support team, even as I have some issues with the product itself.
I'd like to add one more gripe about the library editing process from the perspective of the 3D package: A user can rename a Device, Footprint or Symbol. Why does no equivalent option in the context menu exist for a 3D Package?


I agree 100%. Eagle is getting BETTER and BETTER. These library issues need to be next on their RADAR. Thanks Jorge for helping all of us.
Are you still required to create a managed library to add your own 3D models to footprints?
Managed libraries are still very flawed and by using them it puts a great dependance on your servers.
You guys think you'll ever create a way to do it locally so we aren't so dependent on you?
@Anonymous wrote:
Are you still required to create a managed library to add your own 3D models to footprints?
Unfortunately yes. You can only add your own STEP models from within a managed library. However, you only need one library for this and once created you can copy the 3D package (not the footprint this is done automatically) into a proper library.
@Anonymous wrote:
Managed libraries are still very flawed and by using them it puts a great dependance on your servers.
You guys think you'll ever create a way to do it locally so we aren't so dependent on you?
I'm sure they will sort this out, given you can use the IPC wizard from proper libraries and the STEP import uses essentially the same web based interface, I can't see why it shouldn't work, but I'm not one of the developers so maybe there is more to it that it would seem....
Best Regards,
Rachael
@rachaelATWH4 How does one assign the same 3d custom model to multiple variants in the same device?
I realize this thread is a year old, however I'm curious if attaching a 3D Package to previously created device/footprint is something that's still in the works. It seems that if I open up a library and generate a 3D Package (using package generator), I cannot assign the 3D Package to an existing device.
I found this thread as I was trying to add a 3D package to a custom device. I was working in a managed library, so I thought my basis were covered, but I could figure out how to add/modify the "Used 3D Packages" for the new device. The answer was found here: https://forums.autodesk.com/t5/eagle-forum/import-3d-package/m-p/8659079/highlight/true#M21195
Where the key step is to create a new version of the library; Library->Create new version...
I hope this helps others who might be in a similar position.
Thank you for posting this. I saw this a few weeks ago but didn't save the link. This post definitely helps, but there are still too many hoops we have to jump through to upload a step and Autodesk need to write up a guide on how to use the system. Uploading 3D models has been a persistent issue for years.
Written. How to add manufacturers 3d model to eagle device.