ubiquitousuk

Two quick questions: (1) Is there a way to padlock the view to SPI, so the pilot's head turns to look at the SPI as you maneuver? (2) When I point the TAD at a target, the target appears as a small diamond in the HUD. When the gun reticule is over the diamond, the diamond disappears, which makes it slightly harder to aim precisely at the TAD target with the gun. Is there a way to make the diamond visible under the gun reticule?

Has the most recent patch introduced a bug into the autostart script for the Dora? I have just come out of an online game where the autostart wasn't working for me.

Worth clicking the link the the OP just to see the video on that page. Amazing footage.

Works for me too now. Thanks a lot Devrim!

Are you doing subtitles or dubbing? I hoping subs so I can listen to the original German. Either way, this sounds great!

My S.O. is a German named Andrea--I kid you not. But I might struggle to persuade her to do the ATC voices :D.

Has anyone had the problem that the autostart procedure fails to start the aircraft as in this video?

My reward did not show up properly in the backers' section, but I opened a ticket and it was resolved extremely quickly. Very grateful for the excellent support.

Look at this for a piece of flying: https://www.youtube.com/watch?v=4iOoiEbtf2w

That is sick.

It sounds like you are trying to bind "thrust up" to your throttle axis, but "thrust up" is a command that can only be bound to a button (not an axis). From the drop-down box at the top of the controls window you need to select "Axis Commands". From there you can bind "Thrust" to your stick's throttle axis.

My trim keys don't seem to work. I have the default bindings: RCtrl+, RCtrl+. RCtrl+/ RCtrl+;. Pressing any of these key combinations doesn't seem to do anything (have tried pressing, pressing repeatedly, pressing and holding. I also tried binding these commands to my hat switch, but still couldn't get any effect. Does anyone know why this might be?. I recently bought a new mouse (MS comfort 6000). Since switching over to this mouse I have found that double-clicking the middle mouse wheel no longer switches mouse look on or off. The middle mouse button works as expected in all other applications. Has anyone else experienced this, or does anyone have an idea for a potential solution? With thanks.

Nothing useful to add other than to say that I am also still getting view lag in 1.2.4 update 4 (as well as the issue reported elsewhere of non-functioning stick shake when approaching the stall envelope).

Thanks, I had a good experience in bootcamp on my rMBP, but will check out the new driver.

I get this behaviour too. If I put on stick input (i.e. if the stick is not centered) then I the view input from mouse look is very laggy. If, on the other hand, I leave the stick in the center position then there is no lag at all. As above, this is with an MS FFB2.

I have a, perhaps, odd sounding question: how do you blow up your engine? I fly the P-51 against the FW with all realism settings turned on. Max throttle, max RPM, WEP engaged for 20minutes+, and no apparent adverse consequences for my engine. Am I doing something wrong? I'm left with the feeling that there is a way to squeeze more power out of the engine that I am missing and that this might be why I have such a hard time maneuvering the P-51 or keeping any speed.

Yes, I am having this problem without TrackIR, see here. For me, the 'steppiness' in views seems to go away (or, at least improve) when I unplug my MS FFB2 stick.

So I did a little testing and indeed the MS FFB2 seems to be related to my problem. If I plug in my old Cyborg F.L.Y. 5 stick (horrible, horrible thing) I get no view lag. The problem returns when I plug the MS FFB2 back in. I tried turning the FFB strengths to zero under "FF tune" in the options (I couldn't see an option to toggle it off altogether) but this did not solve the view lag issue. I do not have TrackIR and am trying to turn the view with the mouse, so I don't think this is trackIR specific. I should say that 2 seconds is close to the upper extreme of the length of freezes that I get. I see the whole spectrum from small fraction-of-a-second micro-stutters as I turn my head to periods where I am unable to pan the view for several seconds at a time. Likewise, when I press an F-key to change to an external/internal view I experience a seemingly random delay before the view actually changes: sometimes it is instant, sometimes it takes as long as a few seconds to switch to the new view. Not sure how to fix this, but going back to the F.L.Y. 5 is a fate worse than death Edit: it seems others are having this kind of problem. See here: http://forums.eagle.ru/showthread.php?t=115472 Edit 2: it seems like I don't get any lag/delay when panning the view with either that hat switch on my stick or with the numeric keypad -- only when moving the view with the mouse or when switching between views. Edit 3: The latest version did not fix this problem for me.

ContraStorm: I think we are having different (but maybe related?) problems. From your post it sounds like the whole game lags (aircraft don't move). My game runs buttery smooth and it is only the view panning/changing that is lagging.

I have recently started experiencing view lag in DCS: Moving the mouse to look around the cockpit: view follows input with a delay of 1 or 2 seconds Switching views: delay between key press and view switch of 1 or 2 seconds. The former problem is particularly egregious because it kills the ability to fly and look around at the same time. Is this a known 1.2.6 issue? I also just got a new stick (MS FFB 2), but don't see how that would be related to my problem. Performance is otherwise good and this issue only recently started. Thanks for any info. Specs: i7 950, GTX 460SE, 12gb, SSD.

Mike Spick - Allied Fighter Aces of World War II - The Air Combat Tactics and Techniques of World War II http://www.amazon.co.uk/Allied-Fighter-Aces-Tactics-Techniques/dp/1853672823

I'm with xcom in thinking that the (post-TF) CloD approach works pretty well. It's still tricky to spot a moving bandit against dark terrain, but one never has the feeling that one is being handicapped by monitor limitations. The glint of the sun reflected from a canopy, in particular, is often just enough to catch the eye so you know where to look. That said, I don't have much flying experience, so I can't comment on how realistic this is/is not. In general, I have some sympathy both for those who advocate realism at any cost, and those who accept a fall in realism to account for shortcomings of our hardware. Ideally we'd have an option to toggle between the two alternatives according to taste.

Here's what it looks like on the reveiving end:

Glad I am not the only one. My current tally is 0 kills, 43 deaths :(