Daniel M

It's one of these two: Snapviewsdefault.lua or view.lua Edit: here's what I use for ka-50 with tir and triple screen setup...otherwise i'm too close to the hud snapviews Snap[9][13] = {} Snap[9][13]["y_trans"] = 0 Snap[9][13]["x_trans"] = 0 Snap[9][13]["z_trans"] = 0 Snap[9][13]["vAngle"] = -15.592758472369 Snap[9][13]["rollAngle"] = 0 Snap[9][13]["viewAngle"] = 110--89.777544238285 <--only changed this Snap[9][13]["hAngle"] = 0 the -- means a comment so it's really Snap[9][13]["viewAngle"] = 110 views.lua line 136 CameraViewAngleLimits[KA_50] = {20.0, 140.0}

This worked for me in DCSW: 1.2.2.7570. OP what is your version? Directory for above should be C:\Users\<username>\Saved Games\DCS\ScreenShots Edit: Sorry just noticed this was under the "Lock on" section...not sure if relevant.

Are you referring to FOV? I believe its snapviews.lua and/or snapviewsdefault.lua(i forget the second name).

What Bushmanni said, but while looking for a NVG Trip screen fix stumbled upon this: http://forums.eagle.ru/showthread.php?t=96477

Because you have to "fiddle" to get the abris info or erbl over the correct position vs just HMS/shkval lock? I really find both to be pretty similar, my personal pref is the PVI but I don't really think it makes that much of a difference either way. Then again, i usually spit out grids and noone listens :cry:

Those mods only edit a config file. You can do it yourself if you'd like. (i'm to lazy to search for the original thread, but this is someone elses find, please credit them) ...\Program Files\eagle dynamics\dcs world\mods\aircrafts\ka-50\cockpit\scripts\config.lua change v_angle_shift = math.rad(11) -- displacement for padlock and helmet to v_angle_shift = 0 (i do v_angle_shift = 0--math.rad(11) -- displacement for padlock and helmet so i can revert back if needed)

Agree that it's easier, but once you get used to the Shkval+PVI TGT Point method, I think the later is faster.

(I only fly ka-50 so not sure how relevant to other craft this is) Do you use numpad/ and numpad* to "zoom in" your eyes? You'll be able to keep your head up and out the window to keep your SA up while scanning for targets. Once I spot the dot, then it's HMS to bring it into the shkval and ID.

Sorry, my typo. Above is what i meant.

Keep your sink rate above 3 m/s and youll be good. Most of the time you ll out range the target any way.

Sorry Doveman, I mean I can't think of any other implementation "scheme" to get beyond the fact that you wouldn't have a FFB stick. Suggestions? Just another technique of using the current systems: Recently I've adopted to using flight director for major changes in direction or when beyond the forward edge of battle(aka I know i'm going to be yanking and banking). Then turn FD off only if I need to maintain a slight hover, this way my trimming is relegated to small adjustments.

There's already two methods?? Central On or Central Off

Have you tried setting TIR to recenter/pause/etc to ctrl+F# ? Or ctrl+shift+F#? No issues with switching aircraft that way/doesn't affect key bindings.

What are you referring to? While the community may be relatively small, 95% of it is helpful, will walk you thru an issue until it's working on your end. I have no issues exporting to triplemonitor setup without a fee?

x2 but ctrl+f12 here

It's our revenge against the AI see thru trees :D

Except F10 and Padlock :D

I can not duplicate using center trim option. I can "understand" this happening with that option turned off because your joystick is moving the virtual joystick. You trim to hover, pretend perfect 0,0, get to step 4 and when you hit trim the virtual joystick is trimmed forward(for fwd flight) but the computer is also reading that you have pitch input so it forces a nose down, am I incorrect? I forget what the timing is but, don't you have half a second to get the stick "recentered" in the non-center trim option? Aka step 4 should be 4) Trim button is quickly clicked(without holding it) and joystick returned to center? *edit: i might have the center trim option reversed....i use the "old way" of click trim, and you get no joystick input into the game unless you recenter joystick, vs the new way of "it recenters after .5 seconds"

I'll randomly get the can not connect to a certain server for "a day" and then the next day(and for a while past that) no issue. (i'd agree with the earlier post that maybe the server semi-hangs but it still reporting a heartbeat to the master server) Not to speak for ED, but I'm pretty sure they've mentioned multiple times that they are working on fixing the net code in general with the next update: http://forums.eagle.ru/showthread.php?t=99109 3rd post

1. Standard Operating Procedure 2. Dis guy(i believe, it's been awhile)

OP can you post the crash and error files? http://forums.eagle.ru/showthread.php?t=88164

1.5km+ engagements it is! Thanks

I can attach a tacview file if anyone wants to see but was wondering: I've been trying to work on my hms/close range game and got hit a few times by ak rounds. They ended up taking out my main and common hydro. Is this "realistic". I know we're "armored", and its "lightly armored". I thought it was the equivalent of like an IFV? Am I under the incorrect assumption that we are "impervious" to small arms fire? BTW this was me the whole way back for 20km to the farp :joystick: , but I made it :D

could not duplicate the issue via notepad, wondering if there's not enough of a delay? (using default). will experiment

It occurs in game as well unfortunatly