All,

I have put together a collection of tips and tricks for TrackIR that people may find useful. My TrackIR 5 is running beautifully smooth with WOFF PE. Hopefully this will help some folks.

Happy Flying!

Updated Version 1.1 TrackIR Setup Guide

NOTE: updated to version 1.1 Includes important information about Priority Settings and I/O Priority Settings see text in bold


My current TrackIR profile is here: https://drive.google.com/open?id=1Z-Nun-XznfbtyHBZxqr3JGnGOsGwIWkE

Thanks HarryH!
Made this a sticky.

Thanks HarryH. I had forgotten about changing CPU affinity for TIR. I downloaded this and will be referencing it. I have purchased Process Lasso a few years back and have used it, but honestly I can't say if I have ever noted a big performance increase. Both WOFF & WOTR has always performed well for me. The latest WOFF PE is giving me trouble when I enter a dogfight though and i have bad stutters with still goo FPS (49+ up to 60). So I will be experimenting to see what gives. Thanks again.

S!Blade<><

Not just affinity, but also the priority setting can make a big improvement. Hope it helps!

Thanks for all the research and info.

You are welcome, Lucky Shot. Happy flying!

Thank you, Sir! Very appreciated

Good info Harry... many thanks!

Hi folks;

The following refers to Windows 7:

I noticed a few here using third party apps to set priority and affinity so I thought I would identify another method that can achieve the same without using third party apps.

1 Make a copy of your shortcut for TrackIR. Find the shortcut icon for the program you want to set priority and affinity for, right-click, and select Properties. Navigate to the Shortcut tab.

2 In the target field, you will need to append a string before the current target path. Replace the text "Program Name" with the name of your program:
C:\Windows\System32\cmd.exe /C START "Program Name" /high /affinity 4

In my case, I am using TrackIR5. The line I am appending would read as follows:
C:\Windows\System32\cmd.exe /C START "TrackIR5" /high /affinity 4

Proviso as reported by user "epower" for windows 10:
1) in the TrackIR5 properties make sure the 'Run as Administrator' box is ticked.
2) also In the TrackIR shortcut properties, under Advanced, tick the 'Run as Administrator' box

I have an I7-4770 processor which has 4 CPU's (quad core). so:
Where you see affinity 4 is the core to run the program on which i my case is CPU 2. The cores actually do start on their numbered value but the numbers are in hex. See the following for a listing of the core values:

CPU 0 (Core 1) is 1
CPU 1 (Core 2) is 2
CPU 2 (Core 3) is 4
CPU 3 (Core 4) is 8
and if you have these:
CPU 4 (Core 5) is 10
CPU 5 (Core 6) is 20

We can also set the priority to low, normal, high where we have selected high in our example:

3 Once you have this string constructed, paste it to the beginning of the target path right before the path to the ".exe". My entire target string looks like this:
C:\Windows\System32\cmd.exe /C START "TrackIR5" /high /affinity 4 "C:\Program Files (x86\NaturalPoint\TrackIR5\TrackIR5.exe"

4 Once you have put in your string, click Apply on the Properties window. If asked for Admin permission, simply click Continue, and then hit OK.

Now lauch TrackIR from your new shortcut.
Do a CTRL+ALT+Del keystroke to launch "Task Manager".
Go to the "Processes" tab and look down the list for your TrackIR program name.
Once you find it, right mouse click on it and look for the "set Priority" and the "Set Affinity" .
place your mouse pointer of the "Set Priority" and note if it reflects the setting you placed in your TrackIR shortcut.
Right click your mouse on the "Set Affinity" selection and note if affinity is set you your desire choice.

