Leaderboard

Looks like the A-10C has gotten another comm upgrade to the AN/ARC-210 Gen IV Warrior Programmable Digital Communication System. This is a pic of an a-10c from the 188th with the new radio instead of the old arc-186 used for FM in DCS a-10c. If ED ever plans to have an A-10C 2.0 patch like black shark i would find it cool to keep the jet up to date as much as possible and include the new arc-210. Here is some info about the radio. http://www.imrex.com.sg/Products/128/416/AN-ARC-210.aspx

BS2 EN - Russian Voice pack (~70 mb) Copy the archived RUS folder to \\Sounds\Speech\Sound in your BS2 folder. All Red Coalition comms will now be in Russian (English subtitles will still be present) Nate

That was quick, enjoy. EDIT:- Added to mod forum too http://forums.eagle.ru/showthread.php?t=81232 Nate

Конечно нужно...РП тебе диктует давление аэродрома на который ты заходишь. Даёт оно то, что ты видишь правильную высоту на данном АЭ на который садишься, например в условиях плохой видимости(СМУ). Чтоб не было такого: ты заходишь на посадку, например в тумане, на альтиметре у тебя 1500 ft., а ты вдруг столкнулся с землёй.

BlackShark 2 NOT !!.. Simply adding a number to the end of the title and slapping a price on it does not make it a new game. This is simply an update with a price. Number of supporters for your products just dropped by 4 :)

