DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to make nine game-ready props from one prompt with Image to 3dlab

Generate one sheet of props and split it into separate named 3D props with LODs and compressed textures.

Who it is forA 3D artist or solo game developer who needs a set of background props, such as barrels or crates, without modelling each one.

The problemMaking each prop separately means a picture, a 3D run and a clean-up for every item, which is slow for a prop set.

The outcomeNine separate upright props, each with three levels of detail and compressed textures, ready to drop into a game engine.

What you need first

  • An Apple Silicon Mac or an NVIDIA PC (Linux or Windows per the README), or a Linux AMD card with ROCm for the Pixal3D route
  • Terminal access to run the install line
  • Free disk space for model weights, for example 8.4 GB for Pixal3D and 6.6 GB for Front + back
  • Full Xcode on a Mac if you build Pixal3D locally

Steps

  1. Install with curl -fsSL https://assetfurnace.com/install.sh | bash and let the studio open.
  2. In Setup & Status, set up the Pixal3D backend, which the README lists as the best-results option.
  3. Press + Create and type a prompt that asks for a grid of props on one sheet.
  4. Choose Create, then Nine props, to run the whole sheet to 3D in a single run.
  5. Download the separate props from the studio and import them into your engine.

Prompt for your agent

Using the AssetFurnace repo at <install folder>, generate a prop sheet from the prompt '<prompt>' and split it into nine props. Verify that nine separate named props are produced, each with three LOD levels.

Caveat. The README says prop sheets were built and contributed by a community member, and it does not state how many prop styles work best, so test your own prompt first.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page