NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix

[Toolkit feature]: Drag n' Drop Auto Ingestion Support

Open
#712 4 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

feature good first issue jira toolkit
Dominant language
No language data
Stars
1.7k
Forks
99
PR merge metrics
No merged PRs in 30d

Description

Contact Details (Optional)

No response

What is the context of the feature/improvement?

In the RTX-Remix Toolkit, I think it would a handy feature to have the option to drag and drop a texture into remix that will auto ingest/replace on the selected texture at the time of drag/drop if Remix is able to identify what texture is to be replaced by using the same filename identifier (albedo, height, etc). This would be very helpful for workflows involving browsing current assets in one window and having Remix open in another, a local drag and drop. Attached is a look into my recent workflow, looking through my asset folders of free CCO textures as I'm looking what to replace.

Please describe the feature/improvement?

Currently it looks like drag and drop is only supported in the Ingestion tab, spreading this feature to the modding tab making the point that receives the drag and drop would make the ingestion/replacing much easier for users who may be less experienced. Sort of an opportunity to learn the toolkit by having remix assign the textures automatically when a drag and drop happens if it's able to identify the texture. A workflow using AmbientCG or PolyHaven textures where they have the _albedo, _height would let users easily start replacing textures.

What would be your solution? (optional)

Drag and drop would work replacing the current selected texture if Remix is able to identify the texture is being dropped. As far as the ingestion folder, maybe a folder like "Drag'nDropped" or "Dropped" identifying that these items were added via drag and drop.

Version

106.0.0+release.118399.fcefe91f.gl

Media

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.