Jump to content

A25 Feedbacks from testing


Recommended Posts

2 hours ago, Nobbi said:

On Wildlake biome Nubia and Eurasia Steppe is not working and for Agaen-Anatolien some errors appear about the iberean champ missing.

Nubia (I think the same for Eurasian Steppe):

ERROR: JavaScript error: maps/random/wild_lake.js line 286 farmEntities[currentBiome()] is undefined @maps/random/wild_lake.js:286:95

ERROR: CMapGeneratorWorker::Run: Failed to load RMS 'maps/random/wild_lake.js'

 

Agaen-Anatolien:

ERROR: CCacheLoader failed to find archived or source file for: "simulation/templates/units/iber/champion_infantry.xml"

ERROR: Failed to load entity template 'units/iber/champion_infantry'

 

Fixed in https://code.wildfiregames.com/rP25773 thanks.

Link to comment
Share on other sites

33 minutes ago, ValihrAnt said:

Played a game on 25760 and my sword cavalry had issues hitting cavalry archers that were retreating. They'd get in range, start attacking and then stop as the enemy had ran outside of their attack range(?).

You mean the melee Cav thta's attacking the retreating camels? It seems to me they're actually hitting, it's only the animation that's cut short.

  • Like 1
Link to comment
Share on other sites

Just now, wraitii said:
32 minutes ago, ValihrAnt said:

Played a game on 25760 and my sword cavalry had issues hitting cavalry archers that were retreating. They'd get in range, start attacking and then stop as the enemy had ran outside of their attack range(?).

You mean the melee Cav thta's attacking the retreating camels? It seems to me they're actually hitting, it's only the animation that's cut short.

Yep. I didn't go to replays to check if they actually hit as we were right about to start the next game but the lack of sound and the cut short anim put me off there. Would be nice if just atleast the sound played as then you'd have confirmation that something did happen with the attack despite the animation being cut in half.

  • Like 1
Link to comment
Share on other sites

1 hour ago, ValihrAnt said:

Yep. I didn't go to replays to check if they actually hit as we were right about to start the next game but the lack of sound and the cut short anim put me off there. Would be nice if just atleast the sound played as then you'd have confirmation that something did happen with the attack despite the animation being cut in half.

Indeed. Tricky issue, I think it's not new in SP but probably in MP. Made & ticket & a diff: D4154

Link to comment
Share on other sites