I bought a Warthog in late September and it took me about a full week to get my TARGET profile up and running, as it took me some time to learn how to translate my "thinking in Foxy" into TARGET syntax. Since then, though, DCS was crashing on me every single time I ran it, anywhere from 5 to 30 minutes into a flight. I suspected it was due to my Warthog not being set up correctly and "flooding" DCS with keypresses, but it was only yesterday that I finally got it all worked out and the problem solved. I figured it might be worthwhile to compile a bunch of the useful info that I've come across in learning about TARGET; if I'd had all this info in one place when I started, I could have saved an immense amount of time. While the official TARGET documentation is useful, I found that it inexplicably left out information that, for my uses at least, was absolutely critical to setting up a profile. If you plan on customizing your HOTAS layout for DCS using TARGET, I would highly recommend that you read its documentation first. After that, but before wasting hours trying to straighten out your confusion, come back here and re-read the info below. I should note that pretty much ALL of the info below comes from other people on this and the SimHQ TARGET Programming forum, people like ivanwfr, PeterP, etc. All I've done is gather it all together in one place. Note that in the following, when I talk about using TARGET, I'm talking about using the Script Editor, not the GUI. Although the GUI is probably 'easier', the Script Editor makes it much easier to utilize the incredible flexibility and power of TARGET. So here goes: First and foremost, there seems to be a lot of confusion (myself included, at first) about the different usage options for the Warthog within DCS. They are as allows, in increasing order of complexity: 1. Pure plug-and-play, i.e. pure DirectX mode. The result of an impressive collaboration between Thrustmaster and ED, you can simply plug in the Warthog, completely forget about anything to do with TARGET, and when you start up DCS, "everything just works". All of the buttons and axes on both the joystick and throttle will automatically be assigned to their correct functions in-game. So if you want your Warthog to faithfully mimic the real A-10C HOTAS and not do anything else, this is the option for you. Although convenient, this method also has a lot of limitations. For example, although in DCS you can assign a joystick button to act as a 'shifted' state, this will only give you access to a second 'layer' of commands, whereas TARGET lets you essentially create six layers (unshifted and shifted, for U(p), D(own), and M(iddle) states of a 3-position switch of your choosing). Those additional layers (beyond 2) will NOT be available to use if you use option #1, however, because DCS does not by default recognize them. Also, you won't be able to make use of more complicated key assignments that involve things like pauses and repeat functions. So, while these limitations are probably OK for a lot of people, they're worth pointing out in order to draw a contrast with the other methods of using the Warthog in DCS. Before going any further, it is important to understand the limitations of using a controller in pure DirectX mode. When DirectX sees a controller that you've plugged in, it will recognize a maximum of 32 buttons and 8 axes on that controller. These can be 'directly' used in-game and are often automatically set to perform certain default functions, e.g. Button1 = DX1 = fire guns. You can also manually assign them in-game in the controller properties page, e.g. click on "Fire guns" and then press Button1 on your controller. But what happens if you have more than 32 buttons or 8 axes on a single controller? In that case, those 'extra' buttons/axes are not assigned DirectX names, and so from DirectX's perspective, they're not even there. However, you CAN pass keyboard assignments through those buttons/axes, provided you have some programming utility outside of the game (TARGET, Foxy, etc.) that can handle that. So, let's say you have a 33rd button on your joystick. By default, pressing this button in-game will do nothing, because DirectX doesn't see anything beyond 32 buttons. But if you've programmed that button from outside the game to represent, for example, 'G' for landing gear, now when you press that button in-game, the game simply sees 'G' and doesn't care where it came from. So given all of the above, how does DCS manage this automatic assignment of HOTAS functions on your Warthog? DCS sees your Warthog as two separate devices -- joystick and throttle -- each with up to 32 buttons and 8 axes available. For every device that DCS detects, it creates a separate lua file in C:\Users\[name]\Saved Games\DCS Warthog\Config\Input\A-10C\joystick\, which lists every possible function available within the game, and it is these lua files that change when you manually assign a controller button or axis to a specific command via the in-game controller options. Specific to the Warthog, because DCS 'knows' that your Warthog button is supposed to correspond to a specific function, it automatically assigns the button to do that in the lua file. Here's an example: In the Joystick.lua file, if you were using a stick other than the Warthog, you'd see this entry: [158] = { ["up"] = 351, ["name"] = "Weapon release", ["category"] = "HOTAS", ["down"] = 350, }, -- end of [158] Nevermind the actual numbers (158, 350, 351); what this is showing you is that DCS has a command available called "Weapon release", but that no button on this controller has currently been assigned to it. If you have a Warthog plugged in, though, you'll see this in your Joystick - HOTAS Warthog.lua file: [158] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN2", }, -- end of [1] }, -- end of ["combos"] ["up"] = 351, ["name"] = "Weapon release", ["category"] = "HOTAS", ["down"] = 350, }, -- end of [158] And this is now showing you that Button2 on the joystick (=DX2) has been automatically bound to the "Weapon release" function; DCS already knows that DX2 on a Warthog joystick is supposed to activate the "Weapon release" function. DCS follows this logic for all the other assignments on the Warthog, and that's how it "just works" when you plug it in for the first time: it will automatically assign the 19 buttons (+POV hat+2 axes) on the joystick and 32 buttons (+POV hat+axes) on the throttle to their appropriate commands within DCS. 2. Plug-and-play with some in-game assignment changes. This one is almost identical to #1 except that now instead of just using all the default controller assignments that DCS has set for your Warthog, you then go into the controller options screen and manually change some of the assignments. You still don't need TARGET or need to muck around with lua files, but again you're going to be limited to only using unshifted button states on your Warthog. 3. Using either joystick or throttle as plug-and-play device, with the other programmed via TARGET. Although I can't readily think of why you'd want to do this, it is possible. This would allow you to have one controller operating as a pure DirectX device (i.e. no shifted states available, and with the 32/8 limitation) with the other being controlled through TARGET and acting as a pure keyboard-emulation device or hybrid DirectX/keyboard-emulation device. In this case, you need to EXCLUDE the 'DirectX-only' controller from your TARGET profile with a line like: Configure(&Throttle,MODE_EXCLUDED); Note that this is also how you exclude your Thrustmaster MFDs, if you have them and want to assign them in-game rather than thru TARGET. In that case you'd use: Configure(&LMFD,MODE_EXCLUDED); Configure(&RMFD,MODE_EXCLUDED); 4. Using both devices through TARGET. This is by far the most flexible and powerful option, and was the way I wanted to go because I knew that even though I wanted the majority of my Warthog's buttons and axes to be assigned realistically, I wanted to customize some of the buttons on both the joystick and throttle beyond what could be done via the in-game controller options. If you go this route, you're going to have to work on the lua file itself in addition to your TARGET profile. When you set up and run your TARGET profile, DCS is now going to see your Warthog as a 'virtual' controller called "Thrustmaster Combined". Apparently this creates some problems because, while DCS still tries to automatically assign functions to your HOTAS in-game, this can conflict with what you're telling TARGET to do. The result is that you need to make sure your TARGET profile and Thrustmaster Combined.lua files are coordinated (more on that below). Here's a very important point (first made by ivanwfr): for some reason, if you try to assign actual keypresses to the buttons on your throttle via TARGET (as opposed to simply letting them act as DirectX buttons that can be bound in-game), DCS often has trouble interpreting them correctly and may unintentionally hold them down, so to speak, such that DCS ends up getting 'flooded' by excess keypresses that will eventually crash it. Frustratingly, these 'excess' keypresses are invisible to any keypress analyzers (like TARGET's Event Analyzer) so you won't necessarily know that this is what is crashing your game. The solution, then, is to try to keep as many of the throttle's buttons and axes operating as DirectX buttons/axes as possible. Thus you must present these buttons as DX buttons to DCS. You can do this in TARGET by simply 'declaring' the correspondence between physical button and DX number, like the following: MapKey(&Throttle,FLAPU,DX22); MapKey(&Throttle,FLAPD,DX23); And for any buttons or axes on the throttle that you want to assign a more complicated function, you can do that without messing up the other buttons being simple DX buttons. Here's an example that toggles a 'zoom CDU' function on the Mic Switch Down [shifted] button, with the unshifted simply appearing to DCS as DX5, which can then be assigned a function in-game (or via the lua file, which is the same thing): MapKeyIO(&Throttle,MSD,SEQ(CHAIN(PULSE+Toggle_zoom,D(150),PULSE+Zoom_CDU),Toggle_zoom),DX5); But, as I said, you'll want to minimize the use of assignments like the above on the throttle; if at all possible, you should use as many of the allowed 32 DirectX buttons and 8 axes on the throttle and then assign them in-game (i.e. via the lua file). Note that when explicitly passing DX buttons to DCS via TARGET, you now can use shifted states on these buttons, because you're defining the shifted assignment through TARGET (see above example). At this point it probably makes sense to list the correspondence of DirectX button name with physical button name (inexplicably, this does not appear in the TARGET documentation anywhere!). Note, again, however, that these codes cannot be used together at the same time inside of TARGET, because you're only allowed a total of 32 buttons and 8 axes on your virtual "Combined" controller. The main use for the first list (the 19 DX buttons on the joystick) would be for option #3 above where you make use of the joystick from within TARGET (presumably using a combination of DirectX button assignments and keypress emulation commands) but allow the throttle to "just work" by EXCLUDing it from your TARGET profile and letting DCS see it as a pure DirectX controller. The second list (the 32 DX buttons on the throttle), however, is useful for most people who would use option #4, combining both controllers in TARGET but keeping most throttle buttons as DX buttons. Note that, if you could somehow create a TARGET profile that included the joystick and throttle as separate DX controllers with all of the assignments below, you'd get the exact same result as option #1 where you simply plug the Warthog in and it "just works" -- because DCS would simply see two separate controllers that are pure DX devices, and it would recognize that it should assign specific DX buttons on each to specific functions in-game. Joystick: TG1 = DX1 TG2 = DX6 S1 = DX5 S2 = DX2 S3 = DX3 S4 = DX4 Trim Control H1U = DXHATUP H1D = DXHATDOWN H1L = DXHATLEFT H1R = DXHATRIGHT TMS H2U = DX7 H2D = DX9 H2L = DX10 H2R = DX8 DMS H3U = DX11 H3D = DX13 H3L = DX14 H3R = DX12 CMS H4U = DX15 H4D = DX17 H4L = DX18 H4R = DX16 H4P (Hat4 pressed down) = DX19 Throttle: Slew Control SC (slew control button pressed in) = DX1 Mic Switch MSP (mic switch button pressed in) = DX2 MSU = DX3 MSR = DX4 MSD = DX5 MSL = DX6 Speedbrake Switch SPDF = DX7 SPDB = DX8 Boat Switch BSF = DX9 BSB = DX10 China Hat CHF = DX11 CHB = DX12 Pinky Switch PSF = DX13 PSB = DX14 Left Throttle Button LTB = DX15 Engine Fuel Flow Norm/Override Switches EFLNORM = DX16 EFRNORM = DX17 Engine Oper Motor/Norm Switches EOLMOTOR = DX18 EORMOTOR = Dx19 APU Start/Off Switch APUON = DX20 Landing Gear Warning Silence LDGH = DX21 Flaps FLAPU = DX22 FLAPD = DX23 EAC On/Off EACON = DX24 RDR/NORM RDRNRM = DX25 LAAP Autopilot Switches APENG = DX26 APPAT = DX27 APALT = DX28 Throttle Idle Detents IDLERON = DX29 IDLELON = DX30 Engine Oper Ign/Norm EOLIGN = DX31 EORIGN = DX32 Coolie Switch CSU = DXHATUP CSR = DXHATRIGHT CSD = DXHATDOWN CSL = DXHATLEFT Continued below...

