Leaderboard

@Kuky The problem is the file name corretly line common = ".\\Bazar\\World\\_MIG-21_YUG.cdds";

I've made a keyboard layout for printing (PDF). I've also uploded it to http://files.digitalcombatsimulator.com/en/86355/ where it is being reviewed. I've compiled it from the A-10C Key command list.xls and from the A-10C KEYS.pdf. If you find any errors or missing any default(!) keys, please report it as a comment and I'll update it. :book: dcs_a10c_keyboard.pdf

Sorry, it's a top secret system. :P

Если скачаете и установите патч 1.1.0.9 или полную версию 1.1.0.9, у Вас будут русские субтитры и английская озвучка.

The ASI won't register the low speeds used for taxying. Fortunately, the aircraft is equipped with an Advanced Taxi Power Setting Synchroniser (ATPSS) device. This gives the pilot visual feedback on the power setting used and and the resulting speed trends. It is easy to miss at first, but if you look closely you can see it above the lower cockpit frame. It is transparent and made from plexi glass.

Three today's screens.

That was it yufighter, it's working now! Hvala! :thumbup:

kinda how I feel :D

Taken from some multiplayer flights :) 6 by Ross A J Miller, on Flickr 8 by Ross A J Miller, on Flickr 7 by Ross A J Miller, on Flickr 5 by Ross A J Miller, on Flickr 9 by Ross A J Miller, on Flickr 3 by Ross A J Miller, on Flickr 2 by Ross A J Miller, on Flickr 4 by Ross A J Miller, on Flickr 1 by Ross A J Miller, on Flickr

Hey Kuly I don't understand what the line should be in the graphics.cfg file.Can you post a copy paste from a working line of code?Sorry to bother yo uall with this but I simply can't figure it out :d When I tru to open the file you specified my notepad freezes and I get (not responding) message.What should I do?

You're right. We fly these approaches as 90° Roll-In maneuvers. To do so we generate an IP at about 4-5nm away from target. Now let's say the heading from IP to target is 090°. We now use the offset-function to generate the roll-in-point. In this example it would be target-mark/wp as initial point and 3551.8 (355 is the direction off the target and 1.8 is base distance + 0.2nm turn-radius). Now generate a new flightplan: 1. IP 2. RIP 3. Target (you can as well generate the AOD with the offset function and feature it in the flightplan) 4. IP. TAD will now show a nice approach triangle. And yes: 375 is the planned release speed, but I don't pay too much attention too it, because it's enough workload to begin with flying the approach with the target well aligned at checkpoint alt! However it's really fun, once you manage to take out MBTs with single Mk-82s. :)

Я точно не помню , после 20й попытки был в бешенстве , при попытке соединения есть окошко "кнопка" запросить пароль , нажимаешь на неё , и тебе на мыло приходит ссылка , которая выводит на изменение профиля на домашней странице home ED , помоему я перешёл по ней и ввел новый ник и пароль после чего всё заработало . П.С на всякий случай ты меняешь пароль на домашней странице ЕД , не на форуме , т.е у тебя могут быть разные ники на форуме и ник регистрации на сайте . ЕД вы чего молчите ?

Я указывал. Модификаторы -> Добавить -> Добавлял нужную кнопку джостика. Потом её можно указывать как модификатор где угодно.

Got a "beta" version of my mod working... you can install it and fly mia/Smokey's "Operation Saturn". Gonna release the "official" first beta version when I integrate most of chatIOlibv2 functionality. Very shortly after that, or perhaps before I "officially release" it, I will be doing some guides. I just tried to hack into my mod, from the mission environment, and access functions I wasn't supposed to in the net environment. The security method I used stopped me cold in my tracks :) It's really pretty cool watching the daemon and print passing data into net... here's a snippet if anyone is curious: Some of this communication could be reduced by implementing Luasocket in unprotected environments, but a good deal of the communication will be from a protected environment to an unprotected environment.... just because the only environments that a mission maker can access, or can be accessed via a trigger, are protected environments. But gonna definitely need that print function next patch to make it easier for folks to use this.

Part 2 of first post.... Last night I finished cutting the gauges out using a basic hole saw set and jigsaw for the larger holes and MFD's. Cutting done! Paint Check! (Yeah I changed to primer grey) MFD's Check! Both MFD's Check! Plexiglass backing! And that's the first couple of chapters on the project. My next bits of planning include using an old projector I have to display the gauges and MFD's in one image using helios. It's all guess work right now and might not even work but at the moment I'm crossing each bridge as I get there. I don't plan to use replica switches and I'm leaving out a few gauges and will probably leave out a few panels when I get to the side consoles. As for the side consoles I using another members work as a base Dimebug. He's done great work creating plans for the side consoles and I'll use that as a starting point but I'll probably modify it to fit my way of doing things (Thanks for your excellent work and inspiration Dime). I owe a lot of ideas, methods and inspiration to many pit builders here and on other sites and I thank you all as you're too many to name! I'll keep updating the progress as I go along. Thanks for reading, Hitch

Блин, как только доделаю свой "полетное место" , наверно в окончательно уйду в мир DCS. потому что на сегодняшний день это единственный симулятор летая в котором не просто хорошо проводишь, время но и развиваешся как человек интересующийся авиацией в целом.

stop (stp)v. stopped, stop·ping, stops v.tr.a. To halt the motion or progress of So stop criticising me..It's just single post..

Simple solution: Those modders that have issues with existing modscripts, or specific wishes with scripts they want to implement, talk to each other about them. There appears to be a couple of you. Start a thread and discuss. This will allow a couple things: 1) A central location where developers, testers and other interested parties can find your thought. 2) A central location for you to learn from each other about any workarounds that may exist. 3) A central location that testers can peruse towards assembling a shortlist to bring up with the developers. Right now the devs have no way at all to really know what you guys use, how you use it, and why. There's no way for them to make an informed decision. This change was brought about due to the exposure of a serious security vulnerability, but there was very little in the way of resources for the developers to learn how to plug the hole yet still keep things in good shape for modders. They have a job to do which is mostly spent hunkered down over an SDK writing code. They don't have time to read scores of threads spread over many forum sections. Moderators do, but we may not have the time to really think about how each thread ties into another, and it's only one of us that has a really solid grasp of LUA. So please, help us help you. Collect all your thoughts in one place. I'd recommend starting a relevant thread in the wish list section, discuss it well (and try to help us out through including some layman-friendly explanations of what things you suggest would do) and we might be able to make things happen for you. But in the present chaos, it'll be extremely difficult.