Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Asset Forge

Create your own 3D models and 2D sprites! · By Kenney

Importing collections

A topic by alwaysawake created May 30, 2020 Views: 182 Replies: 2
Viewing posts 1 to 3

Delete if not the right place.
Has anyone had success importing models from the other Kenney packs and other low poly assets?

At the moment I'm having pretty good success with the Kenney packs, however, I often get a page or two of unclickable assets that have incorrect thumbnails and the name of an object with "._" at the start of the file name (as pictured below). The objects without the "._" in the file name work fine, and the "._" objects seem to be weird duplicates. I'm unsure if there's even a simple way to fix this and whether or not this is just an issue with the obj files or the way AF caches thumbnails. The picture below shows the list of available assets but none of them are clickable and won't import into the scene. This would be less annoying if they sort order of your collections would put items start with a period "." at the end instead of the start. My only work around so far is to either type in the name of the asset I want, or work from the last page in each collection. I have tried basic troubleshooting steps like rebuilding thumbnails and reinstalling but no success.

I'm also really curious as to whether anyone has figured out importing the Synty Polygon assets, as I have quite a few of those that'd be great to import. So far I can import the mesh without any problem except maybe scaling (which is an easy fix with meta.ini) but I the materials don't import so I get a mesh with a plain white material. If anyone has some wisdom around how to fix this please share your secrets.

Hoping for 2.0 version in Mac soon, as collections aren't working in Mac and the gizmos are bit cumbersome. However, I'm loving the 2.0 previews on Windows so far. Awesome work by all involved!


What you'll need to do is create a folder in /Collections/ and name it "Fantasy Town" (or whatever pack you're going to import), in that folder put the OBJ and MTL files found in the downloaded package. Do not put any other files in there.

Thanks for the reply. I resolved most of the issues by deleting the collection, opening AssetForge to let it rebuild the thumbnail cache, closing it, then reimporting the collections. I think the "Do not put any other files in there" part was key to this problem. The ones that were broken had rogue .fbx files or folders that I copied over from the original pack (curiously they were empty folders named gITF, Materials, Textures). I just assumed AF would ignore anything that it couldn't read.

An interesting bug I noticed is if you create a collection folder with the same name as the default collection folders (e.g. Buildings), then your assets will show up in the default folder plus its own custom folder which is kind of nice. Would be great for AssetForge to just merge these and not have the duplicate Buildings folder in the custom collections section or bypass this altogether by allowing to add or remove assets from the default collections.