scommander2

I guess that more users on the server will generate the kind of the load to slow down but also affect to the user sides (FPS)?!

I am used to report the filename (false-positive) that gets captured by AV, and its signatures back to the AV vender so that the AV vender will add the filename into a whitelist to avoid for the next AV database up. However, I can only do my AV vendor only.

Cool, good to know... Thanks!!

Similar one?

It is not a preventable, and it is not practice. Put the file into the exception list and move forward since it is a false-positive report.

No offensive: how can the code get compiled with the binary code contains the identical signature in the AV database? If yes, should the code to be written again?

Is the file ""F14-HeatblurCommon.dll" still under ..../F-14/bin folder after the fresh installation?

The repair had performed?

My win 11 does the core parking enabled, so I had disabled it. And, I did not find the warning message of the core parking in your dcs.log. Is it okay so far?

How about the following thread?

What happened if without PL: 2025-03-15 02:26:09.324 WARNING APP (Main): ProcessLasso is running And, manually set process affinity by using Task Manager->Details (looking dcs.exe), right mouse button click for "set affinity" for selecting all P-Cores (0, 1, 6, 9, 7, 8, 18, 19). A good sign is that no CPU core parking is shown in dcs.log

For 265K, P-Cores are not sequential likes 12/13/14th gen by checking the 200s "Compute tile Floorplan". The following is not sure: 2025-03-15 02:26:06.669 INFO EDCORE (Main): common cores: {7, 8, 18, 19} 2025-03-15 02:26:06.669 INFO EDCORE (Main): render cores: {1, 9, 0, 6} 2025-03-15 02:26:06.669 INFO EDCORE (Main): IO cores: {2, 3, 4, 5, 10, 11, 12, 13, 14, 15, 16, 17} according to dcs.log. All P-Cores are used in either common/render cores...

Please check the following thread:

I will say that the file "F14-HeatblurCommon.dll" was compiled with the code contains the identical signature in the antivirus/defender virus/trojan database. Maybe "F14-HeatblurCommon.dll" will be updated/compiled in the future contains no antivirus/defender "possible" signature. I think that it is the exclusive rule about because the antivirus venders can't guarantee the files get catched are 100% virus/trojan for sure, and it is relied on the user to determine the file is false-positive or positive-positive. Not offensive: It is very impossible to re-code/re-compile the file to meet all antivirus requirements, and it is not practice.

Should Windows defender do the same exclusive rule:

Cool, thanks.

- [ADDED]F-14A/B Afteburner Effect Desync {https://forum.dcs.world/topic/356998-bug-f-14ab-afteburner-effect-desync/} added the known issue into the fix section.

@draconus and @WarthogOsl, thanks and it is the known issue.

Hi, I guess that it may be related to the artwork from the F2 view for the F-14 right engine for afterburner.

Yup, Avast did complain that dll file and I have to put it in the exception list

It is interesting now because I also use Avast, and When Avast is running then defender is turned off. Let me run Avast with targeting on the DCS world directory. PS: I do have F-14.

Is it possible to exclude "E:\DCS world" from AV or defender then repair it again?

Hi @Special K, thanks for the explanation. Another dumb question: should I assign P-Cores with dcs.exe by using the process affinity so that render/common cores will land on P-cores (hope)? There is my dcs.log: dcs.log

A quick question about core parking disabling on Windows 11: does it mean dcs.exe run on P and E cores with no restriction for the render cores (or, okay with the common cores. My understanding the IO cores should be in E-cores)? Thanks.

Hi @Aapje, thanks. How about 9950X3D? Is it too new to tell?