All Activity

Yes. But threads are not processes and ideally we can multi process all those pathfinders instead of threading them. Thread still leaves them ok the same core Also could the simulation updates on each entity be done in parallel? That would also mean a mega performance boost

Js isn't threaded but the pathfinders and other systems are you can see what the threads are doing using the web page profiler 2

Tested A27.1 rc1 — the situation is still the same: it crashes with Vulkan and GPU skinning enabled. (No crash log, 2 errors in Windows Event Viewer)(Same as issue 2 in the post below) (issue2)Event viewer.txt

I am on A27.1 RC2 and this is what the consumption looks like when playing a giant 2v2 fight: With A27.1, you can stress out 1 virtual core to 100% and reach smooth performance in game. However, the engine is not parallel-processed yet; the jobs are still all piled up on 1 CPU core instead of distributed out to all. Your 40% utilisation could be true for overall if you are dual-core, but if you are capped at 40% on each core then it's probably caused by the performance issue with Spidermonkey.

Looks very alike the a27 bug/lag that should be fixed with a27.1.

AI is probably researching this thread to train itself to recognize mental breakdown patterns.

What OS are you on ?

I rarely hit 40% utilization on my pc even during very intensive matches with lots of ai's. Is that an issue with my pc or is that an issue with the game. It stutters constantly even in the very early game. Not sure why it's doing this.

This is one of the greatest insider joke threads that I have ever seen on the forum, absolutely made my day! Explanations for those who don't understand: the first gif is a depiction of a player called nababu, who is JC's mascotte in the lobby and has great synergy with him when playing in the same team. The memes for "it's over" and "never begun" are for vinme. The third one is every other mascotte in the lobby, e.g ycswyw. The frog who pokes knife into socket is an abstraction of noob players suiciding by provoking fights with massively larger armies.

Hey, Thanks for the suggestion, however the handling of available payments is not handled by us but rather by SPI, which currently does not accept that way of payment as far as I know. Maybe they negotiated with them since they are patroned by them as well, or maybe they have another account.

neverbegun.mp4

UPDATE: Version 0.7.3 Changes: Fixed a bug with recruiting Champions Fixed a bug with recruiting Support units, set the limit to 50. Added recruitment of Cavalry and Infantry at the start of the game for more defense against early rushes. PETRA_Expert vs Base PETRA

cosmic

CyG869G.mp4 never begun progui user playing without cheats

videoplayback.mp4

normal mascotte

it's over

evil mascotte bolivar.mp4

Some people are also experiencing issue 2. Testing an old AMD's driver: 31.0.14057.5006 (Adrenalin 23.5.2). The result of issue 2 is in this thread: And interestingly, the situation for issue 1 is a bit different. OpenGL has the same problem when running in fullscreen mode as well.

@little Guest, suggest to try the 0.27.1 release candidate as it contains some vulkan fixes and is fully compatible with 0.27.0.

Note that 0.ad Ubuntu PPA has been updated recently: https://launchpad.net/~wfg/+archive/ubuntu/0ad and https://gitea.wildfiregames.com/0ad/0ad/issues/7756 @Loic WIf you use a Linux VM running Ubuntu, then you should be able to play the latest release.

Dear 0.ad community, I would like to donate to this wonderful game. Recently and through other open source projects, I've learned about Liberapay https://liberapay.com/ This allows the batching of small payments so that fees are amortized. Liberapay explicitly ask members to not bug people that have not yet joined, so I apologize in advance for doing it nonetheless, but I was wondering if 0.ad community would consider this as a payment mean in the future. Projects such as LibreOffice are using Liberapay, and there are other people willing to donate through this platform: https://liberapay.com/on/twitter/play0ad Thank you! Raffi

The closest I found in AMD's driver is 31.0.14057.5006 (Adrenalin 23.5.2). The following are the results of my test. OpenGL + GPU skinning disabled + fullscreen mode: fine OpenGL + GPU skinning disabled + windowed mode: fine OpenGL + GPU skinning enabled + fullscreen mode: fine OpenGL + GPU skinning enabled + windowed mode: fine Vulkan + GPU skinning disabled + fullscreen mode: fine Vulkan + GPU skinning disabled + windowed mode: fine Vulkan + GPU skinning enabled + fullscreen mode: crash message, crash log, 1 error in Windows Event Viewer Vulkan + GPU skinning enabled + windowed mode: crash message, crash log, 1 error in Windows Event Viewer The crash message looks the same as the original poster's. (Adrenalin 23.5.2) crashlog.dmp (Adrenalin 23.5.2)crashlog.txt (Adrenalin 23.5.2)Windows Event Viewer.txt