RyanR

Nice... but canopy is sooooo hazy. -Ryan

Honestly, I'd just ask here in the forums when you get in a jam. Keep an eye on the change log going forward. I feel like things have stabilized a bit after some *big* changes in 2024. -Ryan

Is this for serious still broke?? -Ryan

Thanks. My brain is farting on where (AKA what sim) I used radio-nav on a USAAF plane. Maybe I'm just thinking of the F-86. All my memories seem to merge into one these days. I've mostly been doing WWII sims for the last 30 years.... but got sucked into the jet age in DCS, now I'm trying to get back into taildraggers again. First time in DCS. It's just odd that this stuff basically isn't implemented, considering the "every rivet" mindset in the sim. -Ryan

To which, I gotta reply: "Yeah, but..." The tech being in its infancy doesn't explain its complete absence in DCS on the WWII maps.... and that it apparently only works in-game on modern-ILS frequencies. -Ryan

For the life of me, I can't get radio compasses going. A key piece of navigation for the period. Chuck's guides say that this is because ED has failed to implement any of this infrastructure.... and if we're lucky, these instruments might work using ILS frequencies? Which didn't exist for the period? So, are we relegated to the F10 map, or kneeboard markers? Might as well just make GPS available for 1944, too. NS430. Sheesh. -Ryan