21 hours ago, Stan` said:

Thank you. Steppe Agean-Anatolien is working now but the two other biomes are not working at all with Rev25778:

Generating Wild Lake of size 320 and 8 players.

Setting biome generic/nubia.

...

ERROR: JavaScript error: maps/random/wild_lake.js line 286 farmEntities[currentBiome()] is undefined @maps/random/wild_lake.js:286:95

ERROR: CMapGeneratorWorker::Run: Failed to load RMS 'maps/random/wild_lake.js'

and

Generating Wild Lake of size 320 and 8 players.

Setting biome generic/steppe.

...

ERROR: JavaScript error: maps/random/wild_lake.js line 286 farmEntities[currentBiome()] is undefined @maps/random/wild_lake.js:286:95

ERROR: CMapGeneratorWorker::Run: Failed to load RMS 'maps/random/wild_lake.js'

Edited by Nobbi
Link to comment
Share on other sites

Two more things. :) In structure tree values for mercenaries are still rank 1 although they will have rank 2 and a minor thing what I saw is that roman army camp still says it can build rams in description.

  • Like 1
Link to comment
Share on other sites

On 04/06/2021 at 6:26 PM, Yekaterina said:

That big blob was just 1 tree

Screenshot_20210604_201557.thumb.png.7e96c82c9740dddcc13f93998d2a4b90.png

I'd like to keep the giant canopy Acacia, because it's so cool and Acacias can get that large. But I have 2 possible solutions to the gameplay problem you mention.

1. Reduce the frequency of this variation in the actor, perhaps by 5 (the "giant" acacia variant will show up 5 times less than it does now).

2. Make the giant acacia variant into its own template, so that it can be used sparingly as a decorative option (but gatherable, perhaps with a little more wood). 

Link to comment
Share on other sites

3 hours ago, wowgetoffyourcellphone said:

I'd like to keep the giant canopy Acacia, because it's so cool and Acacias can get that large. But I have 2 possible solutions to the gameplay problem you mention.

1. Reduce the frequency of this variation in the actor, perhaps by 5 (the "giant" acacia variant will show up 5 times less than it does now).

2. Make the giant acacia variant into its own template, so that it can be used sparingly as a decorative option (but gatherable, perhaps with a little more wood). 

Another solution: make the entire giant canopy into its selection box, so that units cannot go under the canopy and you cannot build under it. You chop wood by standing next to the canopy instead of going under it. 

Link to comment
Share on other sites

On 19/05/2021 at 6:45 PM, Gurken Khan said:

IV. Stopping to advance after attack order. What prompted my rant feedback. It changed from a23 and I really hate it. When I gave a group of units an order to attack a unit, they used to go to a point where they could attack and then take it from there. Now, if that target is killed or temporarily out of sight, they stop dead in their tracks or do some stupid stuff, like capturing a house or something I'm really not interested in. So if that behavior could be changed back to how it was in a23 I think that would be just great!

I noticed the stop in place if the targeted unit is killed no longer occurs in a25. But a similar stop occurs when a building's foundations are destroyed or if the targeted unit garrisions. 

Is this on purpose? It seems like the three should all be the same. To me, it also doesn't make sense why units would stop walking to an area where a building was planning if its foundations were destroyed beyond the commanded unit's LOS. 

  • Like 2
Link to comment
Share on other sites

3 minutes ago, chrstgtr said:

But a similar stop occurs when a building's foundations are destroyed or if the targeted unit garrisions. 

Is this on purpose? It seems like the three should all be the same.

I agree, and I'm very much in favor of how it was in a23. "If I can't stop that specific unit from garrisoning I'm not stopping any other units either, instead I will stay back here and maybe shoot at a field or try to capture a house." §$%&! darned NO! Advance you stupid idiot!

  • Like 2
  • Haha 1
Link to comment
Share on other sites

3 hours ago, chrstgtr said:

I noticed the stop in place if the targeted unit is killed no longer occurs in a25. But a similar stop occurs when a building's foundations are destroyed or if the targeted unit garrisions.  

Mh, I can't reproduce any difference.

However the units switch into attack-walk towards the original point, and so might side-tracked en-route. This was actually something I'd explicitly changed in rP22567. IMO it'd be worse to simply ignore enemies while walking there, since you'd get free kills. But I didn't really anticipate that units would stop to capture buildings.

I'm not sure it's a release blocker enough to fix it now tbh. You can easily avoid this behaviour: order units to walk somewhere and then queue an attack-order when you're 'in-range' of where you want them to attack. It combines well with the auto-formation feature too.

Over shorter distances, it shouldn't make much difference.

Link to comment
Share on other sites

On 02/06/2021 at 3:04 PM, StarAtt said:

Open a terminal, simply copy this entirely and paste:

 


sudo apt update && sudo apt install subversion build-essential cmake libboost-dev libboost-system-dev   \
    libboost-filesystem-dev libcurl4-gnutls-dev libenet-dev libfmt-dev   \
    libgloox-dev libicu-dev libminiupnpc-dev libnvtt-dev libogg-dev   \
    libopenal-dev libpng-dev libsdl2-dev libsodium-dev libvorbis-dev   \
    libxml2-dev python rustc zlib1g-dev wx3.0-headers libwxbase3.0-dev libwxgtk3.0-gtk3-dev libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5 -y && svn co https://svn.wildfiregames.com/public/ps/trunk/ 0adsvn && cd 0adsvn/build/workspaces && ./update-workspaces.sh -j3 && cd gcc && make -j3 && cd ../../.. && binaries/system/test

enter your password and wait until it says "...............OK!" and you can find pyrogenesis in binaries/system/

You can learn terminal during the build though.

Just to list some of my adventures on it. I initially thought that when I saw a program called pyrogenesis.exe, I had to use wine. I also tried to do in the terminal cd 0adsvn/binaries/system/ and then type pyrogenesis, but then on my OS, the pyrogenesis variant did call the 0ad version which is in the mint repositories. What did work was using 0adsvn/binaries/system/pyrogenesis

Initially I thought that I probably messed to much with my OS, which results in me now having a brand new Mint 20 installed instead of Mint 19. I wanted to upgrade anyway.

I did play the subversion and the graphics look great. I must admit that on the a24 version, I put the graphics on low to boost performance, so I might not do a fair comparison. Age of Empires 4 has been shown on E3 and their fans would be spoiled if only it looked as good as 0AD.

The path-finding also seemed good, but on the other hand I did not push it to the limit either.

So from my first game, it is big plus for A25. If only mercenaries were well balanced...

 

Link to comment
Share on other sites

1 hour ago, wraitii said:

Mh, I can't reproduce any difference.

However the units switch into attack-walk towards the original point, and so might side-tracked en-route. This was actually something I'd explicitly changed in rP22567. IMO it'd be worse to simply ignore enemies while walking there, since you'd get free kills. But I didn't really anticipate that units would stop to capture buildings.

I'm not sure it's a release blocker enough to fix it now tbh. You can easily avoid this behaviour: order units to walk somewhere and then queue an attack-order when you're 'in-range' of where you want them to attack. It combines well with the auto-formation feature too.

Over shorter distances, it shouldn't make much difference.

Agree2021-06-14_0008.zip, not a release blocker. I was able to reproduce the difference between stopping when walking to build a destroyed building and continuing to walk to a point where a targeted enemy that was already killed. Garrisoning is harder to replicated because AI doesn't garrison much but I saw it happen before and I just can't find the replay of it. 

  • Thanks 1
Link to comment
Share on other sites

26 minutes ago, LetswaveaBook said:

Initially I thought that I probably messed to much with my OS, which results in me now having a brand new Mint 20 installed instead of Mint 19. I wanted to upgrade anyway.

Please don't upgrade any further to 21.04. Ubuntu 21 is toxic. 

I recommend fedora 34, because on fedora the dns package manager is always up to date and more stable than Arch. Just use 'sudo dnf install 0ad' and it will give you A24 instead of A23 if you use apt. 

Snap is slow. Flatpak doesn't always work smoothly. 

  • Thanks 1
  • Sad 1
Link to comment
Share on other sites

16 minutes ago, Yekaterina said:

Please don't upgrade any further to 21.04. Ubuntu 21 is toxic. 

I recommend fedora 34, because on fedora the dns package manager is always up to date and more stable than Arch. Just use 'sudo dnf install 0ad' and it will give you A24 instead of A23 if you use apt. 

Snap is slow. Flatpak doesn't always work smoothly. 

ok, next if i will change a Linux. whey not Fedora. maybe in next years

  • Haha 1
Link to comment
Share on other sites

Just now, seeh said:

ok, next if i will change a Linux. whey not Fedora. maybe in next years

If you have a very high IQ then you can try Arch based stuff. I am not clever enough for Arch and I don't have the patience to install it. 

Link to comment
Share on other sites

Another thing which I want to be changed is the behavior of units leaving a building you loose on an enemy through capturing. Your units will be released at the point you have when no destination is set instead of walking to the destination point you set last.

Link to comment
Share on other sites

5 hours ago, Yekaterina said:

Please don't upgrade any further to 21.04. Ubuntu 21 is toxic. 

I recommend fedora 34, because on fedora the dns package manager is always up to date and more stable than Arch. Just use 'sudo dnf install 0ad' and it will give you A24 instead of A23 if you use apt. 

Snap is slow. Flatpak doesn't always work smoothly. 

 

I always advise you to download LST, Ubuntu 20.04 is stable and fast in my view, of course your graphic environment has a lot of influence on that.

  • Like 1
Link to comment
Share on other sites

I used to be a fedora user from Fc3 to f11 got tied of getting a nose bleed with every new version as fedora added some new tech, fedora is Red Hat's experimental platform. Switched to Mint with the Cinnamon desktop and @Lopess is right on with LTS(Long Term Support) which is supported for a minimum of 3 years.

Enjoy the Choice :)

  • Like 2
Link to comment
Share on other sites

+1 for Ubuntu LTS 20.04 (Focal Fossa). I've been an Ubuntu user since LTS 10.04 (Lucid Lynx) and it just keeps getting better with every release. 

But you have lots of other good distros, depending on what you want. For example, if you're into network security, digital forensics and all of that stuff, you could get Kali Linux.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...