Leaderboard

You know the problem: You fly a mission and the default countermeasure programs are not proper for the mission (task) or you don't like them. You have to change the presets or create new programs. But in both situations, you have to do this in every start up sequence or respawn. Finally, I found the file in which the default programs are stored. an_ale40v_params.lua "\Eagle Dynamics\DCS A-10C Beta\Scripts\Aircrafts\A-10C\Cockpit\AN_ALE40V\device\an_ale40v_params.lua" programs = {} -- Old generation radar SAM programs['A'] = {} programs['A']["chaff"] = 2 programs['A']["flare"] = 0 programs['A']["intv"] = 1.0 programs['A']["cycle"] = 5 -- Current generation radar SAM programs['B'] = {} programs['B']["chaff"] = 4 programs['B']["flare"] = 0 programs['B']["intv"] = 0.5 programs['B']["cycle"] = 5 -- IR SAM programs['C'] = {} programs['C']["chaff"] = 0 programs['C']["flare"] = 4 programs['C']["intv"] = 0.5 programs['C']["cycle"] = 5 -- Default manual presets -- Mix 1 programs['D'] = {} programs['D']["chaff"] = 1 programs['D']["flare"] = 2 programs['D']["intv"] = 1.0 programs['D']["cycle"] = 3 -- Mix 2 programs['E'] = {} programs['E']["chaff"] = 2 programs['E']["flare"] = 2 programs['E']["intv"] = 0.5 programs['E']["cycle"] = 8 -- Mix 3 programs['F'] = {} programs['F']["chaff"] = 4 programs['F']["flare"] = 4 programs['F']["intv"] = 1.0 programs['F']["cycle"] = 10 -- Mix 4 programs['G'] = {} programs['G']["chaff"] = 4 programs['G']["flare"] = 4 programs['G']["intv"] = 0.5 programs['G']["cycle"] = 10 -- Chaff single programs['H'] = {} programs['H']["chaff"] = 1 programs['H']["flare"] = 0 programs['H']["intv"] = 1.0 programs['H']["cycle"] = 1 -- Chaff pair programs['I'] = {} programs['I']["chaff"] = 2 programs['I']["flare"] = 0 programs['I']["intv"] = 1.0 programs['I']["cycle"] = 1 -- Flare single programs['J'] = {} programs['J']["chaff"] = 0 programs['J']["flare"] = 1 programs['J']["intv"] = 1.0 programs['J']["cycle"] = 1 -- Flare pair programs['K'] = {} programs['K']["chaff"] = 0 programs['K']["flare"] = 2 programs['K']["intv"] = 1.0 programs['K']["cycle"] = 1 -- Chaff pre-empt programs['L'] = {} programs['L']["chaff"] = 1 programs['L']["flare"] = 0 programs['L']["intv"] = 1.0 programs['L']["cycle"] = 20 -- Flare pre-empt programs['M'] = {} programs['M']["chaff"] = 0 programs['M']["flare"] = 1 programs['M']["intv"] = 1.0 programs['M']["cycle"] = 20 -- N Test Programm programs['N'] = {} programs['N']["chaff"] = 6 programs['N']["flare"] = 6 programs['N']["intv"] = 1.5 programs['N']["cycle"] = 13 need_to_be_closed = true -- lua_state will be closed in post_initialize() Presets are available from A-M. Here is my own: program N. NOTE: If you change default programs or create new programs, keep the CMS limitations in mind! Interval: Inputs in 0.25 sec. steps from 0.25 to 5 seconds. Cycle: Valid inputs from 1 to 99. Advantages: - Change default programs (faster as in cockpit) - Create new programs N-Z (faster as in cockpit) - Permanent stored and loaded at every start up/ respawn Hope, that helps anyone. kind regards, Fire

