Jump to content

wraitii

WFG Programming Team
  • Posts

    3.245
  • Joined

  • Last visited

  • Days Won

    63

Everything posted by wraitii

  1. The feature can be disabled individually for ships if people prefer so. I _believe_ this is incorrect, as an arrow that hits its intended target only its the intended target and not any other target that may overlap it.
  2. My take for now: Units overlapping is not a desired outcome of the pushing logic However, it is quite a bit harder to prevent it and actually make pushing work and/or pathfinding work. The pathfinding benefits of pushing outweigh the cons of units overlapping I don't know if I'll have time / how much time I'll have for A26. Possibly little. So I wouldn't expect this to get much worked on. It's possible that there could be tweaks to pathfinder.xml to improve things. Do you mean that e.g. A24 already had problems with this or are you talking about the A24-A25 SVN version?
  3. I think it's left-click for actions that you click such as clicking the Patrol icon, and right-click for hotkey-triggered actions, such as attack-move (or using the patrol hotkey)
  4. For what it's worth, my opinion is that this will never work Looks cool nonetheless. IMO there are a few basic problems: - If you want 'realistic' ship movement, you either need to have only rowing ships, or some notion of wind. Players do not want to have to care about that, and some maps could be basically unplayable if ships aren't able to go sufficiently into the wind (which, as square-sails, they might not). - If you don't want fully realistic movement, you would still need some sense of inertia: acceleration, stoppage, turn-rate. This is a rather complex problem, but it's made worse by the sheer size of ships. They are already completely unusable, so making them more awkward is not the move. Part of the problem is that our maps are much, much too small. You'd need to make them at least 10 times bigger. The engine can't support it, unfortunately. - The simplest solution is to make ships 'AoE2 like', which seems to be the direction AoE4 takes (haven't played the beta), and I'm not surprised. Basically all RTS of this specific sub-genres have done that.
  5. I've noticed that too, on _some_ maps, in _some_ cases. I absolutely cannot figure out what's happening, profilers show nothing... My best guess at the moment is that it has something to do with how we limit frame time, but I'm just really unsure.
  6. (I'll ask the usual question -> are you using formations?)
  7. Caesar III used birds to highlight fish areas, which I think is a decent and semi-realistic option, if water cannot be made transparent / people don't want jumping fishes.
  8. There's other solutions: add some flying birds, more fish that jump out of water.
  9. This was done on purpose: https://code.wildfiregames.com/D3706#161503 The choice can always be reverted, but IIRC we had reasons for it, see convo there.
  10. Thanks for the report -> this was actually a bug in the C++ height map loading code, hence why it happened there.
  11. mh, if anything we fixed the code. it's plausible that there's still some issues that make the AI able to ignore restrictions though.
  12. Maybe, maybe not, but it was bugged in A24. The default settings are that those orders aren't executed in formation, so most players will probably not notice.
  13. I guess not particularly reported or not reported. Fancy orders don't really work that well with formations (gathering is pretty broken, too, compared to regular units, and I'm sure many others). Not going to be fixed for A25 anyways.
  14. The actual motion of any single unit (including the invisible 'controller') is in C++, however the code that calculates offsets for a given unit is in JS, in formation.js. The problem is that you'd want the offset to adjust each turn, which might be tricky to do at the moment. It's really two pieces of code: - Formation.js decides where to put the unit in the formation - CCmpUnitMotion.h in C++ handle the motion. These are both rather complicated files, but you can take a first look at them and see what you understand.
  15. Just as a quick update for everyone: a lot of the team is on holidays / not super available for the past few/next few days, so releasing won't be as timely as we'd hoped, but we're still going to get there soon, no worries.
  16. The way formations work currently is that units are assigned an offset to the 'formation controller', an invisible, large entity (paths like a ram/elephant). Then they try, at all time, to go to that offset. The 'formation controller' itself is moving normally. This is why turning looks weird: suddenly the formation controller rotates and the offsets change a lot, and it's very un-natural. Fixing this efficiently would require a rethinking of the system, so it's not that trivial.
  17. Here is the second 'Release Candidate' of Alpha 25 - Yaunā We've entered Commit Freeze, which means we only now fix Release Blocker issues that we might yet find. Downloads - Current bundles are for SVN revision 25808 Linux data and build MacOS Windows Things to note: We've not tested translations yet. I think it's time to do so. If there are errors, report them on transifex. Mind your mods -> they might introduce issues or Out Of Sync. Save your A24 config file somewhere, ideally. Notable changes since the last bundle: Fix the bug where saving while paused would make everything disappear Fix a crash related to patrolling small bug fixes Currently known issues: We've had a few crash reports. Please provide crash dumps or stack traces, when able. What to do if I have an error or notice something weird? Post your commands.txt (replay) and the interestinglog.html file from your folder. You can also reply to this thread. What to do if the game crashes? Update your crashlog.dmp and crashlog.txt see https://trac.wildfiregames.com/wiki/GameDataPaths What to do if I have an Out Of Sync? You should go in your logs folder, find the replay (commands.txt at least), the mainlog/interestinglog and find the OOS dump folder. Zip all these files and upload them here. We need the reports from two players to compare them: One OOS and one non-OOS players at least should upload their oos_dump files. Things you may want to test (non-exhaustive) Launch a random game Launch a skirmish. Connect to the lobby Play on the lobby with someone Launch Atlas and try things out there Open Unit tests demo (To see if there any breakage in displaying entity's) (It's in scenarios) Enable feedback and see if it works (Main menu) https://videos.pair2jeux.tube/videos/watch/ca45fa29-c120-487e-af9c-cf52020666ab Connect to and use mod.io Test replaying new games Test Screenshots (F2) Test Big Screenshots (Maj+F2) Test hotkeys Test Saving and loading a game. Test Quickload/Quicksave And of course playing games.
  18. That will only work in a dev copy. The correct change is in user.cfg, which you can find via http://trac.wildfiregames.com/wiki/GameDataPaths
  19. @hyperion: my point was mostly about the "alpha" or "rc" monikers, which don't really appear in our releases anyways. The release name format is `0ad-0.0.X-alpha-`. I do agree that we probably could have used `0.X.y`. I'm not sure it's a great idea to change the scheme while still in the same 'alpha' version. I expect we'll reboot some things after A26 (which I would like to be the last 'alpha' kinda whatever happens, but we'll see).
  20. Correct Yes, ships have 'pushing' like units do, which makes them slightly more usable, but also overlap quite a lot.
  21. Would you happen to have the replay of that? The units should be able to unstuck themselves, but it's plausible in such situations that this doesn't happen because of the overall movement from everything. We had a few reports of similar situations in past alphas - this type of situation is basically the worse case of the current pathfinder system...
  22. Our minimum supported resolution is 1024x768 and we don't really make much of an effort to support smaller screens in either direction. So I wouldn't expect somebody from the team to suddenly fix this tbh, but we might accept a neat patch.
×
×
  • Create New...