P5138

Loving the skin. I just modified the generic version with working bort numbers to fill out the squad for those of us (probably only me) who actually use them: If you want, I could send you the Bort decal file, so that if you were to decide to make a generic 9./JG53 version with the group bar and bort numbers... :music_whistling:

Just to verify it a bit more, we did another high-altitude flight, going up to just above 30K ft, and the 109 was not contrailing for anyone in the formation.

I was flying in formation with a pair of 109s on the Virtual Aerobatics server while I was in a 190, and at around 25000 to 27000 feet, the 190 began contrailing. Neither of the two 109 contrailed. One of them, to check the contrails, went up a few thousand feet more (to around 30K ft), but still contrails didn't start. All 3 of us in the flight didn't see contrails for the 109s at altitudes that other planes were producing them. Did the 109s have such contrail characteristics? Here's a screen cap showing what I'm on about.

I am unsure if this is actually a bug or not, as I don't own the module yet to check (c'mon Steam release!), but I'm having issues fully preparing Bf-109s in one of the missions I'm creating: I set the 109s to be clients, but I do not have access to the Radio tab in the editor to set the 109's frequencies, like I do on the 190 I own. Is this normal, or should there be a tab there even for people who don't own the plane, so they can incorporate it into missions fully?

Unless I'm missing something, there is currently no way to put single-digit numbers on the 109 using the bort# on the generic stock skins. Unlike the FW-190, filling in a single digit for the 109 puts a leading zero on the side. Ideally this should work like the 190D in that the Bort shows up to two characters, right justified against the +. Also, though this is more of a request, is it possible to expand the Bort settings to allow some alphabetic input to allow for Rank Marks in the area so that there could be officers within a staffel without having to either create specific liveries or a new character set for a designated officer livery? (This is also an issue on the 190). In other words, making it so we could fill in the bort# for two planes with, for example, A2 and B4 and the plane markings would show up as "<2+" and "<|4+" respectively.

I started playing around with the Borts for the P-51D and the Dora a few days ago, as I was woefully disappointed with every aircraft on servers having the number 10. After some experimentation I have found out this much (these are my notes, and may be incomplete in some places): Mission Editor Bort# Parameter Translation for P-51D: ABCXYZ AB=Squadron Code corresponds to the pairs of P51D_BORT_NUMBER_FRONT (Most used, directly in front of the Roundel on US planes) P51D_BORT_NUMBER_REAR (In the area of the Roundel on US Planes; No idea why this is here, or for that matter, why these are split into sided groups.) C=Plane Digit (36 options 0-9,A-Z) (All three of these are set to the same value): P51D_BORT_NUMBER_COCPIT_01 (Under the windscreen area of the cockpit; used in Canadian skins) P51D_BORT_NUMBER_TAIL_01 (Directly Aft of Roundel) P51D_BORT_NUMBER_FIN_01 (On After section of Vertical Stabilizer and Fore section of Rudder) XYZ Tail Code P51D_SERIAL_NUMBER P51D allows for Bort assignments from all alphanumberic digits onto each decal location. theory: Decal Files are any size, but split into the pieces that they need and parsed based on the bort input. observation: this may not be entirely correct of the P-51; characters in the tga files are not laid out on a grid, but are instead laid out with equal spacing between letters. The "characters" in the file, can therefore, probably be any size, but must not have any empty columns until the 64 or so pixel break between characters. theory: A 36-section file of icons will be split into sections for 0-9 and a-z. These are probably parsed in an order defined by DCS, and the order is not adjustable by skinners. observation: This is correct. I'm fairly certain the shapes of the individual characters don't matter, just the order of them. By the way, all this corresponds to the third row of each bort section, the "DECAL" Line. In the DECAL Line you define what file is used to create the Bort Characters. In the first two rows, you define, probably, though I'm not sure, the diffuse map and the specular map for the characters. It's probably best to not change these lines. To give an example, I filled in the Bort Parameter as follows for one of my planes with the 364FS, 357FG skin: C5Z853 This, on the Stock Skin, shows up as follows: As can be seen, the "P51D_BORT_NUMBER_FRONT" area shows "C5" designating the 364th, the "P51D_BORT_NUMBER_TAIL_01" section shows "Z" to mark this specific plane, and the last 3 digits of the tail correctly mark this as number 853.

