marcus4hire

Greetings: As some of you may or may not have noticed, a few weeks ago I built an LED headset and got it working with my webcam and FacetrackNoIr. I was pretty proud of myself. After some initial headaches I got it working and have been using it regularly. Been pleased with it so far. But there are some 'finer points' I haven't figured out. This brings me to my question(s). What can I do to prevent re-calibrating every time I sit down, scoot in my chair, or bump my headset?? This isn't a question of deadzones (I think). I have it all setup just how I like it. It just seems like I have to sit in the EXACT same place, same way, and hold my head the same each time I use it or I have to recalibrate. Some times I find myself doing it a few times in session as I adjust myself in my seat. Is this just a shortcoming of FacetrackNoIr or would I have the same problem with a full on commercial tracking system?? The one I am most concerned about is my 'zoom'. I constantly adjust in or out to get myself seated in the cockpit just right. Is this where programming a cockpit zoom in/out comes in (I see it mentioned a bit here on the forums)?

FINAL UPDATE That seems to be what the problem was. The very first training mission, 'Cockpit Familiarization' does not work too well with FaceTrackNoIR due to the reasons stated above. Every other mission seems to be working fine. In fact, my 2nd profile (for all other planes) works fine with it too. So maybe that will help somebody with the same problem someday. Don't use the first training mission as the "base line" for setting up your IR. I can tweak it forever but, right now, it is pretty spot in. Most planes are pretty identical but there are some that I prefer slightly different from others for various reason. In my opinion, it is best to setup a 'standard' FacetrackNoIR profile and then tweak each individual plane in game. For me, it is mostly deadzones. I am going to start putting together a detailed post about my experience getting into DIY track IR in the hopes that it may help somebody else. Thanks for all of the advice and help! Oh, and Accella works just fine as well as the EWS filter.

I may very well attempt to delete the config and see if that fixes anything. More for peace of mind than anything else, final confirmation that the problem is fixed. I should have added that I wasn't too concerned about that particular mission, it was just the first one I tried to see if it worked. Thanks!

Thanks for the tips. I am going through each setting/option in Facetrack in at a time to see what happens. I'll try the Accella filter. The EWS filter has worked so far and I like the options but don't guess they matter if it doesn't work. I THINK I may have found an answer. It has tested out so far..... When testing Facetrack in A-10 I used the very first mission. This is labeled 'Cockpit Familiarization' or something like that. In this tutorial user access is disabled. THIS is the mission that it acts wonky on. I loaded a few other random missions where you are in full control etc. and it works fine. No inverting the roll axis back and forth. It is only on that first mission that it had trouble. So, I am wondering if there is something setup in there that Facetrack doesn't like?? I will keep poking around with that, and the Accella filter and report back.

Greetings: I had posted a couple of other threads regarding my ventures into FactrackNoIR with a DIY LED build. This will be my last thread before I give up. Have a DIY LED setup and am using FacetrackNoIR with Pointtracker and the EWS filtering. Runs FLAWLESS on my WWII planes and the F-15C. The only remaining problem is A-10C. Sometimes it works, sometimes it doesn't. Sometimes it is wonky, sometimes it is perfect. Almost always have to invert the roll each time I start and run it. It is just all around inconsistent with A-10C which is the main reason I wanted a trackIR. Generally, I can get it working with a few loads but I can't find the pattern. Don't think there is one. Followed all of the instructions online. Have latest version of FacetrackNoIR and have the 64bit fix. All loaded where it should be. Like I said, sometimes it works, sometimes it doesn't. Getting frustrated and my skills and Google-fu are running out. About to give up on A-10, which sucks because FacetrackNoIR works with everything else. Thanks for any help. I included some snips below, because everybody likes pics!

Greetings: I had posted a couple of other threads regarding my ventures into FactrackNoIR with a DIY LED build. This will be my last thread before I give up. Have a DIY LED setup and am using FacetrackNoIR with Pointtracker and the EWS filtering. Runs FLAWLESS on my WWII planes and the F-15C. The only remaining problem is A-10C. Sometimes it works, sometimes it doesn't. Sometimes it is wonky, sometimes it is perfect. Almost always have to invert the roll each time I start and run it. It is just all around inconsistent with A-10C which is the main reason I wanted a trackIR. Generally, I can get it working with a few loads but I can't find the pattern. Don't think there is one. Followed all of the instructions online. Have latest version of FacetrackNoIR and have the 64bit fix. All loaded where it should be. Like I said, sometimes it works, sometimes it doesn't. Getting frustrated and my skills and Google-fu are running out. About to give up on A-10, which sucks because FacetrackNoIR works with everything else. Thanks for any help.

Greetings: I posted a thread earlier in the week but seem to have that figured out. I will try to keep this brief. Built an LED and set it up with my webcam and FacetrackNoIR. I followed the numerous online instructions for setting up Facetrack in DCS A-10. Got the headtracker folder loaded etc. Once it was loaded I set up the provided DCS A-10 file for P-51, Fw-190, and the Bf-109. It works great with those three. Love it! Problem is, I can't get it to work with A-10. Well, I sorta can. It clearly recognized my LED headset but....is a bit wonky. Like it needs to be setup especially for A-10. Is this often the case? Here is my question: I don't want to modify or mess with the settings as I have it with the 51, 190, and 109. How should I proceed? Do I rename and move the headtracker file and then setup another one especially for the A-10? If so, where do I put the file for the other three planes? I do appreciate any help.

