Newbie here, help guys!

[JACN]

Hi all,

 

This is the first time I face the new DCS product since the (AWESOME) LockOn & Flaming Cliffs.

 

A few days ago I got my BS (spanish) "boxed" copy...but after seeing the patch announcement, I decided to wait just a little bit more...(:cry:)...for installing the "patched" BlackShark.

 

For the moment, I have a couple of questions. Surely later the number will grow, but don´t worry, I´ll try the "search" button as first option ;)

 

My questions:

 

1) Is the released patch (ENG) compatible with my spanish version?. I think the answer is "no"...but, sorry...I can hardly wait!

 

2) Is BS with the new patch multi-core compatible?

 

Thanks in advance

 

Álvaro

Edited August 11, 2009 by JACN

[STP Dragon]

1. No

2. yes (see readme)

[JACN]

Thanks for the concise answers. :) But if 2=yes what about the "dcsmax"? (to be true I have no idea what does it do but, for what I´ve seen, it seems to be some kind of multi-core affinity tool)

 

Álvaro

[Nate--IRL--]

DcsMax's function to change processor affinity is no longer needed. I still use it to load missions though.

 

Nate

[JACN]

Ok, thanks guys!

 

Álvaro

[STP Dragon]

DcsMax's function to change processor affinity is no longer needed. I still use it to load missions though.

 

Nate

 

I know this.... but what will happen if you use the processor-thing of DcsMax anymore?

[Nate--IRL--]

I know this.... but what will happen if you use the processor-thing of DcsMax anymore?

 

Nothing. BS does it automatically now.

 

Nate

[Panzertard]

I know this.... but what will happen if you use the processor-thing of DcsMax anymore?

 

Yesterday as we tested online on our server, and sharing the experience over Teamspeak we learned the following:

- Initially some people got very good FPS, others not. (Due to the patch settings Affinity to All cores).

- Some folks improved their FPS by manually adjusting affinity from 4 (all) to 2 cores.

 

It may look like that some systems runs a bit better if you let the system to be able to "breath" a bit. :)

Altough we didnt see any trends (Lo-End vs Hi-End systems or ATI vs Nvidia) ....

[JACN]

- Some folks improved their FPS by manually adjusting affinity from 4 (all) to 2 cores.

 

Manually?...using OS tasks administrator or with DCSMax?

 

Please, tell me DCS BS multi-core support is better than M$ FSX...:doh:

 

Álvaro

[Panzertard]

Manually?...using OS tasks administrator or with DCSMax?

 

Please, tell me DCS BS multi-core support is better than M$ FSX...:doh:

 

Álvaro

 

Affinity-testing was performed manually with the Taskmanager.

 

DCSmax and loading of the "default / favorite skin" caused some other issues for one or two of the players. (Crash / noncrash + performance issues).

Staying away from DCSmax resolved that issue.

[JACN]

Ok, but does it mean after the patch I´ll still need to manually set affinity every time I launch BS? :(

 

Álvaro

[Panzertard]

Ok, but does it mean after the patch I´ll still need to manually set affinity every time I launch BS? :(

 

Álvaro

 

No? Why? It's automaticly set to all cores by DCS.exe - should be working good enough for you. :)

[sweinhart3]

If I understand it right DCS is not really threaded for multi core use. The affinity setting simply moves other OS related tasks to the other cores. Am I correct with this understanding?

[STP Dragon]

V 1.0.1.(a) supports mulit core use. V 1.0 not.

[Feuerfalke]

If I understand it right DCS is not really threaded for multi core use. The affinity setting simply moves other OS related tasks to the other cores. Am I correct with this understanding?

 

It's not that simple and no, DCS doesn't control OS-related tasks.

 

A multithreading software can spread up different tasks for different CPUs. In much simplified terms: Core 1:AI, Core 2:physics, Core3: FM, etc. DCS cannot do that.

DCS can benefit from multiple cores, though, as modern OS like Vista/Win7 is able to spread a single thread over different CPUs and it automatically assigns own tasks to cores with less workload. That is, if the program allows it - and 1.0 did not.

 

With 1.0.1 or using the affinity methods for 1.0 and e.g. running TrackIR, Teamspeak, ... together with DCS, workload is shared among the available CPUs. Of course this takes some organization, so depending on programs running, OS and config, you can also watch that you only benefit from multiple CPUs until a certain degree and thereafter in the worst case even lose performance. As Panzertard and Dragon2781 posted, the only way to be sure if you are effected is to test it. My DCS runs a faster on 4 cores than on 2, for example.

 

So, the difference between 1.0.1 and 1.0 is simply, that 1.0 did not natively allow the thread to be calculated on more than one core and 1.0.1 does.