2alpha-down0

It's been a thing with the LAU-3 pods for as long as I can remember.

I seem to recall having the standby indicator drift as well sometimes.

Got mine in yesterday (8/16 preorder from Connection). First impressions, coming from an original Odyssey: - Coming from another WMR headset, it was plug-and-play, aside from adjusting graphics settings for performance. - Ergonomics are way better. Much lighter weight, smaller overall, and fits my face better. With the Odyssey, I'd get some ambient light leaking in around the sides, especially with the stock face pad. With the G2, I get a perfect, repeatable fit and no ambient light pollution. Adjustment of the Odyssey to fit different users is quicker and easier, but that's not a big consideration for my use case. - Headset tracking seems more stable; makes sense given it has four cameras vs. the Odyssey's two. - The IPD slider "feels" more precise than the adjustment wheel on the Odyssey. Range of adjustment is smaller than the Odyssey. - The off-ear speakers are... different. Sound quality is fine, but you will definitely need to crank up the volume if you're coming from headphones. For immersion in flight sims, with clicky HOTAS switches, rudder pedals, and other noisy peripherals (JetSeat, in my case), I don't think they're the best solution. - Field of view is noticeably narrower than the Odyssey. - The cable management loop is larger than the Odyssey, and removable. This will make moving and cable-managing my PointCTRL much easier than it was on the Odyssey. - Clarity is incredible. The Odyssey is no slouch here, but the G2 is on a whole other level. Individual pixels are essentially indiscernible, and SDE is simply not a thing. Before adjusting my DCS settings for performance, framerate was terrible but visual quality was amazing. Even after adjusting settings to get acceptable framerates (45 FPS with reprojection), it's still a huge improvement over the Odyssey. If text in a cockpit is blurry in the G2, it's because the texture is dated (older modules like the F-86), IPD is off, etc.; it's NOT the fault of the headset. My 1080ti is clearly the limiting factor here, and I can't wait to see what one of the new RTX or 6000-series cards can do.

I've made a couple multiplayer ones for the Early Cold War discord. We're flying one on Sunday.

Probably talking about his upcoming campaign: https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-5e-tiger-ii/231428-f5-e-black-sea-resolve-79-campaign

I just noticed that you’re on stable. I am on OB, but since they are the same version right now I’m not sure how much of a difference that makes. Sent from my iPhone using Tapatalk

Everything’s normal on my end. Sent from my iPhone using Tapatalk

I get it... but I'd rather not.

@BIGNEWY @NineLine any comment? Can this be moved to the bugs section?

Looking into it further, if stations 3 and 5 are released before 2 and 6, there is no delay in release for either set of stations. With unlimited munitions, once the stations repopulate, the delay on 3/5 occurs regardless of release order.

I don't think that's the case. The Weapon Delivery Manual for the F-5 mentions no such intent, and specifically says that all stations may be used with the ripple function. There are also bombing charts for different ripple quantities (2, 3 and 5 bombs).

- Select stations 2, 3, 5, 6: Bombs release normally, outer stations first, with no delay between button press and first weapon release. - Select stations 2 and 6: Same as above, no delay between button press and first weapon release. - Select stations 3 and 5: Bombs release with a very perceptible delay between button press and weapon release, as if waiting for the outer pylons to release first regardless of the fact that they are not selected. This can result in reduced accuracy if not accounted for. This occurs regardless of ripple interval. Is this accurate to the real aircraft, or is it a bug? f5 bomb.trk

Any further details available on the ZSU-57-2 teased in today's F-16 video, or other Cold War AAA coming to DCS? I'm glad to see this unit type and time period getting some attention.

I don't think anyone here expects charity. However, DCS is free to play. There's no real denying that air defenses and EW are pretty fundamental parts of a modern combat simulator. If it truly is becoming so complex and time-intensive to maintain and improve the core sim that improvements to it have to be paid for, then perhaps it's time to drop the free-to-play model.

Not to mention the two little slices of that area we currently have are ~90 GB combined. It's nice to dream... just budget for a 1-2TB SSD for your DCS install while you're at it.;)

Select Jettison switch to Off External Stores selector to Safe Gun/Msl/Camera switch to up position. Missile pylon switches to up position. Wait for lock tone and shoot. Seeker uncage is only done once you have a lock and really only if you need to pull lead on a maneuvering target. Seeker cooling isn't normally an issue. To be frank, given the current state of the F-5, the occasional delay/failure to lock we're seeing is probably just a bug and not a simulation of anything.

You don't need to lock anything with the radar, or even have the radar on, for the AIM-9 to lock and track. I've experienced a similar problem on occasion with the missile failing to obtain a lock. With enough time, it clears up and the missile will obtain a lock... almost as if the seeker isn't getting cooled initially.

You have to use the SRS radio overlay and manually tune.

Same issue here.

No, still broken.

The range indicators are fixed. Not sure when it happened as I've used a cockpit mod for a while, but I just switched back to default and it's been fixed.

Is there a waitlist for the aux push buttons that plug into the HMS?

This does appear to be caused by the 2.5.6 shaders mod. Deactivation and Steam file validation fixed the problem. Thanks @Sharkku and @BIGNEWY!

Interesting. I’ve been using this mod as well and only recently started having these problems. I’ll uninstall and try again. Sent from my iPhone using Tapatalk

Any particular map or air base involved? I haven't experienced this.