Well I guess you could say it is finally here. I have been busy doing other things and grew sick of looking at this on my computer, so here it is. Fully multiplayer compatible. I recommend uninstalling ALL currently installed mods before installing this. Not intended for use on older systems. Best used on high performance computers. Special thanks to Blaze and the LockOnFiles team. SIM-MOD A-10A Warthog, Gys and Valery F-15C Eagle, 3GO Su-27 Flanker, and many other included mods. SIM-MOD A-10A Warthog + A-10 cockpit fix by UWBuRn SIM-MOD A-10 Weathered Skinpack by Ruggbutt "Live To Fly, Fly To Kill" A-10 skins by Deadman F-15C Eagle by Gys and Valery F-15C Cockpit textures by Aeroscout, DoctorK, and Mustang F-15C 141st Wolves Turkish Air Force Skins F-15C Inner burner textures by Postal2 JASDF F-15J textures by Yakuza2 3GO Su-27 Flanker Sorbcija Model by Albacore 6DOF Cockpit Mod by GOZR Ricardo's HD Cockpits Walmis Weapons (only AIM-7 and R-77) Teka Teka's Coastline Mod Teka Teka's Realistic Moon Small Waves fix by Mario80 Concrete FARP by Mario80 B-8V20A, B-20, UB-32M1, UB-13 models by Beczi DeeperBlueSky v1.1 mod by Blaze & SilentEagle CloudMod v1.0 by Mitch Janssen Russian Blue Afterburners by Majesco Hardened Aircraft Shelter Textures v4.0 by Mustang Replacement Structure Texturepack v7.0 by Mustang Naval Vessels Metal Framework Texture Fix by Mustang Black Road Textures (Full Markings) v2 by Mustang Total size = 474Mb Download: Mirror 1 - Direct Download (2.11) Mirror 2 - MegaUpload (2.11) LockOnFiles Thread: Here LockOnFiles Download Page: Here ===Version 2.1=== Fixed F-15C skin list for America and Israel ===Version 2.0=== -Completed version. -Included multiple miscellaneous fixes. -Added multiple aircraft skins and files. -Added 2000L fuel tank to A-10A. -Added weapon model upgrades and fixes. -Added multiple environmental upgrades. Known issues: -LUU flare model and texture may not show up correctly in-game. -CBU-97 has been configured but removed from the A-10 loadout due to an unknown problem that causes FC2 to crash to desktop on weapon release.

I don't have a problem with the plastic. CH makes plastic all over and their sticks are all very high quality. Something that you don't get guaranteed for a metal joint. Besides that, I've already modded my TMW. I'm simply not a friend of 400 Euros Arm-muscle-trainers. As a friend of mine said: Planes have to be flown with two fingers, not like a constant fight with white knuckles. I was pretty sad they didn't make the spring for the stick adjustable, but I simply removed it. Instead I moved the 4 smaller springs on top of the ring. Now the friction along the steel tubes is largely minimized and the stick is very smoothly move-able to all extends. No center play, no uneven resistance. Very comfortable. And you don't need to be Schwarzenegger to make little precise adjustments in a dogfight. Besides that, it eases the pressure on the plastic balls. Works nice for me.

Good news, I have taken the grease of the spring and added it in to the ball socket, now the stick is smoother. The question remains for how long it will be this smooth. I guess that the amount of grease differs on each unit, so if you incounter the sticktion and you are bothered about it, you could open *at your own risk* the stick and do the same as I did. If TM is paying attention here, it would be good not to save on grease at the production line. I'm very happy to make this "discovery" since I was afraid the 400 euro stick would not live up to all my requirements. For now, it does. If someone knows what type of grease TM uses, please post it as it looks like we will need to add some grease every now and then. *EDIT* Adding grease did not solve the problem over time.*EDIT*

