Stan`

Sounds like it warrants a regression ticket

Please upload replays to replay pallas so everyone can see them

After a discord discussion there are some other options possible, such as tweaking build restrictions. In this case though, it would not be possible to change the passability class number restrictions without touching C++ code.

After some discussions on Discord it would seem his armature was corrupted.

See https://gitea.wildfiregames.com/0ad/0ad/wiki/ExportingErrors Either you have loose vertices or multiple materials, and neither are supported.

Transparency should work in baking. You're right about variation, though

Can you test since I gave you some extra rights ?

Was it still pointing to 0ad/0ad ?

I've added you to https://gitea.wildfiregames.com/org/0ad/teams/contributors can you try again with the main repo as lfs ?

Just to check you could make the lfs point to your fork instead.

@Itms updated Gitea yesterday could you try again @Cayleb-Ordo

Yeah it's old news now.

Usually when baking you should import the actual model.

If you start the campaign automatically there might be a way to force gamesettings.

Well it needs to be checked. Usually the least textures the better. They don't need it but it doesn't hurt to try. Also you might get away by tweaking the UV2 to give more space to some stuff.

Well if you have questions do not hesitate Mmh if the map type is scenario and assuming it's correctly set in the XML you shouldn't be able to change it but I'm not sure. Maybe it only applies to civs.

Well you could add it (copy the code) to a modded component and do some stuff on death. With a list of tokens (templates)

To me the title is clear ^^. It's about catching exceptions. Initially that doesn't help performance but makes using threads simpler. (So more things might be moved to another thread in the long run.) To me this ticket was a mega ticket to keep track of all that was to be threaded hence my confusion

You can bake at any resolution to get more crisp details. In the game though currently most textures are 1024*1024 and ideally we shouldn't go above this unless you have a 20k tris model. Small items should either have smaller textures, or to reduce fragmentation be baked in the same texture as the main mesh they are used on.

`SpawnEntityOnDeath` Only creates local entities, it's meant for say debris, or an explosion decal. https://gitea.wildfiregames.com/0ad/0ad/src/commit/32edc28cda72d0c9cd70937d7c46c58322bcf040/binaries/data/mods/public/simulation/components/Health.js#L403

Short answer: it depends. On lower end machines, graphics are gonna eat up your GPU causing your CPU to starve. So for those, graphics and model quality will be the bottleneck. Getting the state for unit selection is quite slow as it pulls a lot of data (https://code.wildfiregames.com/D1618). Querying interfaces, (e.g getting a component for an entity) might be faster with better data structures https://code.wildfiregames.com/D1739 / https://code.wildfiregames.com/D4718 Creating entities is a bit slow too IIRC. E.g our upgrade system could use not having to create and destroy entities https://code.wildfiregames.com/D4991 Other hints in patches by wraitii https://code.wildfiregames.com/search/query/1SOtiSQV9ik8/#R This looks interesting https://gitea.wildfiregames.com/0ad/0ad/pulls/8521 OUTDATED but maybe still interesting https://gitea.wildfiregames.com/0ad/0ad/wiki/GamePerformance EDIT: also https://gitea.wildfiregames.com/0ad/0ad/issues/5874 which has a weird title cc @phosit

Could be a recent update to Gitea cc @Itms

You might try to make a weathered version of the boat texture to make it look like it's been there a little while.

Looks really cool! Maybe the stone wall could use a few more details to look less blocky but otherwise good job.

If you can't take criticism, don't participate in a community project. Do you have a reference that would make a worthy addition to the wonder?