Stealth_HR

I will redo the worksheet later today - I have been taught how to set a GCI frequency on the Leatherneck sub-forum, so I plan to include the procedure on the worksheet, and update Ch.1 (Авария) accordingly. I should probably add a guide to Russian numbers, just in case - maybe even other Russian code-names if I can find where they're used (such as code-name Mushroom and so on).

I see it know - it's under "Advanced options" > "Perform Command" > "Set frequency". Much obliged! LNS, sorry to have reported an issue that turned out to be a PEBCAK! :cry:

Well, this wasn't easy. The FC2, FC3 and Su-27 manual are all equally out of date - most of the phrases are technically correct but aren't exactly what Bitching Betty / Nagging Nadia / Repetitive Rita says. :D Here's a GDocs spreadsheet of all the DCS miscellaneous stuff I collected. You'll find the list of Nadia's phrases on the second sheet, and a list of subsystem acronyms on the third. While working on this I noticed a few phrases do not have soundbites: "Bug out", "Gear up", "Negative" and "Rogue" - they are 0 seconds in length. I've also noticed there are quite a few of them that I'd literally never heard - such as the "Check flight controls", "Increase RPM", "Throttle back engine" and the "Launched missile! Determine direction of threat!" I checked the EN soundbank and they're all present, but I have no idea if they are used as I hadn't flown anything Western in a while. Hope this helps. It's been fun making it, I had wanted to do it for a while anyhow!

While making a spreadsheet for radio channels, frequencies and airports I noticed an oddity regarding the MiG-21bis radio channels and the mission editor. If I place an AWACS in the ME, its default frequency is 251 MHz, but it's changeable in the editor, so I can: set the AWACS on 150 MHz (MiG-21bis channel #1, Авария), or set the MiG-21bis' radio channels (say again, channel #1, Авария) to 251 MHz and I will be able to call it. On the other hand, if I place an EWR like the 1Л13 or 55Г6, I am unable to change its radio frequency. It's permanently stuck to 124 MHz which is, by default, both on channel #0 (Рабочий, the wing channel) and on channel #9 (used by AFB Krymsk). Is this intended? Should it really work that way in reality? I assume not, as each comm source (other than a wing internally) should have its own frequency channel. The first free frequency on the map is 142 MHz - can the EWR be pinned to that frequency? Alternatively, can it be pinned to 150 MHz which is already channel #1 (Авария)? I realize channel #1 is the emergency channel and the EWR isn't exactly the right person to talk to on emergency channels. :D Finally, is this even something you need to fix or is this more ED's domain? :music_whistling: Thanks!

As far as I can tell (and I recall from previous experience with LOMAC, FC1, FC2 and FC3) the frame-rate drop happens due to the canopy scratches - the reflections and refraction calculated as the light passes through them are what causes the massive FPS drop. There is a pair of textures that need to be modified - one contains the scratches, one contains the smudges (mud, dirt, dust on the cockpit). I have tried to edit them, but I don't have a tool to separate the alpha layer which contains the scratches.

I've been meaning to make a translation table for some time, along with a transliteration/pronunciation guide. For starters, to help you with your "bingo fuel" phrase, it's рубеж возврата meaning the limit of return. :thumbup: I believe I saw the entire phrasebook in the Russian and English FC3 manuals, I will look around in a few hours and hopefully start compiling it. I'll also provide a list of airports with their proper names, code names and MiG-21 frequencies/channels.

Glorious Soviet pilot spilled in-flight Koffee, thus he uses Glorious Soviet Tumansky to dry his clothing. Tumanski stronk. Pilot stronker.

If I recall right, canopy freezing happens (internally) but the graphical engine does not support it yet - it should be present once EDGE rolls out.

Also, to the right of the AB light is the "second AB" light, for when you're afterburning, you've switched L57 on and you're below 5000m ASL.

Tried it, made it, works perfectly. Much obliged!

The best way to eliminate the problem is to figure out when you want to level out, flip yourself inverted, then level out and flip back from inverted. That way you keep a constant positive G load and the engine won't flame out. The same principle is used when you want to dive for a ground attack. Invert, pull until you're at 30-50° attitude, then flip back from inverted.

I've been terrorizing Hoggit with the "heavy breathing" photo, I'm this close to posting it here as well if the Flogger proves true.

Which means it may be the F4F Wildcat, F4U Corsair, F9F Panther, F2H Banshee, FJ Fury, A-4 Skyhawk or the AV8B Harrier II. An impressive selection however you go about it, though I'd be particularly happy about either the latter two.

Thanks for taking the time. One of the things that worries me a bit is how DCS will handle "debouncing" the switch. Does the fact it's defined as a value_down mean it will actually require a single key-press for each switching motion, as opposed to say the wheel-brakes which require a hold-down for it to work?

Thanks, Metal Hawk, I'll get on it when I get home. I'll likely make a JGSME patch out of it, for myself. In hindsight, no wonder the camera shuffling felt so regular, it was a sine-wave along all axes.

I'm not an LUA developer, however... When I look at the Weapons manager selector in the default.lua file, I can see that the value_down switches between 0.0 and 1.0 in increments of 0.1. So if there was a way to: * get the initial value of the switch on startup * have one keypress add 0.1 to the value (wrapping around from 1.0 to 0.0) * have the other keypress subtract 0.1 from the value (wrapping around from 0.0 to 1.0) that should take care of the rotary. It's kind of obvious, but I also imagine, kind of tricky to pull off.

Excellent fix there. I only wish all the custom cockpit makers had seen this and added it to their versions.

As everyone says, it's not flyable because it's not released, however... I'm not able to check at the moment - is the jet actually marked yellow, as a flyable?

Whenever I switch to the F2 view (for screenshots and the like) the camera initially sways. I know there's a key combination to stop the swaying (and that it differs from module to module, e.g. in the MiG-21bis) - but is there a way to permanently switch it off?

To check if the nosecone is moving, once you performed the start-up procedure on the ground, find the КОНУС switch on the left vertical panel in the cockpit and switch it off. You can then use the small rotary knob on the nosecone position indicator to manually set the cone position anywhere between fully retracted and fully extended. Also note that the with the earlier MiG-21 models the nosecone was much further in the intake, so if you're going by real-life photos, always compare with the bis model.

Can't wait to see this hit the shelves. I feel I should snag this.

Thank you, QuiGon, I had a tough time finding the Drop Center Fuel Pod key, as well.

Hey, Dolphin. Can confirm the bug is still visible in 1.2.14.35513 (Steam open beta channel), in singleplayer.

That's a standard Soviet/Russian concrete-penetrating bomb, used to destroy hardened bunkers and runways.

One of the recent patches introduced the need to start the on-board power on first. Can you try hitting RShift+L and see if the HUD and panels light up before starting your engines?