Jump to content

vladislavbelov

WFG Programming Team
  • Posts

    1.419
  • Joined

  • Last visited

  • Days Won

    24

Everything posted by vladislavbelov

  1. Shaders don't, but a video driver does. I.e. we still support Intel video cards, which can have a version 3.0 or lower, that doesn't have many nice features. I wanna change the current shadow mapping way, because for low angles we have a low resolution per terrain unit. I'd like to use PSM or CSM, and I'm more near to CSM, i.e. 2 cascades. I agree about HDR. Also we don't have deferred rendering yet. About formats RGB16F or RGB32F has enough precision, but it's expensive. So if R11G11B10F will be enough, then we have to use it. Because it's 4 times cheaper. FPS meter isn't enough, we need to use more strict tests. Because the FPS meter has a noticeable error.
  2. It's not possible yet, because we don't drop GL2 yet. But it'd be good to have a switchable renderer in the future. What's broken? It doesn't run? You can make screenshots from the game. https://code.wildfiregames.com/D1402 The current postprocess isn't completed. I.e. we can't select multiple effects. Also HDR isn't actually HDR, it's usual LDR, but with color corrections. We need to use R10G10B10F or RGB32F for true HDR. Any filtering is noticeable under a low hardware. It'd be good to know you hardware and some charts to compare results. I'd like to see MSM.
  3. If make the shadow more expensive, we can use moment shadow maps. That's good, but our blur is pretty simple (just a linear), it'd be good to replace it by the Gauss one. It's pretty hard to make the water realistic and beautiful at the same time, especially without real references (i.e. the contrast). Also did you use my patch for the water vertex shader fix? Because the current one is broken, so the specular light is calculated wrong for heights != 15. It'd be good to have screenshots to compare before/after states.
  4. I agree, we definitely have to avoid "using namespace ..." (except very rare cases). Especially we have modern IDEs to autocomplete it. The "icu::" would be better, even for the patch reading.
  5. Hi @gabewarr11 and welcome to the forum! It happens immediately after the start and you didn't see a main menu ever? Could you attach a crash dump and crash info from the game logs folder: https://trac.wildfiregames.com/wiki/GameDataPaths ? Files are called crashlog.dmp and crashlog.txt, also mainlog.html, system_info.txt files would be useful for us.
  6. Did you test other LAN games/applications? Is it the first try to connect these 2 PCs?
  7. I agree with @Lion.Kanzen about dark gradient, it needs to be lighter. Also how it looks for small border shapes? Like small rings? Because it's harder to make a nice border with wider sprite.
  8. Helmets are too different by colors from the rest model, isn't it? I think they should be a little bit lighter.
  9. Another way to get the callstack: as you're in the gdb on the crash, you can type bt to print the current callstack.
  10. I think, the shortest way is to override the getBatchTrainingSize function: function getBatchTrainingSize() { return 5; }
  11. You probably downloaded the .torrent file (it requires an additional program that can open and download such files). But you can download the installation file directly. There is a link under the big gray button. @Itms @implodedok May be we need to make the link more noticeable.
  12. Also Revert all local changes and Cleanup the repository may help to make Update.
  13. You can find information about hotkey/shortcuts in our wiki: https://trac.wildfiregames.com/wiki/Manual_Settings#KeyboardShortcuts.
  14. Hi @MlemandPurrs! We needs more information about your system to detect a problem: Does music play in other applications? What operation system do you have? What audio configuration do you have: headphones or speakers, audio card? Do you use laptop or desktop?
  15. Hi @Venqui and welcome to the forum! You can find most information about development in our wiki: https://trac.wildfiregames.com/wiki/GettingStartedProgrammers.
  16. The rule "material is the trend" is the rule only for copy-paste games. A game can have own designed solution. So I suggest to not exactly follow trends, but to design good view.
  17. The text isn't well read, the blue background is too opposite for the gold logo. Also I think, it'd be good to have a background with "historic"/"game" style, not the abstract one. IMHO.
  18. Current solution is don't use these materials, because it has wrong rendering algorithm (I have ideas only in mind, currently I'm still pretty busy with our GUI rendering). Actual ticket is #4219 (last fix was by @elexis: r18890).
  19. I think step-by-step changes are enough. Because it's harder to review and find small errors in a huge patch.
  20. Where it crashes? Could you retrieve a stack trace? It seems working for me on macOS, I'll try on Windows later.
  21. It can, but the patch isn't for main game files (like JS or XML). So there is a chance, that the Atlas will work.
  22. Patch's author still works on it. You can install it on SVN (with a nearest to patch version, because it may have conflicts with the current version). Download patch (diff) from https://code.wildfiregames.com/D825 and apply it on the repo (how to get repo): patch -p1 < patch.diff And compile the game.
×
×
  • Create New...