lxsapper

Kuky. About "The game zooms out a bit". Are you refering to when pressing Numpad_Enter? I've read somewhere in the forums before that the sim for some reason does not start in it's default FoV as defined by the Lua's it's only when you press Numpad_Enter that you are actualy at default FoV.

He's talking about the Push function on the slew cursor. But there's more, the push function on the Mic Switch. And the Up on the mic switch (this one is modeled on the A-10C but has no function), so all of those can be mapped to extra functions (like TrackIR functions, if you are willing to program the whole thing in TARGET).

Excelent tool Highwayman! I usually draw it all by hand in sketchup and then use the protractor. But this saves time.

There is the option to clear all assignments of a particular controller. Doesn't that end up beeing the same?

70º shouldn't be too bad. But at 1m away correct FoV would be +- 65,5º.

Kuky may I make a sugestion? If it was me I would make calculations to figure how much of my real FoV that display is really covering and use only that value. Stretching should be a lot less noticible that way. It's a bit hard to belive that with even with such a large display that it's covering 80º of your real FoV. I know it can be tempting to use a higher FoV to be able to see more but I think it would be more enjoyable to match it. I'm speaking against myself here a little. Because I also have a higher FoV on my screen than the real FoV it covers. But I'm only using a 32" display at about 1m away, I can't remember what that figures to now, but I found it to be too funnel vision like to use effectively in combat. But I think if I had a 58" screen I would for sure be using matched FoV.

Hi romeokilo, I have a question. How do you interface the LCD panel that you took from a rear cam view kit? They're not usually VGA are they?

Saitek's Combats aren't all that great. Not very smooth (lot's of sticktion), jitery, etc. But hey do have adjustable tention and as I understand it bigger travel range, wich also helps to keep control. Even I'm usually agains't curves because I think they bring more harm than good. You may want to take joey's sujestion and try to see how they work for you. Also keep in mind that you should really keep your yaw input to a minimum during takeoff with Flamming Cliffs level aircraft. In DCS level aircraft (and real aircraft) you disengage nose wheel steering above 50-70kts. In FC aircraft you cannot they will both work toguether all of the time. As you have discovered that can lead to "problems".... Other than that practice and try to gain a feel for it.

Listen Blooze, I don't even know Why I'm bothering to reply to you. Considering the arrogance you lashed out at everyone who did. But This is really quite simple. The HUD is a colimated and calibrated image to sit in the cockpit I'n the place you see it. It's not by acident that aiming simbology and FPM are on target. You can't just move that image up or down, and expect it to be hitting the same spot. Take a gun with a colimated sight atached, if you leave the gun fixed and move your head about. The aiming reticule will not move. But move the gun one inch up, and you will be hiting the target one inch up. Now if you were to move only the sight upwards but not the gun. The zeroing would be all wrong for that distance. In the A-10 it's wxactly the same. The Image beeing projected on the HUD was designed to work with the aircrafts avionics exactly where it is. In DCS I supose it would be possible if you could actually edit the HUD files where it determines what gets drawn where and all that complicated matematical shit. It wouldn't be a case of just moving the drawing on the hud glass upwards. All the aiming symbology would have to be recalculated for the new "sight" position.

Use even slighter movement! No more tham 1-2mm on my saitek's during the take off run.

The DCS view is not entirely correct. I mean it is. But it's not the on the pilots normal seating position. The default View in DCS actually has the pilot leaning forward quite a bit. I belive this is for the convinance of beeing able to see all of the HUD. If you move the head back to a estimated position of where the pilot's head would actually be(not allmost over the knees like it is) , you can't see all of the HUD without having to move the virtual head around. This can be tiring and awkward even with trackIR. Yes I did try it, and went back to ED's default view. But The whole cockpit design makes a lot more sence and is easier to use when the head is back where it should. Try it, it will give you a new perspective.

"He" would be Me! :)

Very Similar! :D

I don't know about the fighterstick, but I hear CH programing software is excelent. In Thrustmaster's TARGET you can easely program a key to send F1 on the first press F2 on the second and so on, and it clycles back to the start. I Imagine doing the same with CH software is not hard at all. You can do it with saitek software, you can do it in FOXY. As to the how to do it in CH... you will have to ask someone else. :)

Rotary controls are usually used in real aircraft to control the radar antena elevation. The F-16 (not sure about many other types but f-15 and f-18 only have 1 rotary) has 2 rotaries on the throttle one is the "radar antena elevation knob" the other is rather misleadingly called "range knob", to be fair it does control the range (zoom) of the TGP when the TGP is SOI and when the FCR is SOI and in GM or GMT it controls the radar gain. I can't recall of the top of my head but I think the Range knob has no AA function whatsoever. I don't miss the rotaries in say for ex. falcon bms, because the warthig has more functions than the f-16 hotas and the game easely allows those functions to be programed on a HAT. So the rotary is a nice touch for fedility's sake but not essential. I don't miss it in DCS because FC aircraft commands I would put on an HOTAS don't come near to use all the HATs and buttons on the warthog. Plus you can use the Inc/Dec resistance knob on the base of the warthog to controll the Antenna Elevation if you want. It's not on the throttle levers per say, but close enough. I might miss it when F-18C or eventually an F-15 on DCS level comes about because the throttles part of the HOTAS on those aircraft are preaty much the same as on the A-10C (some controlls change position) but the left throttle lever on them also has a rotary above the pinkie switch. Still you can use the resistance knob just like before. On the other hand if you rather have the zoom view (like me) assigned to that knob even though you will be missing one analog controll on the throttle you will have pleanty remaining on the stick, since those aircraft sticks have less HATs/buttons than the warthog does. So all in all, you should have no lack of controlls to assign all the functions you should need.

