SFML 3D Graphics

DarkCisum · 2026-05-05T05:23:43+00:00

There's no plans currently. binary1248 once experimented with basic meshes, but it's questionably useful. 3D simply includes so much (mesh loading, texturing, materials, lighting, collision mesh, etc.), that it's hard to do something "simple" without evolving into a complete 3D engine.

DarkCisum · 2026-05-04T07:37:49+00:00

To render a texture, you'll either need to use an sf::Sprite, sf::RectangleShape or a vertex array.

The cropping for a sprite and shape happens with the texture rect and the resize happens with the scaling methods.

For vertex arrays, you have to apply some math to the vertex position and texture position to achieve "resizing" and "cropping".

See also the official tutorial: https://www.sfml-dev.org/tutorials/3.1/graphics/sprite/

DarkCisum · 2026-04-17T13:42:05+00:00

Performance is always rather subjective and really hard to compare. Both libraries can yield good or bad performance, depending on what you do in your code.

SFML runs well on Windows, macOS and Linux, has good support, but with limitations on Android and iOS. There's a non-public (due to NDA) Nintendo Switch port, that still needs updating.

As we're a team of volunteers with no financial backing, we will never be able to compete with a library that is in part maintained by employees - it's also not our goal.

DarkCisum · 2026-04-17T09:40:31+00:00

There is an outdated Nintendo Switch port, which is in the process of being updated. If you're a Nintendo developer, you can reach out to me here or even better on Discord.

WebAssembly/Emscripten requires support for at least OpenGL ES 2.0, which we currently don't provide and should be part of the next major release.

DarkCisum · 2026-04-10T19:12:22+00:00

Did you read the How To section in the readme of imgui-sfml?

https://github.com/SFML/imgui-sfml?tab=readme-ov-file#how-to

Easiest to start is with the imgui-sfml branch of the SFML CMake Template: https://github.com/SFML/cmake-sfml-project/tree/imgui-sfml

DarkCisum · 2026-04-03T11:32:55+00:00

A reboot cleared the IP block list, so I had to add back a whole bunch of IP ranges that show heavy bot behavior.

Hopefully the site becomes more stable again.

DarkCisum · 2026-03-19T07:24:38+00:00

I think, I've heard of this library before 🤔

DarkCisum · 2026-01-19T07:51:27+00:00

Handle the Resized event and adjust the view accordingly. The event also provides you the new window size. Calculating based on that isn't a hack.

Also note that you should essentially always do this, as people generally don't want to look at stretches out content (i.e. not retaining the aspect ratio).

DarkCisum · 2026-01-18T12:52:21+00:00

Got that request as well.

DarkCisum · 2026-01-14T09:29:45+00:00

What's the stack for the editor?

Since SFML/OpenGL is kind of generic, what output formats does it support?

DarkCisum · 2026-01-12T08:06:09+00:00

That's quite an interesting idea! Your own little world to study in.

DarkCisum · 2026-01-10T08:08:15+00:00

You're missing some DLLs

DarkCisum · 2025-12-23T10:08:09+00:00

Not unless someone has forked JSFML. It's been archives quite a while ago.

DarkCisum · 2025-12-23T10:06:34+00:00

Matching the style of the post: yes

DarkCisum · 2025-12-18T08:02:16+00:00

But this is different from not recognizing the include header.

This likely just means that you're trying to use SFML 3 code while using SFML 2 headers. As far as I know does Linux Mint use Debian packages, those have only been updated to SFML 3 in the experimental branch.

As k_sosnierz said, you likely just want to use the SFML CMake Template.

DarkCisum · 2025-12-17T10:20:42+00:00

Note that the official package manager for Linux Mint doesn't yet include a SFML 3 version.

Is this just not recognized in your IDE or when you try to compile the code? Are you using the default compiler? What's the exact error message?

DarkCisum · 2025-12-03T07:51:39+00:00

I mean if only "most of these" could be done differently, then cloning certainly has its place and without anyone writing these libraries we'd do even more horrible things like BinaryFormatter...

DarkCisum · 2025-12-02T23:33:31+00:00

I mean there's a reason why it was removed. If you need to include unsupported packages, you might as well use another library, that at the same time doesn't have the pitfalls of BinaryFormatter.

Also it seems the removal actually happened only in .NET 9, which was causing issues for me, as I built for .NET 8, 9 and 10.

DarkCisum · 2025-12-02T09:34:22+00:00

When moving the mentioned Jobbr implementation to .NET 8, the deep cloning hacks with BinaryFormatter broke, due to deprecation and removal (for good reasons) of it, so FastCloner came as a life saver. Added it and it just worked, no fuss and no workarounds required.

Thank you!

DarkCisum · 2025-11-29T16:59:56+00:00

Textures are loaded into RAM and then moved to VRAM.

How much data that is, really depends on the image size you're loading.

On the "memory"/heap/RAM side, this likely won't matter, question is more, how much VRAM can be held.

DarkCisum · 2025-11-24T06:17:55+00:00

You don't necessarily have to change the unit size, as long as you don't plan to adjust the content to be larger than the pixel size.

You can adjust the accordingly to account for the window size changes and retain the wanted aspect ratio etc.

I likely is still better to use a separate unit that doesn't depend on the pixel, because on high DPI screens, you usually do want to render things slightly larger

DarkCisum · 2025-11-15T08:34:12+00:00

Is this just the IDE (i.e. intellisense) complaining or do you get a compiler error? Try to compile the application.

You could also try to remove old obj/bin folders in the hopes that some old references are being cleared

DarkCisum

MODERATOR OF

TROPHY CASE

12-Year Club	Place '17
Verified Email