Hacker News Reader

Comment by marcodiego | Hacker News Reader

I don't know if it supports HDR on MacOS but, AFAIK, it doesn't on windows and in Linux it is only supported with Wayland.

Though I don't like the Wayland x X11 flamewar, I'm happy to see some modern features are only supported on Wayland.

That may please the crowd that will be able to say "sorry, I can't use x11 because it doesn't support a feature I need" bringing some symmetry to the discussion.

Edit: correction: it is about the development 5.0 version: https://devtalk.blender.org/t/vulkan-wayland-hdr-support/412...

View on HN

> I'm happy to see some modern features are only supported on Wayland.

Why?

If anything that's a reason to why I wouldn't fully jump to blender.

I have been working on my own hobby game engine for the past 15 years and have been excited to introduce Blender to the workflow. If this is the case I don't like it. Wayland has never work for me the same way as X has.

What else are you going to use on Linux?

Nuke, Maya?

If they spent 15 years on the engine as is, what's another few more years rolling a proprietary modeling system?

On a serious note, I do wonder if this Wayland only limitation is something a fork could work around.

I don't think there's an X11 HDR standard, one would need to be created and implemented.

If the starting point is that Wayland is missing features that X has, the good outcome is not getting to a point where neither option has all the features, the good outcome is that either one has all the features.

That's at the cost of lots of duplicated work by the already sparse number of people capable of implementing a graphics server.

There's also a third option where Wayland is foundational and the X11 network protocol is implemented on top of that for people who need it. Why should a network GUI service implement a driver to talk to a specific model of video card?

> That's at the cost of lots of duplicated work by the already sparse number of people capable of implementing a graphics server.

Yeah, it kinda sucks but this is where we are.

> There's also a third option where Wayland is foundational and the X11 network protocol is implemented on top of that for people who need it. Why should a network GUI service implement a driver to talk to a specific model of video card?

Agreed; I have long argued that it would have been far better to transition to everything on the same backend with effectively rootful XWayland being the only (bare) X server, and then after that try to deal with the rest of the stack (if you really must). And maybe in 2026 we'll finally start to see movement in that direction with https://gitlab.freedesktop.org/wayback/wayback

It definitely does on macOS and I think also on Windows. You have to set the color management for the viewport to Display P3. In older versions this precluded you from using AGX or Filmic, but I think you can actually use AGX with Display P3 now.

I really wish to could use Wayland, but there is too much problems or bugs related to the software I use for work and also play. I will test it again with this new version Blender (that was one of that software with problems).

In general, most repositories use old stable versions of Blender. And often folks are reduced to using snap to maintain version specific Compatibility with add-ons etc.

Also, getting the most out of Intel+RTX CUDA card render machines sometimes means booting into windows for proper driver support. Sad but true... =3

The reality is most commercial software and users are on Windows machines. It is fundamentally a Blender interoperability, and 3rd party platform license compatibility issue. We all wish it wasn't so, as many artists find the Windows file systems and color-calibration concepts bewildering.

Making a feature platform specific to a negligible fraction of the users is inefficient, as many applications will never be ported to Linux platforms.

Blender should be looking at its add-on ecosystem data, and evaluate where users find value. It is a very versatile program, but probably should be focused on media and game workflow interfaces rather than gimmicks.

Best of luck =3

I agree with you, but I think this limitation is for much simpler reasons, like "the contributor only knew how to make this feature in Linux, and only in Wayland". cross compatibility for stuff a base as color grading can be a thorny issue.

If nothing else, it's better to have some implementation to reference for future platforms than none.

We've all seen too many plugins become version specific or indeterminately broken

https://www.youtube.com/watch?v=WFZUB1eJb34

Someone needs to write a Blender color calibration solution next vacation =3

The significant majority of the film and animation industry uses Linux.

Linux RTX CUDA drivers are getting better, but really depends on the use-case. For a Flamenco render farm it makes sense for sure.

Creatives on wacom tablets and Adobe products etc. will exclude the Linux Desktop option. =3

Not just for the farm, the large majority of the movie and tv vfx and animation you see is done by artists using Linux workstations.

Not the artists I meet, they love their wacom tablets and pressure responsive painting programs... i.e. most of the other software is windows only.

I like Linux (use it everyday), but many CAD, Media, Animation, and Mocap application vendors simply don't publish ports outside Windows.

Most studios have proprietary workflows with custom software. =3

Indeed but this is a discussion about Blender and you posted originally:

> Making a feature platform specific to a negligible fraction of the users is inefficient, as many applications will never be ported to Linux platforms.

All the large studios use Linux, that's why all the third party software that is used in feature animation and vfx is supported on Linux. So I'm just saying 'negligible fraction of users' in the case of Blender (which as a project would like to increase adoption in professional feature animation and vfx) isn't really true.

I am sure Studios account for a small portion of the 4.5 million unique downloads each release. Note that less the 20% of users ever touch film or animation projects, 73% are single users, and most related user applications are Adobe products.

Stats are available from the published 2024 feedback data:

https://survey.blender.org/feedback/2024/

Best of luck, =3