Rongor

I also got that "PCM" in the VTB screen constantly and there is no explanation in the manual about what it intends to tell me

What about using a trigger ?

You won!

Rhein-Ruhr could hardly be left out since at least half of cold war NATO airbases in Germany were west or at least close to it. People shouldn't only focus on American related Ramstein, Spangdahlem and Bitburg exclusively. Cold War air bases would rely on Büchel, Nörvenich and NATO at Geilenkirchen as well. Also RAF bases in Germany like Laarbruch, Wildenrath, Brüggen and Gütersloh.

Maybe start to describe the problem and explain exactly what you are doing. "not working" can mean so many things... Nobody has a clue what is going on by reading what you wrote so far.

If it doesn't illuminate at all even while doing the test, it might be a bug. Depending on how a training mission is scripted, the flashing yellow instructor brackets might continue to light up in case you pressed a button "too early." There are training missions which are waiting for the event to happen only after the instruction text has come up, so cancelling a caution before might then prevent to trigger something the mission script is waiting for to continue the course.

Hey Ugra, in case you read this, please also include the radio navigation installations for 1980s Berlin: NDB: Lubars DLS 413.5 kHz N52.613899, E013.363600 Tegel West RW 392.0 kHz N52.545067, E013.151062 Tegel East GL 321.5 kHz N52.572316, E013.426114 * Helmholtz DBR 347.0 kHz N52.463688, E013.288902 Planter DIP 327.0 kHz Mahlow MW 309.0 kHz N52.344471, E013.387504 Schonefeld SL 299.0 kHz N52.392601, E013.570000 Gatow GW 370.5 kHz N52.469628, E013.138005 VOR: Tegel TGL 112.30 MHz N52.561512, E013.287567 Havel HVL 113.30 MHz N52.461115, E013.142778 Tempelhof TOF 114.10 MHz N52.473120, E013.405401 TACAN: Tegel * N52.461115, E013.142778 * Tempelhof TOF * N52.473120, E013.405401 * * - Tegel East NDB coordinates is wrong by showing the 1990s location. This NDB had been located just within West-Berlin close to the border in the extended TXL rwy 26 approach centerline until the cold war ended. I yet have to find its precise former location - I do have published approximate coordinates for Planter NDB though I still have to investigate its exact location as I did for all the others (literally pinpointing locations), will update when I achieved satisfying precision. - I am 99% TOF VOR had a co-located TACAN and 30% certain TGL VOR did as well. I'm still investigating for original maps featuring these 2 VORTACs. last update 06.02.2025

Schau an, jetzt wird mir auch klar warum Du mir dauernd die A-10C Bugreports abnimmst, wenn Du die ohnehin dauernd fliegst. Braucht ihr bei Gelegenheit Hilfe in Südossetien? Bin momentan stabil proficient...

Airspace was strictly handled according to the Four Power Agreements, under permanent control of a joint center https://en.wikipedia.org/wiki/Berlin_Air_Safety_Centre All allied flights had to follow the 3 defined traffic corridors between Berlin and Western Germany. No NATO aviation here, keep in mind this was based on an agreement between the 4 victors of WW2, not between NATO and the Warsaw Pact. While any failed deconfliction would likely have ended with a Pact/NATO standoff, it was a purely quadripartite issue. East Germany had introduced hgh pressure sodium-vapor-lamps to save electrical power consumption.

Not sure about this. When you look closely at all the other screenshots of the Berlin scenery, you will notice that there are sandbag barricades everywhere, so Ugra seems to create a city which is already prepared for or already in ongoing conflict. I highly doubt the border zone would've remained lit in this case. It would certainly look good and create an eerie resemblance of how these places looked back then.

Beyond transport flights there wasn't much going on with mil fix wings. We had 3 airfields operating in West Berlin: Tegel (TXL-EDDT) was obviously best known for being the civilian airport of West Berlin. Being located in the French sector, French military made some use of it, though nothing noteworthy. The military apron later was handed over to the Bundeswehr for use of the Flugbereitschaft of the DoD (government/state flights) Gatow (GWW-EDBG) was located in the British sector and 100% operated by the RAF. Tempelhof (THF-EDDI) in the American sector was operated by the U.S. military, yet allowing regional civilian flights most of the time. Naturally, U.S. activities were much more noticeable. In the British and French sector (I lived in the French sector until 1985) you could see the occasional patrol of an Alouette (F) or Gazelle (UK). In the American sector, the situation was remarkably different (had moved into the American sector in 1985). I remember vividly how it felt like there was almost always a U.S. Huey not too far away. The Americans certainly did several patrols a day with Hueys sometimes, a stark difference to what I was used to when being in the British or French sectors, where you didn't notice that much military presence at all. I can still remember almost daily battle sounds coming from the Grunewald training ranges, sometimes even tanks did some practicing. Good old times...