Несколько пожеланий и идей Пожелания (надеюсь, скромные): 1) Исправить недоразумение, когда строения сбивают самолеты. 2) +1 к надежному контролю за скоростью при рулении, взлете с рулежек. Но здесь возникает другая опасность - вулч своего аэродрома. Поэтому можно предусмотреть снятие ограничений на скорость руления и возможность взлета по рулежке в том случае, если возле аэродрома появляется вражеский борт, скажем, в радиусе визуального контакта (2-5 км или сколько там потребуется). 3) Ввести также жесткий контроль направления взлета. Сколько раз я был сшиблен или почти сшиблен "оптимизаторами" на взлете в темноте - не передать. Например, при разбеге против установленного напраления взлета виртуальный РП подает радиокоманду на запрет взлета, а по достижении некоторой скорости (скажем, 180 км/ч) пилот-нарушитель выбрасывается с сервера, борт исчезает с полосы, но не засчитывается в потери. Если же произошло столконовение союзных бортов на взлете до достижения виновником 180-ти км/ч и борты таким образом записаны в потери, а пилоты погибли, нарушитель правил бпнится на 10 минут (например). Соответственно, запретить руление по взлетке в любую сторону - если скорость борта не превышает 50 км/ч (например) в течении 20 секунд (тоже например), виртуальный РП требует немедленно освободить полосу и при невыполнении требования пилот выбрасывается с сервера. Борт просто исчезает с полосы и также не записвается в потери. Точно так же - при возникновении столкновений нарушитель банится на определенное время. Таким образом мы избежим раздолбайства и вредительства со стороны несерьезных товарищей. 4) Часто бывает полезно прокладывать индивидуальный маршрут полета для выполнения какой-либо конкретной задачи. Например, горами на ПМВ пройти во фланг группировке противника. Было бы неплохо иметь возможность индивидуально составлять маршрут полета для своего борта, чтобы он выводился на МФД. Также, можно было бы предусмотреть возможность сохранить маршрут в простой конфигурационный файл текстового формата для многократного использования и передачи коллегам по авиасоединению. Еще можно обеспечить опцию показывать свой маршрут союзным бортам при нажатии какой-то кнопки в интерфейсе, чтобы скоординировать действия индивидуальных пилотов и целых групп. Таким образом мы увеличим полезность опции маршрута на МФД, ведь сейчас он практически не используется в сетевых вылетах. 5) Реализовать работу обзорных РЛС различного радиуса действия, чтобы их услугами могли пользовать РП-человеки при поединках "отряд на отряд". РЛС должны честно облучать самолеты, выдавать их координаты, иметь ограниченную зону обзора (не только радиус действия, но именно зону обзора - специалисты поймут). Сейчас единственные "глаза" РП в таких вылетах - РЛС комплексов ПВО. Соответственно, уничтожение коплекса ПВО - убивание двух зайцев одним выстрелом - обезоруживаем противника и ослепляем его в данном районе. Обзорные РЛС поправят эту ситуацию и сделают поединки отрядов более интересными, потому что РП сможет видеть вражеские борты даже при полном уничтожении системы ПВО, а противнику придется изощреннее строить тактику. Пункты 2 и 3 увеличат порядок в сетевых вылетах сборных солянок. Ведь только при поединках отрядов можно договориться о правилах руления и взлета. А при обычных сетевых вылетах сервера временами напоминают аркадное месиво - кто куда и как хочет, так и рулит и взлетает, мешая другим. Ну а пункт 5 добавит реализма при командном взаимодействии в групповых вылетах. Вообще, хотелось бы побольше узнать о том, как в симуляторе реализована работа радиолокационного оборудования (на самолетах ДРЛО и комплексах ПВО), если возможно.

Итак, приступаем к бэта тестированию! :) Прошу вносить предложения и замечания. Кому всё нравится - не буду возражать против печеньки в репутацию... ;) CH CM_BASIC_GUIDE_RUS_V2.rar

