Robin_Hood

On Scribd you can also find a -34 (Non-Nuclear Weapon Delivery Manual) dating from the same era (1979, revised 1981). It is interesting, but outdated.

Never heard of this, good tip!

The switch is the Fuel Quantity Indicator switch, and only changes the display. Actually, it only affects the LEFT and RIGHT counters at the bottom of the indicator. Two things you need to remember: 1. The TOTAL counter and the pointer are not dependant on the switch position. The TOTAL counter always indicate total fuel (all internal + all external), while the pointer always indicate total internal only. 2. The LEFT and RIGHT counters are tied to the switch. So for FEED, INTL WING and EXT WING, the LEFT and RIGHT counters indicate the fuel left in the left and right feed tanks, wings, and external wing drop tanks, respectively. For the TANK 1 and EXT CTR, the LEFT counter indicates the fuel left in the Tank 1 (main internal fuselage) and external center drop tank, respectively. The CONF position indicates fuel in the left and right CFT, but as they are unavailable in DCS, they will always show 0. For fuel systems this page has some good info, though it has not yet been updated per the new working indicator switch. Hope this helps :book:

Indeed, and unfortunately there is no way to know that, or change the waypoint, in any other mode than NAV. Still better than a few years back, when the HSI wouldn't be updated when out of NAV mode :)

ILS should work on the Kuznetsov. That's pretty much the only help you can get, because as mentionned, the meatball doesn't relly work (and never really has).

Hopefully it would save some work, though I think it would still need quite some attention (esp. due to canards).

