The current pre-release of the client ("pioneer" in the version) is only compatible to itself. So you can only play with other testers. Please be aware!

Categories

  • Announcements regarding our community

    64 Topics
    140 Posts
    FichomF
    If you've played co-op missions Operation Blockade, Tha Atha Aez, Golden Crystals, or Overlord Surth Velsok recently, you've probably run into it. You saw patches of ground replaced by a red-and-black stripe pattern, where the mission's terrain should be. It wasn't a graphics setting or a broken install. Every player loading those four missions saw exactly the same thing. These four missions bring their own custom terrain textures, and the path to those textures had gone out of date, so the game couldn't find them anymore. Instead of showing the intended ground, it had nothing to draw there, so it fell back to the glaring placeholder pattern players have been reporting for a while. That's now fixed. The deployment chain has been corrected so it always points to the right path for each mission's own textures, and the fix has been checked thoroughly. It was checked against versions the community had already patched manually, and by loading the missions in-game, with several players confirming the terrain renders correctly and nothing else broke in the process. If these missions put you off before, now's the time to give them another shot. Load one up and see the difference for yourself. Have fun out there! Thanks to Seraphim-Noob and Brutus5000 for fixing this Bug! Full technical details are documented in the pull request. [image: 1787772060434-786a385e-70f1-4848-a4d0-0676f603b4fe-image-resized.png]
  • The real competition starts here.

    275 Topics
    7k Posts
    MrBreastsM
    Sign up.
  • 471 Topics
    5k Posts
    BlackYpsB
    We still need logs to investigate this
  • A place to talk about whatever you want

    2k Topics
    27k Posts
    D
    All units can fly. Flying units are vunerable to AA. The larger a unit is, the slower it flies.
  • 3k Topics
    16k Posts
    N
    The sound error FAQ is outdated. We now know the cause of the bug being that the engine causes memory corruption when using an unsupported sound configuration. What the FAQ's troubleshooting covers is: Disabling surround sound and enabling stereo, which is a supported configuration Adjusting audio hardware/software configuration to shuffle memory hoping the memory corruption doesn't land somewhere where the game crashes once it reaches there Turning off sound entirely (/nosound) so the bugged code is never reached Your crash address 0x00915402 pops up for other sound error victims, so it is likely the cause. We fixed a different common crash/desync bug so this is the only remaining one afaik. Another way to fix it right now is to play on the new engine, which fixes the sound bug. You can do this by downloading the alpha client and selecting FAF Develop when creating a new game. For others in the future, I expect the next stable client update will support launching the new engine, rust client should get an update for it soon, and eventually we'll get the new engine on normal FAF.
  • For people who want to add more stuff to FAF

    625 Topics
    8k Posts
    NuggetsN
    @Nomander said: @Firv If you have the sound bug (due to 7.1 surround: "unknown speaker configuration" + "xact3dapply failed") the sounds on the new engine will be weird with now-functioning distance attenuation (quieter) and LFE/subwoofer channel (more bass for explosions/impacts). Is that your case? Yes i had that too. You barely heard anything when zoomed out. Normally you can hear a gunship or whatever attacking when zoomed out and try to find it. In that game you just didnt hear it at all
  • A readonly copy of our previous forums on phpbb3. (Not all uploaded files are available.)
    Search only via google using the site:forums.faforever.com option.