Configure Paths for 3D user libraries is confusing me

[eepete]

I’m finally upgrading from version 5 to version 8.0.8 (long story…)
Target machine is Windows 11, fully up to date on a sizable machine.
Fresh install on new machine, brought over my files and libraries from another machine that I’ve used for about 80 PCBs. The updating of schematic symbols and footprints worked like a charm. I am however struggling with getting a path to the directory I have that has step files for the footprints I’ve created (or downloaded for some parts).

In the foot print editor, each part I’ve created has a hard coded pathname to the step file. I want to use the paths so I can share my libraires with others I know that are working on PCBs and coming up to speed on KiCad. I know I’ll have to go through each part and modify the 3D model path, not a problem. Do it this once and I’m “good to go” forever.

My first question is does the “tilt of the slash” matter? When I look at what is displayed when in the “Footprint Properties” in the foot print editor and I click the “Configure Paths…” button I see both forward and reverse slashed in the environment variables generated by the new install:

In the 4th row entry, both \ and \ are used. Does this matter?

The 1st line does not have a trailing \ but the other lines do. At the bottom, you see what I tried to set as an Environment Variable. But at the top line, the file can not be found ? I entered what you see and tapped the “return” key.

The 2nd problem is:

The file and correct step file exists:

And if I type in the full path name, the step files shows up.

I searched the forums for “User Step File Library” but didn’t see anything that helped. I tried all variants of forward and backward slashes and having a slash after the closing brace of the environment variable and not.

Any help of what I’m doing wrong would be apricated. If there is a specific step by step document then advise. And finally some clarification on the exact syntax of the environment variables would also be appreciated.

KiCad is awesome, and coupled with OshPark for PCBs it’s a huge win. I’ve got a big board project for this year with a 500+ pin ball grid FPGA and I suspect the various improvements in V8 will help. No doubt after I get used to the improvements (and set the colors back to what I’m used to), I’ll be wishing I had upgraded sooner and be thinking “Wow, I could of used a V8 !”

• pete

[dsa-t]

You have E\:, should be E:\

[eepete]

Thank you so much for that catch… “digital dyslexia” strikes again.

For future readers:
I had to edit the 3D model, then set the correct configuration path. At that point, when you enter the path for the step file, you still see an error. I had to do an “OK” after editing the path to the part.
If you then go back and click on the “Footprint Properties”, you will see if the step file loaded correctly or not.

I also note that if you leave the trailing backslash off of your environment variable you must add it into your path to a given step file. I had no trailing \ in my Environment Variable, so the entry for the pathname to the step file looked like:
${PETE_3DMODEL_DIR}\2301844-2.stp

Just for grins, I then went back and added the trailing backslash onto my Environment Variable. I was then able to enter the step file path without the backslash:
${PETE_3DMODEL_DIR}2301844-2.stp

So as one might suspect (and I would claim as it should be) the Environment Variables macro is indeed a literal replacement.

I still am curious as to why the 2nd entry in the default Environment Variables for KICAD8_3RD_PARTY did not have a backslash at it’s end, and why in the KICAD8_TEMPLATE_DIR there are both forward and backwards backslashes. Does the software just “clean up” slashes as part of the process of correcting for the operating system you are one? I’ve done this in systems I’ve made because when you’re jumping between Windoze and Unix, it’s easy for the “digital dyslexia” to kick in.

Thanks again to dsa-t ! And if someone can comment on the above idiosyncrasies of the default Environment Variables that would be nice to know, but I’m good for now and can finish my transaction to Version 8 and share my libraries with the new users of KiCad.

• pete

[paulvdh]

@eepete

So as one might suspect (and I would claim as it should be) the Environment Variables macro is indeed a literal replacement.

Almost. Best I know, it can swap slashes and back slashes, depending on your OS, and when both the environment variable and the link that uses it has a (back) slash, then one is removed. Note that the KICAD8_TEMPLATE_DIR also does not end in a backslash.

Your screenshot also shows both slashes and back slashes in between directory names. On my Linux box (this should be OK). On my linux box, it only shows slashes (which is normal for Linux).

[eepete]

Thanks and OK on that. It all makes sense and the process of appending file names to directory paths matches what I’ve done when writing software. Classic “Be strict in what you send and graceful in what you receive” stuff.

IDK if it’s worth looking at why the defaults on a fresh load had a mix of “slash slants” or not, it was confusing to me but then again I had a stupid mistake in my Environment Variables path name. It’s so hard to make smart mistakes.

Next task is to explore new features, and I’m very interested in having a default setup for things such as track sizes, size of text on silkscreen, etc. I keep meaning to figure that out but finding time is difficult- it’s time to make time to better use KiCad.

Thanks to you and other moderators and users for your time.

• pete