ShuRugal

I'm not sure if this is a DCS F-14 bug, or a DCS World bug, but I've only encountered it in the F-14. It seems that with the update that added the F-14, we got "touch to toggle" switches. Which is fantastic, it really is. The problem is that some switches require the grip trigger to be held to interact (so you get the "finger laser") and others do not. The problem I am having is the ones which do not require the grip trigger to be squeezed. It seems to be switches on the right side of the cockpit which are more likely to be a problem with this: I cannot interact with any left-panel switches unless I squeeze the grip. The right panel, however, appears to be open-season: If the VR hand passes through a switch, it will activate it, regardless of whether I am using the grip trigger. This causes problems when I interact with menus or put my touch controller down so i can grip the stick. So far, I have managed to: Jettison the canopy (about 75% of the missions flown so far) Turn off the generators (50% of the time when I set hand controller down) Toggle the hydraulic transfer pump (the other 50% of the time when I set hand controller down) toggle bleed air source (25% of the time) reconfigure my HUD and MFDs (about 10% of the time) All in all, it's fairly annoying. I have started keeping my hand controller on my lap (rather than its hook on my chair side), but i still end up starting many missions with no canopy, because the canopy jettison lever is exactly where the "start mission" button is after loading in. In fact, the first two times I tried to run a cold start training, I thought I was experiencing a bug with the canopy failing to render, because I jettisoned it before I could even get past the briefing pause screen.

I would lay money on this being the problem: I gave up using the Logitech software to map buttons to keystrokes for that exact reason. I've found that when multiple keystrokes are delivered to Windows simultaneously, a handful of random other keys will be ignores until the first couple are released, but not all others. I first ran into that problem 15 years ago playing Freespace 2 with no joystick on a Windows ME box. Flying with the number-pad, I could only pitch OR yaw if i was holding down spacebar to shoot; I could not do both.

I found a copy of ONC H-7 dated 1994 which shows 1-2 degrees for the area the DCS PG map centers on. Doesn't state what the drift is, though, not sure what it is today. EDIT: This chart indicates that the current (is) magnetic declination for the Persian Gulf is more or less bang on 2 Degrees East.

After a recent patch, it seems that my VR hands vanish when entering the cockpit. I can see them in the menus, though.

I would die of laughter if there were significant complaints about that. People have been getting chewed out forever on this forum for complaining about things being "not fair" in this sim.

looks like a decent fix, but i cannot find the hud definitions files for the eagle and the flanker...

2.1 mostly default VR presets with some tweaks to AA settings to clean thins up a bit 2.5 pixel density

So, I just tried some of the FC3 birds (F-15 and Su-27) for the first time since getting Oculus.... the HUD is completely useless. Could not see a thing in any of the color modes, and the HUD filter is physically missing from the cockpit ingame.... I love the wraparound visibility and immersion, but holy shit, i thought trying to see things on a regular monitor was a PITA.... I did notice that one of the recent updates has massively improved UI readability in VR.... When can we expect HUD visibility to do the same?

That's contradictory even for you, mate.

So, you're saying it's a deliberate choice by the developers to not simulate real-world visibility? I find that rather a large... quantity... to swallow.

20/500 ish. I'm legally blind without glasses. About average. Clarity was to the horizon, but scattered showers in the area meant lighting was moderate to poor. Maybe I stated that. I should have been more clear: I frequently cannot see aircraft in DCS from abeam when they are banked towards me with the light above and behind me. Definitely. Yeah, don't you just -hate- it when real life fails to align with your preferred facts??

I realize I am a bit late to the party here, but just thought I'd throw my 2 cents in (even if it will never be read by the devs... who would sift through 60 pages of this?): Last weekend flying out of Hanover (KOFP) with my instructor, I was easily able to to spot traffic in the pattern around KRIC... 15 nautical miles away. Most of the traffic in and out of KRIC consists of short-haul passenger service (Dash 8s et al) and general aviation. At one point, I was able to spot and identify a Cessna 172 making his crosswind turn out of KRIC.... I know that's what he as because 15 minutes later, he was on the ground at KOFP... If I can spot a 172 at 15nm IRL, but I cannot spot an F-15 at 5 in DCS, something is very VERY wrong.

It always makes me laugh when I see someone say this sort of thing... Until I realize that the irony is probably cruising in their blindspot, then I just get sad.

If we're going to start pulling up wishlists on the grounds that "X module has this feature, so Y should too" then how about an SM-3 upgrade for the Su-27?

I think this thread is nearly 500 pieces of supporting evidence for the last statement, there.

Considering how many of them have killed real-world pilots, I think your confidence in the stability of the aircraft is a bit misplaced.

yeah, between that, my new job, and catching up on nearly a decade of home-maintenance for my grandmother...

DU has less to do with penetration than the length of the round. A-10 fires 30x173mm 395g projectile, and the KA-50 fires a 30x165mm 304g projectile. The A-10 round has nearly 30% more mass at only ~9% less muzzle velocity (1010m/s vs 1100 m/s), meaning it has 20% more momentum and 10% more kinetic energy, but that's not the interesting bit... The interesting bit is that the depth of penetration of a projectile into a target is largely determined by the length of the projectile and the relative mass of the projectile and the target. As a rule of thumb, a projectile will penetrate half its own length into a target of equal density (or its full length into a target half the density). Comparing against RHA (7.84 g/cm3) a 165mm DU (19.1 g/cm) projectile should be expected to penetrate roughly 200mm given a 90-degree impact, whereas the extra 8mm of the GAU-8 would translate into an extra 10mm of penetration given the same conditions. (the GAU-8 real world specs call for 76mm at 300m range and 30-degree slope, which jives pretty well with the numbers i just crunched, yay.) Basically, the longer, heavier round of the GAU-8 will penetrate an extra 10mm, starts with more energy, and will carry more of that energy to the target (same frontal area, 9% less velocity means roughly 18% less drag force acting on a heaver round). This means that it can punch deeper and cause more damaging side-effects like spall, as well as having more ricochet potential once inside, creating higher impact heat, and having more energy left over to punch through things like engines and crew.

ty, all. Can't wait to get more hours put in and get my cert!

Cut the back right out of it...

Check your control bindings. If you are using rudder pedals with toe brakes, the axis probably need to be reversed.

CCIP and CCRP are automatically switched in the FC3 modules. CCIP: when the impact point is visible in the HUD, you get a circle indicator and when trigger is pressed, weapon will release. CCRP: if impact point is below HUD FOV, a diamond symbol appears. to bomb in CCRP mode, follow the following steps: 1: establish level flight and alight diamond with target 2: with diamond alight, press and hold the release trigger 3: while holding trigger, steering/banking cues will appear. steer and bank the aircraft to keep the triangle marker centered on the top of the CCRP reticule. 4: while passing through the computed release point, weapon will release if trigger is still held.

if it says target lock is bound to tab, you have modified from default, or your control bindings have been borked by an update.

I want this version: https://en.wikipedia.org/wiki/Piper_PA-48_Enforcer