Add support for user images to ImGui integration of SampleBase

[Marlax0]

I see SampleBase has ImGui integrated, but it doesn't have support for user images or custom font textures.
A working example of this for NRI would be really useful, and I guess this would be the most convenient place to do it.

Ideally the Descriptor* would be used as the ImTextureID, but I'm not sure how to make that work with NRI's design.

I'm currently very inexperienced with NRI, but integration is clearly not as simple as:

nri::Descriptor* image = (nri::Descriptor*)drawCmd.GetTexID();

if (image)
{
    nri::DescriptorRangeUpdateDesc descriptorRangeUpdateDesc[] = {
        {&image, 1},
        {&m_Sampler, 1}};

    NRI.UpdateDescriptorRanges(*m_DescriptorSet, 0, helper::GetCountOf(descriptorRangeUpdateDesc), descriptorRangeUpdateDesc);
}

NRI.CmdSetScissors(commandBuffer, &rect, 1);
NRI.CmdDrawIndexed(commandBuffer, {drawCmd.ElemCount, 1, indexOffset, vertexOffset, 0});

(As UpdateDescriptorRanges() is immediate but CmdDrawIndexed() buffered.)

Since the descriptor set part of NRI sort of resembles Vulkan, perhaps this issue is relevant: ocornut/imgui#914

[dzhdanNV]

Hi! As it was discussed here NVIDIA-RTX/NRI#111, it does make sense to develop an NRI-based ImGui backend and (ideally) just get it published in "ImGui" repo. But as a start, why not do it in NRIFramework? I will add support to user images soon...

[dzhdanNV]

I think, the productization should be done in this order:

• fully functional ImGui renderer in NRI framework
• wrap this into a standalone NRI extension
• reorganize into an ImGui backend

[Marlax0]

I think that plan sounds great.

To learn NRI, I wanted to create a simple 2D sprite batcher utility, which generates triangles and draw lists in a similar way to ImGui.
So from my perspective a fully featured ImGui backend would be another excellent example to learn from.

I ended up just grabbing a DescriptorSet* from a frame-buffered pool, whenever the current batch texture changes.

I'm sure there is a better way, so I'm looking forward to seeing what someone with more NRI experience can come up with for ImGui.
I picked up NRI after exclusively learning D3D12, so the whole DescriptorSet concept is new to me.

[dzhdanNV]

I ended up just grabbing a DescriptorSet from a frame-buffered pool, whenever the current batch texture changes.

Sounds right. IMO, to minimize copy operations 2 sets are needed: one for all static stuff, another one (with several instances) for a texture (which can change). The another one should be allocated from a ring buffer, big enough to maintain desired number of user textures per frame multiplied by number of frames in flight.

so I'm looking forward to seeing what someone with more NRI experience can come up with for ImGui.

We will see what I will be able to reach :) What I use now does vertex data packing to minimize CPU-GPU traffic and offers minimal HDR support.

I picked up NRI after exclusively learning D3D12, so the whole DescriptorSet concept is new to me.

NRI tries to not introduce new concepts. DescriptorSet is from Vulkan. It's there because... Vulkan is the common denominator (i.e. D3D12 and even D3D11 can be made looking like VK, while VK can not be made looking like D3D12). DescriptorSet in D3D12 backend is just a continuous range of descriptors in a DescriptorPool (descriptor heap in D3D12).

[dzhdanNV]

Closing this, because I gonna implement Imgui rendering as an extension in NRI: NVIDIA-RTX/NRI#136