Jump to content

vladislavbelov

WFG Programming Team
  • Posts

    1.338
  • Joined

  • Last visited

  • Days Won

    22

Everything posted by vladislavbelov

  1. We can do some things and I have a patch for that: https://code.wildfiregames.com/D4602. But I'm not satisfied with it yet.
  2. It looks like the one of savegame files was corrupted. Could you backup your savegame files (you might find paths to them here: https://trac.wildfiregames.com/wiki/GameDataPaths#Linux) and clean the folder? Also might do it step-by-step to find the corrupted file.
  3. Maybe an assertion but the error window wasn't shown? We need logs if there is crashlog.txt.
  4. My minimap patch isn't a feature, it's an optimization. And according to the open RB list I have some time to make a proper patch.
  5. How can I help? Minimap looks ok, maybe add some comparison screenshots?
  6. I have ideas how to fix the issue, but I need to finish GL stuff first.
  7. Wondering how many frames per hour UE5 might give for our average hardware
  8. Yes, it might because of failed creation of some textures. Could add debug checks to the config file: renderer.backend.debugcontext = "true" renderer.backend.debugmessages = "true" renderer.backend.debuglabels = "true" renderer.backend.debugscopedlabels = "true"
  9. Maybe just models with too close geometry.
  10. Unfortunately FXAA isn't supported on macOS yet. Because it requires GL3.3+ shaders support, but macOS can't provide it for GL2.1 mode that we use. I plan to add a possibility to disable an option for platforms where it's unsupported.
  11. 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.
  12. 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.
  13. glibc added a new macro M_PIf to workaround the bug few months ago, I'll fix that tomorrow.
  14. Thank you very much for testing! I added a fix, though it might have a bit different stack. Could you try the latest SVN?
  15. I've committed few additional checks to the SVN. Could you update and compile the game?
  16. 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.
  17. Could post your graphics options (advanced tab)? Also do you have steps to reproduce?
×
×
  • Create New...