This may help. Fanatec makes a set of pedals for driving sims that use a shock for the brake pedal, and this is a suggestion for an improved shock from some users: http://www.isrtv.com/forums/topic/11365-clubsport-pedals-2014/?p=109433

Thanks for the video. My father was a crew chief in the 128th, and I never knew about this, which is odd, because he accumulated just about every photograph and video taken by anyone in the unit that he could contact. In fact, I made a few liveries for the 128th AHC in DCS of one of his choppers along with others that I could find decent shots of. Here's a shot of one of them in DCS. (The liveries are still very much a WIP)

I'm using the app, and except for a couple issues it's working without a hitch (the compass shows the wrong value and my lua script to activate the export isn't working in missions with selectable aircraft). The answer to your question is you paste exactly what follows after the colon, modified for your directory structure: dofile( "C:\\Users\\[username]\\Saved Games\\DCS\\Scripts\\telemetryUH1H.lua ")

Would you mind sending a PM to me too? The first mission is still giving the same error at MediaFire.

An easy way to find out is to check the throttle handles (and listen to the engine RPM) while on the ground as you go up in throttle. Once you start to go into the latch where the throttles lock into auto you'll hear the RPM drop and auto mode is engaged. (I think it's a little bit above 75%) Once you find it, you can just note the location in the future.

I've got the same problems in XP with the stock campaign. Also in Admin mode. I've been trying to figure it out too, but can't seem to make sense of it.

Speak to a Russian and most likely they will say that Russia won the war and the other allies just distracted the Germans while they did all the hard work. I wanted to also add that it isn't terribly difficult to learn the Russian alphabet and phonetics proper, it would take a week, at most. I'm just saying that even after 3 years of being in university-level Russian I still can't pronounce things correctly much of the time. Also, with the Russian pronunciations, if you have a copy of the Russian version and go into the tower sounds directory, you'll find a few of those places read out by native speakers. (Along with a bunch of other basic words...)

Sadly, most of those words are already spelled as phonetically as you can get without using Cyrillic characters. The only help I can offer is that, for the most part, the letters in those spellings are pronounced like Spanish letters in the pronunciation of the word, that is: i = ee (or "hard e", in English) o = oh (or "hard o", in English) u = oo (or "hard u", in English) e = "yay" (if stressed), otherwise "ay" a = ah (or "soft a", in English) Consonants in those spellings are pronounced the same a English and the oddball characters that Russian has (й, ь, ы, and to a slightly lesser extent ъ, and щ) are practically impossible to convey through a written, online discussion. At least I can't think of how to describe them in words. I will exemplify this with the note that in those spellings, the apostrophe " ' " represents the Russian soft sign (ь) which gives a "soft" pronunciation to preceding consonants. This is a really tricky part of the language because native English speakers don't hear a difference between soft and hard consonants but it can change the meaning of words entirely. (I should probably add that I am not a native speaker, so anyone who has more expertise than me should chime in if I made a mistake above) Also: Min. Vody is an abbreviation for "MinerAlnie VOdi" (I've capitalized the stress on the proper syllables, I think); it's duplicated on your list.

PM: "Private Message"; like an Email but for use on forums. If your forums are stuck in Russian (which mine are), then it will be called (phonetically) "Lichnoe Soobschenie".

I thought it would be interesting to have towers, at least those at civilian airports, set to their "correct", real-life frequencies. So far I've collected a tentative list: Anapa 119.8 Krasnodar_P 120.6 Sochi 118.5 MinVody 128.0 Nalchik 118.3 Batumi 120.0 Kataisi 125.5 Does anybody know where I can find the frequencies for the other airports?