Multi monitor set-up guide: DCS-A10c & BlackShark 2 Display your MFCDs, CDU, RWR etc on a 2nd, 3rd etc monitor Initial note: This guide is to help people create bespoke multimonitor configurations in DSC-Warthog, no matter what your configuration the principles are the same. Please add any tips or correct any errors i have made. I'll adjust this accordingly. My set-up is two 22inch displays side by side, i'll use this as the primary example, but the logic covers any set-up. I have included several monitor set-up examples to help explain the principles. Essential Requirements: Full screen OFF (ingame). Extended desktop enabled in Windows. The 'primary' monitor, in Windows, needs to be your top left most monitor, otherwise you may have problems. You need to create one lua file. BlackShark 2 note: Shkval is Left_MFCD Abris is Right_MFCD ** Before editing DCS files please read this post: http://forums.eagle.ru/showpost.php?p=599686&postcount=1 The Guide: 3 steps Step 1: 1st thing you need to do is workout your total resolution of your combined monitors. Use the image below to help you work this out if you are unsure. Here you will find 3 example layouts.. Note this figure down, this is your combined resolution. Step 2: Create you own bespoke multimonitor *.lua file and save it here: \Eagle Dynamics\DCS A-10C\Config\MonitorSetup\ How do this: (Read through this entire section before starting your *lua file), 1st time through you might well go WTF!, but trust me it is not that complicated. :) First look at the default existing files in this location; (\Eagle Dynamics\DCS A-10C\Config\MonitorSetup\). They are good examples and the default ones provided with the game: There is one example original ED file: LMFCD+Camera+RMFCD.lua My example: My_example.lua NOTES: What it all means: ED have used wording rather than numeric x/y coordinates. This is to allow flexibility. You can also use this format, but i find it more complicated, so i use the numeric pixel option. In ED's method screen.width = the combined width of all your monitors, (x), screen.height = the combined height of all your monitors, (y). So for me screen.width = 3360 (2x1680), screen.height = (1050) I wanted both MFCDs on my 2nd monitor, this is located on the right of my main monitor. Both my monitors are 1680x1050. Center = your cockpit view x=0, y=0; is always located at the top left corner of your 'primary' monitor, in Windows. The x & y coordinates always refer to the top left corner of each element. i.e the location of each MFCD is their top left corner. You do not generally need to edit viewDx, viewDy or aspect. But it's worth checking the aspect ratio. This is calculated by dividing your width by height of you cockpit monitor. name = is the name that will be displayed in the game options drop down under Monitors. (Make it unique) width = & height = are x & y resolutions in pixels associated with each item, cockpit (centre), MFCDs, RWR, CDU etc. Look at the spoilers below to explain the x/y system: Screen coordinates explanation: 3 example setups to help explain screen coordinates. Both x & y start on the top left corner of the left most monitor. x goes across the horizontal while y goes down the vertical. My example set-up displayed: - putting it into practice, refer to my lua file My_example.lua above to understand what is going on. Ok now you should be able to start creating your own bespoke multi-monitor file accordingly to your own set-up, if i have made this clear enough and you have wrapped your brain around how this all works. I'd suggest you use my example above and edit it to suite your setup. You need to save this file as file type .lua and save it in \Eagle Dynamics\DCS A-10C\Config\MonitorSetup. Step 3: Launch the game.. go to Options. (Here you need to do two things) Firstly you should now be able to select your bespoke file from the drop down list labelled; MONITORS (If it is not in the list you have most likely made a small mistake with the lua code.. check for missing { , ) etc. if any part of the code is missing it will not be available to select.) Secondly you need to enter your combined resolution, you can simply type this in. This is the total resolution you worked out at the start of this guide. See image below: Your aspect ratio will alter itself. General Notes: You can edit you monitor file on the fly, i.e without having to quit the game. Can save a lot of hassle. If you don't get the results you want simply quit flight, alt tab, edit the file, alt tab back and click fly again... your new setting will be used. I hope this is clear enough. Enjoy. Screenshot of my set-up: ____________________________________________ ____________________________________________ Advanced section: Adding CDU, RWR, Clock etc as Viewports = Please read icemaker's thread http://forums.eagle.ru/showthread.php?t=70716 on how to do this. Below is my present setup incorporating MFCDs, RWR & CDU Incorporating Hawg Touch: Clear Dark's Hawg Touch program: http://forums.eagle.ru/showthread.php?t=71729 My Hawg Touch profiles: http://forums.eagle.ru/showthread.php?t=70364 I'll be releasing a new Hawg Touch profile for the MFCDs, CDU & RWR shortly. Just awaiting to clear up a issue with it. Here is what it looks like: Updated 27th June 2011.

I thought I would release the beta version of my airfield diagrams for DCSW as the charts are at the point where I need to print a copy and then work my way through the airfields to get the rest of the detail right. The radio frequencies, elevations, directions and measurements should be accurate with the mission editor the F10 view and the A10C's internal MAGVAR. I'll do the release as a separate thread to the design discussion to avoid the release getting lost in that thread. I'm working through tower placement and taxiway labelling in addition to points of interest however a lot of the Russian airfields dont have the taxiways labelled which complicates the matter, I'm thinking it may be worth waiting until the DCS release prior to revisiting this. I've also added references to the ADF's from the BS manual and if the interest is there I will release a Russian air force version with Metric measurements once the maps are finished. If anyone picks a bug or has some reference notes for the airfields let me know. UPDATE: Updated airfield name plus some error corrections For those of you printing this, I recommend printing in color to A5 directly, as the map lines blend better in color then gray-scale, however you can print 2 per page on A4/letter Airfield Diagrams.pdf

Сажают, и без шасси, и с передней стойкой... Посмотри...

I must say though, Frazer...I had a lot of respect for you before, and this only raised it higher. Too many people would simply say "Oh, this sucks" and walk away. I'm not happy that this appears to be a QC issue in terms of how the grease is applied (and how much)...but there's worse ways it could've played out.

No, just the right throttle is the same between the A-10C and the F-15E. The left A-10C throttle is from the A-10A.

I like to engage light targets at 2 miles out with my cannon. As soon as the range indicates 2.0, I fire and break away. This works fine for light armored targets. I also don't like to zoom, especially on my HUD. I go into the IFFCC menu page and turn off the CCIP occult. I lock my target with the Targeting POD and I switch to CCIP mode. I put my gun cross over the targeting pod diamond, engage PAC 1 and fire. I tought myself how to fly the A-10C in Nevada and it was alot easier to spot tanks on the desert ground. Once I started flying the instant action missions, I found it really hard to spot even a URAL truck in the grass. That's why I figured out a new way to be able to engage my targets from the safest distance possible.