If all of the above is done correctly, TrackIR will always start with the Priority and Affinity you chose, automatically from now on.
[
Hope that helps.

Best Regards

Robert, thanks for the additional info!

Is it also possible to set the priority to "realtime" using this method? I've found that works best, at least for me (noticeably better than high). Lasso can set priority to realtime, but warns that Windows may switch it down to high, so I end up having to check after each reboot what it is set to.... would be nice to set and forget

HarryH;

Yes you can. I tried it on my end but saw no perceptive difference. That said it might be beneficial to you so go ahead.

Best Regards

Setting anything to real-time priority is a really bad idea. In a word, "foolish" (his word, not mine):

https://devblogs.microsoft.com/oldnewthing/20100610-00/?p=13753

And then there's this:

"You should almost never use REALTIME_PRIORITY_CLASS, because this interrupts system threads that manage mouse input, keyboard input, and background disk flushing. This class can be appropriate for applications that "talk" directly to hardware or that perform brief tasks that should have limited interruptions."

from https://docs.microsoft.com/en-us/windows/win32/procthread/scheduling-priorities?redirectedfrom=MSDN

TrackIR is constantly gathering control input from the camera, and is completely opposite "performs brief tasks".

Of course, I'm sure people trying to get a game running better on their computers by trial and error know better than this guy...probably at least one video on YouTube that says this is a good idea.

Thanks, Robert, I'll give it a try.

Harry

Kknowsbear raised some valuable points on this so be cautious and reconsider not using real time priority

OK then. Thanks both of you for the warnings, but I've been running the TrackIR.exe for several days now on cores 1-5 with real time priority, with the game running on core 0 at normal priority. I'm not experiencing any negative issues whatsoever. My input devices are all responding perfectly. I'll engage in what I hope will be a constructive deeper exploration of this. I'll set up a new thread where yourself, KKSnowbear and anyone else who's interested can discuss it. I'd like to know the downsides, if there any, along with the real-world dangers to one's PC system, if any, so that I can advise people accordingly in my TrackIR tutorial.

Kknowsbear;

I don't think anyone believes TrackIR is the solution to stutters, we are just looking to TrackIR performance response enhancements.
Let's not mix the two together please. Your cautions were worth noting and advice acknowledged.

Best Regards

I assume I'm "the user" in question. I have blocked kksnowbear. I am tired of his arrogance and I refuse to read any more of his snarky, unhelpful comments.

I don't believe there is a "one size fits all" solution to the stutters either. Each machine is different and there are multiple factors in play. My machine is stutter free at this point but I readily admit this may not still be the case when our campaign advances into 1917 / 1918. I've tried a few QCs in 1918 but it's not the same stress test as campaign mode.

I've amended my TrackIR setup guide to include a warning about Realtime mode. I'm still using it and it's working perfectly well with no negative effects whatsoever. Joystick response is fine, SSD isn't chugging. TrackIR and WOFF are running on completely separate cores. I do agree with kksnowbear's previous comments about consistent frame rates and I have preached the virtues of G-SYNC running at 1/2 refresh rate to deliver a rock solid 72FPS for some months now. That's definitely been a big part of taming the stutters for me.

As for credentials, kksnowbear thinks he's the world's gaming PC expert. I built my own rig and I just completed a PC build for a video editor (msi x299 gaming pro carbon ac with i9 LGA 2066, 64GB DDR 3200 mem and Nvidia RTx2800), so yes, I know what I'm doing for the most part. I just don't brag about it.

I can't believe how amazing WOFF PE is, all things considered. I also can't quite believe how much better it's running for me than UE was this time last year, but I have worked pretty hard at it and I've spent some $$ on hardware. I've shared my discoveries and I've benefited from the knowledge of others in this community (Panama Red, yourself, Buckeye Bob, Ankor and many more). Onwards and upwards, minus the bear

Harry;

For my benefit, would you kindly explain what your personal system consists of. Since you seem to have so far, put the stutters to bed, I would like to compare it against mine as a base starting point. Following this I will probably try your solution.

Best Regards

HarryH I agree with all you said, I have had that person blocked for quite some time for all the same reasons.

I thought your Idea was worth a shot, to bad it did not work out for me, really glad it is working for you.

Please keep'em coming - you never know what might turn out to work.

Regards,

MSI Z370-A PRO mobo

Intel i5-8600K @ 3.6GHz

Corsair Vengeance LPX 16GB (2x8GB) DDR4 2666MHz

Samsung SSD 860 QVO 1TB

Nvidia GTX 1070 8GB GDDR5

Dell S2716DG monitor @2176 x 1224, 144Hz rr (WOFF looks gorgeous at this resolution. Videos don't do it justice).



Not exactly top of the line. There's more to all this than horsepower, although raw power doesn't hurt I suspect I think it's about balancing every aspect of the system in an optimal way. That includes WOFF workshop settings.

I'm happy to discuss more of this with you via PMs. Frankly, I'm tired of trying to help people publicly and constantly having my threads hijacked. Too bad really.

Since this is now the stickied Track-IR thread, I know I would find it useful if people could post some good profiles or links to them and maybe HarryH would be kind enough to edit them into a section in the first post. I am always looking for a better profile!

Sure, no problem. I'll put my current profile up there to kick things off...

Hi Harry,

Hope you are doing well in the New Year! I haven't had much time to chime in on the boards lately - RL is as busy as ever and it seems my flying time was scant over the last six months. I wanted to post, however, to thank you for all of your efforts in smoothing out WOFF. I tried applying your settings for TrackIR, as well as your workshop settings in WOFF:PE. Our system specs are pretty similar except for video cards and monitors, which you are leading on

Dropping the roll rates down to 0 in TrackIR seems to help, but for me, and I think this is the case since we are running nearly identical processors, is getting TrackIR off of Core 0. Once it's not fighting with CFS3, the head panning works much better. I'm not seeing a huge difference between Realtime processing or leaving it be, but moving it away from competing cores is huge - at least with this chip set. The other change that's had a massive impact are your workshop settings. I copied them verbatim and I notice a MASSIVE improvement in the sim's smoothness. I am no longer getting any hangups looking around in sim. Pausing the sim on startup and then panning around a few times with the exterior camera loads everything up nicely and from there, it's been smooth sailing, even in 1918 with medium air activity.

I think the biggest difference between your approach and what I've tried is that you are willing to drop the graphics back further than you think they need to go. That leaves a bit of a buffer so that when the sim gets busy there's enough slack left in the engine and the computer's hardware to keep things going smoothly.

Can't thank you enough. I'm also doubly impressed that you managed this with no mods, no editors, and no outside help. This is an extremely solid baseline, especially if you are running in the 3.6ghz range of processors.

Cheers Harry!

Excellent! You are most welcome, and it's great to get the feedback that this stuff has helped you. Props to RAF Louvert who originally tipped me off the the CPU 0 thing.

Yes the detail settings are a useful dial to help balance performance. The other one is air activity. I'm very glad you've taken the time to experiment and find some improvements for yourself.

Cheers!

HarryH,

Thanks for all your work here and for the awesome TrackIR Guide.

I have a 4 core i5-6600K and wanted to run TrackIR on cores 3 & 4 but couldn't make it work.
I was having some difficulty understanding the whole core and hexidecimal number thing for the Core affinity shortcut you describe above until I stumbled on this site. Perhaps it will be useful to others.

https://www.eightforums.com/threads/cpu-affinity-shortcut-for-a-program-create-in-windows.40339/

What helped me get the info through my thick skull was the visual below: (apologies for the absurdly large graphics)



Just below on the same web page is a link to a Binary/Decimal/Hexidecimal converter. I've put my config in the graphic, which spat back the Hex number 'C'




I also experimented with running TrackIR on Cores 4,3,2. Entering "1110" gave the Hex number "E"

Best Regards,

epower

Thanks, epower! I hope it's helping you run WOFF with TrackIR better. Thanks for the info.

In a moment of unimaginable genius I unpinned my modified TrackIR shortcut from the taskbar.

Following Robert Wiggins' excellent instructions on page 2 of this thread, I could get the Priority to stick but not CPU affinity.

Running as administrator solved the problem. Under advanced in the Shortcut properties.

Hi Robert, and everyone: I am trying to get my TrackIR shortcut to set "priority" and "affinity" as Robert Wiggins explained in his post at the bottom of the first page. I have changed the target string to ...

C:\Windows\System32\cmd.exe /C START "TrackIR5" /high /affinity 4 "C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe"

TrackIR starts fine ... so far so good. When I go into Task Manager and check the details on my TrackIR.exe, the priority is set to 'High" (as expected, great!). But when I enter the 'set affinity' menu it shows all 10 cores checked off. I tried it with affinity 4, affinity 04 (zero-four, hexidecimal for cpu core 2), and affinity 38 (hexidecimal for cores 4+5+6). Same result.

Any suggestions as to what I might be doing wrong?

Cheers!

Edit: Just saw epowers post above, so I set the shortcut to 'run as administrator" in the advanced settings. Still no luck.

Scout,

Check out my post from 6 April above and the binary to Hexadecimal converter linked there.
If you have a 10 cores and want to put TrackIR on cores 4,5 & 6 your binary number is 0001110000 which converts to a hexadecimal value of 70.

Hello,

First thing to consider is that, almost always, computer stuff starts counting things at zero, not one. Zero is a number, it has value. In computers, having 'nothing' and having 'zero' is not the same thing. This is why 77_Scout comes up with 38h instead of 70h - there's a place being dropped.

Also, Windows has a calculator built in (you probably know already), but it does hex, binary, and other numbering systems...the diagram below shows how it works:

Calc menu View > Programmer
Radio button group middle left > Bin
Input the number you want converted, starting at zero (R>L) for first core (in this case 1110000)
Radio button middle left > Hex (number displayed is changed to hex; in this case 70)

Hope this helps.

Thanks, KK. Didn't know that about the Windows calculator.

Glad if it helps. There are also other options, including a Data Conversion mode that I use a lot (standard>metric, Fahrenheit>Celsius, etc). Fairly handy. The Scientific view has trig functions, log, etc.

Hopefully the attached screenshot will show how I got hex 38 for the cpu affinity setting.

Regardless, I have tried several different numbers, including Roberts very simple example of '4', and it seems to have no effect.

Yes - in that example, it is Core 3,4,5 (as opposed to 4,5,6). 3,4,5 = hex 38, which is what you entered in that calculator (as shown in your screen shot).

However, in the post above, you actually wrote "hexidecimal for cores 4+5+6", and that's why epower (and I) read and converted it to 70h. That's why I made the point about starting at zero, not one. If you drop a place at the Least Significant Digit (specifying cores 3,4,5 instead of 4,5,6) then what should be 70 winds up being 38.

I think what you meant is the "fourth, fifth, and sixth" cores - which is actually cores 3,4,5 and isn't the same thing as saying "Core 4+5+6" (which, of course, would be the fifth, sixth, and seventh cores). Not trying to nitpick, but In this case, it matters, because...well, because getting this detail wrong means you get 38 not 70

I hope I'm explaining this OK.

As to why it's not working otherwise, I couldn't comment. I've never found it necessary to change the Windows priority for TrackIR (certainly not as a means to correct stutter in WOFF). Just saw this about the hex/bin conversion, and thought I'd pitch in.

Thanks! Yes, I was a bit off with my counting/labeling.

I have noticed that the affinity menu in my Task Manager shows 12 processors (0 thru 11). My cpu only has 6 cores, but 12 threads, so I guess these are actually threads shown. Perhaps that affects how the affinity value must be entered in the TrackIR target string?

The 12 represents the number of what are called logical cores (as opposed to the 6 physical cores you have). Yes, as you said, this is about threads (which, logically, is how your machine 'sees' the CPU) vs physical parts of the actual silicon die (chip) in your CPU.

They have to be considered separately because they can operate on 12 distinct operations simultaneously (or effectively near so, the the external user anyhow), which is the benefit of having more threads than cores.

TBH, I don't see a reason why 3/4/5 would work any differently than 4/5/6 (assuming you weren't explicitly trying to avoid a certain core, and assuming that specifying multiple cores for TrackIR isn't problematic - this I don't know. You did say you tried just 4, so not sure there).

Maybe try just using 0 or 1 - just as a test - I assume all you're checking is that the affinity is being reassigned as per Robert's instructions, and not whether there's a difference in the game. Is this correct? If you can get past this basic test/the command line issue, then you can re-assign as you wish as a next step.

I would also say that the command line can be very simple but it can also be very unforgiving. If there's a mistake anywhere, be it typo, a space where it shouldn't be, a number in the wrong format, a path specified wrong...all these 'syntax errors' will usually result in the command failing, but sometimes it will tell you and sometimes not (depends on the details of what part is wrong, I won't bore you with that now). I can say that every time I had trouble getting a command line to work is because I had something wrong in the way I was putting the command in.

OK, I tried using 01 as a simple test (good suggestion) and no luck.

Yep, I am looking at the 'processor affinity' check list in Task Manager to see if it changes, and all processors remain checked off no matter what I do. I am not doing any testing in-game (i.e. in WOFF) so far.

Epower says that my target string matches his exactly (except for hex C, which I also have tried now) so if I have a typo in there it is well hidden.

Thanks for all the ideas and feedback! I may have to just give up on it. TrackIR works fine 'as is' so no worries.

77_Scout;

I just noticed your post and I realize there are a multitude of threads on this topic here. I am wondering if you read my recommendations here and whether you tried it.
Here is a link to my post setting afinity permanent for an app

Hiya Robert...not at all to speak for others, but yes, that's the post he's saying he referred to, but hasn't had any luck getting it to work. TBH I haven't used it and therefore couldn't say what the problem is - maybe you can review his post earlier, and comment further. I did look over what you wrote, and what he says he's tried - they appear to be the same thing, so I'm at a loss for why it's not working for him if it works for you.

My input here is pretty much limited to how the cores are numbered, and thus how the hex-coded numbers should be specified in Windows. (Core1 is not the first core; that would be Core0 etc.) Well, that and the nifty features that few seem to know about with Windows' Calculator

KK, thanks for the reply.

Scout, are you running windows 7 or 10?

Hi Robert: It's a fresh install of Windows 10.

Scout, I don't have much experience with W10 but I will do some research to see if I can narrow down the problem.
I know it works fine on W7.

Regards

Hello Robert, I did look back over your post, but it doesn't distinguish between W10 and W7 (unless I missed it)...if you're not sure, would it be worth mentioning in your instructions that it's tested in W7, but not 10? Just a thought.

Like I said, I haven't done it so I can't really comment on how it works.

From what I have been able to decipher, the process I outlined fow W7 is the same for W10 but you must ensure you are logged on to your PC with a userid that has administrator priviledges. Maybe this last point is your problem

I guess my point was, if you hadn't specifically tested it and thus don't know for sure, maybe it would be a good idea to add that to the instructions

Again, just a thought.

Hi Kk

Oh I have tested and use it on W7 successfully. At the time I posted my insteuctions I had not given any thought to W10.
To your point. I will update my post to reflect this.

Regards

Right, yes I understood that you had already used/tested it in W7, sorry if that wasnt clear. I was referring to having tested it in W10.

I would wait to see if other users with Win10 have the same issue as me. If it works in Win7 you would think it would work in Win10 ... I might just be an outlier or be screwing something up.

Cheers!

p.s. Robert: Can you confirm that when in Task Manager at the TrackIR affinity menu you see only the selected processors checked. This is what I expect to see, but all my processors (0 thru 11) have checkmarks.

I'm running windows 10 and it works for me, but my i5-6600K doesn't to my knowledge hyperthread.

The eightforums page I linked in the original post had a long discussion about the process as well as a number of posts from folks trying to do the same thing.
LINK

Cheers,

epower, could you elaborate upon 'it works', please? For example, are you saying you are using the command line method, and when you use Task Manager to check, TrackIR shows both priority and affinity have changed accordingly? As an aside, can you change it at will? Meaning, if you change command line for either/both affinity and priority, does what is shown in Task Manager 'follow' each change?

As a test, I'm trying it on my machine (Win 8.1 - no laughing, it's for a reason )...and (for TrackIR) neither priority nor affinity change, regardless of settings in the command line. And I know the command line is entered correctly, because (as a test) I went to another app's shortcut on my desktop, using the exact same command line and it works - the priority and affinity both change per the command line. So, it does seem confirmed Robert's command line instructions will work, but not *always* on all machines - and it looks like it's not necessarily about which OS you're running, either (and not a problem with the command line or instructions).

I've been doing a little research over the past couple days when I had a minute (not much TBH) and I read about quite a few cases where it appears others had problems getting this to work as well. I even read somewhere that the individual program (in this case, TrackIR) can have/has control over it, and (?) possibly even forces it at runtime, in spite of what you specify from the command line. Several instances of people using the exact method, but couldn't get it to work. So I wonder if it comes down to the application - in this case, the TrackIR software - maybe even which version(?).

For reference, I'm using 5.4.2.27545 (version number reported in Task Manager...in Control Panel/Programs/AddRemove, it says 5.4.2.0000, and on the NaturalPoint website, it just says "5.4.2" both of which are obviously misleading). Be interesting to know what others are using.

I'm not saying I know any of this for sure; up until this morning I've never used any of this. My 'theory' is strictly speculation based on this discussion, my own testing, and what I've read elsewhere on the subject, and TBH I kind of consider it a long shot. But it might explain why it works for some and not for others.

EDIT: Incidentally, I wrote NaturalPoint and filled out a ticket with their HelpDesk, just to see what they say about the matter.

KK,

Like you, I'm using the same TrackIR5 software version. 5.4.2.27545.



Yes to both.

After confirming, per your question, that I could change affinity and priority by altering the command line in the target field, I deleted my shortcut and then couldn't reproduce a functioning command line for priority. Some gnashing of teeth and highly intemperate language later (salted the wife's zoom call but good, let me tell you) I found the answer.

