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.

    274 Topics
    7k Posts
    CalcicreteC
    i'm challenging jagged to sign up and duel me within the 2nd qualifier. Let's see if he dares...
  • 471 Topics
    5k Posts
    BlackYpsB
    We still need logs to investigate this
  • A place to talk about whatever you want

    2k Topics
    27k Posts
    N
    Buff brick DPS 295 -> ~304, returning 50% of the DPS it lost after the last nerf (down from 312.5) because: the nerf's goal was to make brick weaker vs Percy, and now Percy is strong vs brick, so there is space to buff the DPS the nerf's goal was to make brick weaker vs othuum/harb, and while in a 1-unit-composition matchup this nerf made it more fair per mass, the brick needs to be more unfair because their lack of shields makes sniper DPS and Ythotha AoE very strong. Their stats also struggle to beat GC/ythotha + harb/othuum compositions a bit too much, which makes getting Megalith too difficult. Monkeylord is not good against GC/Ythotha at all, so mega is required to fight those T4s efficiently without just winning hard in T2 and getting an overpowering army at later T3. Add the Pulsar, which is the unreleased cybran T3 long range anti shield unit. It was wanted by old balance team, then it got delayed and eventually canceled by Rhaelya looking for an alternative solution before adding new units. Since no alternatives have been proposed and I don't see what would work better, I think the unit should finally be added. It solves the shieldless arty's low DPS against snipers and the struggle against mid-late gun coms that OC all your bricks if you try to attack anything while easily tanking with shield upgrades and mobile shields. Make firebeetles jump at enemies. it looks cool and fits the theme makes them hit in the middle of unit clumps more consistently, including on attack move/attack orders. reduces pathfinding needed increases their effective attack range The jump range in my prototype is around 5, which is the current detonation trigger range, and is small compared to any gun (LABs have 14 range). I think after the last nerf beetle is pretty good for gameplay but is a little weak because it dies very easily, especially at T3 stage, if you don't have basically equal unit counts and are in range to tank for the beetles, so that's why I'm interested in trying this new mechanic as a straight buff.
  • 3k Topics
    16k Posts
    R
    Thanks for the info, i'll check it the next time i get logged out
  • For people who want to add more stuff to FAF

    625 Topics
    8k Posts
    S
    @Xiaomi So yes your right, i think I'm approaching the ceiling on what can be done, although I'm sure there are always clever tricks to go further. Do bare in mind though that, that trace is a 64k air battle, the normal balance of the game simply doesn't run in to that kind of unit count, even if you played with 64 players. I do think a lua thread pool api could be introduced similar to love2d , but that would really only help with big chunks of work like ai and such. with this i would imagine some task api where you opt in to certain data (unit position, eco, intel, etc...) to be copied over to an isolated lua thread, then you would set a duration of ticks for the work to be completed in, such that it remains deterministic, if it hasn't completed in time the sim would wait. something a bit like this in the sim (this is pseudo code just to illustrate the idea) -- Plain-data arguments, deep-copied at post time local taskArgs = { thing = 5, } local dueInTicks = 10 -- Which parts of the sim to copy over local unitsView = { fields = { 'Position', 'Army', 'BlueprintId', 'Health' }, categories = categories.MOBILE, armies = 'enemies', } local access = { Units = unitsView, Terrain = true, PathGrid = { 'Land', 'Amphibious' }, Economy = 'own', } -- Which task to run: a module path and a function in it local taskModule = '/mods/myai/lua/tasks/threat.lua' local taskFunction = 'Compute' local pending = Pool.PostTask(taskModule, taskFunction, taskArgs, dueInTicks, access) -- do more stuff local ok, result = Pool.WaitForTask(pending) -- resumes at exactly post tick + 10 then the worker script function Compute(args, View) local units = View.Units local count = units.Count() for i = 1, count do local position = units.Position(i) local health = units.Health(i) -- do stuff thats slow... end return args.thing * 42 -- plain data, handed back at the due tick end This has the advantage of allowing devs in the lua to break up work in to as many threads as they see fit, and with so many cores now available, more tasks are always better. https://love2d.org/wiki/love.thread There is also robloxs thread model where you can have read only access in parallel, and write access is then serialised. https://create.roblox.com/docs/scripting/multithreading but yes you are right, it is in conflict with how supcom was made, perhaps another possibility would be to allow some wasm runtime (still allowing scripting of a sorts, just compiled), but I'm not sure if those are actually that much faster than the luau vm. of course you could move the whole game to native code, but then you lose modding and such... interesting none the less
  • 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.