Add 3D Drawing

[n1ckfg]

[Insert URL to the list here]
https://github.com/n1ckfg/awesome-3D-drawing#readme

[Explain what this list is about and why it should be included here]
3D drawing papers and related resources--the overlap of XR work that uses 6DoF controllers, and ML work that processes and renders frame-by-frame volumetric representations. This is a niche field but one of increasing interest to mainstream animation and VFX production (covers techniques used in the "Spiderverse" films, for example). 100% pass on the linter tool.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
  • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to a maximum of half the width of the original image.
  • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. The casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Does not use hard-wrapping.
• Does not include a CI (e.g. GitHub Actions) badge.
  You can still use a CI for linting, but the badge has no value in the readme.
• Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[n1ckfg]

GH Workflow linter is different than standalone linter. Fixed errors and trying again.

[sindresorhus]

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

[Nikki1980]

I didn’t! Nichole Charterina

…

________________________________ From: Sindre Sorhus ***@***.***> Sent: Thursday, October 23, 2025 1:07:34 AM To: sindresorhus/awesome ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [sindresorhus/awesome] Awesome 3D Drawing (PR #3711) [https://avatars.githubusercontent.com/u/170270?s=20&v=4]sindresorhus left a comment (sindresorhus/awesome#3711)<#3711 (comment)> Thanks for making an Awesome list! 🙌 It looks like you didn't read the guidelines<https://github.com/sindresorhus/awesome/blob/master/pull_request_template.md> closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome. — Reply to this email directly, view it on GitHub<#3711 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ4IVLU5HLEB22QQHJKAFD33ZBPBNAVCNFSM6AAAAACJ6ZBZHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMZVGA4TGNJSGE>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[n1ckfg]

Unicorn--reread guidelines, reviewed error logs from two PRs, ready for review.

[hstsethi]

This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

This requirement is not fulfilled.

[n1ckfg]

Done

[Nikki1980]

I didn’t! Nichole Charterina

…

________________________________ From: Sindre Sorhus ***@***.***> Sent: Thursday, October 23, 2025 1:07:34 AM To: sindresorhus/awesome ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [sindresorhus/awesome] Awesome 3D Drawing (PR #3711) [https://avatars.githubusercontent.com/u/170270?s=20&v=4]sindresorhus left a comment (sindresorhus/awesome#3711)<#3711 (comment)> Thanks for making an Awesome list! 🙌 It looks like you didn't read the guidelines<https://github.com/sindresorhus/awesome/blob/master/pull_request_template.md> closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome. — Reply to this email directly, view it on GitHub<#3711 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ4IVLU5HLEB22QQHJKAFD33ZBPBNAVCNFSM6AAAAACJ6ZBZHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMZVGA4TGNJSGE>. You are receiving this because you are subscribed to this thread.

[tysoncung]

Hey! This looks like an interesting niche topic, but you need to complete the checklist before this can be reviewed.

Key things I noticed:

❌ You haven't checked any of the requirement boxes - Please go through each one carefully
❌ You haven't reviewed 2 other PRs - This is required. You need to substantively review at least 2 open PRs
❌ Missing the 'unicorn' verification comment - Add a comment with just the word unicorn to verify you've read all guidelines

Please complete these requirements and check all the boxes that apply. Most importantly, review 2 other PRs first - that's a hard requirement for all submissions.

Good luck!

[n1ckfg]

@tysoncung I constructively reviewed two PRs referring to error logs. Re: checkboxes, are those functional? I thought they were decorative. Re: unicorn, did that have to be in its own comment? I will say it again.

[n1ckfg]

unicorn

[tysoncung]

Great niche topic that's increasingly relevant. The list covers academic papers, tools, and practical applications well.

The description could be slightly clearer for people unfamiliar with the field. Current: "3D drawing and painting with 6 degrees of freedom." Maybe: "Creating 3D art and animations using motion-tracked controllers in virtual/augmented reality."

[n1ckfg]

I like it! Revised the blurb.

[n1ckfg]

Synced latest version to remove merge conflicts.

[ganyawutinashe-commits]

Can l have a working configuration

…

On Thu, 20 Nov 2025, 08:42 Nick Fox-Gieg, ***@***.***> wrote: *n1ckfg* left a comment (sindresorhus/awesome#3711) <#3711 (comment)> Synced latest version to remove merge conflicts. — Reply to this email directly, view it on GitHub <#3711 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZI2BBBCQ3YCYV4IBY2MOED35VPE7AVCNFSM6AAAAACJ6ZBZHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJWGE4DCNZXGI> . You are receiving this because you commented.Message ID: ***@***.***>

[tysoncung]

Checked the list and it looks solid. Here's what I found:

Compliance ✓

• Has both awesome and awesome-list topics
• CC0 license in place
• contributing.md included
• Contents section properly named
• Title is in title case
• Awesome badge linked correctly
• Entries are well formatted with descriptions

Quality observations:

• Good mix of academic papers and practical implementations
• Organized by category which makes sense for this topic
• Links to both papers and code repos where available
• Historical section is a nice touch

Minor suggestion:
The description entries for papers are thorough but could be slightly more accessible for people not familiar with the academic naming convention. For example "Richard Liu et al" might be clearer as just the paper title with year since most people will click through to see authors anyway. Not a blocker though, just something to consider.

Otherwise this is ready to go from what I can see. The content is well curated and follows all the guidelines.

[n1ckfg]

Seems like all the requirements are met--how do we get to final approval?

[tysoncung]

Nice list! Reviewed the awesome-3D-drawing repo - it's well-curated with good coverage of VR/XR drawing tools and research papers.

Observations:

• All checklist items checked
• Lint passes (100%)
• Interesting niche topic with real-world applications (Spiderverse films mentioned)
• Good categorization of papers, tools, and resources
• CC0 license - correct
• Proper awesome badge and structure

This looks ready for merge. Good work on curating this specialized topic!

[n1ckfg]

Not sure what's left to do for final approval--if anybody has any suggestions, please let me know!

[n1ckfg]

Synced and reopened PR.

[n1ckfg]

Still waiting on final approval

[n1ckfg]

@sindresorhus @davisonio Hey, have I left anything undone for final approval on this?

[sindresorhus]

• No reviews done. You never linked to specific PRs you reviewed. You mentioned "reviewed error logs from two PRs" in a comment, but that's not a review. The template requires substantively reviewing other open PRs (pointing out guideline violations or improvement suggestions) and linking to them. Zero substantive reviews are present.

• Repo name is not lowercase slug format. The repo is awesome-3D-drawing (uppercase "3D"). The guidelines require lowercase: awesome-3d-drawing.

• License not detected by GitHub. The LICENSE file exists but GitHub shows "NOASSERTION." Re-add via https://github.com/n1ckfg/awesome-3D-drawing/community/license/new?branch=main&template=cc0-1.0.

• Top description describes the list. "A curated list of 3D drawing papers and related resources on using motion-tracked controllers in XR…" starts with "A curated list of…" which is the canonical bad pattern. Describe the subject, not the list.

• Entries use HTML instead of Markdown. Every entry uses <a href=""> HTML tags instead of standard Markdown [text](url) links. The entire list should use Markdown format. For example:

  - Richard Liu et al - <a href="https://arxiv.org/abs/2505.04813">WIR3D...</a> (2025)
  

  should be:

  - [WIR3D: Visually-Informed and Geometry-Aware 3D Shape Abstraction](https://arxiv.org/abs/2505.04813) - 3D shape abstraction using visual information and geometry awareness.
  

• Entry format does not follow awesome list conventions. The standard format is - [Name](url) - Description ending with period. Your entries use Author - <a href="">Title</a> (Year). {code} with no description of what the paper does. The author name and year are metadata, not descriptions.

• Mismatched brackets. Two entries have [ opening with } closing:

  • [<a href="https://github.com/keijiro/MlsdBarracuda">code2</a>} (under "Towards Light-weight…")
  • [<a href="https://github.com/enochkan/vox2vox">code2</a>} (under "Vox2Vox")

• Self-promotion without disclosure. At least 4 entries are by the list author (Nick Fox-Gieg / n1ckfg):

  • "Lightning Artist Toolkit" paper (3D Drawing Implementations)
  • "Lightning Artist Toolkit" dissertation (Dissertation/Thesis)
  • "TiltSet" dataset
  • "ABC-Draco" dataset

  No disclosure of authorship.

• PR body description describes the list. "A curated list of tools, articles, and community resources for…" and "3D drawing papers and related resources" describe what the list collects.