The solution lies with Administrator privileges and the way Windows handles them with shortcuts, at least on my Win 10 Pro 64-bit system.
Creating a shortcut of a program set to Run as Administrator puts the nice checkered shield on the shortcut icon but that's misleading.
Both the Shortcut AND the TrackIR5 application must have the 'Run as Administrator' box checked in their Properties.

Here's what worked for me:

In the TrackIR5 properties make sure the 'Run as Administrator' box is ticked.
Create a shortcut for TrackIR5.exe
In the TrackIR shortcut properties, under Advanced, tick the 'Run as Administrator' box
Replace the Target field of the shortcut with the appropriate command line. My example:

C:\Windows\System32\cmd.exe /c start "TrackIR5" /high /affinity C "C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe"

Start TrackIR5 from the shortcut and check TM for Affinity.

epower/KK;

I have noted your suggestions for windows 10 and updated my original thread post..
I would appreciate you reviewing it to see if it all now makes sense: TrackIR5 procedures to set affinity and priority

Robert,

I might put up a more detailed set of step by step instructions, just to cover all bases.

Also, I believe it would be helpful to link or discuss how Hexadecimal numbers get generated and how Binary number relates to ones CPU cores. I found your instructions excellent by and large but still needed to go hunting additional info for what I wanted to do with my configuration (Run on cores 2 & 3). My post earlier in the thread HERE might be useful info to include, especially the way the binary number tracks to computer cores. This particular graphic really helped me understand