Thrustmaster Warthog Profil for DCS:BlackShark v2.0: DOWNLOAD

Hi ED, Is it a known problem that the servers are missing in the list after a view hours? STP Server Nr. II is missing in the list after ca. 30-60min. STP Server Nr. III the same problem. 33rd Squadrons Servers same problem. Is it known?

Ok here goes: I had a wild idea today to take my motorcycle helmet and build a bracket so my 23" flat screen could attach to it. This way when I look around, I always see the image. I taped my trackIR clip to the front. I fired up Blackshark and couldn't play more then 3-4 minutes without getting sick to my stomach!! Has anyone else tried anything like this?? I would like to have a helmet or VR glasses that done this but I can't find a commercial one with a decent resolution.... Update: 11/8/11 VIDEO HERE: .

Alt-Tab action immediately after entering game, boosts FPS by nearly 50%! Additionally the HDR is correctly rendered following the Alt-Tab. I saw mention in a separate BS2 thread regarding the Alt-Tab action, but I thought I would post as a new thread simply because it has such a dramatic improvement in FPS, as well as correctly enabling HDR. Note, I was going from 10 to 18 FPS before alt-tab to 28 to 30+ following (in pit with shaval and map on), along with correct rendering of HDR. Outside pit, 45 to 50+ FPS. Other settings set based on other thread suggestions, but this Alt-Tab trick gave me the greatest FPS boost. Not sure if this is a bug that can be fixed, but at least for now, every flight will start with Alt-Tab! Nice work ED! Back in the Black Shark saddle again!

