Jump to content

wraitii

WFG Programming Team
  • Posts

    3.399
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by wraitii

  1. Interesting development. Do you have any statistics on OSX version usage? I believe it's mostly a few reluctant users on 10.6 and the rest basically on 10.8/10.9
  2. It's almost there, but if feels a little too mechanical. I get this weird feeling that all legs move one after the other and not together. Can't pinpoint why though.
  3. We should definitely ask Zaggy fot the .blend files though, I don't believe they're on SVN. Great work on the animations though Enrique, feels pretty natural!
  4. Some more reports: I run it fine in Xcode usually by rebuilding the workspaces after running the "build osx bundle" script. However in both cases I get a ""GL/glx.h" file not found" error in HWDetect.cpp.
  5. AI overhead mostly comes from inefficient data storage as JS sucks at that. Filtering, pruning, iterating: all fairly advanced stuffs that could be done well with (a lot of, perhaps) work in C++ basically can't be done in JS beyond some basic points.
  6. Gave it a shot. Can't run ./build-osx-libs.sh directly because the 10.7 SDK is removed in the latest Xcode. Changed to 10.8 and ran the script fine until the game compilation, which failed. Started XCode, had to re-switch all the schemes to Release (this is annoying, if it could be changed it'd be great). Tried to compile. Seemed to go fine but I've got an error on every project, "Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool failed with exit code 1", which is somewhat odd.
  7. Looks quite good, Enrique. I'm assuming this is one of the more recent armatures where you have the IK?
  8. There's a weird "elongation" effect on the front leg (particularly visible on the right one), but other than that it looks pretty good.
  9. Tried again with 2.69. There's definitely an issue with our existing animations. New armatures now export more correctly, there is however still an issue with branching bones (see picture). This usually will break IK. This is probably the thing that makes importing our existing armatures slightly broken, too. Animations would probably work mostly right, but because of above weirdness it'll bug. This might be a limitation of the Collada format, though…
  10. Concerning the fishing boat: I'm definitely able to commit it. However the animations might have to wait a bit.
  11. I kinda likes the old one, it was very reminding of AoE 1 (ah, the power of nostalgia)... BUt it's probably not the most realistic, and those look very good too.
  12. I've failed to compile 0 A.D. against the 10.9 SDK (Mavericks), apparently because there are some issues with Boost and some fundamental C++ library files in "Graphics"... (note: this was compiling using Xcode, not the script. Also I'm still under 10.8 so this might be linked).
  13. Okay, the new version has been committed to SVN. Again, no real log changes, but tons of behind-the-door changes, so it needs testings, and I also need feedback: do you find it harder/easier than before? What should it do differently? Stuffs like that. Hopefully it's a little faster than it used to be, I'm not really sure. No naval support or savegame support as of yet.
  14. Sorry guys, I've been a little stopped this WE (had a very fun WE with fellow students, but I had to rest for a bit). I think I'll be able to work on 0 A.D. properly this WE though.
  15. I'm opening a topic at last for an issue that we discovered a long time ago and that might finally be resolved (opening it to remember to check that it's actually fixed). The issue is that our old collada armatures don't load up nicely in Blender. A change in 2.68 should have fixed this, however now 2.68 can't load those old armatures. A ticket for that has been opened on the Blender Bug Report. Latest update is that it's been closed after a report that "I was getting the same crash with 2.68 on linux64 (whichever revision was packaged with Fedora 19), but the same model imported fine with the latest nightly build. So this issue has probably already been fixed." Ticket is here. I recommend we try again with Blender 2.69 to see if: A- our armatures load up B- they load up nicely.
  16. It looks disabled to me too. I would suggest trying a marble-like texture?
  17. The might might look better centered in that. Perhaps.
  18. You could check that by activating the developer overlay (alt+d by default I think) and checking "reveal map". As for the new AI, I've fixed an important bug regarding naval transport this week but have lacked time. I'll try to work on it more tomorrow, and try to commit it sometimes next week. We'll see.
  19. I think fixing the range manager will fix this definitely (the entity map patch)
  20. It appeared that without any particular reasons, GLSL was much slower on some computers, so it at least seems worthwile.
  21. In the interest of releasing A15 quickly, it would probably be good to commit this as soon as possible so it can be debugged. As far as I know, we've reached a fairly acceptable level of "it works" on most compilers/systems in the early testers. Though I think it still needs some UTF8 support and stuffs?
  22. wraitii

    AI error

    I can't recall if I've added some tech checks for units in A14 for Aegis, but Aegis definitely shouldn't build stuffs from town phase/city phase if it's not phasing up.
  23. I don't remember exactly how the whole things read, but it's very clear now.
  24. I think it will be released in a few weeks from now. Historic_bruno, just to be clear, are your issues with the SVN AI or my beta above?
  25. Sounds like it's getting stuck on something... I'm afraid this is a "wont fix", I've changed this logic in my repo already so the error is about 100% non-reproducible.
×
×
  • Create New...