vladislavbelov

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?

I suppose you didn't get the point of the only on/off.

You need to replace count="9" by count="10" in the following lines in gui/summary/summary.xml: <repeat var="x" count="9"> <object name="titleHeading[x]" type="text" style="ModernTopLabelText"/> </repeat> ... <repeat var="x" count="9"> <object name="Heading[x]" type="text" style="ModernTopLabelText"/> </repeat> ... <repeat var="x" count="9"> <object name="valueDataTeam[i][n][x]" type="text" style="ModernTopLabelText"/> </repeat> ... <repeat var="x" count="9"> <object name="valueDataTeam[i][x]" type="text" style="ModernTopLabelText"/> </repeat> ... <repeat var="x" count="9"> <object name="valueData[n][x]" type="text" style="ModernTopLabelText"/> </repeat> You might also want to adjust some padding/margin/width values in layout.js (in the same folder) to fit better on screen.

Could you attach the full logs? Also do you have a minimal mod to reproduce the issue?

I see you just want to add the feature It depends how you look at it. Problem it solves: - No ugly corpses disappearing - See all lost units instead of few - Much more visible (because colored) than corpses to detected lost units (circles can be drawn using unit icon) Problems it adds: - Nothing

Look at them when terrain has maximum passable slope.

Blinking selections on minimap and terrain on the icon hover, and red icon with skeleton in bottom right.

It seems you're contradicting to yourself. Firstly you said "crucial to know what units you lost", which I understand as it's important to you (as other competition oriented players) to react timely on that. Now you say "But people want to see the corpses not 2d icons.". 2D icons is the fastest way in terms of performance to know about all units, not only about last X. But now your prefer visual style over competition.

I believe you got my point. We have 1.5% with 4K and 17.5% with GL2.1, so no choice at the moment. But I hope to move toward 4K. Not quite true. We were talking about toasters and support in general. And we support them not because of UI.

I feel a biasing in your opinion. Having intermediate numbers means inconsistent visual effect: you can't predict which unit will disappear. So your "crucial to know what units you lost" doesn't work always, only when you have no continuous battles or you have the pretty high setting. In our code it requires workaround to implement that. Also there is a better in terms of performance solution: showing 2D icons instead of "heavy" units.

Not in our case, we still have a lot of users with small displays (1366x768). You're talking more about aliasing and similar stuff. Pixel perfect in our case is more about how an image fits onto a display. Also shifting and scaling affects how GPU renders it.

For example Raspberry Pi, or platforms that still support only OpenGL1.5 and not higher. I agree to move forward, the question is how many people we're ready to "lost" and when. Not quite right, in that case we loose only people which think that if a game doesn't use RTX or something similar then it's a bad game. Because the game is playable on the modern hardware, even with scaling. You need powers of two only by technical restrictions of the final texture. So if UI uses an atlas then a piece of it can be a not power of two. Not only, you also have a lot of visual elements like buttons or icons that affect an impression.

It'd be good if you could attach the logs after that error. You may find logs place for your system on the wiki page: http://trac.wildfiregames.com/wiki/GameDataPaths.

Because artists want to make the game more beautiful but they don't have strict checks like reviews for programmers, not all of them follow the existing guidelines. I had a discussion about that with Stan and I need to make an article with guidelines and some tools to control the creativity. And I agree we have a lot of content that is bad in terms of performance. It's possible to scale textures down, but for models it's a lot of work for artists.

For gamers - yes, for our audience - I doubt. A lot of people are far behind modern technologies. Sometimes I've been asked what do we do to support toasters. I'd love to switch to Vulkan and more modern techniques. But it's impossible at the moment to target mainly for 4K. Yeah, kind of that.

So you mean pixel perfect UI, that fits into pixels without rounding/scaling. And there's important note: you don't need to design UI for 4K, the main thing is ratio. That's why I mentioned that if you use sizes for UI elements divisible by 4 then you can fit a UI designed for 720p to any higher resolution. It only requires to choose correct image, like 32x32 texture for 1080p and 64x64 texture for 2160p. But you don't need to change its layout.

Nope, but related. I don't want to spoiler and make any promises. Because it's not the priority for A25, but I hope.