@Necroscope: It is absolutely fine to put the Warthog stick onto a Cougar base. Everything will work except the new button (CMS push). Based on one person's input, it may not seat properly on a U2NXT Cougar base, but mine worked perfectly on a stock Cougar as well as FCC...and I've been told by other VTBers that it worked fine w/ FSSB as well. @Frazer: I had a final preproduction unit that I ran from the end of May into October. It was always smooth except one day when the (hand cut, preproduction) o-ring slid a bit out of place and I had to reposition it. Hard to say how many hours I put on it...but it had at least some use nearly every day, and usage was pretty heavy the first 2 weeks during preparations for E3. Teej

Чет вспомнилось еще - бортовые номера и лейблы чтобы можно было с клинта задавть. А то бывает сквады вылеты делают и вечный "горох". Основные схемы окраса пусть от сима будут (выбираем из списка клиента) а вот номера и лейблы - чтобы можно было самим с клиента давать (ники то идут,а вот жтого нет).. ограничения по размеру лейбла только сделать, ну а на модели место привязки на любой тип ЛА ИМХО не так уж и проблематично... ну и ссовтетсвенно отдельный кешь на лейблы чтобы был и по чесуму и датам проверялос, чтобы валиднасть была. Ну и с клента это тупо на сервак и так загрузится в папку а клиентам если что с миссей и придет, если у клиента не будет лейбла... (чет расписался про КО) ПыСЫ как вариант сделать 1 файл в котором будут сквадовские лежать, причм этот фал чтобы пбыл валиндным - дерадать его у ДКС, ну и обновлять по мере наполнения... либо при поможи перепаковки у клиентов чтобы не передвавть все время, а выкачивать дельту раз в 2 недели, если будут именения, или раз в неделю... ну и картинки на нормальность чтобы проходили как раз времени зватит, тем более сквады уже в основном устаявшиеся еденицы и их не так уж немеряно... ПыПыСы тригеные зоны - для опрелеления объектов зданий в зоне - "мертвы" - "целы" (типа 10 домов попало в зону и сколько потом после налета целых чтобы число выдавалось) и зона "мост" - цел, уничтожен. А то вот с мостами через "же" целостность проверять приходится, причем автомобильные можно проверить, то вот ЖД иногда не реально, даже вернее не реально совсем.

A note there - there is sometimes extreme overclock headroom in cards. For example I saw some versions of ASUS 5850's clock up above 1GHz in core clock, making them handily beat 5870's. If overclocking is on your radar you should make sure to choose the card specifically for that, since there are manufacturarers that bin the chips specifically for this purpose and while they charge a premium it is often "worth it" compared to the next step up in architecture version.

Про заброшенность говорить пока рано. ЛОКОН конечно уже в истории, но что-то в замен его вероятно появится.

Тынц :pilotfly:

Just finished my 2nd LOFC movie :) Btw, it's made on old LOFC 1.12b :P Comment, rate please ! Watch in HD !

Well, the general idea is that you should set your texture detail in a game's settings such that your graphics card never gets overloaded. One possible reason for stutters and graphical issues can be that when you set it "too high" the card will start borrowing regular RAM for additional vRAM, which causes an insane amount of traffick through the PCIe controller and memory controllers. Issues with HDR/AA/AF on budget cards is usually caused by their commonly severely cut compute-core budget (often no more than a quarter of a "fullsize" card, and slower clocked to boot). But yes, future-proofing is definitely an argument here. I am giving it some thought, but since I'm only going for a 470 on my upcoming build it'll be easily replaced whenever I need it, so I'll settle for the 1.28GB option from ASUS on that. (The price diff from the 800MHz 460's to the 470 is so small I went for them, even though the custom chipset ASUS uses on their 460's is very very tempting.)

next DCS what Do you wnat the next DCS to be i really really would like the harrier jump jet and here is why: now that would add an extra dimension to Flying don't you think?

I have been putting the latest beta of A-10 through the paces, and I still think Falcon 4 Allied Force is a better military simulation. I'm not trying to start a fanboy flame war, but I find it incredible that a sim that first started out in the late 90's, and later upgraded by Lead Pursuit a few years back, is still the king of military flight sims. I'm not saying A-10 is bad. It's just not at the level of Falcon 4 Allied Force yet. I hope the final version comes close, and future patches narrow the gap. I would also recommend that anyone considering checking out Falcon go for Allied Force. In my experience the free version of Falcon are more trouble, and Allied Force works pretty much perfectly out of the box. Just get the HiTiles addon and Aeyes widescreen cockpits. Multiplayer is excellent and stable as well. Falcon 4 Allied Force is still the king IMO.