UPDATE TO ORIGINAL MESSAGE After some poking around here and there online, I figure it out. As I have a Steam version of DCS, the file path is just a little different from what I found everywhere. For those who may experience the same problem, here is the file path I installed the FacetrackNoIR 'headtracker' folder into: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin As you can see, there was no 'dcs a-10c' folder prior to the final 'bin'. Right now I have everything up and running. Takes a lot of tweaking but I will eventually get it and it is usable now. In looking at some old screen shots of FacetrackNoIR I see a setting under the 'translations' tab for 'neutral zone'. That is what I really need, but my version doesn't have this option. Should I just program it into the curves? Also, I am using the A-10 profile for all of my planes. Guessing this is okay? Eager to find some suggested settings or tweaks. My biggest problem is twofold: 1) How to set a dead zone, the view moves with my breathing or any twitch. Gets old. 2) I am trying to get the view to pan at the same speed as my head and not so twitchy. Is there a specific setting for this or is it, again, built into the curves? I do appreciate any advice. ORIGINAL MESSAGE Greetings All: Last night I ventured into the world of track IR. I made my own LED tracker per Freetrack instructions and got everything setup. Well, Freetrack kept crashing on Windows 7 so I moved to FaceTrack NoIR intending to use the LED mode. I completely understand the instructions and 'fix' for DCS but seem to be missing a file path. This has come up before with other addons etc. and I want to get to the bottom of it. FaceTrackNoIR says to use the following file path: Steam>steamapps>common>dcsworld>dcs a-10c warthog>bin HOWEVER, here is the file path I have: Steam>steamapps>common>dcsworld>bin As you can see, no a-10cwarthog file. What gives? Like I said, I have seen this before. Also, does anybody know where I should put the FaceTrackNoIR files to get them to run in DCS? I understand the instructions, just not sure what the contigency is for different file paths. Thank you for any and all help.

The 109 requires TONS of touch. It is a very 'touchy' aircraft. The tiniest of variables can make takeoffs and landings very different from one another. As an aside, while the buildings aren't period correct, the maps is sort of a WWII map, for the 109 anyway. JG 52 flew all around the area during the war. Been reading some pilot accounts and they name all sorts of towns and airfields they were based. Many are on the map.

Thank you. I knew the bit about pushing forward to unlock it but guess I read over the part about it getting stuck. That should answer it as I recall I will alternate between the two brakes just to see if I can get some type of response. This must unlock the tail wheel and get her turning. I very much appreciate your taking the time to quote that. Back to the manual for me!

As an aside, I would just like to extend a formal 'thank you' to the devs and this forum. Everybody has been most helpful, patient, and polite. I have flown a lot of sims but DCS has the best community by far and the forums are vital to fully understanding some of these aircraft. Thanks all!

Greetings All: So my Dora is coming along nicely. However, I have one issue I am trying to get to the bottom of and that is turning the plane while taxiing via left/right brakes. Does anybody else experience trouble getting it to turn to one side or the other, seemingly at random? I am GUESSING (still doing some tests) that it has to do with the weight and fuel contents. If I have it anywhere over 50% or so full it seems almost impossible to get it to turn cleanly. Is this normal? If I have a belly tank I notice that I have to really gun the throttle to get it to turn. Taxiing can take several minutes and the most I can get is a fraction of a turn. Let's say I am turning 90 degrees with a moderate fuel load. I have to darn near push the throttle all of the way and inch it into the turn. Throttle up, moving, turn, stop, get moving again, turn, stop, etc. But when the plane is light I can drive it around just like a car. Is all of this just from extra fuel load? I haven't even tried it with 100% fuel. I think, so far, I haven't had anymore than 70%. Any thoughts are appreciated. I'm gonna go fool with it some more and report back. ETA: Nope. I just taxied all over the place with no real trouble at 100% fuel. Maybe a hair more throttle but that was all. Had some problems right at the end but after a turn or two it went away. Do the brakes get hot?? Are they just 'iffy' at times (assuming you have random failures on)? I have read that planes of the era didn't have the best brakes. Is this what is being modeled at, seemingly, random?

Oh, I'll prolly continue to mess with curves and whatnot but I don't feel an immediate need to make any changes. I just have trouble with the fact that curves are one of the most discussed topics and many swear by them but I do alright without them. That isn't a jab or snarky remark. On the contrary, I wonder what I am doing wrong.

I completely understand stiff springs and sticktion, as you called it. Why I stopped using my Saitek stick. Had a 'catch' on it which is very well known but, whatever I did I couldn't get it to go away. Made fine inputs impossible. Otherwise, I like the calibration it had.

That helps as well. And goes along with what I was taking away from playing with curves. Guess I misunderstood some of the other threads and posts. I get the difference between a full length stick versus a short throw desktop stick. But as long as I am attentive and don't throw it around the cockpit, I experience little, if any, trouble. Kept departing at first but, over time, I learned just how much I could get away with. To get off on a tangent: In my opinion, the idea of snapping the stick from one side to the other is very 'Hollywood'. You see the same thing with cars in the movies. People are way over-steering compared to how you drive in real life, with small inputs on the wheel. I imagine planes are similar. You don't slam the stick all the way to one side and pull for all your worth, you have to pay attention to what the plane is telling you. In ACM, it sometimes feels like you are barely turning when, in fact, you are coming around at a pretty good clip. Thanks again.