Taz1004

Well, only thing I can think of is that maybe some (or part) of those keys are mapped to something else. If it fails to work again, then I'd try changing the RAlt + RShift + Numpad as well as RAlt + Numpad0 key to something else. Also, I'm not seeing F14 in /Saved Games/Config/View/SnapViews.lua Maybe HeatBlur saves it somewhere else. That might be related to the issue I'm not sure.

It works for me. Maybe it's module issue. What module are you doing this on? Is User Snap View Savings checked in Options?

Thing is the datalink target points I save contains altitude info. But not the one from the wingman. Or the target point made in ME. I have not tried target point saved from ABRIS. And like I've said, sometimes it's above, and sometimes it's below. Targets in Shooting Range Caucasus I tested were at 584 feet. So it was slewing to altitude below that.

My Shkval was looking low in that Shooting Range Caucasus map. I thought maybe it was looking at 0 altitude but maybe not if it's looking high at some maps. I was trying to make use of the Datalink but it's pointless if only thing I can do is store target myself and shoot it myself. Someone on another thread was telling me Ka-50 is feature complete. Pretty much only thing I can do with it is point Shkval at target (on clear day only) and shoot Vikhr at it. And Ka-50 doesn't get fixed with track either. No one at ED is working on it currently so making track is waste of time. Maybe I'll make one once I start seeing Blackshark contents in patch notes. But after Hornet, then Viper, A10C-II, then Apache, I doubt it'll be anytime soon.

Well, that's done for performance reasons. If the trees bother you more than frame rate, /Config/graphics.lua Line 370 Increase it to 3 or higher. Of course set in-game visb range to Extreme.

That's nothing compared to what Google does. https://policies.google.com/technologies/location-data?hl=en-US

Unfortunately, A10C HUD are raster. Not vector like F-16C. You can try the thinner HUD part from this. Or this is even thinner one I use now. Taz1004_A10C_II_HUD_Line.zip

I'm having this issue and googled it. And this 5 year old thread came up. Anyone else still having this issue? I even created target points in ME and tried to slew to it and it points to somewhere totally off. I was testing it on Instant Action Shooting Range.

Well, the issue seems a lot more complicated. With the shader cache disabled, I didn't have any issues on short or instant missions. But on longer campaign missions like Operation Piercing Fury, the issue came back. Even fresh after deleting fxo and metashaders2. It may be the fog in that campaign or it may be related to the duration of your flight time. It could also be several factors affecting it together. This type of bug is hard to troubleshoot because it's inconsistent to reproduce and takes long time to test.

I get those errors too. On unmodded clean install.

I thought those were flashes and yours is more persistent. Reason I'm suspecting GPU is because on the other thread, others can reproduce. Yours is not. And strange coloration is typical signs of failing GPU. Or failed GPU overclock. https://www.techjunkie.com/six-signs-graphics-card-might-dying/ It may be another factor but just to be on the safe side or at least rule it out, dust off your GPU. Even if the GPU temp is in good range, other component may be dusty. Then try underclocking it using AfterBurner.

Glitch from failing GPU is never predictable. But if I had to guess, aircraft burning has thicker smoke which may require more draw calls.

Those are usually signs of failing GPU. Try underclocking it and if it gets better, then you'll know if it's GPU or not.

You can give this a try if you feel adventurous. GearVR lens mod would greatly improve quality too. If you already have GearVR or can get one for fairly cheap.

What 2 versions? SP and MP?

I'd love to try it if you send me a pimax. But even with Vive, I can vary between +/- 30' of FOV.

Vive Pro with lens mod eliminates sweet spots. So you can increase its IPD to widen FOV. Your eyes don't get crossed just because you increase IPD. You're just looking straight through different parts of the lens. So if someone with actual IPD of their eyes at 60mm, but increase Vive's physical IPD to 75mm, is actually greatly increasing the FOV. Or if you decrease it, you get tunnel vision. But no difference in sense of speed. If you increase in-game IPD, that's different story since you're spreading the in-game left and right camera apart. Effectively making your in-game head bigger. Which in relation makes the world smaller. Which would decrease sense of speed.

Where in mission editor? It doesn't show up on A10C divert page either.

Obviously missed the point. That same 600kts at same altitude in Caucasus vs Syria will give you different result. Was the point. I didn't mean Syria is exactly same as that video or perfectly realistic. I meant it is "closer" than Caucasus due to better scaling and more detail.

I was looking for a mod for this as I found myself instinctively avoiding these grooves running down the runway. And few mods that were made seemed to be outdated. As always, I made this for myself and perhaps some others might find them useful. And I bought Persian Gulf and Syria but keep finding myself coming back to Caucasus because it has most campaigns and missions. These textures are from Syria runway textures. I simply resized and changed repeats to match that of Caucasus. So credit to Ugra for texture source. DOWNLOAD INSTALL: Extract to main DCS install path or use mod manager. Would likely cause conflict with other terrain mods that modifies runway textures. Either merge or install this mod last. Is it IC Safe?: No texture mod is IC safe unless the server turns off "Require Pure Texture" Is there performance hit?: No, textures are same size as default.

I already mentioned that. But we're not talking about camera lens here. FOV in VR literally means viewable angle versus Focal Length is distortion of the view. They are completely separately controlled in game engine unlike a physical "camera" Plus, I can change physical IPD of my Vive Pro from 60mm to 75mm. Effectively changing Field of View angle. I get very tunnel vision with 60mm but makes no difference to "sense" of speed.

Thank you, finally a response. Does Kutaisi ILS actually show up on your F10 map? It doesn't on my end. All other airports show up just fine so I don't think it's same issue as you had yesterday. And does ILS actually work at that frequency?

FoV (Field of View) is often mixed up with Focal Length. Because in "camera", changing focal length would change FOV as a "result". But FoV is only talking about how much you can see in front of you and focal length is changing the lens distortion like if you're wearing glasses or looking through binocular. Focal length would change sense of speed. But not FOV. If I'm driving at 70mph and cover left and right side of my eyes with my hand, it does not change my sense of speed. And in VR, focal length is supposed to match that of real life and can't be changed.

This is actually related to this One of the topic that comes up from time to time. But it has more to do with level of detail than FOV. In Caucasus, some gaps in concrete runway is twice the width of my A10C's front wheel. And potholes size of a person everywhere. Most of the trees in the cities are way too large. Many of them tower over 5 story buildings. Of course your sense of speed will be halved if you fly over trees that are double the size. ED obviously did this for performance reason. To use less trees to cover the same amount of area. Syria I think done better job of scale and does yield better sense of speed. Which is also why it's heavier. Smaller but more detail to cover the same amount of area as Caucasus. I think this video is fairly close to the real footage posted above.

Obviously... but I wasn't talking about speed of the search. At 30 or 60, some targets just wouldn't show up "at all" on my radar even when I'm pointing right at it and wait for complete cycles. But it shows up with 10'. As if the radar "power" gets stronger with narrow azimuth.