vladislavbelov

Pretty cheap for a professional software ~3x of annual Netflix subscription, I remember Maya costs much more.

Does it make sense to use xNormal if Blender has a builtin baker?

Minimized != paused. Also we don't always know when a window is completely invisible. Also we had crashes on some cards when we do or don't draw to an inactive window.

It's not static, you can move your camera while paused, you can use UI while paused. To fix overload one might enable V-Sync or use FPS limiter. If it's all enabled then the hardware isn't good enough to handle its current graphics settings.

For Windows it's a complete game installer made for the current development version.

I mean not the A24b release, but a release build for the SVN version. Yeah, you need to go step-by-step and build. But the good thing is that you can use binary search: if you have a range [A, B], when on the revision A the game is broken and B is fixed you need to check the revision (A + B ) / 2. And then depending on results you need to go to [A, ( A + B ) / 2] or [( A + B ) / 2, B]. That feature is built-in in git, but maybe there is something similar for svn.

Ideally I'd like to have answers for the two following questions: Is it really fixed or is it still reproducible for a release build of the game? If it's indeed fixed which commit is the reason?

Not necessary, just select all projects with Shift and then open properties once.

Is it A24b or a different version?

Could you try svn version (https://trac.wildfiregames.com/wiki/BuildInstructionsGettingTheCode)?

Are installed GPU drivers up-to-date?

They have the same style but they don't share a single palette

I think all our icons are unrelated in visual term. They don't have neither the same palette nor style. For it me it looks like random images.

Currently I don't need dumps, first I need to find an option that triggers the crash. @feneur could you remove the post limit?

Could you try to disable all options step-by-step except GLSL (GLSL should be always enabled)?

Again, try disable other options first, non-glsl shaders will be removed.

With Vulkan our art isn't so slow since Vulkan allows to submit data via command lists - less app/driver time per each draw call. And all this stuff should be supported, have unified interface between new and old APIs.

That does work in general, but it won't solve the performance issue. Our art is unoptimized for old hardware/API, we can't have a lot of drawcalls there. That's true that a cut helps. But in our case it's not enough. We have no strict technical rules and tools to control the engine usage. Without strong cooperation the game won't be faster. All results will be publisheb on the page https://feedback.wildfiregames.com/results/.

I'm worrying only about how many meshes on a visible scene at once. In case of wonder if it doesn't completely reuse existing textures for other buildings then the best implementation is to use a single mesh with a single texture with a maximal side not more than 2048 pixels (atm).

It depends on how it's going to be used. How many different meshes are going to use these textures. Will be these meshes always rendered together or they're unrelated.

The "Off" option has maximum performance. Supporting intermediate states means additional cost of support for graphics. We also could render only half of objects in reflection/refraction maps, but it also requires additional support. I don't mind for that solution. It won't help in the only case when many units are killed at the same time and many units have been already completed in queues.

Hi @JPRuehmann! Could you attach logs and system_info from the logs folder. You might find it for your system at https://trac.wildfiregames.com/wiki/GameDataPaths#Linux

I don't remember, maybe some code is unified between tabs. So you need to use different widths for different tabs.

I notice the popping even with 200, when a battle is big enough, like 200vs200. Bigger battles make them even more noticeable. I can feel the irritation in your words. I'm not against feature, I'm against the intermediate numbers. Why? Because the current implementation adds coupling (which is bad) and adds visual degradation. Since we have nobody to be responsible for overall visual impression of 0 A.D. I'm worrying about that, since I'm doing graphics. It's a biasing, please do not present your opinion as a truth. Why do you need corpses if your computer isn't powerful enough for them? Why not icons with number of lost units?

Have you read the posts above? About inconsistent popping in a case of intermediate numbers?