Redglyph

Wrote a bug report in LN bugtracker a while ago, but no more feedback than here. I suppose this module isn't maintained anymore.

That's probably for the bug section, yes. Could be handy on an Avro Lancaster, but not an F-5 ;)

I also found some discrepancies between the headings (or the distances) in the flight plan and - at least - the instruments, so flying from FYTTR to JAYSN to FLUSH for example will not work with headings 306 then 318, but haven't investigated that yet.

Hello there :) Have you received any news from ED about this problem?

Great material, thanks for sharing it! :)

DCS v 2.0.4.59428.142 A few issues noted in the Bf-109 module in Nevada terrain. * Quick Start mission, Nevada Bf 109 K-4 Cold Start The preset channels are: 1=39 MHz, 2=40, 3=41, 4=42, but the Groom Lake ATC is 38.6 MHz. As a consequence, it is not possible to communicate with ATC. Using the ME to edit channel 3 to 38.6 solves the issue. * Nevada Bf 109 K-4 Takeoff Same problem as above. * Nevada Bf 109 K-4 Free Flight Flight plan lands at Nellis AFB, 38.7 MHz, same problem as above. * Nevada Bf 109 K-4 Dogfight Same, though it's not planned to land. * A in-flight kneeboard sheet, an automated note in the briefing or another contraption to have the frequencies of the preset channels would be handy for the pilot, otherwise he/she doesn't know which channel is set to what. * The structure of the mission folders is a bit redundant and not optimal to find the files, I'm not sure whether it's due to the history of the installed files or the actual structure: Missions ├───EN │ ├───Campaigns │ ├───QuickStart │ └───Single ├───QuickStart └───Training Perhaps one parent folder per terrrain is better?

That's what I thought about AI. I didn't get that with the F-4 or the Tomcat, though the F-4 tended to quickly go up like a rocket and not come back down, if I don't kill this guy on the merge there's a good chance it'll be a draw, with him very high in the sky. Perhaps the F-5 bleeds energy faster with its engine, and the AI tends to get to the floor more quickly to keep the speed up. Still, here it should have been 2 wins per HD, and one per kill, but something didn't register. I should have kept a track of it to understand what happened. 1) I can understand about VR, I haven't got that kind of gear so I didn't realize. For my part it's probably a bit of laziness, being able to listen and grabbing the information is a skill that can be trained, so it should be a good opportunity. For people who are not fluent, ... yes, I suppose you'll need an option. Perhaps using a switch of the cockpit to turn subtitles on or off? ;) Or F10 in the mean time, hoping they add a way to set mission options (that'd be awesome). 2) I suppose it depends on the sound settings, but the ambiant sounds don't seem exaggerated to me, the other jet is right next to the player's after all. If I close the canopy it's fine. 3) Yeah, it's just the way it comes, it's a bit unexpected. The FAM would have been a possibility for the pilot to get a few landmarks before having to navigate by himself. But I do enjoy the opportunity to learn another way to find my bearings :) I had that quite a few times when flying with an AI wingmen, they easily crash into moutains :/ I remember winning against the F-86 in Mig-15's part of the Museum Relic campaign, with no ammo left, just by turning around and grazing the hills ;) Hopefully they'll get better at this.