I've done this type of post elsewhere, but here's a reference of about what you'd see from 1 nautical mile above. I know visual acuity varies from person to person, but in my experience this seems like a pretty accurate depiction. Do you really think you could see an infantryman from this slant range? I'd say you'd have your hands full finding a tank from this distance let alone a single manpad toting individual.

The context you are looking for is really very simple. You want to fly from point A to point B. A and B can both be waypoints, or, A might be your current location, depending on the type of navigation you want to do. But really, anything you think of in navigation is nothing more than geometry - A, B, and how you get from A to B. Is there a designated course? Will you fly it? If this is the case, just set up your instruments appropriately for the task, and the manual tells you what you need to know to set them up. You might find it a chore now, but in time you will start finding these things very useful.

Upwind is the same as your departure heading. By the way, military aircraft often (always?) use the overhead break pattern for landing. A good tutorial using Falcon as reference is located there: http://www.72ndvfw.org/resources/train/OverheadBreak.pdf

Awesome! Thanks for your service. I personally haven't deployed with the A-10's, but was part of a unit for 5 years. We recently converted to an Airlift wing.

I cant wait! I just got back from Afghanistan loading on these bad boys so Im stoked to test drive these! I have been working on the A-10 for 2 years now

The manual doesn't assume you have the TM HOTAS, but it does refer to the actual controls the pilot would be using. Same thing as when it says to turn the TGP switch on; it doesn't assume you actually have a switch labeled "TGP", it just means to do whatever you do to flip that switch in game. It might be by clicking on it, or using a key binding, or a voice command, or just thinking really hard about it. So when it says "DMS FWD" it just means "do whatever you do to cause the command 'DMS FWD' to be sent to the game". In the controls screen, one of the categories is "HOTAS". This lists every control which is on the real-life stick and throttle of the aircraft. You can bind these controls to your own stick, or use the keyboard commands. There isn't a command listed to "adjust zoom level of the TGP". The keypresses for doing those are whatever are assigned to the "HOTAS DMS Up" and "HOTAS DMS Down" commands in the controls screen. Many of the HOTAS switches have a different function depending on what the current Sensor Of Interest is; which is what those tables in the manual show. DMS Up/Fwd changes the scale of the DMS if that's the SOI for example, or switches to the next waypoint if the HUD is the SOI. There are some zoom commands available in the controls configuration, but they allow you to control the viewpoint (or "game camera" if you will), not a function of the aircraft.

I don't think it's cheating at all; you get a better look at your target, but you also lose all peripheral vision, and if you zoom right in to levels that might be unrealistic for a pilot with good eyesight to achieve 'naturally', you pretty much sacrifice all situational awareness. Think of it as game-enforced target fixation. Not only are you completely focused on one single thing, but even if you do suddenly remember there's a world outside of the straw you're looking through, it's very disruptive to actually do anything about it. It probably also depends on what your setup is. If you've got a large, high-res screen, zooming in will be much less necessary than if you're playing at a lower resolution.

Well in R/L you would have ground troops and smoke to light the target area. Also zooming in a sim is like someone else said compensation for draw distances and graphics. Now using external views well thats a bit of a different subject if you ask me... But I can see both sides of the argument. The TGP is there for aid and works fine but sometimes you just need that extra zoom to confirm what you are doing.

Real pilots most certainly DO NOT use binoculars when straffing the target ;)

There is NO latch in the real jet or any dual throttle mil a/c. You fly with the throttles the way they are and use them independantly to start the A/C and also sometimes if needed or in an emergency independent use would be required. Other times you just move them together for dual thrust/engine RPM's as required. Nope...no latching mechanism in the real A/C. Fly em unlatched like the real thing. Its fun! AM sure TM can take it. Know from job experience..sorry no pics of the throttles but here's a few of some fun on the job! :)

nothing special, straight out of the screenshots folder

