Nope, no issue here. tested the 6.0 installer even in a windows sandbox.
Was K:\KiCad the location of KiCad 5.1? If it was, and you installed 6.0 on top, you created a conflict.
@marekr yes I installed on top since it was told me that I could do it without issue
here the topic: https://forum.kicad.info/t/from-5-1-12-to-6-0-just-overwrite/32662
Now the point is: how to solve it.It’s not proposable to delete everything since I have all settings, custom libraries, scripts, plugins etc.
Delete just the bin folder and reinstall kicad in the same location.
1 Like
Heh actually found the bug here, the installer wasn’t set to erase the /bin/plugins folder.
4 Likes
I have just installed Kicad 6.0 and I have a similar issue. I havew two separate folder, with Kicad 5.99 and Kicad 6.0. In Kicad 5.99, 3D models all work ok, but in Kicad 6.0 the default ones do not work. If I right click on them, they work, but they don’t work in the view on the entire PCB. What is the solution?
Example:
@Cezar_Chirila Check my answer above. You need to create a variable that on 6.0.0 was changed with another name and it doesn’t work on previous project.
@tormyvancool Unfortunately my problem is a separate one than yours. As I have upgraded from 5.99 (essentially 6.0 nightly - prerelease) there was no need to add any missing variables. I’ll dig and update if I can find a fix. As I have previously mentioned, strangely, if I check an individual part, the 3D renderer works, it is only broken when I try to view the entire PCB.
Later Edit: I am such an idiot. The “Toggle SMD 3D Models” was disabled by default. That fixed it. Sorry for causing any trouble.
1 Like
“Toggle SMD 3D Models”?
I also had this issue and it was fixed by adding the missing KISYS3DMOD to point to the same location as KICAD6_3DMODEL_DIR. I did at some point in the past download the updated zips from the git repo so I may still bump into some that are missing but so far so good on my 6.0 test project.
@themaninthesuitcase Indeed it’s exactly what I did to solve it (see previous comment wher I posted the screenshot). It has to be tackled because it is an issue.
Probably the old variable is contained into projects, hence opening them, we face out this issue. The new variable is valid for new projects only :-/
One PC where I had installed some of the recent 5.99, 6.0 rc1 and rc2 builds before release had no 3D path problems and included the old missed path
Another PC where I waited for the 6.0.0 before adding to 5.1.12 had the path missing
This was usefull info, I got two missing components into my 3D picture.
1 Like
It’s this. I opened my 6.0 test project in a text editor and searched for the old path variable:
Seems the upgrade doesn’t update the old path to the new one. This may be by design, but given it’s the old system path it feels like an omission.
@themaninthesuitcase this is clearly a bug. Because when you open a project on 6.0.0 it’s asking you
- to import the settings from the old version
- it’s old project and it will be saved as new (or something like that)
It doesn’t import the custom paths at all (my custom libraries I had to re-import them manually)
When it saves the old project converting it, it doesn’t change that variable.
The screenshot indicates that the footprints embedded in your board file are old and point to the old model location. (3d model paths are embedded inside each footprint, and footprints are embedded in the pcb file when they are used).
When/how was your test project created? If it was created with old (pre-v6) libraries, this makes sense.
The footprints released with v6 use the v6 variables, so my suggestion is either:
- update your libraries to ones released with v6 (if not already), and use the update footprint from library function in pcbnew for each of your footprints to get the new paths
- or define ${KISYS3DMOD} to point to the same place as the v6 variable; no footprint updates required
It was a project created with 5.1.10 upgraded by 6.0 as a test project. I would have expected that this would be managed by the upgrade but thinking about it footprints are “user data” so changing automatically them as part of an upgrade is probably not smart.
I’ll have a look at manually updating them, I already have KISYS3DMOD set to the v6 location as above.
I ran “Update Footprints from Library…” in the Pbcnew Tools menu and it fixed all instances of this issue.
3 Likes
@themaninthesuitcase great suggestion! I applied it right now, on an old project: it works. Thanks a zillion