Sov13t

I created a diff thread in the Mods and Addons board.... http://forums.eagle.ru/showthread.php?p=864643 Me and Distiler were discussing it on HL and I tested it out. Rep to Distiler!

In order to change how big the chat log is (while the chat box is not active) you need to edit the following file chat-log.res located in /FUI/Resources/Multiplayer/ \dialog \begin \tag{-1} \coord{0, 18, 1023, [color=Red]60[/color]} \musthavecursor{0} \acceptmouse{0} \topmost \layer{900} \end \multicolumnlistbox \begin \tag{2} \coord{20, 0, 1003, [color=Red]60[/color]} \defaultitem{Multiplayer/def_list_box_item.res} \columnswidth{200, 803} \rowsnum{10} \readonly{1} \visiblescrollbar{0} \end You need to edit the \coord{x, y, w, h} lines. The last parameter is responsible for height, each line of text is 20px as such setting this parameter to 60 (highlighted in RED) will only leave 3 lines of text max while the chat window is CLOSED. To edit how the chat window appears when it is open you need to edit chat-say.res, but it is a little more complex as there are way more coordinates to mess with. Credits for this go to Distiler and Acedy (http://forums.eagle.ru/showpost.php?p=676501&postcount=52). Thanks and enjoy.

Bad news, it is impossible to change chat size. Chizh answered my question on the RU side: http://forums.eagle.ru/showpost.php?p=864521&postcount=3257

GG, are the charts available in an organized fashion, or are you referring to the ones referenced in various threads randomly?

Вопрос который мы вчера с A.S пытались решить но не смогли: Как можно уменьшить размер окна чата в Мултиплеере ГС2.0? Спасибо.

Bumping... a thread that still should be "open"... I did some messing around with various files, and I believe that the answer lies within the Theme.lua inside BlackShark/Themes/ folder.

Su-33 - 12,800 кгс (kg force), ~28,219.170 lbf (pound force) Su-27 - 12,500 кгс, ~27,557.783 lbf F-15C - 12,500 кгс, ~27,557.783 lbf This is based on numbers mentioned in the FC2.0 Q&A thread by devs, verification needed.

Editing network.cfg and setting height to whatever doesn't seem to change anything at all... :cry:

Notching is the best maneuver to evade missiles. Effectively putting the missile at 3 or 9 and lowering closure rate will yield the best results. Once you are in the notch you want to dispense chaff and flares once the missile enters terminal stage of its flight path (depends on missile and situation). If you mix in a vertical component into your notch (diving) you make your chances that much better. Do not panic. Do not waste chaff or flares early. You want to judge the distance from the bandit/sam and mentally calculate the amount of time it would take for the missile to enter "danger" zone. Do some offline testing and see how many seconds it takes for missiles to reach you and develop situational awareness in space and time... everything is dynamic and you pretty much have to adapt to whatever situation you find yourself in.

Must be a mistake.. For the SPO Volume Ralt + . and Ralt + , are used, if I remember correctly.

From my tests thus far, it is not worth betting on the fact that the ER launched from Rmax will hit, it is purely to scare the bandit. As such, providing better launch parameters for the ER is crucial in the outcome of the fight. I find the best time to launch is 40-35km, with 5-9 second interval between missile launches. By this time it is possible that the bandit will fire at you with an early AIM-120C/B, some pilots will spam you with up to 3 missiles (witnessed online already), in these situations it is better to perform a tactical turn (180 degrees) and extend full burn, you want to minimize closure rate as much as possible. Notching is also a very good option, but it all depends on the situation you are in, if you are going to start marking while diving between 12,000m to ~5,000m you are inviting more bandits to switch on you and thus getting into deeper trouble. There is an infinite amount of scenarios :) not a simple equation.

Одни опровдания и запугивания. Не серьезно. Можно было просто сказать: "Да, действительно, задача была подогнать интерфейс под Западный рынок. Чтоб не откладывать релиз Русской версии сделали как есть, у вас есть возможность все поменять как вам угодно" Красные не красные... синии не синии... розовые не розовые... факт что одна западная техника это факт, от него тов. Рег_зеро увы не уйти :( Конечно же, это мелочь, конечно же нас, Славянов этим не подавить... просто на некоторых это как видите подействовало больше чем на других, не надо их за это ругать, банить или еще чего... дайте им высказать мнение и не обращайте на это внимание... Спасибо.

Perhaps why some people are noticing an increase while others aren't is because of BS engine taking advantage of multi-core systems, and those that aren't noticing it are running single core? Just a wild guess. Personally for me, it runs smooth... no crashes... and that is lovely.

Very few commands actually changed. You will just need to redo the ones that changed. So you can use your FC1.12 profile as base and modify/refresh key binds that do not work or are out of date.

Bump, just so that more people see this, since FC2.0 ENG came out.

Создавал, вчера летали. Даже Тов. Улрич заходил :) было весело. Миссии которые идут с игрой прикольные... макс игроков на моем серваке было 4... никаких аномалий не замечал.

Hey guys: Thought I would share my experience, and hopefully help others with configuring their Saitek hardware. The input configuration in FC2.0 is just like the one in Black Shark, as such you are presented with two options: 1). Configuring all the buttons inside the game. 2). Creating a profile using Saitek's software. I went with option 2, because I already had an FC1.12 profile and because it takes better advantage of the capabilities of my X52 Pro joystick (modes and such). So here is what I did: 1. Clear all joystick button binds for any inputs in the game. Use the very neat feature of "Clear All in Category" (could be named differently, I have RU version). 2. Set up all my Axis in the game - curves, deadzones etc. 3. Exit the game and open up the Key Bind PDF that come with the game (inside the Doc folder) and start migrating my old FC1.12 profile to FC2.0. 4. Very important: FC2.0 is very sensitive to "Key Presses" vs. "Macros" for example to start left engine Home + Right Alt only works as a "Macro" and not as a "Key Press" (which is what I usually used). However, for any binds that use SHIFT key as the modifier (such as moving your radar cone around) you want to use "Key Presses" not "Macros", also make SHIFT the first KEY in the sequence for example SHIFT + ; instead of ; SHIFT. So, from my experience any binds that use CTRL or ALT as modifiers use "Macros". For binds that use SHIFT as a modifier use "Key Press". 5. Run the profile. 6. Enjoy :) Hope this helps at least someone.

Супер!!! Пожалуйста :) А по мултиплэеру тоже встанет? :)

Как можно избавится от Ф-15ых в фонах менюшек и загрузки? Пожалуйста помогите :)

Получается для деди ГС2.0 серверов нужно еще один ключ покупать? Или просто если на деди ставишь свой ключ то вместо одной активации ты сразу две сжигаешь? Никогда не хостил КА-50 деди из за этого не знаю как оно активации жрет. Спасибо.

Great news! Thank you for the release! ED :thumbup:

У меня Лок Он 1.0 оригинальный на Английском... будет ли Русская версия ГС2.0 работать с Английской версией Лок Она? Спасибо.

On the Russian side of the forums, there was a mention of a slight delay for weapon systems synchronization before the missile goes off the rail... Can you please go into some detail on this, in this thread? Thanks.

Gotcha, thanks! Interesting topic nonetheless. (the electronics of the warheads)

Can someone please provide, an explanation as to why a SARH would be more vulnerable to CM vs ARH? (not based on P-27 vs AIM-120/P-77 due to the obvious age difference of the missiles, just purely theoretically) I thought with the host's radar pinpointing the target, the SARH has to be less worried about hitting chaff rather than the actual target. Thanks in advance.