Классный дизайн!:thumbup:

Uploaded and awaiting review by the Moderators. Nate

Ok cool, I'll upload it to the ED File repository and will post a link when it gets approved. Arclight, English subtitles will be present. Nate

HELL yes :D Ain't a Russian bird if it don't sing in Russian is what I'm sayin'!

Народ Вы только что реально проснулись али с Луны?) - http://www.lockonfiles.com/index.php/files/file/1688-su-27-with-r-77/ -Ракеты Р-77 на Су-27 работают аналогично МиГовскому сценарию+возможности РЛС Сушки выше. -На 104ом вроде давно работает мод с Р-77. -в кабине есть часы,считай по ним.

Nice! It worked just copied from BS1, no need to edit configs or anything! Just create new RUS folder, copy&paste, done. Now if I understand properly you can't do this for wingman, ATC voices just betty.

http://www.dcs-fan.ru/download/filelockon/modslockon/viewdownload/9/360

Джойстик Saitek x 45. Использую только один модификатор: кнопку под мизинец. Полностью хватает для реализации HOTAS А-10. В Акуле Точно также, только еще не полностью настроил все кнопки. Осталось вывести настройки автопилота. Свитчи не разу не пользовал, т.к. уже сейчас очень много функционала. В принципе на Сайтеках от 45 есть 3-позиционные переключатели режимов, используя их в качестве модификатора можно вывести все мало-мальски важные команды на джойстик, только вот запомнить это будет тяжело:) Я после рабочей недели вначале иду в оффлайн, чтобы вспомнить что у меня и где назначено:)

Я тебе по этому скину даже могу сказать под каким позывным летал читер:megalol: Вчера и на АКАДО были снова... Скоро на АКАДО будет авторизация, тестовая стата...

wow, just checked out those links. Looks realy good.

It's only a placebo effect. The changes were made deeply in the rotor mechanics, a minor mistake in vertical hinges were found. As a result the angular movement became more sharp in initial acceleration while the general damping in angular movement even increased a little bit. It was THE ONLY change we made. These changes do not affect on any other aspects of the flight model.