F1 is cockpit view, F2 is similar to spot. don't think there is a view similar to tower, but take that with a pinch of salt, I don't remember that well. In any case, just a humble opinion.... Pure waste of controler buttons!

I recently purchassed an Asus ROG Vulcan ANC and I'm tremendously happy with it. It does cost a bit (payed €99.90 for mine) but I think it's well worth it, it only have virtual 7.1, but I think it's really good virtuall surround. Can be Jack Plugged or USB (has to be USB to use the virtual surround and amplifier features) but it's still a great when used as a stereo jackplugged headset. ANC works eigher way but has need of an AA batery in the headset it self. The reason this solf for me however, is that my kids kept destroying all my headsets, granted they were cheap ones but at the rate they were going... , this headset comes it a nice protective case but the big plus for me it that the wire disconects on the headset it self (the microphone does too) wich I allways do even when briefly leaving my desk so as not to give my toddler any chance of yanking the wire and knoking the headset to the floor, like he used to. He also did that with my warthog throttle once (not a dent on it to my sinking hearth's surprise) but that's a whole diferent story and I digress. The great part is that the disconnecting wire makes it repleaceble and for me with all the tumblings to the floor previous headsets took, with hearpieces coming apart and beeing put back toguether. In the end it was allways the wiring that killed them.

It's just a smart upscaling of objects based on distance that gets smaller to non-existent as an object gets neared to you. It works surprisingly well and is not that noticeable (it's not very blatant) it's also optional. But it is a controversial feature and like you say it can interfear with distance estimation. This is actually if I remember correctly a rather new feature in falcon (since OF or maybe even the new BMS), because falcon used to have (since at least falcon 3) fixed scalling options that went something like 1x 1.25x 1.50x 2x. That WAS a big mess on distance estimation!

Most likely a pinched wire. It happened to me once with the FLCS grip connected to the warthog base (too long to explain, maybe the video clears it up ). I mention this because after I found the faulty wire (problem with the hasty wire isolation I did after soldering the wires from the grip to the cable) I could use the grip again but had some ghosting issues when pressing 2 or more buttons simultanious. After re-ataching the warthog grip I concluded that my Wathog base was still working fine, and that the wires short circuit damaged the logic circuit inside the FLCS grip itself (lucky me). This all to say "hang in there and fingers crossed" as the FLCS, COUGAR and Warthog grip's insides are very identical right down to the electronics. The Cougar and Warthog use a more recent modern and minituarized version of the logic chips than the FLCS does, but they do exactly the same function. On another note I was able to repair the S2 button on my Warthog's stick wich was defaulting to a allways on situation, but that was a problem with the button itself and not related to this sort of malfunction.

By the way one thing I find a ton of help in a dogfight (I may be stating the obvious here) is to use a moderate amount of smothing in you trackIR profile, the view will feel a little less responsive but you will apreciate the view "stabilization" when trying to keep sight on a fast manovering target that is 600m away and "backgrounded" by the ground.

A real pilot is not zooming when moving his head forward (as stated before) you hud will look a lot bigger because it wen't from beeing 50-70cm away or whathave you, to beeing 20-30cm (this figure are not exact just an example), do it with your hand, with your arm streached and then right againt your face, it will also work with the letters on a book you are holding. But moving your head forward 50cm won't do squat for the aparent size of a target that is 10m wide and 3km away!

I don't know why this is so hard to understand. But of course objects are going to look smaller on your monitor if you have a relatively smaller monitor. They will look the size relative to the FOV you are using (IMAGINE THAT!) The only way the object will look the same aparent size as it would in real life is if your in game FOV is set to FOV your display actually covers in your (real world) view. And yes that will be too danm narrow for most people. It's too danm narrow for me and I'm using a 32'' TV at about a meter distance. This isn't a problem with the DCS engine it's what any half-assed 3d engine would do. Now you could argue that you rather have some sort of smart scalling as falcon uses to overcome monitor size and pixel density limitations, and that allright. But it's also allright for a developer who feels more "purist" about this feature to refuse to implement it. I don't know what ED's take on it would be. I have rather mixed feelings about it. On the one hand it helps a ton to overcome our current hardware limitations, can't wait for a big (say 65'' curved) affordable 4k TV. On the other hand it's a cheat and meesses up distance perception, as it alters the relative size an object should be at a certain distance.

Also as far as I know and stupidly as it sounds when you enter the cockpit you are not at "default" zoom, you get default zoom by hitting "Numpad Enter" once.

Well since you got it all figured out. Maybe we just won't tell you what you are too arrogant to learn (or too lazy to read in TARGET itself. By the way pleanty of reasons not to use TARGET, and the only reason I do is because TrackIR has a such a limited and in many regards bad software design (DX button recognition for once).