of course it's TMS yeah, looking good now. I guess its the same for the A-10C II. I do fly it as well, though currently I am doing some campaigns which only run on the non-II version so I couldn't test. There's some oddity still with the BULL/CURS option. If you select this one, the TAD will conveniently show the bulls bearing/range of the cursor, still the HUD symbology won't show the Bullseye (nor the cursor) as hook. In fact you can then still hook and unhook any TAD symbol as usual, which will affect the HUD symbology as usual. Only this won't be reflected on the TAD. So the TAD will neither show you which TAD symbol is currently hooked (or if there's no hook) and continue (as expected) to display the bulls/cursor bearing and range. In the other hand, the BULL/CURS option only shows bearing/range after any symbol has been hooked. Its unclear to me if 1. the ability to still "secretly" hook any TAD symbol to have the HUD hookship symbol guide you is realistic in this state, 2. this shouldn't happen (and is in fact a bug) or 3. if it should be hooked on the bulls or cursor instead by default, placing the HUD hooksymbol on one of these 2 as well...

Much better. Lending your suggestions, how about this: Of course this version is longer, Though I think it could be worth it, as it pretty much contains everything especially a new player might need to understand the whole concept at once.

The problem with this thread you created here is that you put up a wrong claim as basis. If you would actually go by the FAQ, there would be no room for any of your assumptions and "concern". Not only do you incorrectly point to the FAQ for your claim, the FAQ actually outright states that the module will not be based on guesswork. Your made up 85% are entirely fiction. Triggering unnecessary concerns by commenting on made up stuff is the only thing concerning here. It's the main reason there are so many others

The houses seem to be gone in this build which provided the background for Wags' AMA YT video thumbnail. Of course the forested area should rather be a park

Exactly. You are focusing on a situation in which the current SPI has been designated by a hooked TAD object already. Which the manual also seems to expect: It's actually claiming "Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when you have hooked a TAD symbol with the cursor", which is worded problematically, as you really don't have to have a hooked TAD symbol for the Hook mode to display on OSB18, you only need to move the TAD cursor over any TAD object, regardless hooked or not. SPI'ing is neither a requirement for hooking nor is the manual addressing the SPI status at this point. The problem isn't the manual mentioning how the SPI will move from one hooked object to the next if it has been designated on an initial hooked object. The issue is the manual providing this info at a point where the reader expects to learn what happens when an object gets hooked. The optional prior SPI'ing is left out in this explanation, while actually being a precondition for the claim the manual is making. So either the "SPI is moved over the hooked object" should be dropped from the text entirely, or it should be added further down as an optional use case for when the pilot has designated the current SPI by any hooked object. Designating a SPI by the TAD isn't required to hook anything. Only precondition for hooking is setting TAD as SOI. The manual doesn't mention this requirement. Instead it claims hooking would place the SPI over the hooked object. Which is not the case. So it shouldn't be mentioned this way in the first introductory paragraph as if it was.

I think this thread entirely runs on subjective feelings and has nothing to do with anything factual around what ED is doing. ED and its 3rd party devs are creating modules for DCS, depending on the access of documentation. Nothing has changed. Just carry on and enjoy DCS.

Not on my end. Even with TAD as SOI, hooking any object won't make it SPI. The reason for this is hooking being performed by DMS up short. Only DMS up long would set the SPI at that currently hooked object. The green part is correct though.

page 308 claims the SPI would be placed on a hooked symbol This is not the case and it would annoyingly affect a current SPI if it was.

These videos are regularly mixing any DCS assets and are not intended to focus on modules supporting only a specific timeframe. Since map modules are separate from aircraft modules, its really up to the players and server hosts to decide what to mix and what not.

These houses shouldn't be there at all, not even in the 70s. I think after WW2 rubble had been removed, no houses have ever been there. Btw (common misconception), Alexanderplatz is on the other (east) side of the railroad, the area north of the Rotes Rathaus which includes the TV-tower is west of the railroad and not the Alexanderplatz.

unfortunately not yet, hard to narrow it down Judging by this still image from the video, we can expect an 80s version. This Terminal at then Berlin-Schönefeld airport (east German) had been opened in 1976 I think, so the possible time frame is from 1976 to 1989

All good fellow pilot, as a Berliner, I'm happy to help. Imagine my excitement about this map coming, great times!

Doesn't matter as I've lived in Berlin during Cold War times already and the width of these roads didn't change. The segment shown between Siegessäule and Brandenburger Tor has been this wide since before WW2 as it had been part of the Ost-West-Achse in the infamous Germania layout. You will find cold war pics showing the same width, I only chose recent pics because they are much easier to find.