Bourrinopathe

Yes it's been reported >>> example <<<. ED is probably going to fix it asap. A moderator should move these posts or delete the thread to avoid cluttering. Thanks ;)

Excellent work! I made a pdf out of it with some color coding and translation adjustments. >>> DCS russian terms addendum <<< I've used the corresponding Bitchin'Betty's warnings where available to ease the English <-> Russian transition. (I've never used Betty in a russian aircraft though - what a weird idea :lol:) We just miss a few audio warnings. I will try to process the missing messages with a voice recognition guinea-pig but the results may vary! Thanks for sharing!!! :clap_2:

The russian manual is not yet available. We'll have to wait for the next update. ;) (unless some lucky one already has a WIP-version) Thanks for your suggestion anyway!

Fantastic! Thanks a lot! That's really helpful. I was struggling with that one. (and I need the russian terms for an audio file using some voice synthesis.) Learning the different russian warnings should be part of the training to fly the Su-27 :thumbup: I'm eagerly waiting for your translation table! (in the meantime, I'll try to find that FC3 russian manual (nothing in the english one)). [EDIT: the FC2 russian manual has a few messages but it's not up to date - DL here - pages 239-240]

Hi there, I'm looking for the "nagging nadia" warnings russian text messages and the corresponding phonetic transcriptions. The audio files are available in that folder: \DCS World\Sounds\Speech\Sound\RUS\Common\Betty\Messages There's a "VOICE MESSAGES AND WARNINGS" section in the DCS Su-27 manual, but everything is in english. All I managed to dig out of the internet is that .pdf with some messages (from the venerable Lock On). >>> direct download <<< Example: Unfortunately, I'm not familiar enough with the russian language to find the right cyrillic spelling by ear. I tried to find the "bingo fuel" cyrillic message by myself and that didn't go too well :megalol: робирщ басврата <-- see? that does not even exist! (said Google) (it's different from Lock On) So if there's a valid transcription somewhere (with the russian text), please help me save the few neurons I have left! Thanks!

Here's the fuel gauge warning lights with the corresponding fuel levels: And that's the note next to the HDD: I only tested the first warning light and it's on with 5014kg left (not 5590kg as suggested in the note). (Su-27 for DCS 1.2.14) UPDATE: the in-game values are: Бак 4,1....5014 kg Бак 3.......4004 kg 1.5...........1504 kg Бак 5.......1004 kg 0.6.............604 kg Based on the Su-27SK manual, there should be 4 fuel tank groups: Схема расположения топливных баков The Su-27 has a rather precise fuel consumption sequence elaborated to preserve its maneuverability/balance (Center of Mass (CM)) (depending on the initial fuel quantity): Based on the sequence, the first warning light is on when the tanks 4, 1 and most of the wings tanks are empty (tank 3). On the fuel gauge, the lights do not exactly correspond to an empty tank (=Бак): Б4,1 probably stand for Бак 4 and 1 (9400-5014=4386kg --> Su-27SK tanks 1+4=4180kg | that's close enough ;) ) Б3 obviously stands for tank 3 (5590-4430=1160kg (using the note | close to the Su-27SK manual (1060kg))) 1.5 is the 1500kg warning (+ vocal warning message) Б5 (880kg warning (note)) should mean there's a tank 5 (?) there's a 800kg vocal warning message too. 0,6 is the bingo fuel last warning (w/ vocal warning message and bingo fuel vocal message) The fuel measurement has an accuracy of ± 170 kg. Game/sim-wise, it's pretty straight forward and there's really no problem using that gauge. The fuel is burning, the light goes on, ok there's roughly that fuel quantity left. Done. But I'd like to know if there's a specific known structural fuel system schematic for the Su-27S? Or if anyone could confirm there's a tank 5? (or what it means) (I'm curious) And if you have the exact value for the fuel quantity left for each warning lights, please do share :thumbup: (values added above) Any detail would be appreciated. Thanks!

{"su27_tex01_BN31", 0 ,"xxx",true/false}; is the first number background (main front texture used) {"su27_tex01_BN31", 3 ,"xxx",true/false}; is the first number (empty or numbers .tga file) {"su27_tex01_BN32", 0 ,"xxx",true/false}; is the second number background (main front texture used) {"su27_tex01_BN32", 3 ,"xxx",true/false}; is the second number (empty or numbers .tga file) The su27_detail and su27_detail_compos references are not necessary (I've tried on a few liveries - it uses the default texture).

Apparently, it affects every Su-27 skin, yes. Of course it's a bit cumbersome to change every description.lua, but ED have certainly changed the structure to improve the liveries system. All our liveries are a few copy/paste away. I'd suggest a free software like Sublime Text to edit the files. The dual pane is a treat when you want to chain-copy/paste: Notepad ++ is also a very competent tool. It may be part of the DCS World 2 improvements. Hang in there. ;)

Thanks a lot for the test LJQCN101! I've highlighted some values on this one: standard atmosphere used I was interested in the Mach number for the max sustained turn rate. The highlighted "21°/s" is just a rough value. It's easier to remember. (thanks to Esac_Mirmidon for the original file and information)

Fixed! I have simply checked the Su-27 stock skins description.lua What's changed is the BN31 and BN32 with the "index" 3: {"su27_tex01_BN31", 0 ,"Su27_tex01_BW_Bourrin",false}; {"su27_tex01_BN31", 3 ,"Su27_numbers_BW",false}; {"su27_tex01_BN32", 0 ,"Su27_tex01_BW_Bourrin",false}; {"su27_tex01_BN32", 3 ,"Su27_numbers_BW",false}; I don't have the time to test and identify the difference between BN31 and BN32. But the nose number is visible from any distance. Here's the Su-27 Air Force Standard livery definition: livery = { {"su27_tex01", 0 ,"Su27_tex01",true}; {"su27_tex01", 3 ,"empty.tga",true}; {"su27_tex01_BN31", 0 ,"Su27_tex01",true}; {"su27_tex01_BN31", 3 ,"Su-27_numbers_red",true}; {"su27_tex01_BN32", 0 ,"Su27_tex01",true}; {"su27_tex01_BN32", 3 ,"Su-27_numbers_red",true}; {"su27_tex02", 0 ,"Su27_tex02",true}; {"su27_tex02_compos", 0 ,"Su27_tex02",true}; {"su27_tex03", 0 ,"Su27_tex03",true}; {"su27_tex03_compos", 0 ,"Su27_tex03",true}; {"su27_tex03_compos", 3 ,"Su-27_decol",true}; {"su27_tex04", 0 ,"Su27_tex04",true}; {"su27_tex04", 3 ,"Su-27_decol",true}; {"su27_tex05", 0 ,"Su27_tex05",true}; {"su27_tex05", 3 ,"Su-27_decol",true}; {"su27_tex06", 0 ,"Su27_tex06",true}; {"su27_tex06", 3 ,"Su-27_decol",true}; {"su27_tex07", 0 ,"Su27_tex07",true}; {"su27_nose_numbers", 0 ,"Su-27_numbers_red",true}; {"su27_tail_numbers", 0 ,"Su-27_numbers_red",true}; {"su27_tail_numbers_top", 0 ,"empty.tga",true}; {"su27_tail_numbers_down", 0 ,"empty.tga",true}; {"su27_detail", 0 ,"Su-27_detail",true}; {"su27_detail_compos", 0 ,"Su-27_detail",true}; } countries = {"RUS"} Thanks again for your help. You showed the way :thumbup:

I tried it and no nose numbers visible up close or zoomed out. I'll try different manipulations later. Thanks for your help Mainstay!

From \DCS World\Bazar\Textures\Su-27.zip the numbers texture have a bigger size (2048x256). My texture is smaller (1024x128 ). I'll try a bigger size and report back. [EDIT: no luck with the size or file type (.dds or .tga)]

Thanks a lot Mainstay! Almost there! I added the BN31, BN32 and the detail/detail_compos with the corresponding .dds file. No more messed up texture. The nose number appears while zooming out, with the first distant LOD model. I was suspecting something like a bad reference file but I couldn't find any reference in \Bazar. Here's what I have now: livery = { {"su27_tex01", 0 ,"Su27_tex01_BW_Bourrin",false}; {"su27_tex01", 3 ,"empty.tga",true}; {"su27_tex01_BN31", 0 ,"Su27_tex01_BW_Bourrin",false}; {"su27_tex01_BN31", 3 ,"empty.tga",true}; {"su27_tex01_BN32", 0 ,"Su27_tex01_BW_Bourrin",false}; {"su27_tex01_BN32", 3 ,"empty.tga",true}; {"su27_tex02", 0 ,"Su27_tex02_BW",false}; {"su27_tex02_compos", 0 ,"Su27_tex02_BW",false}; -- top {"su27_tex03", 0 ,"Su27_tex03_BW",false}; {"su27_tex03_compos", 0 ,"Su27_tex03_BW",false}; {"su27_tex03_compos", 3 ,"empty.tga",true}; -- right wing {"su27_tex04", 0 ,"Su27_tex04_BW",false}; {"su27_tex04", 3 ,"empty.tga",true}; -- left wing {"su27_tex05", 0 ,"Su27_tex05_BW",false}; {"su27_tex05", 3 ,"empty.tga",true}; -- bottom {"su27_tex06", 0 ,"Su27_tex06_BW",false}; {"su27_tex06", 3 ,"empty.tga",true}; {"su27_tex07", 0 ,"Su27_tex07_BW",false}; {"su27_nose_numbers", 0 ,"Su27_numbers_BW",false}; -- specific design nose numbers {"su27_tail_numbers", 0 ,"empty.tga",true}; -- no standard tail numbers as it overlaps the BW sign {"su27_tail_numbers_top", 0 ,"Su27_numbers_BW",false}; -- specific design tail top numbers {"su27_tail_numbers_down", 0 ,"empty.tga",true}; {"su27_detail", 0 ,"Su27_detail_BW",false}; {"su27_detail_compos", 0 ,"Su27_detail_BW",false}; {"pilot_SU_body", 0, "pilot_su_BW",false}; -- modified helmet and patches } name = "Beta Wolves (Bourrin)" countries = {"RUS"} (I can't rep you more apparently. I'm not famous enough ;) )

