Vista and Multi-core/Multi-CPUs, Continued

[dragonhammer]

Tip for the people that have an quadcore en 64bit vista,you guys don't have to jump thru all the hoops to get 4 cores running it does that by default for all processes.

[DragonRR]

Tip for the people that have an quadcore en 64bit vista,you guys don't have to jump thru all the hoops to get 4 cores running it does that by default for all processes.

 

Blackshark's default setting is ONE core only!

[dragonhammer]

if you check the affinity of the process you can see 4 cores enabled and working all 4

[DragonRR]

if you check the affinity of the process you can see 4 cores enabled and working all 4

 

I have no idea why you get this. Are you sure you are looking at the correct process "dcs.exe"? The fact that it doesn't, by default, allow for multicore is "known". I have Blackshark installed on two different 64bit Vista machines (Russian and English) and neither machine, by default, have affinity set to more than core 0.

[dragonhammer]

I am at work right now but will look into to check if i am looking at the right process, i shall post screenshots to confirm.

[DarkWanderer]

This may have been fixed in english version, among other minor (not patch worthy) changes.

[Mxyzpylk]

Tip for the people that have an quadcore en 64bit vista,you guys don't have to jump thru all the hoops to get 4 cores running it does that by default for all processes.

 

I have a quad core AMD Phenom 9950 and It is only set to 1 core on my Vista Ultimate x64 system also.

[LIONPRIDE]

hmmmm

 

Almost right. Try to get two physical processors running with Home or Basic, it's not going to happen. For instance I have 2 processors in my system and I need Ultimate (or business).

 

 

I have the VISTA HOME version ... so this won't work for me anyhow?

 

-----------EDIT--------------

Tried it ... it "runs" with no hassles but there's not a noticeable difference in frame-rate improvement. As a matter of fact, this 'fix' disables my TrackIR when it's used. ... interesting ....

 

-----------------------------

 

 

.

Edited December 18, 2008 by LIONPRIDE

[Guest]

I have the VISTA HOME version ... so this won't work for me anyhow?.

 

This will work for you. Vista home supports only one PHYSICAL processor, but an unlimited number of cores on that processor. So, dual-core, quad-core etc all work fine in Vista Home.

 

In the unlikely event that you actually have two physical processors in your system, which is fairly rare, then Vista Business or Ultimate edition is required to take advantage of the second physical processor.

 

-----------EDIT--------------

Tried it ... it "runs" with no hassles but there's not a noticeable difference in frame-rate improvement. As a matter of fact, this 'fix' disables my TrackIR when it's used. ... interesting ....

 

-----------------------------

 

First, how long did you give it to work? The fix will generally not kick in until about 30 seconds or so AFTER starting a mission. Second, do you have vsync enabled? If you do, then the FPS will never exceed the refresh rate of your monitor, and you will not be able to see a framerate improvement until you get into a heavy mission.

 

Finally, I can guarantee that it did not disable your TrackIR. The script has no relationship with TrackIR whatsoever. My guess is that you may have forgotten to load the TrackIR driver before starting.

Edited December 18, 2008 by wombat778

[Prophet]

The TIR software is finicky with BS it seems.

 

Sometimes I have to restart the TIR software. Sometimes the pause and reset key dont work, and I have to reset direct input from the TIR software...

[DragonRR]

Yes unfortunately TIR is disabled (well actually it hangs) when I use Wombat's script. I haven't got time to fully test this atm but I might try releasing 1 or 2 of the 4 cores on my system and see if that makes a difference. I'm pretty sure I've had TIR running with 4 cores on DCS.exe by setting it manually.. but I'm not absolutely certain.

 

I didn't notice this yesterday (when I first tried the script) because I wasn't using TIR.

 

Oh I should point out that whilst I don't always play the game with TIR running I've used it several times and this is the first time it hasn't worked/hung.

 

EDIT: I've just tried it again with Wombat's script and it worked fine.

Edited December 18, 2008 by DragonRR

[Guest]

I would be quite surprised if the script itself is causing TrackIR problems, because it really doesn't do anything other than set the affinity. I suppose it is possible that TrackIR does not like it when Black Shark is set to multiple cores. However, I always use a TrackIR and it always works fine for me when using the script.. Interested to hear if others are having the same experience.

Edited December 18, 2008 by wombat778

[xell]

No. Running Vista 32 with your script and TIR. No problem at all.

 

Running as i would expect!

[DragonRR]

Well I've tried it 6 times now and only on the first go did TIR fail with a hang. I think it MIGHT have been because I had the head tracking window open as I ran BS. Normally this hasn't been an issue, TIR detects BS and auto closes any track windows but maybe it struggled this time.. :book:

