All Activity

Updated the title.

So basically the game only works with Vulkan if you have GPU Skinning off and you're playing in Windowed mode? The former is expected since there is a bug there, but the later I do not know.

What is your driver version? When I have time, I'll try to see if I can reproduce the same situation.

Disabling GPU skinning does nothing. What happens, when starting a game, it starts to load, then goes to windowed mode with the error message popping up to continue or exit,(clicking continue the game just closes after a few seconds). Just tried running the game in windowed mode, and it does finally work, but units have artifacts, which I found goes away if I disable gpu skinning and restart the game.

How does it work with GPU skinning disabled? I guess it might be the same issue as point 2 in this post, except for the driver version — I only know it's older than Adrenalin 24.9.1. By the way, could you test whether you’re experiencing the issue mentioned in point 1 of that post and reply there? Vega GPU users seem to be pretty rare. Thanks!

in my experience, larger maps are stronger for cav because there is more space to exploit the speed difference.

I agree. Melee cavalry needs to be faster than ranged cavalry if its supposed to be a counter. And if ranged cav already falls in that range, thats also good. But it might be better to equalize the speed of all ranged cav to a greater degree (so its not 1.3× to 1.6× but instead maybe 1.3× to 1.4×), then we could reduce the speed of melee cav while still having melee cav quicker than ranged cav (maybe at 1.5× to 1.6×)? Lastly I wanted to add two more things I think are relevant to the cavalry issue as a whole: For one the entire game is incredibly quick by the numbers; fast queue times, fast build times, fast gather rates. Thus, it feels like cavalry needs to be even faster to keep "the same advantage" as in other, slower rts. Additionally most games are played on "standard mainland settings" or even ambush nomad or pizza, all of which are very small. You can see this by looking at how often people build additional ccs to get more map control (it doesnt happen often, atleast not in my games). Small maps also make cav more effective, since the moment you see them coming, they are basically already in your economy, thus you need to be very quick in reacting to defend sufficiently.

My first try as the Han dynasty. HanVSPtol_H.zip

I just make the PR https://github.com/JustusAvramenko/delenda_est/pull/70 that enable the summary work again and the game itsel work in current development phase :), let me know

Ranged cavalry are already within that range (x1.3-x1.6 of inf equivalent) melee cavalry have more and I feel it is smart gameplay-wise as melee cav intuitively can be used to: engage backlines be able to counter ranged cavs raid with comparable effectiveness as skirmisher cavs. All 3 scenarios require melee cavalry to have this additional speed.

OK. Here are the files I'm guessing are the correct ones. I've reinstalled the game multiple times and same issue every time. Last install, I installed to USB drive, and after getting the same error/crash, transferred the USB to my desktop and Vulkan worked fine. crashlog.dmp crashlog.txt mainlog.html

Yes, this is what is needed. Options. Cavalry can raid well, but it should 100% die to spears. At least, it shouldn't be cost-effective at killing it's supposed counter unit.

but do they have to be twice as fast? wouldnt 1.5× or even 1.3× as fast be fast enough? I feel like this would be an unnecessary "unification" of playstyles across different civs. A civ with good defensive options could (if walls, forts, towers werent so bad) secure their eco without needing to keep troops at home and force the enemy cav to take a fight by attacking the enemy base. Then the cav die to normal spearman and no "quick" counter unit is necessary.

Hi @Shafe, welcome to the forums. If you would attach the files as described in the error message people could actually look into it,

More examples of shield walls:

Reinstalled the game twice, and no luck, Vulkan crashes every time when starting a game, OpenGL works fine. Before installing Alpha 27, I had the pre-release of Alpha 27(0.0.27-rc-27645) and Vulkan worked just fine, to confirm, I uninstalled Alpha 27 and reinstalled the pre-release and Vulkan works fine. If it helpful, game was installed on a Acer laptop with a 5700u. This is the message that pops up when the game crashes. Much to our regret we must report the program has encountered an error. Please let us know at https://gitea.wildfiregames.com/0ad/0ad/issues/ and attach the crashlog.txt and crashlog.dmp files. You may find paths to these files at https://gitea.wildfiregames.com/0ad/0ad/wiki/GameDataPaths Details: unhandled exception (Integer divide by zero) Location: unknown:0 (?) Call stack: (error while dumping stack: No stack frames found) errno = 0 (No error reported here) OS error = 0 (no error code was set)

As you can see from this thread, a consensus will never happen as for the solutions @real_tabasco_sauce makes the all the balancing PRs that get approved by the team atm. So rly it's almost about convincing him. With current production stats (cost, prod time..) more durable units actually makes the game feel more spamy. This because there are much more situation where both sides can sustain sending troops on the front-line, replacing dying units by new one for a long while. Since melee re-balance, this happens more rarely, as battles tend to play out slightly faster. I'll maintain that it did have a positive impact on the gameplay, also because it put less importance on sniping making other things matter more.

I’ve left it alone so far. Or are you saying it should be lowered? everyone chill out, these aren’t final! I’m setting up some stuff in the community mod. If we spend some time testing seriously, we can figure out what works and what doesn’t.

I like this strategical discussion. It's important to clarify what "we" want before you/we do any changes. Regarding this, my opinion is that more durable and fewer units on the battlefield what makes good RTS. More micro abilities not just Attack move and few target-fire clicks... It seems 0AD is too spamy now.

I believe the best way to balance cavalry is to eliminate the "blending in" or stacking of units on top of each other. In other words, make the unit collision work as it should. This would make it impossible to have a 30 spear cavalry death ball in just one tile. It will also nerf the range advantage that some champion spear cavalry currently has.

I prefer this. We make cav because we want speed. Otherwise, who would do cav when inf is cheaper and more useful as workers? Definitely not. Units die too fast now and we just see people getting vapourised. 2v1 or bad fight = instant death -> more demanding on good ally and pocket -> less tolerance and more toxicity -> more DoctorOrgans behaviour + exclusion of newer players @real_tabasco_sauce please reconsider the bonus on spear cav against other cavs. The issue is, most civs don't have spear cav. So as soon as someone makes a dozen spear cav, these civs Gaul, Brits, Athen, Maury, Sele are banned from using cav (unless they spam spear champs in P3). Is this what we want? Suggestion: due to the special nature of spear cav, we should give every civ a counter unit, e.g. fanatic, or just give every civ a spear cav option.

Of course they are. I just found it funny how the AI can recommend even a semblance of strategy for 0 A.D, and lay it out in phases.