Hi, I have a texture display issue since the end of the last year. Probably after an update. Upper left: close view: the nose number should be red. I've checked the description.lua, the related texture (Saved Games\DCS\Liveries) and everything seems fine. I didn't change anything at all. Upper right: zoomed out: the aircraft textures are suddenly placed incorrectly. Lower left: close view: AI aircraft, same mission (it's the first Su-27 tutorial mission). This time it's all messed up in a close view. Lower right: slightly zoomed out: the textures are in place and the nose number is not blue but red. The issues are consistent in every mission I start. It does not seem to affect the other 3D objects. I first tried to repair my installation to no avail. Then I uninstalled DCS and its modules, and reinstalled it. The only thing that remains from my former installation is the Saved Games\DCS folder and the JSGME mods folder in the DCS installation folder. I know it was fine before a specific update but I can't identify the problem. I'm using FC3 + DCS World latest version (1.2.14.35734), no mods. Otherwise, I have no specific hardware issue. Is that a known problem? (I couldn't find anything relevant) Could anyone think of a fix of some sort? Any help will be greatly appreciated. Thanks!

For a non-EU customer: Fat Black Mamba: $350 Black Mamba PRO: $300 (please verify the prices with VKB) You will have to add the taxes and shipping cost. Afaik, it should be shipped using a DHL international parcel.

Thanks for the info on the macros. I managed to map one on a button but I couldn't find any way to record/define that macro anywhere. Fortunately, I don't think that's a major feature many simmers would use. So far, the Black Mamba has been a perfect match to fly the Su-27 with the default profile and the correct mapping within DCS.

@Burnett: Hi, The firmware versions can be downloaded from their FTP (as well as the documentation and softwares) >>> Mamba firmware <<< (the recent v1.59A firmware you can see in the screenshots has been directly provided by VKB - I don't know when they'll upload it on the ftp) (don't hesitate to contact VKB) @Harle: My pleasure ;) The modifiers are mapped as : SHIFT --> momentary (without "track as button"). The lack of documentation is VKB's weak point. Otherwise the hardware is top notch. Same goes for the software even if the Device Config software isn't particularly intuitive (to say the least). Among other things, I still have to test the macros feature, though…

Thanks for sharing your profile. I have completed a 3 MODES configuration using the 3-position slide switch (as modifiers). It does not modify the PoV hat and the encoder inputs except for the button. I've used the VKB button tester as a visual reference and configured the three modes separated in three groups of two rows. MODE 1 --> buttons 1 to 15 (button 15 is the encoder button - 16 is not used) MODE 2 --> buttons 17 to 31 MODE 3 --> buttons 33 to 47 For example, the trigger (button 1) changes to button 17 in MODE 2 (VIS) and button 33 in MODE 3 (BVR). One important thing is to define the maximum number of logical buttons in the Global tab: Here's the logical layer: The last logical button (#47) is the encoder push button (configured in the reference #55). You can define the logical button on any reference you want. As you can see, I have many grayed out references because I kept a clear visual reference based on the button tester layout. I did not modify the PoV, so it triggers the same commands in each MODE. The encoder (buttons 13 and 14) kept sending the signals in the three modes. It may be how it's encoded, because if you don't assign a new logical button to each push button in each mode, they don't send any input in the new modes. I hope this description can help you in your configuration, but keep in mind that I own the Black Mamba PRO and I don't have as many buttons/rotaries/... as you have on the joystick base. >>> my 3 modes config file (experimental) <<< (it behaves like a joystick with 30 buttons, 1 PoV and 1 encoder with two inputs (L/R))

Great video as always! The focus on the real procedure relative to the switch position is a nice touch. Thanks Rich.

Hi Harle, I didn't try a full three modes configuration myself. I only tested a configuration using the momentary SHIFT function on a selector position (S1). Then I assigned a Shift button to the physical layer so that it activates a logical (virtual) button previously defined (in the logical layer tab). Not a fast method but it seems to work without any issue as the device uses virtual buttons (up to 128 with the NJoy32 PRO controller). I've just checked the result with the VKB button tester. What configuration did you use? (I'm not sure I'm doing it the right way.)

Hi there, I'd like to know if any of you is using a complex configuration with the Black Mamba, and, for example, using the selector switch (BVR/NAV/VIS) as a mode selector (and thus modifying every other button and hats accordingly)? Would you use a printable reference layout? (A4 or A5) Or even a tablet-ready reference image?

I'm just discovering you're working on the Su-27 and Ka-50 missions and I'll gladly buy your productions ASAP ;) Good luck in producing high quality missions!

Learning a language is a long process (unless you're gifted). For the Su-27, you could just learn a few words to catch the important orders without reading the subtitles (too much). For example: copy, target, group, engage, etc. (and some numbers). Nevertheless, it would be near impossible to catch that kind of conversation with only a few words: (from the campaign teaser) I hope there will be several exchanges like this one in the campaign. It adds a very welcome human dimension to the typical military jargon. (and I think I would never have bought the campaign if it had been voiced in english ;) )

Difficulty-wise, would it be better to complete the Fortress Mozdok campaign first?

More Su-27 in my Su-27! A Su-27 new complex campaign with russian voice over was an insta-buy for me. :thumbup: I'm really happy ED produced this kind of content. Of course, I have no idea about the quality yet, but I'm confident ED would release a high standard content. No problem whatsoever in the buying process: DCS website --> E-Shop --> buy/payment --> launch DCS --> Module Manager --> the installation popup suggests I download the campaign --> DONE and ready to play. It weights 44.7Mb. I won't have the time to play it until a week or two at best, but my Su-27 thanks you immensely! Additionnaly, I think the shop would benefit from some screenshots, even if it's difficult without spoiling the content. May be the first briefing pictures and descriptions ?