Leaderboard

Greetings, It is my first post on this forum. It is great to be part of this community! I would like to introduce to you my first DCS: BS mod as well as my first lua scrpt:) I have created input shortcuts which are taken from user configuration rather than from script file itself. Mod can be downloaded from here. (ModMan 7.3.0.0 compatible) Screenshots: - custom tooltips text - custom tooltips size and lifetime - tooltips size comparision And the readme.txt: -------------------------------------------------------------------------------------------------------------- Input shortcuts on Cockpit Tooltips v. 1.0 10 July 2010 -------------------------------------------------------------------------------------------------------------- OVERVIEW -------------------------------------------------------------------------------------------------------------- 1. Introduction 2. Package contents 3. Instalation / uninstalation 4. Script files info 5. Known/predicted issues and limitations 6. ToDo 7. Thanks to 8. Contact 1. INTRODUCTION -------------------------------------------------------------------------------------------------------------- NOTE 1: This package was created to extend great mod "Tooltips with Keyboard Shortcuts" created by Miguez (many thanks for the inspiration). Thread about this mod can be found on ED Forums ( http://forums.eagle.ru/showthread.php?p=615135#post615135 ). NOTE 2: Another usefull mode I have extend in this package is the "Cockpit Tool Tips (Hints) improved visibility" mod created by Bucić (thanks for excelent start point) ( http://forums.eagle.ru/showthread.php?p=890758#post890758 ) What it extends? No key shortcuts are hardcoded into the scripts. Shortcuts are taken from current user configuration before the mission load. Tooltips format is widely configurable. (even too widely, perhaps) Tooltips size and lifetime is configurable from within gameplay menu. What are the benefits? Shortcuts are always compatible with your configuration, even if the configuration has changed. Background of my work is really simple. I have noticed that when we change some key bindings we have to change originally modifed (see Note 1) clickabledata.lua script manually. As a result we have two places where our bindings are stored. I was digging up tons of LUA scripts to find a way to link cockpit tooltips with the input commands programatically. Finally, oryginal game hints have been extended by the key sequence currently bound to each input option, so there is no need to modify clickabledata.lua file in case of key binding changes. 2. PACKAGE CONTENTS -------------------------------------------------------------------------------------------------------------- This package consist of: BlackShark\modules\me_options.lua - widget bindings/load/save BlackShark\modules\me_options_form.lua - labels initialization BlackShark\modules\dialogs\me_options_gameplay.dlg - new widgets to configure tooltips Config\tooltips.cfg - Tooltips configuration file FUI\Resourcesbs\DHint.res - hints lifetime and delaytime and size Scripts\Aircrafts\Ka-50\Cockpit\clickabledata.lua - entry point for hint_map.lua script Scripts\Aircrafts\Ka-50\Cockpit\hint_map.lua - searches for input mappings 3. INSTALLATION / UNINSTALLATION -------------------------------------------------------------------------------------------------------------- Before instalation make sure that you back up all your oryginal/modified files listed above. Installation/unistallation using ModMan 7.3.0 or later is adviced. Mod is compatible with DSC: Black Shark v.1.0.2 In case of any conflicts with any existing mods or serverside files, please inform me by email. (My email address is at the bottom of this file) 4. SCRIPT FILES INFO -------------------------------------------------------------------------------------------------------------- First of all. It seems that files can be unreadable to the game when edited with unsupported encoding. All files provided in this package are encodd with UTF-8. hint_map.lua This file has three purposes: A. Read all user input configuration and store it in local table for further use. B. Create mapping between cockpit switches and input options available to the player. C. Replace old LOCALIZE function implementation with the new one. A. ______________________________________________________________________________________________________________ package.path = package.path .. ';./blackshark/modules/?.lua' local NewInput = require('NewInput') dofile('scripts/input/layout.lua') dofile('scripts/input/aircrafts.lua') local oldGetDeviceType = getDeviceType ______________________________________________________________________________________________________________ These lines initiate oryginal tools which provide support for input configuration files. ______________________________________________________________________________________________________________ local function addDeviceCommandCombos(commands) ______________________________________________________________________________________________________________ This function adds all key shortcuts for specific command to local variable inputShortcutsMap. ______________________________________________________________________________________________________________ local cfg_path = 'Config/Input/Aircrafts/' local aircraftName = 'ka-50' ______________________________________________________________________________________________________________ Some named strings. local devices = NewInput.getDevices() ______________________________________________________________________________________________________________ Gets all devices currently detected by the game. ______________________________________________________________________________________________________________ for i, device in pairs(devices) do local path = getLayoutPath(aircraftName, device) local layout = Layout() layout:open(path) addDeviceCommandCombos(layout.keyCommands) addDeviceCommandCombos(layout.axisCommands) end ______________________________________________________________________________________________________________ Function "getLayoutPath" finds configuration file path for input device in hierarchical manner ('\Config\Input\Aircrafts\ka-50\keyboard\keyboard.lua' or '\Config\Input\Aircrafts\ka-50\keyboard\default.lua') For details see 'scripts/input/aircrafts.lua' file. Next the Layout wrapper object is created based on configuration file. Then keyCommands and axisCommands are added to map. B. ______________________________________________________________________________________________________________ hintInputMap = {} -- CPT MECH hintInputMap["Gear lever"] = {"Gear lever"} (...) -- ZMS_3 (Magnetic Variation Entry Panel) hintInputMap["Magnetic variation selection rotaty"] = {["Left"]="Magnetic variation knob left", ["Right"]="Magnetic variation knob right"} ______________________________________________________________________________________________________________ In this part mapping is created for each hint. For example, "Gear lever" has only one function which is titled exactly the same "Gear lever" in options menu. But "Magnetic variation selection rotaty" has two functions: "Magnetic variation knob left" and "Magnetic variation knob right", thus first function shortcut will be displayed on the tooltip as "Left = ( RShift + RCtrl + M )" and the second one as "Right = ( RShift + RAlt + M )". Finally, the whole tooltip will looks like this: "Magnetic variation selection rotaty Left ( RShift + RCtrl + M ) Right ( RShift + RAlt + M )" C. ______________________________________________________________________________________________________________ local function getInputShortcuts(input, key) ______________________________________________________________________________________________________________ This function builds shortcut string for specified input option (ie. "Magnetic variation knob left") and key (ie. "Left"). If the control has only one function, key will be equal 1 and won't be added to shortcut string. ______________________________________________________________________________________________________________ local OLD_LOCALIZE_REALIZATION = LOCALIZE function LOCALIZE(hintText) ______________________________________________________________________________________________________________ Input mapping search. Replacing of the LOCALIZE function in order to change tooltip string (proposed by Alex O'kean on ED Forums http://forums.eagle.ru/showpost.php?p=615249&postcount=7 ) 5. KNOWN/PREDICTED ISSUES AND LIMITATIONS -------------------------------------------------------------------------------------------------------------- - I have found no explicit linkage of cockpit controls with the key codes placed in input configuration. All mappings are done manually. - It would be nice to have shortcuts placed below the switch tooltips in a multiline manner. (this is imposible at this time due to tooltip size calculations - no "\r" nor "\r\n" extends its height) - Several tooltips are really long. - Mod has been tested only with English version of DCS: Black Shark. It should work in Russan version as well (old LOCALIZE function is still in use), but it should be checked. - New gameplay Menu options are always English. I have found no way to localize them. - This is my first LUA script so there should exist a simpler way to get the same effect with more reliable approach. - Only the "Real mode" shortcuts are supported. They are also displayed in Arcade mode. (I don't know how to get the name of the current aircraft in lua script) 6. TODO -------------------------------------------------------------------------------------------------------------- - Add support for 'arcade' mode - Multiplayer may be affected. Dont know how the server may react on such modifications. 7. THANKS TO -------------------------------------------------------------------------------------------------------------- Thanks to Bucić for his DHint.res file attached to this package 8. Contact -------------------------------------------------------------------------------------------------------------- In case of any issues, corrections or bugs feel free to contact me using email provided in readme.txt file. -------------------------------------------------------------------------------------------------------------- Hopefully this mod will save your time and help to master the cockpit of the Black Shark. Happy flying, Hubert 'Baal' Bukowski

Given I was not able to create a new video note this week (software not cooperating), I've put together a few screen grabs on the A-10C in "old school" colors around the WIP Nevada terrain.

I am very excited!! I just found a way to get rid of the slop completely by accident. I am VERRY happy with my G940 now!! I received my G940 last week and was very disappointed in the slop I was getting with the trim button. I tried a bunch of different settings but none were working. I was fiddling with some settings that others have posted, but none of them got the results I was looking for either. I did a couple of other things and gave up. I then just wanted to play. So I got into a game and after playing for about 2 minutes I realized hey, my slop is gone. I played awhile longer and no matter how many times I trimmed, the stick stayed exactly where I wanted without moving. I wasn't getting the aircraft going all squirrelly anymore either. I don't know what was giving me the results, but i thought I would share my settings with you all and see what you thought. Logitech Profiler settings X and Y Axis Properties Sensitivity 30% Dead Zone 0% Range 80% Specific Game Settings Overall Effects Strength 55% Spring Effects Strength 55% Damper Effects Strength 55% Centering Spring 0% unchecked DCS Black Shark Axis Tune Panel Deadzone 0 Saturation y and X 100 Curvature 0 Force Feedback Tune Panel Trimmer Force 100 Shake 0 I think, (but I don't know for sure), that when you adjust the Shake to 0 on the Force Feedback Panel in Black Shark, the controller gets less confused about the trim. Try these settings and see what you think. Its working awesome on my end. I have the stick set to what I feel is realistic with my real life flying experience. I don't have it all stiff like some other people like to have their settings. The cyclic in a real world chopper only gets stiff when hydraulics are off or when you have lost them, (from my real world experience as a commercial helicopter pilot flying Bells). Thank you Logitech for a wicked controller. I couldn't be happier with my G940 now. :thumbup: :joystick:

Ok Jim, count me in Again, Just love the job on the blackshark Manual, and can see this one being even better. Not only have you guys giving me the best heli sim in the world, Now you are doing it for my favorate combat fixed wing. I dont think im ever gonna thank you enough.

Version 2.1 is online.

Vista is not new ..... nothing wrong with the Gys F-15 ..... so by process of elimination your system is borked. Format C:/

:shocking: ooohhhhhhhhh! Thats Madeira island--Funchal airport (I call it airstrip)--. Known for European tourists for its near tropical weather and bombastic new years fire works. I lived there from 1982 to 84. The runway sections on pillars did not exist back then. We called it, the "airliner aircraft carrier", because it was very hard to land there and planes would apply full brakes and reversers on touch down. Quite a spectacle for the people passing the nearby road (they even stoped to watch). for the passengers it was like a roller coaster, both on aproach as the touchdown. NOT for the faint hearted! There was a fatal accident in 1978, a liner skided on landing and flew off the edge into the sea. Im am not joking. 2 years ago a 747 landed there to test the new runway patch :D Made it..barely :D

A good reminder of the importance of terrain cleareance around the airfield. It also reminds me of the moronic airfield layout in Brazil with... fuel storage tanks at the end of the runway :shocking:

Следующим будет A-10C.

Don't know if anyone's seen these - pic 2 is fairly impressive! http://www.airlineempires.net/blog/2008/04/british-airways-777-lhr-crash-pictures/

I thought threads name is "Funny Stuff" :huh:

Touchbuddy has no graphic relationship to the game itself. You might want to pickup Touchbuddy Toolkit and resize/reconfigure the tabs display to fit the 7" screen as previously mentioned, but if you're running default resolution, most of the user-created profiles should work. The image might be small if you have "older" eyes. Or, you could just build your own profile. WBK's Lomac profile (with or without labels) should work fine a give you the basic set of functions for the A-10/F-15. Other profiles are there for other aircraft; Su-25T, etc. There are some however that will require a bigger monitor area - i.e. DCS:BS - especially those who have integrated additional components like LOVP and BSVP.

Форму зон изменить нельзя, только круглые в плане. С другой стороны, вовсе не обязательно "накрывать" зонами все рулёжки - скорее всего, вполне достаточно будет двух-трёх, которые расположены в ключевых местах. Со взрывами объектов немного хуже. Можно попробовать привязывать взрыв не к самолету, а именно к зоне, но тогда может быть поврежден и соседний самолет, надо пробовать и точно выставлять мощность взрыва. Добавлено. И конечно, нельзя делать центр "взрывной" зоны прямо на рулёжке, это понятно.

зайди в "мой компьютер" -"свойства" - вкладка "дополнительно" - загрузка и восстановление (параметры) и посмотри не слетела ли там галочка напротив пункта "отображать список операционных систем"

Когда за окном +36,нормальные люди на пляжах с девчонками загорают,а не перед компами сидят:smilewink:

The key is range. You correctly point and lock your sensor with the laser rangefinder on. This provides enough data to the aircraft's computer in order it to calculate the impact point. The "trajectory indicator" you mention is actually the Calculated Impact Point. If you have locked a target beyond the rocket's range (usually 3km) the reticule will drop too low. This means, theoretically, that in order for your rocket to travel that much distance to the target you have to fire it with your nose pitched up. Practically, even if you were able to do that, your results will be poor since the rockets will disperse too much. If you take your time and approach the target you 'll see the reticule will eventually come up.

Ну чтож поделать.

Свежие скрины: http://forums.eagle.ru/showthread.php?t=55892

Format C:/

:)

Some experimentation....

Incredible! Nevada and the Hog looks fantastic!

Lol what is that supposed to mean? ::huh: Aren`t the others human as well? :lol:

Justice, the only word that describes this cup. The best team, with the beast play, the best behaviour and the best human group are the champions. We deserve this cup more than anything, JUSTICE ¡¡¡

Taker, подняли. Потом сервак закрывался на вылет РАФа, уже все работает)

Thanks everyone, I think I will try to get into this, but I guess i will be doing this all over again when DCS: A-10c comes out.

Можно, но сильно много триггеров пойдёт. Перекрыть рулёжки триггерными зонами и если высота юнита в зоне ниже чем уровень аэродрома + 3 метра а скорость выше 100 км/ч - взорвать юнит. Но нужно делать для каждого самолёта.

Ну у кого бабок на абрис не хватило, тот может себе принтер купить. ;)

That's the one way you can look at it. On the other hand: - steep learning curve = huge satisfaction of every bit learned - you learn real aviation knowledge every day - you can learn basics and go into combat in a day (24 hours of flight/reading time :P) to avoid getting frustrated (?) (7 How to Take Off and Blow Up Stuff) Then you can supplement your skills according to a prioritized list: * flying: basic maneuvers and aerobatics * autopilot+flying http://forums.eagle.ru/showpost.php?p=921771&postcount=448 + FAQ + http://forums.eagle.ru/showpost.php?p=862899&postcount=363 (get the book mentioned there!) * emergency procedures * countermeasures http://forums.eagle.ru/showthread.php?t=54285&page=3 * ... Most buttons are used but at the same time most of them are used rarely e.g. on startup. To get an idea of what commands are used most frequently take a look at various joysticks button layouts like mine for example. Also getting the cockpit tooltips mod with keyboard shortcuts is the first thing you should do (check my sig).

Sniper, Check this out: and this : http://en.wiki.eagle.ru/wiki/Resources_for_New_Pilots In the second one, there is a link to Leading Edge training video. It's big, but well worth the download.

A common misconception regarding steam. Well to an extent. Steam has whatever is the latest version that has been uploaded to them by the developer. However if a new version comes out and is never updated by steam you can download and install the correct version from another source. Also if you are worried about updates. See Exhibit A. Exhibit A You can choose whether to allow automatic updates or not. Case in point ARMA2. Up until recently the ARMA 2 1.05 and 1.07 patches were not part of steam. I downloaded them from a gaming site and installed them separate of steam. The game worked fine as expected. Granted you can't tell it you want to download version 1.01 rather than 1.05. So in that sense its lacking a feature, but why would that even be a problem? About Modern Warfare2, it was decided to be exclusively incorporated into steam for whatever reason. Not all games are like that, actually very few are. Come to think of it, outside of Valve games and Modern Warfare 2, I can't name any other games off the top of my head that require it. But hey, you want to blame steam for Modern Warfails problems well... I think your taking issue with the wrong people. And lets be honest, "Steam Exclusives" make up probably less than 2% of new releases on PC, its quite a non issue. But they can still buy and play the game from somewhere else.

No NO no NO no NO no NO!!! No Steam ever! Steam is single handedly ruining the PC gaming market: -games release late -updates are inconsistent -inability to perform manual version management is troublesome -if steam goes down you cannot play the game you paid for!!!! -if there is a problem with multiplayer, steam will never care. And the developer can blame steam. Down with Steam!! They are the WORST thing to happen to PC gaming, EVER!!! Just my 0.02

A Steam version would be fantastic. You'd be able to: * run the games on all your computers (just one at a time though) * no StarForce :) * make backups of games (easy to copy to your other computers) * no piracy either (we want ED to make money and keep making DCS stuff). Looks like an all-round win.

Maybe I should make a separate topic with all A-10 related documents? First post would be modified to include list of all links and brief descriptions. I know that all of these documents have already been "found", even on this forum, but they get buried rather quickly. And it's difficult to use "Search" if you don't know exactly what you are looking for. Words like "Manual" are used too often here to help. And maybe the mods could make it Sticky, if it proves valuable enough. :)

Перезалил на Народ.ру Кампания "БУГ: Боевая Ударная Группа" Размер: 40.70 МБ MadShark, СПАСИБО! Вставь альтернативную ссылку в свой пост.

GREAT first post ... i probably would've started off by introducing yourself, but hey; i'm just weird.

funny, i would think that trolling is bringing up a coment that no one notice or took as a joke and try to make something out of nothing, but i guess this has nothing to do with this topic, sorry.

Посмотрев обучающий трек по посадке в ГС2, решил сделать свой. Объясняется методика взлета, захода 2х180 и посадки с последующим заруливанием на стоянку. Думаю, для начинающих самое то, ведь, если сразу приступать к сложным видам, ничего не поймешь и быстро надоест, начинать нужно с кругов. Сопроводил титрами. 2х180 (ПМУ).trk

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

It would be cool if you could have a friendly ground unit lase the target point for you.