Redglyph

It's not at low altitude, the same is happening at 20k or 5k.

It seems that in mission 5, the M-2000's used to test the lock feature tend to get to the deck and crash in the relief, same old AI inability to cope with mountains. In two missions, I couldn't get behind without them crashing first. Perhaps it would be simpler to be able to follow friendly aircraft and not have to worry about this? Or alternatively, to make sure it happens above flat terrain to avoid the AI problem (I hope they'll improve). Not that I would be able to lock, since the echo disappear after a few seconds on the radar (and I don't know why), and I can't get the slew TDC to move at a reasonable speed, it directly jumps from one part of the VTB to the other. If others have the same problems, perhaps it's worth giving some advice in the training mission, but perhaps it's just me.

I did, and since the targets are visible after cycling PCH/EM I don't think it's a matter of not getting the echo. They just disappear after 15". It's apparently the same in DCS 2, perhaps it's on purpose, I have no idea. Another annoying thing is the TDC cursor, it doesn't seem possible to limit its speed, and it's frankly too fast to use for me. It seems all-or-nothing despite being mapped on an analogue device.

True enough. Thanks again for the references, that book would fit very nicely under a Xmas tree ;)

Great idea, gregzagk, looking forward to it! :)

Thanks for the tips! Actually, as a suggestion, it would be great to get some of those pointers in the missions. It's nice to give such an experience and allow the virtual pilots to try different approaches on their own, but it would be even better to take this opportunity to introduce advices or sketches of a lesson before each encounter. Could be as an option (F10), with a dialogue on the way to the encounter, or as a documentation.

DCS 1.5.5.59744.197 I find those tooltips useful, especially in training missions when you are not yet entirely familiar with all the switches. However, they seem to be disabled in this case, except if I run the training mission from the mission editor. It is enabled in my general options. I've checked in the ME and this is not forced in the mission options. When I'm running a mission from the "mission" menu, I have the tooltips. It might be a DCS bug. Anyone else has the same behaviour?

Hello, DCS version 1.5.5.59744.197 I'm following two aircraft, same level, I'm about 3-4 nm and they're at my 12. If my radar was already switched on (EM), nothing appears on it. If I switch it off, then on PCH for 1-2 seconds, then on EM, I see the contacts for 15", after which they disappear again. I can repeat that as many times as I wish, it's pretty consistent. Is that normal behaviour? Perhaps I missed something, but I'm pretty sure it wasn't behaving like that earlier. How can I keep those contacts permanently? The radar is set as follows, though I've tried different settings: - med PRF - 4 bars - 60° sweep - 5 nm range

It is there, I was talking about the PREP part, sorry for the confusion! It's probably obvious anyway, editing anything on the PCN is related to the PREP side. Not even halfway into these trainings and already learned many interesting new features, very well done! :)

That, or ... you have a non-beta version :lookaround: That was my guess, but so I still believe this instruction was missing, or did I overlook it? Anyway, nice to see those training missions, because this wasn't particularly easy to follow in the manual.

I was busy posting the same here, so I didn't see it. If I'm not mistaken - TOP: you need to enter the correct waypoint in PREP, otherwise your time is outside the admissible range (with a wrong waypoint) - RD: I have the same problem, probably not implemented yet.

