Cobalt DLL falsely flagged workaround (Repost)

[kenzdev1337]

(Summary of the Discord thread about the same suggestion)

While compiling myself the Cobalt DLL, I noticed that my antivirus didn't detected the file as a virus because I compiled it in debug mode.
As soon I compiled the DLL in release mode, the antivirus started to flag the file as a virus.
Then, I decided to do a VirusTotal scan on the debug build to see if this occurred only on my computer, and the file was flagged by only 4 vendors compared to the release build flagged by 51 vendors

VirusTotal links:

• Release
• Debug

However, building as debug causes the code to be slower than building as release.
So to try to optimize to the maximum the code, I tweaked some build settings

Changes :

• C++ -> General -> Debug Information Format: Program database for Edit and Continue => Program database

• C++ -> Optimizations:

  • Optimization: Maximum Optimization (Favor Speed)
  • Inline function expansion: Any suitable
  • Enable intrinsic functions: Yes
  • Favor size or speed: Fast code
  • Omit frame pointers: Yes
  • Enable fiber-safe optimizations: Yes
  • Whole program optimization: Yes

• C++ -> Code Geneartion -> Basic runtime checks: Both => Default

After compiling with these optimizations, the Cobalt DLL is flagged by around the same number than the debug build without optimizations on VirusTotal

Could this workaround be implemented in future versions of the launcher? Thanks in advance

Screenshots:

• Release build scan
  

• Debug build scan
  

• Debug build with optimizations scan (scanned name changed for a reason)
  UPDATE: Someone scanned this file by themselves and flagged it as a malware (obviously it isn't, I will try to contact them about this)
  

[zeroaltud]

doesnt even build on debug XD

[jgc777]

doesnt even build on debug XD

tf are you saying. This guy actually did a good research