Atlas crash on vulkan when generating random map.

[blarp123]

Not sure if this is a known bug, but if I generate a random map in atlas (any size, including tiny, don't think it's an issue with computer performance) it crashes when trying to render the map in vulkan. Running kubuntu, wayland, mesa graphics on ryzen 3400g with vega 11 iGPU. Works perfectly fine on opengl.

[hyperion]

Atlas uses xw toolkit which doesn't support vulkan yet so it's using opengl no matter what you have in your settings. That said this is likely fixed in the 0.27.1 release candidate. Probably a variant of https://gitea.wildfiregames.com/0ad/0ad/issues/7620

[Seleucids]

8 hours ago, hyperion said:

Atlas uses xw toolkit

Could we abandon xw or wx and switch to QT framework, for the Atlas? 

[blarp123]

I saw this comment earlier think it's related. 

Apparently someone already rewriting to use QT?

Edited Thursday at 00:37 by blarp123

[trompetin17]

2 hours ago, blarp123 said:

I saw this comment earlier think it's related. 

Apparently someone already rewriting to use QT?

 

 

Still in WIP

[hyperion]

6 hours ago, Seleucids said:

Could we abandon xw or wx and switch to QT framework, for the Atlas? 

Because you don't like gtk which is used on Linux for wx?

[Seleucids]

4 hours ago, hyperion said:

Because you don't like gtk which is used on Linux for wx?

Well, I think native gtk is fine, as long as it doesn't crash as much as the current wxwidgets system. I have gtk apps that work fine. 

However, I do believe that QT is superior for the purpose of Atlas, because:

Generally more dense widgets, more efficient use of space, which is good for a GUI which has many elements to it

Aesthetically it integrates better into most desktop environments, also Windows OS. 

Perhaps easier when developing , because QT designer really helps 

GTK has some weird issues with appmenus

 

But of course that's just me. Trompetin is rewriting it with 0ad native js code which also solves the problem 

[hyperion]

1 hour ago, Seleucids said:

Well, I think native gtk is fine, as long as it doesn't crash as much as the current wxwidgets system. I have gtk apps that work fine. 

No amount of toolkit switching would have helped here, the crash has nothing to do with wx but is a bug in pyrogenesis.

1 hour ago, Seleucids said:

Generally more dense widgets, more efficient use of space, which is good for a GUI which has many elements to it

Change your gtk theme if you don't like your current one?

1 hour ago, Seleucids said:

Aesthetically it integrates better into most desktop environments, also Windows OS

wx uses native widgets on Windows, how are you gone beat that wrt integration?

1 hour ago, Seleucids said:

Perhaps easier when developing , because QT designer really helps

It's already developed and the maintenance cost for the last 20 years was exceedingly low, you could say qt was rewritten from scratch more then once in the same time frame.

 

Edit: seems wxqt isn't fully dead https://wiki.wxwidgets.org/WxQt