I agree. Specifically for Mission editing and other "shared" features this is an issue. Additionally you might still have some BS1.02 players ask 1.02 questions who might end up getting BS2.0 answers...

He have also some screenshot in screenshot thread: http://forums.eagle.ru/showthread.php?p=1273012#post1273012 http://forums.eagle.ru/showthread.php?p=1270399#post1270399 http://forums.eagle.ru/showthread.php?t=58337&page=388 Would love to hear something about to.

Eponsky_bot а как ты эти значения вычислял или есть метод -выставил вид и где то значения посмотрел?

Иду в гугл:book:

Damn fine answer. I can't say I disagree with that. Although I haven't seen anybody ask how to cycle through targets (they shouldn't be playing this game) or do absolutely nothing. Still, you make some good points.

Q: "Why are there so many password protected servers?" A: Probably because every time we make an un-protected server, 10% of everyone that joins is interested in nothing more than killing every friendly they see. The next 25% are asking questions like "how do I shoot a Maverick?" and then when the answer is "it's complicated" then they ask "well what button cycles through my targets?" The next 35% of folks will join, fly around, doing nothing and saying nothing all mission... so they might as well not even be there. Only like the remaining 30% of folks will actually interact with others and a try to accomplish the mission objective. In the end, if you want to make a public server, it's better to just leave it password protected, but be very open about what the password is. Then the mature 30% will go through the small amount of work required to acquire the password and actually cooperate with others to achieve the mission objective.

Agree or disagree...but I don't really find much humor in that. :(

стр.689 средний тумблер по логике должен быть не AC GEN, а APU GEN.

You're welcome.

+1 to have Russian language for BS2! It is an immersion killer when you start hearing those actors with cheesy fake accents...thank you.

Danke MemphisBelle, du sprichst mir aus der Seele! :thumbup:

Подожди-ка. Но в треке ты самолично сначала запускаешь APU. Если речь об электричестве, то да, для запуска двигателей нужен переменный ток, но он поступает от инвертера, поэтому в процессе запуска генераторы не нужны.

Don't cry, because here are some pics..:D

With a lot of expensive hardware, I think the easy option for you is to go for the full download version. No messing around with old versions and you support high grade sims.

No! The new updated files does not need that any more.

Обещалось , "стреляющие" здания , изменения в пехоте , изменения в "бронезащите " вертолетов , и много чего другово , даже по секрету намекалось на какую то интересную фичу со сбитым ботом . Была просьба , увеличить бк пехоты до 1000 патронов , поставить вооруженные хамеры за все страны нато включая грузию , это ведь две строки изменить ? Приблизительная цитата: " сделано так много , что это будет практически новый продукт " (уж не стал в форуме рытся ) А судя по твоему ответу , ЕД ограничилось "украшением картинки ", до сихпор нет ответа по ОНВ и ИК маркер , а это будет практически единственным средством целеуказания А10-КА50 ночью , "видимость " ЛД в режиме подсвет , что реализовано ? Я понимаю , что вы всем колхозом прикалывались над темой "пожелания к патчу " , но проявить хоть толику уважения к людям покупающим ваш продукт ? реализовать идеи людей , зачастую полезные , и не требующие от вас больших трудозатрат ? радио обмен , опять все как в А-10м ? Не ужели трудно выделить один день и отобрать здравые идеи с форума ? Вы , господа , позиционируете свой продукт как симулятор , и кричите об этом при каждой удобной возможности , а на деле , живя в всоем мирке , продвигаете сурогат из ваших представлений о реальности и личных предпочтений , не будете развивать игру в плане ИИ , редактора , погубите и компанию и сим . Хочется напомнить о нестоль давнем времени , когда на форуме ЧА постоянно присутствовало 8-10 человек , и каждй вопрос новичка этим десятком с радостью встречался и обсуждался по третьему разу . ЕД не стоит почивать на лаврах монополиста , без изменений в ИИ и новых компаний , интерес к ЧА2 быстро угаснет .

For some of those just look at DCS A-10, others (TV towers) are existing A-10 mods. Some are new.

Песок плюс фторопласт, адская смесь :D

Я тоже пользуюсь этим комплектом. Скажу одно, до этого пользовался Т1600, на датчиках Холла. На форумах писали, что Т1600 точнее Х-52. Так вот, приобрёв СН, скажу, от Т1600 ни чем, по точности не уступает. Отличный комплект!

Соглашусь. Я сам летаю на Кугаре. Но Кугар, как он есть, после покупки из магазина, нуждается в серьезной доработке либо в замене механики. Разобрал на второй день и отвез мастерам на доработку. Думаю не каждый готов на это при том, что он стоит не малых денег. Если бы у меня не было Кугара я бы взял СН. Третье место отдал Кабану, девайс интересный, но пока он относительно новый я мало что про него знаю и не знаю как он в эксплуатации. PS СН действительно выпускает промышленные джойстики для кранов экскаваторов и прочей техники.

[quote=ralfidude;1321014 PS: At some point Im forced to join stallturn or the Chinese server... Ugh... 350 ping and above... :( And im playing in NYC. Though it doesnt seem to affect the gameplay much or at all. Just dont fly in formation with anyone... it wont end well. I run the stallturn servers (theres an FC2 one and an A-10C one too, besides the 104th+community pilot statistics), and they are located in New Zealand. Too bad no-one in NYC has made a server available to you (NYC is not the center of the universe dontcha know). Be grateful this is made available to you at all - it costs me a non-negligible amount of money to run each year. My low ping to the server is affected by the high pings and crappy connections of some people joining - but I don't complain about it, I let everyone join (apart from the serial teamkillers, who get banned) - even those in remote corners of the globe like NYC that are too backward to have their own servers (lurlz). 'Bad' ping is a relative thing, and from the server's point of view you are the bad client with the high ping, although a friend in VNAO from NYC never seems to have an issue. The high ping matters less than you'd think. Mostly what matters is the 'jitter', which is the variance in the ping. Plenty of people are able to join from all around the world and use the server ok if the connection at their end is also low and as reliable as stallturns. For formation flying the server ping has some impact but more important is the jitter in your connection and the guy you are flying next too - even if the server's connection is good if you have someone on lowly DSL/wireless/or worse next to you then you always have to be careful. If you don't like the ping why don't you purchase a server box and pay for the server bandwidth yourself (about 1 GB/day). That way you'll have low ping and be able to share with others so they all get low ping. Oh yeah, and you'll also be able to quit complaining about the servers that others provide to you for free because they don't meet your expectations. Sorry if this sounds harsh, but you turn your nose up at the servers that people actually make available to you and think that the server is the problem when from the server's point of view it is your connection that is high. If you took the very simple step of joining Teamspeak you'd find many of the other closer password-protected servers would be made accessible to you.

I have had a teamspeak server up for a while now. Its still open to the public and is used quite regularly. http://forums.eagle.ru/showthread.php?t=75353

My friend and I play constantly, but are downgraded to using the non password servers, which there areabout 2 at any time.... We use Ventrillo and like to talk there, would have to have to join TS and take up comms. So we would go into our own channel, which defeats the purpose... buttttt if we must... then i guess... How do I find the TS information for these servers? It doesnt state it in the title. PS: At some point Im forced to join stallturn or the Chinese server... Ugh... 350 ping and above... :( And im playing in NYC. Though it doesnt seem to affect the gameplay much or at all. Just dont fly in formation with anyone... it wont end well.

you should choose better places to post that, like everywhere but here :puke:

давно читал сетевую архитектуру анреаловского движка, по моему первого анреал тарнамент. Там все просто сделали, клиент тупо шлет серваку какие кнопки нажаты, а тот сам все считает и передает уже только положение объектов. Круче этого, хоть и обещали развитие такой тенденции но что то не срослось, на клиентский комп будут приходить уже скрины, и ни чего 3-х мерного не надо будет считать клиенту вообще, но это уже совсем другая история. А пока клиент сам считает свою физику и попадание ракет, и сервак на слово верит без проверки, то этого не избежать.

Панкбастер не панацея. Я много играю в БФ2 и многого насмотрелся. Панкбастер безусловно дает некоторые плюсы, но и с ним читерят по-черному.

I think the current number of A-10 pilots in the 25th is 30 or so with 15 being very active (as in at least two or three times a week).....we had, at various times yesterday, over 10 pilots on the server...

Может быть. Я сразу в настройках силу обратки сбавил, чтобы он не тряс весь стол при вибрации.