Guys, Lets get some reality in here shall we. I was in the RAF for 12 years have stick time on Gazelle, Puma, Merlin and some fixed wing which was mostly due to the fact that my last 4 years were in the Test and Evaluation arena and I had good access to people testing fixed wing that offered trips to me as I did to them. So, take this from someone whose done it for real, and done it for real whilst getting shot at in some instances. If you want perfection I would go out and acquire a military grade flight stick, throttle and rudders and convert them to PC flying. You'll then get what the guys in the field get, warts and all. Would it surprise you to hear that all the metal linkage in a Puma between Cyclic, Collective and Yaw pedals introduces a few tight spots, lose spots and general non fluidity of movement across the whole range? Mention it to the maintainers though and you'll get what I did when I mentioned it one "Sorry, but a bad workman blames his tools". You know what the perfect joke flying in the military was? Every time you climbed into an aircraft you knew you were climbing into the one supplied by the cheapest, good enough just to do the job supplier. If you'd rather get something closer to perfection then I'd suggest that you order from a supllier here in the UK (Flightstore) who do a helicopter set of controls for £1499.00. Have a look here: Thats 3 times the price of the hog and I can tell you from having a go with it, not a massive amount better for it. Its for rotary wing I know, but I'm sure there's something else on the market for fixed wing too if you look for it. My Hog and a set of rudders came in at under £450. So, there's the rub. I know the Hog isnt perfect, and yes it could have been made completely of metal and yes it would have been more expensive at a guess. I'd rather get the best on the market (in my opinion anyway, and everyone has one) than the old worn Cougar that I had, and for a short time the abysmal G940 that was nothing but trouble. The price is right for what you get and I think its as good as you can expect for the price. A great suit is £2500, a good one is £500, an OK one is £200. I think we have a good stick, and throttle in the Hog for the right price range. We could all go make our own and have something perfect for us, as is we have something that's perfect enough for the market. It doesn't make it bad, it just makes it affordable (ish) and good enough, that's all. Just like all the real machines out there that every nation asks its youngest, strongest and best to go into harms way flying, good enough for the job at the best price point the seller and buyer could agree on. By the way I'm not affiliated with either Flightstore or TM. I'm just a user like everyone else here.

ГС 2 на win7 64 ultimate, до вчера все работало, а вот сейчас не хочет. -error loading module 'me_openfile_form.lua' Unexpectred symbol near "ъ" Открываю значит файл... а там одни кракозябры :lol: ! Кто-нить может кинуть свежий файл? С кракозяберного на английский декодеров, увы, нет :(. Заранее благодарен. ПыСы- вот как-то так... http://i1238.photobucket.com/albums/ff486/gotrol/krako.jpg

4SHIP - BE F16

На сколько я понял, ты не видишь цели. Ярлыки как раз помогут помочь тебе в этом. Тем более что их можно настроить, в том числе дальность и объем отображаемой информации. Что касается видимости объектов, тот тут все сложно. Реальные летчики говорят, что в жизни также если еще не хуже. Кроме того мы ничего специально не делали для ухудшения видимости объектов по сравнению со старым ЛОКОНом, получилось так что с новыми, более контрастными текстурами земли и переделкой старого тумана, объекты стали менее заметны. В А-10С возможность вставлять неограниченное количество картинок уже есть.

как же я их включу в онлайне? и потом ярлыки это немножко не то что я просил. согласен, но сейчас этого никто делать не желает, или нет возможности подробно описывать задание для каждого крафта.

Thanks guys! :drunk:

True. After years of stagnation this seems like a shock therapy for dawdlers like me ;)

Просили без флуда. И вообще, это требование - есть полное непонимание конструкции движка игры.

Хорошо бы еще размер увеличить. 512х512 очень мало.Сейчас это в ЛО2 выглядет просто ужасно и крайне не удобно. И воду под землёй убрать бы:pilotfly:

1. Идея с собственными метками на карте реализована в Арме, например. Только обязательно нужно подписывать автора метки и следить за флудом. Потому как на карте первым делом появляются надписи типа "Админ - м...к" и далее полный набор заборного творчества. 2. Я считаю, что для пилота это перебор. Пилот должен только читать карту. Сообщать о чём то обнаруженном коллегам он должен по радио или чатом. Автоматом по триггеру наносить на карту всё над чем я пролетел на 10000 км - нечестно. Я иногда и на 100м не вижу толпу студентов к которым судьба меня принесла. Получается что: 3. На карту должен метки наносить картодел. И они не должны быть привязаны к реальным боевым единицам (могу ошибаться, но сейчас метка на карте появляется только если под ней на карте реальный объект имеется). А тут именно метки. 4. А вот насчёт редактирования карты он-лайн - давайте помечтаем. Правильнее было бы иметь отдельный слот для РП. Он в крафт сесть не может. Он имеет цвет своей стороны, со всеми вытекающими отсюда следствиями, и вот он имеет возможность ставить метки на карту по Ф10 прямо по ходу полётов. Хорошо бы прикрутить в этот же слот что то типа Жабы... Естесственно, что всё что он нарисовал видно только игрокам его стороны. Можно со слоями, дабы информацию можно было назначать группам. Ну а дальше полёт фантазии не остановить: возможность менять ППМ крафтам для вывода их на цель, менять задачи наземке и т.д. и т.п.