Epower's procedure works for me here. Hurray and thanks!

The only tricky part was finding where the heck the 'run as administrator' setting was in the TrackIR properties ... it's hiding under compatibility settings when you right click the TrackIR icon.

Pleased to report that epower's finding has corrected the issue on my setup as well (well done). Don't know why I didn't think of that It does actually make a lot more sense than the theory I had about versions, etc. To echo 77_Scout's comment concerning the 'Run as Administrator' setting, I would agree it could/should be more clear...I found it OK, but perhaps not so obvious for all

Note this is only to say I've tested how to set priority and affinity with shortcut/command line settings. I still don't use these settings, and still do not find them recommendable on the whole. My research into the matter has thus far corroborated this position. That research is ongoing, and I'm happy to discuss it with anyone open-minded enough to listen.

Gentlemen, I am trying to tweak TrackIr using your guides&tweaks, but I don’t understand this part:

From HarryH guide: “My i5 processor has 6 cores. After much tweaking and testing I have found that allocating the first 3 cores to the CFS3.exe and the remaining 3 cores to the TrackIR.exe gives me the best results”

Question 1: Is it possible to allocate 3 cores to the game when the same guide states “we know the game engine runs on the first core - CPU 0”
Question 2: How many cores should I allocate to TrackIR? (I have AMD Ryzen 7 3700X 8-Core Processor (16 cores) - all others?

Thanks

Hi There,

I doubt that any core allocation tweaks are needed with the latest generations of CPU. That said, you should be able to allocate as many cores as you like to both the CFS3 and TrackIR executables.

What might still be worth experimenting with is the priority value. I still prioritize TrackIR over CFS3.