Jump to content

vladislavbelov

WFG Programming Team
  • Posts

    1.371
  • Joined

  • Last visited

  • Days Won

    22

Everything posted by vladislavbelov

  1. Maybe. I believe we need a JS prototype first to test is it worth or not. As we have lack of C++ developers time. I'd like to avoid gif support.
  2. I could make a config option to set the edge zone size, which might be set to zero to disable it. But it'll be available only in A26.
  3. glibc added a new macro M_PIf to workaround the bug few months ago, I'll fix that tomorrow.
  4. Thank you very much for testing! I added a fix, though it might have a bit different stack. Could you try the latest SVN?
  5. I've committed few additional checks to the SVN. Could you update and compile the game?
  6. It happens on start? The assertion was added few weeks ago. It might be that the bug was silent and now it's detected by the assertion.
  7. Could post your graphics options (advanced tab)? Also do you have steps to reproduce?
  8. Thanks! Is it possible for you to run and play the game with GDB (it allows to resolve the stack with related source lines)?
  9. Yep, thanks! Could you tell which map it was and which steps did you have (like have you just started the game and the map or it was at the end of the match)?
  10. Do you have logs and crashdump from that run? The error might happen on out of memory.
  11. In my opinion the new cursor looks a bit strange, more cartoonish than we had before. (first mentioned here https://code.wildfiregames.com/rP26448)
  12. It has nothing about architecture of the engine. The answer is: We don't build 64bit game for Windows yet, like we do for other platforms.
  13. Thank you for the report, fixed in https://code.wildfiregames.com/rP26302 (it was a side effect of an implicit relation). Could you reproduce the slowing at the end? If yes could you enable profiler (usually press F11) when it's noticeably slow and make a screenshot and attach here?
  14. It's a known thing, thanks. My next patch about framebuffers should fix that.
  15. I don't have an implemented solution yet.
  16. Because somethings else is broken I might have a good solution, but not in priority at the moment.
  17. It's incorrect to replace 2.0 by 1.5 because it should convert [0, 1] range to [-1, 1] range, not [-0.75, 0.75].
×
×
  • Create New...