Part 5c: Fixing the Material Library Fail of our Build

This video fixes the build fail we receive in Part 4. Also the "new" fail of the package name is addressed.
MyPhysical World on Facebook: www.facebook.com\myphysicalworld
On Twitter: @my_physical
On Instagram: @myphysicalworld
Geographic Information System Software:
ArcGIS and ArcGIS Pro are registered products of ESRI: www.esri.com
QGIS is OpenSource at: www.qgis.org
Flight Simulator:
Microsoft Flight Simulator is a registered product of Microsoft Corporation and Asobo Studios
Free Modeling and Graphics software:
Blender (OpenSource 3D software) at: www.blender.org
Krita (OpenSource Graphic Editing software) at: www.krita.org
GIMP at: www.gimp.org
NotePad++ (OpenSource text editor) at: www.notepad-plus-plus.org
FREE PBR Texture sites:
www.texturecan.com
www.texturehaven.com
www.cc0textures.com
www.freepbr.com
www.cgbookcase.com
Please be sure to subscribe, like, and hit the notification bell!
Thank you for watching!
Also, Please consider supporting us on:
Patreon: www.patreon.com/myphysicalworld
Buy Me a Coffee: www.buymeacoffee.com/myphysicalworld

[@sky173]

I just finished watching this series, straight through. It's probably the most comprehensive and detailed tutorial I've ever seen. I can't wait to get to working on some ideas I have. Thanks for sharing. 👍

[@physicsteacher4569]

Very clear as usual on the texture failure error. Keep 'em coming!
One thing I think we all have to face, though, is naming our packages in a way that just invites conflicts in the simulator. The error explanation is flawed in the console log, since they say they want aaa-bbb-ccc- ... -xxx as the format. I strongly believe what the log comment should actually say is: Make your package name in a guaranteed unique form. If you start with your company name, then the type of package it is like modellib or airport or an ICAO, then the specific thing you're creating. In this way, when your package is mounted, it can't possibly conflict with someone else's package. Looking at the Asobo objects, they do it this way. I really feel it's up to us developers to go along in order to fit in. And, by the way, they should correct their sample Simple Scenery to comply.
You are a wonderful example of someone who names items in Blender with meaningful names. Everyone should follow your example.
Thanks again, and keep up the great tutorials. Don't apologize for speaking slowly; it's great for those of us who listen slowly.

[@myphysicalworld3958]

Excellent comment and good points. Thank you for the kind words!