Love the idea of this campaign! Even more with an F-5 :) I tried the first mission and two times out of three, blue went under the hard deck, even though I was well above (probably 6-8k+). One of those times there was no point attributed, weird. Only got a score of 75 and apparently disappointed the boss ;) Well, blame blue for that. In the practice mission, it went once out of three. That's 3/6, so it seems the AI isn't aware of this hard deck, or very fond of it, is that a limitation of the current AI or something I'm doing wrong? Some suggestions: 1) +1 for the subtitles, it can help sometimes, especially with the two points below. 2) Perhaps waiting before the first messages at the beginning, or starting with a closed canopy could do wonders, in the two first missions the player's aircraft is standing next to another one starting up and the noise makes it impossible to hear the message which starts right away. Now I'll try to close the canopy as soon as possible, but that's not a reflex we have usually developed ;) 3) Navigation in the first mission (FAM) is not obvious, also in some areas the TACAN cannot be received because it's too far. Wouldn't it be better if UZI2 was leading the way? I suppose I'll have to check how to navigate from A to B on a parallel to the radials, that must be an interesting exercise :) But the overall impression it gave me on FAM was confusing. The mission card does not give much information, and there are diagrams scattered through other documents but without much structure or pointers as to what to look for before beginning the mission, and once it starts there is an avalanche of indications the player is simply not prepared to. The briefing says "I'll lead the takeoff but once airborne you will take over as flight lead so you can concentrate on learning the area". Well, it's the opposite I think, the pilot is so busy finding the TACAN, checking the distance, rectifying the flight and so on that he doesn't have the time to focus on the interesting parts. Perhaps it's just me, but it didn't seem as constructive or instructive as it could have been.

The official list seems to be WIP here, for both terrains: https://forums.eagle.ru/showthread.php?t=160746

That's right, thanks! I was either red or blue, but the airfield was neutral! :) I set it to the same coalition and they replied. What got me wrong is the ATC is responding no matter what.

Hello, I don't think I missed anything, but I couldn't get the ground crew at the Tonopah Test Range Airfield to reply or do anything. I haven't tested other new airfields, but I did the test at Groom Lake AFB and Nellis, with the same aircraft and during the same mission, where the crew was responding. Any idea where to set this, is that in a lua script? I didn't see any noticeable difference in the ME.

Great to have new airfields! :) I couldn't get ground crew at TTTR, I don't suppose we need to be on a specific area for that?

Same here, it would be much appreciated to have drag chute and oxygen reloaded with rearm/refuel call.

It's in the following posts, the problem was not fixed (see last post from Ranger79 just above).

I had some funny issues with ending successfully a mission with an aircraft considered by DCS as destroyed. So maybe the same can happen with a pilot ;)

The fact 1.5 is Caucasus and 2.0 is NTTR is "coincidental", DCS supports multiple theatres, it just happens that 1.5 was based on Caucasus, and 2.0 introduced NTTR. So each mission defines a series of prerequisites, including the theatre of operations, that's a line you can find in the mission file. For example, ["theatre"] = "Caucasus" In preparation for the merging of both into 2.5, in which people will have Caucasus, perhaps NTTR, perhaps other future DLCs, all missions are now in both branches, beta and alpha. You'll find missions for Caucasus in 2.0 and vice-versa. This particular training contains missions for the Caucasus map, whether they're in 2.0 or 1.5. So yes, it will work :)

I confirm this file is missing in DCS version 1.5.5.58891.190. It's still there in version 2.0.3.57442.107, so if you have the 2.0 alpha you can simply copy the file in the mean time. Or I can upload it here, I just don't know whether it's allowed or not (and it's a big file, too, 8 MB).

For my part it was SP, and the pilot wasn't dead. Besides, I believe the cockpit view is not available anymore once the pilot is dead.

I confirm (1), had this problem today with DCS version 1.5.5.58891.190, after an emergency landing in which the aircraft took fire. Switching the view to other aircraft or to the external view has sounds, but back to the cockpit and the sound is gone.

It's still the same in DCS 1.5.5.58891.190, I'm not sure this has been reported before. So the elevation units in the map are in metre for the airports no matter what, and not shown for the aircraft and other mobile units. The QNH is now shown, which is nice! But still only in inch Hg and mm Hg, not the bar standard unit. Get your calculator ready! ;)

That's so silly of me :D Yes, I can see it now.

Did you put the correct video link? I didn't watch the entire clip, but all I saw was the pilot looking at the window to stay in formation with the flight leader. If that's at a specific time, could you please tell us so we don't have to go through the entire video? So I think we both agree there is stabilization in pitch and roll when in search mode, but there is a problem with the implementation of the elevation which should be relative to ARL and not the horizon.

bump. Problem is unchanged in 1.5.5.58891.190.

bump :)

Works again in 1.5.5.58891.190, thanks for the fix!