Hey Saver, that's awesome! Fantastic work!
I wish you had more time, or could do a workshop — like a guide explaining which programs to use and how to implement these changes.
Or we have to wait until you retire and have more time

I love those new models
Can’t wait to play the mod.

@bobbybandit

The log does not show any unit errors. The mod "BlackOps FAF: Unleashed" v26 (9e8ea941-c306-aaaf-b367-u00000026000) is loaded and should work. (at least there are no errors in log)

please test the Unleashed mod without any other mods enabled.

A thing i saw was "warning: Unknown DirectSound speaker configuration 8. Defaulting to Stereo."
This will crash the game if you don't fix this. (search the forum for soundfix)

@sinhosie

This version will not spawn additional units for humans. Only for AI.

(Have in mind if you want to play this with friends, everyone need this mod installed.
You can have the original and this mod in the same directory but don't activate both at the same time )

AllFactions_FAF_BO_Nomads_AIONLY-V1.zip

In case you want a really deep dive into all the code-side changes that were made to FAF (there are over 4,500 changes):
https://github.com/FAForever/fa/pulls?q=is%3Apr+is%3Aclosed

Update 21.Apr.2025 (v26)

• Added Annotations (MrRowey)
• Speed up functions (MrRowey)
• Fixed CreateProjectileAtMuzzle hooks by returning the projectile to parent function
• Unit bea0402 (Experimental Aerial Fortress) now has a dummy weapon to attack enemies directly below.
• Unit bea0402 (Experimental Aerial Fortress) changed UISelection from tank to air unit

@DJ_Calaco

Wait, really? I never realized that. Thanks for the heads-up, I’ll take a look!

yeah number 3 looks best.

@Aurahead

I created a desktop shortcut to C:\ProgramData\FAForever\bin\ForgedAlliance.exe and use it to start the game (I host LAN multiplayer through the in-game menu).

I replaced this ForgedAlliance.exe with an older version on all computers in the network.

In the next few days, I will test the dev and FAF exe again. Then I can tell you if the actual exe is the issue.

No, I have an i9-14900K, and it works flawlessly with SupCom, including multiplayer.
But I also use an older SupCom .exe because I experienced occasional desyncs with the newer ones, but only in AI matches.
I haven't tested the latest version, so I can't say for sure whether a desync could actually be caused by the .exe.

I wrote a small mod in 2018 to automatically adjust the LODs.
The function is located in AdvancedLOD\hook\lua\system\Blueprints.lua.
There, you can experiment with different settings to find what works best for you.
The code is documented and should clearly describe what happens in each line.

The downside is that LOD settings are specified in the blueprint and then managed by the C# engine.
This means it can only be done with a SIM mod.

If anyone is interested in experimenting with it or using it as a basis for something else, here is the code:

AdvancedLOD-v1.zip

After several hours of debugging, I was unable to fix the issue.
Even after re-enabling the weapon, it only fires when aiming southwest. In all other directions, it does not fire.

This is similar to the issue with drones: the code technically works, but the result is flawed without throwing any errors.

At this point, only Jip can help.

Well, during transport, the function SetOnTransport is executed, which checks whether a unit has CanFireFromTransport specified in its blueprint.
If not, the weapons are disabled and re-enabled upon un/loading and using the enhancementname to find the weapon (in SetWeaponEnabled).
I think the error should be found in this area or at least this is a good starting point for the search. I'll take a look.

@LeFleurBang

from now on you can also start the FAF version directly wihtout using the FAF launcher.

Just make an desktop shortcut of the file C:\ProgramData\FAForever\bin\ForgedAlliance.exe
(ProgramData is a hidden folder!)

@DJ_Calaco

thanks for reporting this.

https://github.com/Uveso/BlackOpsFAF-Unleashed/pull/27

(fixed in next version)

@maudlin27

I find the idea of allowing smurf accounts under any circumstances problematic. Smurfing has always been a contentious issue in FAF, and the platform has consistently upheld a strict no-smurfing policy, even enforcing bans against such accounts. Introducing a system that permits smurf accounts, regardless of how controlled or pre-approved it may be, risks undermining this longstanding rule.

Allowing high-rated players to create temporary accounts—even for challenges—poses significant risks to the community. It could lead to negative experiences for low-rated opponents and erode confidence in the integrity of the rating system. Furthermore, even with strict pre-approval and monitoring, the line between an approved "challenge account" and unauthorized smurfing becomes blurred, potentially opening the door for misuse.

That said, this is just my personal opinion. Whatever decision is ultimately made, I will support it. I have a rating of 0, so from a personal standpoint, it doesn't matter to me either way.

The introduction of Challenge Accounts, as currently proposed, appears unnecessary, as most goals (content creation, fostering creative challenges) can be achieved without additional accounts. The administrative and moderation effort does not justify the benefits. Optimizing existing structures provides similar advantages with less risk and effort.

It should also be noted that there have always been discussions about smurf accounts, and FAF has consistently been against such accounts, even enforcing bans. Now, for FAF to allow smurf accounts under any circumstances is problematic in my view. This could lead to anyone justifying their smurfing by claiming they intended to create value for FAF.

Even though I am sure that the Uveso-AI itself does not cause any desyncs, it is still possible that not all players have the same version or that a file is corrupted. So please also test without the Uveso-AI mod.
Please also post your game.log. The replay generates a new game.log with our game environment and files, but we need to see your files and directories.

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x0095854f

This is a memory error. The only solution is to reduce the number of (unit) mods.
https://github.com/FAForever/fa/issues/1445

The hitbox also applies to projectiles.
I encountered an issue in Black Ops where the hitbox was too small:
https://github.com/Uveso/BlackOpsFAF-ACUs/pull/7
Make the hitbox the same size for every ACU to avoid complaints. Also, ensure it's not too small; otherwise, the commander can only be hit with area damage.

Oh, and when you're in the game, press [F1] to open the key bindings. Under the 'Debug' section, you can see all functions and their assigned keys.