In mission 3, there are a couple of things that could be confusing: 1) Using the RD/TD to set a desired time: it seems to only work when the correct waypoint is selected with PREP. Probably obvious once it becomes a routine, but not said (or I missed it) and I was wondering why there was no "special" indication on the HUD. Quite easy to guess though. 2) The next part is to arrive to Kutaisi from the North, the pilot is said: Let's try to approach press 1 or 7 on the INS keypad to enable data input into the left LCD. The input limitation in this case will be obvious - from 0-0-0 to 3-5-9.9; there are four spaces which you have to use. Enter 1-8-0-0 on your keypad and press INS button. Remember that what you enter here is the bearing you will want to use when you arrive at the waypoint. So for instance if you want to approach the waypoint from the east, you will need to enter bearing of 270.0 as effectively you will be flying west. Press the RD button on the PCA. You will notice a new set of cues on your HUD, similar to those displayed during the bombing run. You should follow them in order to arrive from the desired direction. I suppose the knob should still be on RD/TD and waypoint 3 in PREP. I could enter 180.0 degrees, but pressing RD on the PCA didn't show any special indication to get there. I moved a little further from the airfield to make sure I wasn't simply too close, but without success. I also tried with APP, but nothing special either... so I haven't clarified this one :huh: Note: I suppose it's "Let's try to approach Kutaisi from the North. Press 1 or 7...", unless more is missing, including what to press? And it should be LED, not LCD (but that's from the manual) ;) EDIT Ah. Manual pp. 127: "RD: Roue Desirée, desired route. A special navigation mode not available in open beta." Perhaps this explains that?

OK, thanks!

Hello, Just a simple question, at the end of training mission 2, there's a mention of a "TAS ranging keyboard bind", I have absolutely no idea what or where this is. It's not in the list of the controls, so I can't quite put my finger on it ;) (no "ranging", no "TAS", ... ) It's mentioned a couple of times in the manual, but not what it is, where to find it in the cockpit either. Since the tooltips are currently not working with the M-2000C, it would still be difficult to find that way anyway. "With PCA in NAV mode, press the OBL button. A diamond shaped designator cue will appear on your HUD. Wait until you get close enough to the landmark, then maneuver your aircraft to put it the diamond directly on it and click on the TAS ranging keyboard bind. Remember, that you should have your both your radar and radar altimeter set to on." Anyone knows?

Usually calling the ATC and aborting the take-off solves the problem. Then, once the wingman resumes, you can ask for clearance again (which is optional).

I tried that with one mission but that didn't seem to solve the problem. Perhaps I messed up in setting the radio control at the same time (though I doubt it), will try again.

Should be in today's update \o/

That seems epic, poor instructor! :megalol: I must admit I may have killed a couple with a HO, ... killing myself in the process. I must have got that bad habit from a known youtuber that does it frequently in IL-2 (not the killing oneself part). Have fun out there!

My mistake then, it seems my teasing backfired. He's a French with a (somewhat concealed but still detectable) nice English accent, which is more than what we can say for most of us :)

Great seeing the training missions and the campaign! I can't believe they skipped that in the week-end news, that's the news for this week AFAIC :) Funny immitation of French accent in the training missions, but it's clearly not a French :D You should've asked, there are many here.

Well, if you want to survive a fight, never rely on fairness :D

Nothing is enforced so you should be able to use them, though they aren't really necessary, the other aircraft is easy to spot even without enlargement :)

Yes, not easy those ones, and I can't even imagine the following ones! You have to try different solutions after the merge, but what helps enormously is to hit them at that moment (which is pretty dangerous).

Not sure, ED probably needs to break back-compatibility now and then, when bringing new features or necessary refactorizations, but I never had so many problems with another module. Yes, the fact running missions from the ME (but not when saving them) solves some of the issues is weird. It wouldn't be enough for the first training mission, which is broken beyond any hope ;) A little sad for a first contact with the aircraft. I should probably have a look at how the missions have been designed when I have some time.

It's a known bug with the Mig-15bis, if I push the stick back it goes forward, if I push it right it goes left (back goes back and left goes left normally). Sometimes it "jumps" in a glitchy way. As soon as you taxi a little bit, the controls are back to normal, don't worry. In any case, I don't think it has anything to do with the campaign. Or perhaps it's the "campaign mode", no idea. Or it's linked to the load, who knows... the secret life of a bug is a strange one. I think I never saw a reply from Belsimtek regarding this bug. But then again, it's Belsimtek ;) Example of similar reports: https://forums.eagle.ru/showthread.php?t=176368 https://forums.eagle.ru/showthread.php?t=175912 For ex.