[Purg]

if you check the affinity of the process you can see 4 cores enabled and working all 4

 

If that's the case then you don't need to do anything...?

 

I use AffinityII and occassionally when I check it, it has all 4 cores highlighted on that process but my CPU meter is clearly showing only core 0 is being utilised. If I just click apply, whammo.

[dragonhammer]

I stand corrected its the dcs launcher that runs on 4 cores default but when you start a mission it spawns the dcs.exe wich runs on one core.

Looks like i too have to jumps thru all the hoops to get them working.

But i can say its definitely worth doing since it practically doubles my framerate.

[Guest]

I use AffinityII and occassionally when I check it, it has all 4 cores highlighted on that process but my CPU meter is clearly showing only core 0 is being utilised. If I just click apply, whammo.

 

Yep. This is exactly the behavior that I saw with SetAffinity II. I am almost certain it is related to SetAffinity II trying to set the affinity too soon after DCS.exe is launched.

 

The script I wrote is specifically designed to avoid that problem by waiting for 30 seconds before setting the affinity.

[LIONPRIDE]

Yep. This is exactly the behavior that I saw with SetAffinity II. I am almost certain it is related to SetAffinity II trying to set the affinity too soon after DCS.exe is launched.

 

The script I wrote is specifically designed to avoid that problem by waiting for 30 seconds before setting the affinity.

 

 

.

 

Hey Wombat ... I've been looking around and can't find your original scripts. You have the link? THanx

 

,

[Guest]

.

 

Hey Wombat ... I've been looking around and can't find your original scripts. You have the link? THanx

 

,

 

 

Actually, the ones that Prophet posted are basically identical to my originals, but with a tweak to load Black Shark as well. In short, they are better than the originals, and I suggest you use them

 

But if you really want the my originals, they are attached here: http://forums.eagle.ru/showpost.php?p=590101&postcount=189

 

Note that my original version does not actually load Black Shark. You have to run the script, then load Black Shark manually.

[LIONPRIDE]

Actually, the ones that Prophet posted are basically identical to my originals, but with a tweak to load Black Shark as well. In short, they are better than the originals, and I suggest you use them

 

But if you really want the my originals, they are attached here: http://forums.eagle.ru/showpost.php?p=590101&postcount=189

 

Note that my original version does not actually load Black Shark. You have to run the script, then load Black Shark manually.

 

Well, with the Vert-Sync turned off and the script running I get a jump of about 8-10 frames ... Woo Hoo ! For some reason wiht the script and vert-sync off it really helped.

 

... problem is, My TrackIR still gets disabled when I run the script. So ... in the end, I either loose the 10-frame-rates and get to use my TrackIR or not use it and gain about 10. What to do ... *sigh*

 

.

[Guest]

... problem is, My TrackIR still gets disabled when I run the script. So ... in the end, I either loose the 10-frame-rates and get to use my TrackIR or not use it and gain about 10. What to do ... *sigh*

 

Very weird. I am not sure why it would do that. Does the TrackIR work when you manually set the affinity of dcs.exe using the task manager? Another thing you might try just for troubleshooting purposes is to tick the "Exclusive-load" box in the TrackIR software for your TIR profile. Its just an idea, but it might be worth trying...

[Shrubbo]

Thanks for the scripts and info guys, unlike set affinity II this seems to work every time. SAII I sometimes had to tab out and just look at it to get both cores going (wtf). This just works with no extra crud in my task bar. :thumbup:

 

BTW TrackIr 4 here and no problems what so ever, thanks again.

[Shrubbo]

*EDIT: I did post that I had a problem but the problem is me, see 2 down :)

Edited December 19, 2008 by Shrubbo

[LIONPRIDE]

hmmmm

 

 

BTW TrackIr 4 here and no problems what so ever, thanks again.

 

 

...can't imagine what's doing it on my end? Is the 'profile' that I have selected? Right now I have it set to [flight] because that's what BS is set under. Should I, maybe, put it to default or something? Maybe something with the 'Run as Administrator' settings or something? Baffled to say the least.

 

.

[Shrubbo]

Nah its all good, It's a PEBKAC problem here (Problem exists between keyboard and chair for those that don't know). I would rather shut up about it and slink off but hey I already posted a negative in a good thread so I best speak up.

 

The scripts works perfectly for me with trackir running faultlessly now. The problem that I had was that the trackir sensor had dipped down slightly and could no longer see the third reflector. Only sometime thus the intermittent problem. It wasn't until I used the trackir view tools and looked at what it see that I decided I should turn the light on and look at the trackir sensor.

 

So once again thank you very much guys, this has fixed a pain in the ass.