lamarrr / ashura Goto Github PK

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Describe the bug
Rendered Text is pixelated on zoom or when it is larger than it's rasterized size.
We also presently render the glyphs twice, one for the regular glyph with alpha channels, and another with static strokes, this has the disadvantage that the stroke widths are static and the new stroke atlas is allocated separately.

Expected behavior
Not be pixelated and use less memory

Proposal
Switch to SDF text rendering

See:

Tutorial: https://github.khronos.org/glTF-Tutorials/
Spec: https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html

2D

• Implement Renderer-Agnostic Canvas API
• Implement Vulkan Renderer for Canvas
• Integrate Audio and Video codecs for WebM (video: AVI + audio: Opus/Vorbis) (to be used showcase)
• Integrate animation codec for AVIF (to be used in showcase)
• Integrate audio codec for Opus and Vorbis (to be used in showcase)
• Implement WebP, JPG, and PNG image decoders
• Implement 2D animations (i.e. easein, easeout, etc.)
• Wide Gamut Support for image decoding (png and some formats specify color space) and swapchain images i.e. P3, Adobe SRGB (see: https://developer.android.com/training/wide-color-gamut, https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VK_EXT_swapchain_colorspace.html, https://en.wikipedia.org/wiki/DCI-P3, https://docs.google.com/document/d/17C7UAaLSX2hHOq-hYENeJ1HwMhPCL-e0pb9Pn8rXUok/edit)
  Terms: Gamut: color range supported by device from a color space, Color space: range of values

Widgets & Engine

• Implement Box widget
• Implement Button widget
• Implement Grid widget
• Implement Padding widget
• Implement Stack widget
• Implement text widget
• Implement Flex widget
• Implement image widget
• Integrate and evaluate 2d animations in widgets
• Drag and drop (see: flutter/flutter#30719)
• Add NetworkImageSource for Image Widget, with optional caching specified via image widget props (try_load_from_cache, cache_image)
• Fix text layout
• Remove use of pointers for identifying widgets

3D (Optional. low priority)

• Implement quaternions and operations
• Implement 3d render pipeline
• Implement bloom post-processing (based on unreal engine's) https://www.youtube.com/watch?v=ml-5OGZC7vE
• Implement blur post-processing https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/blob/main/docs/samples/blur.md
• Implement PBR rendering post-processing
• Implement chromatic aberration post-processing
• Implement depth of field post-processing https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/blob/main/docs/samples/depth-of-field.md
• Implement shadow mapping
• Implement particle effects
• Implement bokeh effect
• Implement global illumination

Plugins

• Implement an async streaming http client using CuRL as backend
• Implement async file io streaming (with io_uring as backend on linux if supported otherwise c-posix api, and ioring on windows)
• Implement window controller API and explore solutions to allow creating and attaching widgets to multi-window supported platforms
• Implement clipboard plugin that can copy and paste multimedia content
• Implement vulkan font loader plugin

Infrastructure

• Implement CI for checking for build errors
• Implement basic unit tests where reasonable
• Consider implementing regression tests once the code becomes more complex and more churn is performed in the system

Abstract

• Survey Flutter, React Native, SwiftUI, Web, Chromium, UE5, and Unity's features, strengths, and areas of weaknesses we can work on or improve

Statistics

• Memory Usage and widget
• CPU utilization API and widget
• GPU utilization
• API and task tracing
• Add Vulkan Command Query Pool

Custom UI Graphics Pipelines

https://stackoverflow.com/questions/63166/how-to-determine-cpu-and-memory-consumption-from-inside-a-process

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

presently, rendering large text is very inefficient even with command culling, we should batch text rendering and pack all font atlases into a single sampler2DArray. this will enable us to render all the text in the scene with a single draw command or with instanced rendering and vertex attributes if necessary.
once the new render graph is implemented, this should be trivial to implement

• Bezier Curves
• Bezier Splines

The CI build seems to be broken as it is failing to find the Freetype package's libraries.
I don't know why and a quick search reveals nothing

Presently we are not even specifying if the memory resides on the host or the device, we need to check for resizable bar support and then use resizable bar if it is supported, otherwise fall back to using device buffers.

VecBuffer, for example, isn't specifying if to use device or host memory, vertex buffers can be mmap-d.
Textures' staging buffers should also use resizable bar where possible.
we might need a separate function that isn't find_suitable_memory_type().

See: https://gpuopen.com/learn/using-d3d12-heap-type-gpu-upload/?utm_source=twitter&utm_medium=social&utm_campaign=gpuuploadheaps

Things to think about

• Mouse interaction
• Z indexes in vertex3d
• Nesting and relative positioning to maintain transforms
• Transformation of pointer to widget space using quads?
• How well will this work in a 3d context?
• Widget::draw should probably be relative to the widget's position by default???
• We'll need clip transforms, Canvas 2d to 3d transform??

We need to be able to dynamically create, use, and disable render targets and render passes.

Our sample use cases are:

• Bloom Render Pass
• Gaussian Blur Render Pass (Mip Blitting + Compute stages)
• Acrylic Glass Effect Render Pass
• Offscreen Rendering for Text Rendering Effects
• Post-Processing
• reflection probes

The render graph should be able to efficiently take care of:

• Pass description (arguments, resource types, bindings)
• Resource management and lifetimes
• Resource updates, state & usage tracking, and data flow
• Barrier and Synchronization
• Pass Lifecycle management

To prevent lerp between vert and frag shaders use flat values.

i.e.

flat out vec2 out_uv;
flat in vec2 in_uv;