текущее != известное последнее правильнее и интереснее. если бы было именно известное, то карту реже бы отключали. к сожалению прогнозировать дальнейшее развитие событий и отображать будет наверное слишком сложно, хотя опять же если какие-то шаблоны и вероятность удачного прогнозирования.

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

No dudes you've got it all wrong. The china hat is called the china hat because it is red, and red is the color of communism. In the A10A this was called the Sovjet hat but it has been renamed for obvious reasons. EDIT: It is also referred to as the Osama hat among pilots deployed in the middle-east.

Concerning altimeter settings this might clear the story up a bit...: In general all ICAO associated countries(that's nearly the whole world, not sure about russia tough) use the standard icao regulations concerning altimeter settings. Basically it works this way: As Ronth pointed out there are several altimeter settings: QNH = pressure above mean sea level QFE = pressure at altitude of current airfield QNE = standard pressure setting according to ISA which is 1013,21 hectopascal The pressures can be given either in hectopascal or inches of mercury they are different units but represent the same pressure. In europe hectopascal(hpa) is used, not sure about the rest of the world. 1 hectopascal is +- 8 meters which is +- 26 feet. The altimeter setting defines at which pressure your altimeter indicates 0. So when the pressure on the ground at an airfield(this would be the QFE) is 1018 hpa and you are standing at that airfield and set the altimeter at 1018 hpa the altimeter should indicate your altitude as 0 feet. The regional ATC defines a transition altitude(TA) and transition level(TL). When departing the altimeter is set to the local QNH(pressure above mean sea level) which is given with the startup clearence and is also pronounced in the local ATIS. The TA/TL are given in the ATIS aswell but are not given directly by the ATC(nor with ifr flights). When climbing after departure and passing the TA you should enter the QNE(1013,21 hpa), this is not instructed by the ATC but a standard procedure any pilot(civil/mil) should perform. When descending through the TL you should enter the local QNH which is given to you by the ATC, e.g. "PH-WNM descend to 3000 feet, local qnh 1013" Now when above the TA/TL everybody has the same altimeter setting: 1013,21hpa and this is obviously for a reason. When above the TA/TL the ATC does not give altitude instructions in feet but in flightlevels(FL), 100 feet is 1 flightlevel so FL100 = 10.000feet and FL55 is 5.500feet. When an ATC seperates 2 aircraft flying in the opposite direction by giving them a 500feet altitude difference(minimum alt seperation for ifr flights) and they both have 1013hpa the ATC can be sure that the aircraft will pass each other with no harm. If this wouldn't be done imagine what could go wrong. The N123A is flying at FL120 with the local qnh from his airport which is 1010hpa. The PH-WNM is flying at FL125 with the local qnh from his airport which is 991hpa. They should have 500 feet altitude seperation: FL125-FL120 = FL5 = 5 x 100 feet = 500 feet. But they have different altimeter settings: 1010hpa - 991hpa = 19hpa = 19 * 26 = 494 feet. Due to their different altimeter settings the PH-WNM actual altitude above mean sea level is only 6 feet higher than the actual altitude above mean sea level of the N123A. So basically the ATC has seperated them with 500 feet altitude difference but due to invalid altimeter settings they actually only have a 6 feet altitude difference which would obviously be very very dangerous and would nearly certainly result in a collision... The standard TA/TL is 18.000 feet / FL180 but in some countries their are different standards. For instance in the the Netherlands the TA/TL is somewhere between 4000 and 7000 feet / FL40 - FL70.

Sorry Guys but my english it's no good and i read the manual just a little at a time just because my English is not good. I've found just yesterday that buttons configuration about the FAC, in the PDF file (that you can find here in the forum named "A-10C KEYS.pdf "), at the bottom of this PDF are the keys for the FAC and I was just curious as to how they affect the SIM and if they were fully implemented. Since they are keys in the configuration ... I simply asked :) I really have never fly on an A10 (unfortunately) so I can only know by reading some things here and there on the Internet and I dont've an friend pilot that tells me how things are actually in a real mission. Now i know Thanx

That means, we need a "real" datalink, not the SADL (iirc this is just a datalink for friendly groundunits and other fighters ... but position only. No targetinformation transfer). So you can launch your G-Mav and turn out ... nobody has to laser the target. kind regards, fire

Only few hours of work left, the skin will come with authentic set of numbers too. After that I'll do the Sky Hussars skin then i'll release the three skins in one pack.