Guy Smiley

I tried that before and it literally cost me about 20 frames per second. Right now, I'm running about 25-30 fps going down the runway with TGP off, which is about the minimum I want to be seeing, and up to 60, vsynch on, once airborne. Having the MFDs refresh with every frame however just about totally destroyed me, at least when I tried it on the previous (obsolete 2xx series) driver. So unless the developers come up with a fix, or the 306 driver behaves much better in that regard, I think my only bet right now is to just turn off the flickering mirrors altogether and be happy that the TGP no longer requires setting it to to the every-frame refresh rate. Thankfully I don't seem to be seeing any cloud flicker either at the current settings.

I hadn't actually tried the mirrors, but now that you mention it, yes, these are flickering terribly in the A-10, so perhaps I spoke too soon. The good news (sort of), at least for me, is that the since the Mirrors cause such a crippling performance hit, that I can't use them anyway, so as long as the TGP isn't flickering that is at least partially good news. I haven't had a chance to try the KA-50 Skval yet, but those that too had been previously flickering. Hopefully this driver upgrade resolved that as well.

I was having some problems with flickering clouds, TGP flickering etc. I had previously been sticking with an older Nvidia driver for the sake of FSX, since that seemed to be optimal. I'm running surround screens and SLI and had resigned myself to resorting to the option of 1024 Every Frame. This cost me almost 20 FPS and was basically unusable. So I decided to simply go the latest Nvidia driver, 306 something, and now all the problems seem to be resolved. I can use 1024 Regular and default Nvidia SLI settings, and no problems of flickering encountered so far, at least in the TGP. As a new DCS user and a new member of this forum, I've been spending a signifigant amount of time trying to determine what information is valid, and what is yesterday's news. Since it seems to be working for me now at least in the limited tests I've conducted, I assume this issue is resolved for everybody? All the previous information stickied about this site regarding problems with SLI and multi-monitor flickering surround screen issues is something I can safely ignore now, right?

Maybe you turn off TSAA in game and enable (override) Multi-sampling transparency AA with Nvidia?

Recently in the A-10 I mapped some rocker switches on a CH throttle quadrant to some basic functions such as Hdg Bug increase/decrease, HSI course increase/decrease etc. I found that this method of manipulating the knobs within this simulation is totally unsatisfactory because the sensitivities regarding a "repeat button press" is far too much. It is impossible to manipulate the knobs in such a way that a course or a heading can be selected within any precision. In fact, for MSFS, I have long had an entire controller dedicated to such functions as tuning radios, OBI knobs, Altitude selectors, etc, but unfortunately it looks like I'm not going to be able to use this in DCS, even though the user is apparently able to map the buttons. I am reporting this in the DCS general forums because it probably effects similar functions in the KA-50, P-51, and more knobs than just the ones I tried to map in A-10. Since such joystick rocker switch mappings are commonplace in flight simulation, I actually consider this a bug that needs to be fixed rather than a feature request. Alowing the user to tone down the a given button's sensitivity like they do in FSX (or FSUIPC), would be a great convenience.

Yeah, I couldn't find any way to change the input sensitivity for a joystick button key press. It is worse than I thought actually: even when you release the button the Course and or Heading Bug knob actually continues to rotate as if it had inertia! For instance if my Course knob is set at 180 and let's say I want to put it to 195, it is a matter of lucky timing if you can actually get the heading knob to stop within 5 degrees. Using the mousewheel seems to be the only option at this point, but the whole point of mapping it to a controller is so that you don't have to use the mouse. As many people coming to DCS from the world of FSX know, the function of mapping up and down functions such as hdg bugs, course knobs, radio knobs etc to a joystick rocker switch is such a basic function, that I'm actually going to report this as a bug that needs to be fixed.

Hi, I have mapped both the HSI course increase/decrease and also the Heading Bug inc/dec to rocker switches on one of my controllers. I find that it is way too sensitive. Even the slightest tap on the rocker switch will move it several degrees. This makes it very difficult to dial in a precise course or heading. I searched the forum, but didn't see anything, but apologies if this has been asked before. Is there any way to tone down the sensitivity of the button and/or keyboard command for HSI inc/dec so that I can have more control?

Oh, I see! Thank you for clarifying that. I haven't as yet seen any flickering on any of the MFDs in the A-10 or KA-50, only clouds that flicker at the start of the mission and then go away pretty much as soon as I'm airborne, never to return. I gather this setting therefore doesn't apply to the P-51. I tried the SFR suggestion that somebody had made earlier and it didn't appear to have any effect on the annoying cloud flickering, so I just put it back to the Nvidia Recommended AFR2.

Hi guys, I'm still new to DCS and am a bit overwhelmed with all the info on this forum. I'm finding it hard to distill all the information that may be contained in bits and pieces throughout hundreds of posts! I'm running surround screen with two gtx 480s (4320x900)and I'm getting the cloud flickering. I'm running the 1024 every frame. So is the advice to enable SFR instead of AFR2 in Nvidia Inspector? Do I just keep the same bits provided with the default Black Shark Nvidia profile?

Ah, that's it...the Server.lua. I think that might be the answer I'm looking for and I'll learn about that file. Sorry that we got off on the wrong foot with each other btw.

Did you notice that I never asked how to change the "default eye position"? I already told you that I had done that! And I already read the posts you linked to, but thanks anyway. I asked how to be able to move the eyepoint farther back than is currently permitted by ctrl-shift /. Sorry to waste your valuable time spent answering a question I never asked. Clearly a "lack of will" on my part....

I appreciate this bit of advice, but if I was able to find the answer that simply, then I wouldn't have registered for the forums and asked the question in the first place. All of my searches demonstrate how to address the problem by widenening the field of view from the default 120 to approx 140 or greater. Already tried that, and I don't find that the most satisfactory solution for the reasons already mentioned...Again, I wish to move the eyepoint farther back than is apparently allowed using keyboard commands (ctrl-shift /) or Track IR. Maybe my searching skills leave something to be desired, but I still don't have the answer. All I can deduce from all the threads on eyepoint I have read at this point is that it is "impossible" to move the eyepoint back closer to the headrest beyond the point currently permitted by ctrl-shift / ? Is that true?

I'm new to DCS, and I'm coming from the world of FSX and EZDOK, where you can move you're eyepoint all around, behind the headrest, even outside the airplane if you want. Here is my problem. I run a triplehead-to-go system at a resolution of 4320 x 900. In order to minimize edge distortion and for the purposes of getting the right size on the Hud symbology, I want to move my head as close to the headrest as possible and use the lowest possible Zoom factor that allows me to see the essential instruments, and a little bit of sky. Furthermore, I'm wishing to use the same custom zoom factor for all three planes (A-10, P-51, KA-50). I wish to use a zoom factor of about 120, and I have set this in the custom views. In the A-10 and P-51, this is not a problem. I can use a zoom of 120 and pull my eyepoint back with either the keyboard commands or TrackIR to where it needs to be. I understand somewhat about the View.lua and Snapviews.lua and realize how these eyepoints are adjusted and set as the default view... In the KA-50 however, I run into a "stop" that seems signifigantly more forward of the headrest. No matter what I put in the view.lua, it will only let me go so far back, and then no further. My choice is to either increase the zoom to about 140 (inconsistent with the others) and see a lot of distortion on the edges, suffer from enlarged HUD symbology, or else, to simply be to not be able to see as much of the instrument panel as I would like in my chosen default view. Is there any way or any file to change so that I can move my head just a little bit further back in the KA-50 than is currently allowable without having to resort to an uncomfortable Zoom/FOV?