I concur, IvanK. Don't think I saw a ghost ILS, although the behaviour is somewhat strange. It seems that sometimes when you switch back and forth between NAV and ILSN it keeps the last airfield selected, and sometimes it resets to the default airfield. I noticed recently this issue with the course pointer going nuts when real close, I don't remember it happening before - might be a relatively new stuff (I don't fly the aircraft that often, so it may date from the new cockpit). I agree that waypoints are easier, but they clutter the NAV mode - doesn't it force you to cycle through all waypoints to get back to the early ones ? I wish there was a "Previous waypoint" button.

As I said, as each airfield has a unique course, you can know for sure what airfield you're looking at. Works for both russian and US FC3 jets. And here's the list: (When there are two numbers, it's because the course display is somewhat between the two ; the number between brackets is the one displayd in the F10 map) Anapa: 041-042 (041) Batumi: 125-126 (125) Beslan: 093-094 (93) Gelendzhik: 040 (39) Gudauta: 331 (331) Kobuleti: 070 (70) Krasnodar Center: 267 (267) Krasnodar Pachkovsky: 047 (47) Krymsk: 219-220 (219) Kutaisi: 074 (74) Maykop: 219 (218 ) Mineralne Vody: 295-296 (295) Mozdok: 083 (82) Nalchik: 235-236 (55) Novorossiysk: 042 (42) Senakhi: 095 (094) Sochi: 062 (242) Soganlug: 132-133 (132) Sukhumi: 296-297 (296) Tbilisi: 308 (307) Vaziani: 135-136 (135) As for using that as a makeshift TACAN, I have noted that when in ILSN mode, you will get the distance from the airfield (runway threshold I think), and bearing pointer in the HSI will point to some point lined up with the runway at some distance. Granted that doesn't make it a great precise TACAN, as the distance and bearing indication do not perfectly correlate (because they refer to a different point), but I have found it sufficient to fly acceptable DME Arcs. I haven't really tried that lately in the F-15C, but I don't think it has changed recently. I see though how RTN mode may give a more precise TACAN, as the bearing and range indication refer to the same point. However, it is not that great for TACAN approach, as it gives you a TACAN 7 miles from the airfield. Bottom line is, TACAN or not: whatever the plane I'm in (F-15C or Su-33/27), if I want to go direct to one airfield, all I do is select the correct airfield in ILSN/LNDG mode based on its course, and use the bearing pointer to go there, while the range counter gives me the distance. Of course, if/when two in the future we have several airfield with the exact same course, all of this won't work anymore.

+1, good to know, I figured it was wrong, didn't know neutral trim position was actually the right one.

I'm not sure I understand you correctly. Why do you think russian RTN mode is an advantage over what the F-15 has ? Also, let me say this: You can cycle through the ILS stations and select for sure any airfield you want. The reason is, you can discriminate airfields by their "Course" indication (magnetic heading of the runway). Each airfield has a different course, currently. Ergo, ILS mode can be used as a makeshift TACAN for every airfield in the game. Thanks for the tip about ILS ADI bars, I didn't know that it depended on the airfield.

Yeah, they don't have a proximity fuse I guess

What they mean is that you can now switch the Fuel indicator switch between all of its positions: BIT, FEED, INTL WINGS, TANK 1, EXT WINGS, EXT CTR, CONF TANKS. That is something unseen before on an FC3 aircraft :thumbup: As an aside, the release feels kina rushed to me, not sure why they decided to release it so early. The Su-33 cockpits still has a lot of game-breaker bugs (fuel indicators, airspeed indicator, AoA and G indicator...).

Well, the F-15C is not an F/A-18, so it shouldn't necessarily use the same techniques. Personally, I'll try to go with the -1, so if it says flare, I'll flare. But of course (and this has been said many times), fly the AoA, not the speed. For example, for crosswind landings, F/A-18s manuals say to rudder out half the crab before touchdown, while F-15C manual says not to uncrab at all. I'm sure the people who wrote that had their reasons (actually, in one of the F/A-18s manuals, they actually say that they tested different techniques, and explain why they chosse that one).

I think you would want to be on-speed at 22 units AoA on final, that's what the manual says.

Remember that although the F-15C is just now being blessed with an new flight model, the avionics and weapons systems are still at a medium-fidelity (SSM - standard systems modelisation, I think).

Pitch automatic trim:

I think this is due to an issue with the PTC (pitch autotrim). I believe this is one of the main issues that has been raised and is being worked on. Attitude hold does make it much easier.

I'm sure someone more knowledgable will chime in, but I think the answer to most of those is no, unfortunately. As far as I understand it, although the missiles flight models have been improved recently (AFMs), the guidance modelisation may not yet be up to par. Hopefully this may change with the arrival of fighter aircraft modules.

Just to say that any aircraft can sustain it's corner speed, what it cannot sustain is the maximum instantaneous G at that speed. Although those charts Ethereal showed are really impressive. 8.8 sustained G, that's something! The Su-33 in FC3 can sustain 7.5 G according to my testing. Now I will have to see how those translate in terms of turn rate and turn radius :book:

Maybe, but for the upcoming DCS: 18th Century, wigs will be invaluable :thumbup:

Would be a nice feature, still. Consider the following scenario: You create a dynamic campaign, and create each successive mission using the last one as a Template (pretty handy). Then, for some reason, you need some new country to join the fight (maybe what you did in the last mission made them choose a side - that may depend on your actions). I remember the mod that allowed it in FC2/BS1. I wish it was a default feature. Can someone confirm if it is possible now or not anymore?

No, there is no velocity vector in the Su-33, in FC3 (and I would expect not in real life either). Just check your glideslope and AoA and you'll make it. About trim, for carrier traps, I'd say, don't try to trim your aircraft to the exact slope, but you can trim to lessen your stick deflection. Make it so that you always have to pull the stick slightly aft. Don't overtrim, because you don't want to be pushing the stick forward, and that may induce unwanted oscillations. That being said, I often land and trap untrimmed (but not always).

Clearly the EOS is kinda botched right now, although some great things were recently fixed/added (no gyro stabilization and elevation control). The missiles going ballistic when lock is lost happens, I think, to every missile in the game, and as such is not really a bug, but a simple implementation. Could it be reworked in the future ? Sure that would be great, but it is more of a wishlist item than a bug. If you can show a track where the target aircraft receives a missile seeker RWR warning from 50 km, then I'm sure everyone would agree it's a bug. Firing an R-77 at a target will give him a launch warning from the MiG's radar, as you said, and the launch warning will switch from that to the missile seeker when it goes active. I have always seen ARH work that way in the FC series. On the SPO, you can tell when the switch occurs because the power indicator goes back to zero and starts over. I think the US RWR has a special M indication for missiles (that they indeed should not get from 50 kms away).

Not in real life it ain't ;) If you come too fast, you may either miss the wires (incorrect angle of attack), or possibly break a wire (or even slip off the deck) because the tension was set for a certain speed and weight. Doesn't really matter for now in FC3, though. But the normal way to do it is to use the AoA indexer. You can combine that with the ILS for the slope (either on the HUD or the HSI), because the Fresnel lense doesn't really work.

Yes, it was said that the old map would still be there. Still, it was always my understanding that it would be option a), however awkward it would be. And I don't think I'm alone, just look here for examples. Anyway, great to know that it will be able to run on the new engine. Yes, that is expected, of course.