It's like there's no friction on the wheels. It just goes sideways. Like the ground crew greased the wheels. The training mission (one of which has Tu-95's in it, but whatever) says the plane won't come unstuck until 200kph. But it lifts straight up and rotates 90 degrees at 100kph. That's 62mph. None of the other warbirds in DCS do this. No other simulated D-9 does this.... in the history of simulated D-9's. I'm old. I've been doing WWII sims for 35 years. What gives? This module seems barely simulated. A caricature. I can bank and crank on it, too without it dropping a wing. That's like sacrilage to the 190 folks. Full difficulty is on, too. -Ryan

Punt. Why is this not working or implemented in the maps? -Ryan

Just solved this. I noticed the Phantom and Viggen have a pop-up helper ("enable mirrors") when you hover the cursor over a mirror. The F-14 simply lets you "adjust the mirrors" when you hover. Thinking that HB must have used a similar command in the F-14, I popped into the "adjust controls", searched for mirrors and found that there's a keybinding for enable mirrors. The default key is "M". Back into the cockpit, hit "M", and I have crystal clear mirrors again! I feel a bit dumb. I dunno if the new launcher changed a hidden default. I did notice that "Rain Droplets" was set to "true"... a carry-over from before the launcher came around. The launcher gives you low, medium, and high quality for droplets.... and if you choose one, you can't go back to true. There's some voodoo in the new launcher for sure. Thanks! -Ryan

Hoping this is a something someone has seen. My mirrors have suddenly gone blurry in the F-14, and only the F-14 modules. Mirrors work fine in all of my other planes (F-4/Mirage/F-86/etc/etc) with mirrors. All I can think is that I tweaked a graphics setting in the new DCS launcher. All seemed fine until I popped into the F-14 again, and then I notices the blurry mirrors. I changed the setting I tweaked, but no joy. Blurry. I have all the graphics settings pretty much at "max" and am getting 150-200fps. I've an nVidia 3080 and 32GB of RAM. Any help would be terrific! I can't think of where else to look. Thanks! -Ryan

Very odd..... a remap fixed the hide/show stick problem. I was using backspace (which I think was default), and it would stop working once the chatter started. A fresh reboot seems to have cured my no-guns issue. Thanks for confirming everything works. I was thinking that latest DCS patch might have broken something. Excited to give this a go. Looks like a very cool campaign! Thanks again! -Ryan

No mods or anything..... hmmm. Will look into it some more. Thanks! -Ryan

This explains what I kept seeing in the about the F-5 BFM campaign. -Ryan

I assume I'm supposed to shoot Gator in the F-5.... but my cannon is dry. I have both air sources selected. I fenced in. Followed all the check lists. I'm just chasing an F-5 across Nevada with Jester yelling at me to shoot him. What gives? Also.... but less important... I can't hide the control stick. -Ryan

This is a different issue, it seems. No ordinance dropped.... didn't seem to be ordinance specific. Toggling NAV/A-G doesn't make it go away. It's pretty rare. I've only seen it one or two other times since my original post. -Ryan

Wow? Where can one get these paint kits? I've been having fun with just messing around with the ED templates. Thanks! -Ryan

Two different weapons systems, really. Just turn JDAM's "on".... they'll be happy when you need them. The sensors on the plane get the GPS coords, and then send that to the weapon. The bomb now knows where it is and where it needs to go. Mavericks care nothing about GPS coords. They technically don't even care about what any of the onboard sensors tell them. They're optical. They chase an optical target that you tell them. You absolutely have to boresight them to the targeting pod, which ultimately also aligns them to the HUD to make them easier to target when things get hectic. So, yes, turn on the weapons, and they will do what they need to do in the background. Just remember that Mavericks need boresighting when they come up. -Ryan

OK. I tried making a new simple mission in the Caucus map. Everything works perfectly. As advertised. Track attached. What could have caused trouble with the NTTR map? -Ryan Works in Caucus.trk

To reiterate, all of the following situations are fine: -It's broke. By definition, the Viper is a WIP, and that is totally understandable. I'll live. -It's how it's supposed to be. That these sensors work as well as they do boggles my mind. Technology is incredible and never perfect. -I'm doing something wrong. I will not debate that I am an idiot. In fact, I would debate if someone claimed I'm *not* an idiot. I'm just fishing for some sanity. Are others seeing what I'm seeing? -Ryan

Track attached.... maverick_TGP-offsett.trk F-16 uninstalled, all files deleted, then F-16 reinstalled for the above track. The yellow MFD mod was the only mod I ever used, and I deleted all traces of it. Same result, unfortunately. After this screen grab, I SOI'd the WPN page, slewed the crosshairs over, instantly locked up the target, and blew it up. The discrepency between the TGP and WPN pages is enough that auto-handoff never works. -Ryan

Agreed. I figured the yellow MFD mod would raise some eyebrows. I've had this issue long before trying the yellow MFD mod. If no one else is seeing what I'm seeing, then a reinstall/repair may be on my list. This isn't a bug report, but rather me asking if anyone else is seeing this "phenomenon". -Ryan

Is this as good as it gets? Is it a WIP? Or am I doing something wrong? All/any of these answers are fine. Here's a screen grab. Hot, in air, start. Toasty BTR80 as a targt. Mavericks should be "boresighted" automatically. This is what I'm seeing at 3nm after trying to auto-handoff continuously from 14nm out. Is this what you guys are seeing? As I close the distance, flying straight at it, the offset bewteen the WPN page and TGP gets worse. The reason I ask is that I'm seeing the same problem/offset every time I do the boresight process myself. It's easy enough the SOI the WPN page and nudge the crosshairs over and lock it up. I've noticed this as a problem ever since the INS work popped up. Thanks, -Ryan

Something has been "off" since the INS update a few months ago. A recent fix made it "better", but it can't be right. If this is "correct as is", then auto-handoff does not work at all on the real plane. The Maverick seeker is considerably "off" from the TGP at 7nm.... and the disparity degrades from there. Manual slewing the Maverick in the WPN page works fine, and the TGP gets you pretty close. Though, every time you fire a Maverick, you need to DMS-down to the TGP to get the missile on the opposite pylon to look where the TGT is looking (the SPI). This can't be correct either. In the end.... it's OK right now. I suspect we need to simply wait for the Sniper ATP to come to fruition. -Ryan

I got into DCS "late" (Early 2024), and quickly got sucked into the F-16. I've missed most of the Early Access. I really love the module. Yes there are niggles, but has there ever been a flight sim without niggles? I enjoy the endless learning that comes from the depth of the avionics and modern EW environment. I was just reading the road map, and the last thing on it for EA is the Sniper ATP. Exciting. The existing targeting pod and DMS logic seems to be one of the more frustrating things on the forum. -Ryan

Leave the HAD as SOI for as long as possible. With the TGP in the opposite MFD, it will get closer to the emitter as the HAD gets a better quality location. Not foolproof, though. Still a bit of a needle in a haystack, and you have to slew the TGP quite a bit to find it. I bet this works a LOT better with a donor over the datalink, so you can get down to PGM1 with plenty of distance. Once you find the emitter, marking it is standard stuff. -Ryan