libGDX VS nanovg

Neat, thank you! I'd love to see how it compares to the libgdx IntMap[0].

[0] https://github.com/libgdx/libgdx/blob/master/gdx/src/com/bad...

For anyone interested, LibGDX[1] is a very nice open-source game engine for Java. It is cross-platform (mobile, PC/mac, web). Very popular and well maintained, too.

[1] https://github.com/libgdx/libgdx

Source is also available on github https://github.com/libgdx/libgdx to directly check the implementation of a specific classes.

And let me explain, for example jorbis this library has a lot of nested loops in it, i understand why this library using this, but this is really bad. Because when I am trying to use library with this code, this taking so much time to convert ogg to pcm, and yes I know that converting ogg to pcm is a hard process, but I need to optimize my program, make it more better. The main thing is EVERY decoding ogg file library using the same piece of code! And I am not joking for example libgdx.

What the pcm file contains? And what is the structure? What data I should use for converting .ogg file into pcm? Is there any information about pcm files? Is there any repositories in github that converts .ogg files into pcm? (I am already know there is JVorbis, libgdx and jorbis but thats not what i want)

There's a code snippet showing the seed generation and how it feeds into each RNG pattern but it also mentions the use of a "xorshift128+ algorithm" here: https://github.com/libgdx/libgdx/blob/master/gdx/src/com/badlogic/gdx/math/RandomXS128.java

I can't guarantee you'll get a reply, but Mario and Nate's email addresses are in the AUTHORS file.

I found an example for rendering a [Mesh] object using instancing in LibGDX's tests (link), but I'm not sure how to apply that for rendering actual models.

assuming you use that (https://github.com/libgdx/libgdx/blob/master/build.gradle) as your starting point. You first have to ask what it is that your build should cover. Do you need all the spotless checks and release flags and so on or do you just need to package everything up so that it could run.

Fork this open-source Java + Gradle based project: https://github.com/libgdx/libgdx

BGFX is a general-purpose 3D graphics engine, not a GUI nor vector graphics framework.

Nanovg is an awesome vector graphics library, but has limitations. (1) no ClearType, I fixed in my fork: https://github.com/Const-me/nanovg (2) The only way to get AA is hardware MSAA, unfortunately many popular platforms like Raspberry Pi don’t have good enough hardware to do it fast enough. Nanogui is built on top of Nanovg, shares the limitations.

I agree with the OP that Cairo and Skia are the only viable ones for Linux.

It’s sad because Windows has Direct2D for decades now (introduced in Vista), and unlike 2006, now in 2021 Linux actually has all the lower-level pieces to implement a comparable equivalent. Here’s a proof of concept: https://github.com/Const-me/Vrmac#vector-graphics-engine

> in your words, that "the quality is not good"

Oh, you were asking why I said so? Because I have clicked the “notes document” link in the article, the OP used the same tiger test image as me, and that document has a couple of screenshots. And these were the only screenshots I have found. Compare them to screenshots of the same vector image rendered by my library, and you’ll see why I noted about the quality.

> Vrmacs draws paths by decomposing them into triangles, rendering them with the GPU rasterizer, and antialiasing edges using screen-space derivatives in the fragment shader.

More or less, but (a) not always, thin lines are different. (b) that’s a high-level overview but there’re many important details on the lower levels. For instance, “screen-space derivatives of what?” is an interesting question, critically important for correct and uniform stroke widths. The meshes I’m building are rotation-agnostic, and to some extent (but not completely) they are resolution-agnostic too.

> and it is perfectly capable of rendering high-quality small text on the GPU

It is, but the performance overhead is massive, compared to GPU rasterizer rendering these triangles. For real-world vector graphics that doesn’t have too much stuff per pixel that complexity is not needed because triangle meshes are good enough already.

> it looks like it occupies a sweet spot similar to NanoVG

They’re similarities, I have copy-pasted a few text-related things from my fork of NanoVG: https://github.com/Const-me/nanovg/ However, Vrmac delivers much higher quality of 2D vector graphics (VAA, circular arcs, thin strokes, etc), is much faster (meshes are typically reused across frames), and is more compatible (GL support on Windows or OSX is not good, you want D3D or Metal respectively).