Leaderboard

Is this offer still good while supplies last?

Away ye Go :D

Im repping anyone who posts in this thread, so get em while still hot!

Of course any rep you might give me will only be worth about 70% what it would have been worth 3 months ago before the drastic fall in value of British currency compared to the US........

lol done!

Wow from what occasion? :P Free repness, damn nice :D

Wow, this is awesome! So awesome Im gonna rep you back :thumbup:

"Udijeli malo repa Bog ti sreću dao..udijeli malo repa, Bog ti sreću dao..i zdravlja i repa i tako dalje i tako dalje.."

Someone said a free rep??? :D

It happens. 99% of the world's population are decent people. Most of the rest are in Hyperlobby.

REP ME!!!! :P

(Link to the PDF for people in a hurry.) UPDATED: Link now points to a TV3-117VM/VMA Study Guide.

offer still valid? :D

Hey viper! :P rep imbound

I wish I could keep posting more info. I work on Mi-17 helicopters, and the information I posted it from our internal training documentation, and from one of our Mi-17 Maintenance Manuals. The engines and dust protectors are one of the few things on the Mi-17 that is virtually identical to the Ka-50. I'm not sure there is anything else that is really the same. If there is, I'll be happy to post more info. I was hoping to post info on the autopilot, but I'm not sure what model the Ka-50 uses.

Hi all, As a home cockpit builder, my favourite feature of Black Shark is its ability to draw the Shkval and ABRIS on different monitors. My sincere thanks go to the ED team for responding to community pleas to enable this extremely useful capability. However, as noted in other threads, there are a few problems which arise when using multi-monitors so I've come up with a few suggestions as to how they could be addressed: Problem 1 The multi-page threads in this forum (and others) in which people have struggled to get to grips with the monitor setup files suggest the current format isn't very intuitive for many people. It also generally requires quite a bit of file editing by the user to get everything set up satisfactorily. Suggestion 1a Change the format of options.lua to allow the width and height of each screen to be defined individually. For example: ["screen_1_width"] = 1280, ["screen_1_height"] = 1024, ["screen_2_width"] = 1920, ["screen_2_height"] = 1080, ["screen_3_width"] = 1280, ["screen_3_height"] = 1024, (The numbering of each screen should correspond to their numbering in the Windows Display Settings). Suggestion 1b Change the format of the monitor setup files by adding a line to each section which defines the screen on which that item is to appear. Screen.width and screen.height in that section should then refer to the appropriate definitions in options.lua for that individual screen (rather than the total size of all screens as they currently do). For example, if the options.lua was as above and the Shkval definition in the monitor setup file was like this: Shkval = { screen = 3; x = 0; y = screen.height * 0.195; width = screen.width * 0.5; height = screen.height * 0.5; } ..then the Shkval would be drawn on screen 3 at position 0,200 with a width of 640 and a height of 512. This format is, imho, more intuitive and, more importantly, it also makes it much easier to write a monitor setup file which will work with any combination of screen resolutions. This would enable (a new set of) default setup files to work without requiring any editing by the user, thereby making the process of setting up multi-monitors much more straightforward. Problem 2 The locations at which the comms menu, message box, no-cockpit view lamps and multiplayer GUI are drawn isn't definable, resulting in them being placed in inappropriate positions when multi-monitors are used. Suggestion 2 Allow the locations of these items to be defined in a monitor setup file in the same way as the Shkval and ABRIS. For example: MP_GUI = { screen = 2; x = 0; y = 0; width = screen.width; height = screen.height; } (N.B. As in the previous example, screen.width and screen.height refer to the values for that individual screen, as defined in options.lua). Problem 3 Although having the ability to draw the Shkval and ABRIS on other monitors is very useful indeed, there are several other vital systems which aren't currently displayable (or at least not without extensive knowledge of LUA). Suggestion 3 Create additional modules for these systems and make their positions definable in the monitor setup file. For example, with a two monitor setup we might want the non-main screen to be laid out like this: ..which would look as follows when running: ..and be defined in a monitor setup file something like this: Description = 'Cam, SP GUI & MP GUI on screen 2, everything else on screen 1' Viewports = { Center = { screen = 2; x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } SP_GUI = { screen = 2; x = 0; y = 0; width = screen.width; height = screen.height; } MP_GUI = { screen = 2; x = 0; y = 0; width = screen.width; height = screen.height; } LWR = { screen = 1; x = 0; y = 0; width = screen.width * 0.084; height = screen.height * 0.153; } Master_caution = { screen = 1; x = screen.width * 0.084; y = 0; width = screen.width * 0.041; height = screen.height * 0.153; } Caution_lamps = { screen = 1; x = screen.width * 0.125; y = 0; width = screen.width * 0.178; height = screen.height * 0.153; } Warning_lamps = { screen = 1; x = screen.width * 0.303; y = 0; width = screen.width * 0.255; height = screen.height * 0.153; } Message_lamps = { screen = 1; x = screen.width * 0.558; y = 0; width = screen.width * 0.368; height = screen.height * 0.153; } Counter_measures = { screen = 1; x = screen.width * 0.926; y = 0; width = screen.width * 0.074; height = screen.height * 0.153; } Shkval = { screen = 1; x = 0; y = screen.height * 0.195; width = screen.width * 0.5; height = screen.height * 0.5; } ABRIS = { screen = 1; x = screen.width * 0.5; y = screen.height * 0.156; width = screen.width * 0.5; height = screen.height * 0.8; } Comms_Menu = { screen = 1; x = 0; y = screen.height * 0.681; width = screen.width * 0.191; height = screen.height * 0.245; } EKRAN = { screen = 1; x = screen.width * 0.195; y = screen.height * 0.681; width = screen.width * 0.106; height = screen.height * 0.196; } Nav_display = { screen = 1; x = screen.width * 0.305; y = screen.height * 0.681; width = screen.width * 0.195; height = screen.height * 0.122; } Weapons_display = { screen = 1; x = screen.width * 0.305; y = screen.height * 0.803; width = screen.width * 0.195; height = screen.height * 0.122; } Message_box = { screen = 1; x = 0; y = screen.height * 0.931; width = screen.width * 0.5; height = screen.height * 0.039; } (Other modules which would be particularly useful include the Autopilot panel and the Nav keypad). Problem 4 Parts of the loading screen remain visible on monitors after a mission has loaded unless they're completely covered by the camera, Shkval or ABRIS. Suggestion 4 Add a step during mission loading which draws a black background on each monitor or, even better, allow the user to specify a background image file to be used for each monitor. Problem 5 Several panels (like the nav pad or ABRIS) are ideally suited for display on touch screens. Even for those without touch screens, it would be much easier to be able to operate these controls with a mouse on a secondary monitor than in the virtual cockpit. Suggestion 5 Add modules which have clickable hotspots in the appropriate places for e.g. ABRIS buttons, Nav keypad buttons etc. These would enable something like the following to be displayed: I'd be very interested to hear from any of the ED guys if any of these suggestions are technically feasible, or from anyone else who uses the multi-monitor feature if you'd find the proposed changes useful (or have any other suggestions of your own). Many thanks, DD

Set up a ambush for the lead elements of a German advance. Includes a SP and MP version. http://cid-f33d8b1019e6f4ac.skydrive.live.com/self.aspx/Public/Ambush.zip The mission includes radio voices spoken by my squad mate miRage and myself. We still need to work a bit on the uniformity of the voices and a authentic radio sound (and I need to work on covering up my Swiss accent :)) but I think you get the idea what to expect in the future. Two small tips for the mission: Send your wingman to alternative positions through the target points and generally fly with patience.

No, not the plunge to buy DCS: BS, I have had that since it came out, that's a no brainer! The plunge was to buy my first HOTAS, and I went with the X52 (not the Pro)! I had asked around in the forum for opinions between that and the Cougar, and the Cougar (with all of the almost necessary upgrades) was out of my price range. that and I figured that for my first HOTAS I shouldn't spend too much, to see what HOTAS is all about, and then maybe upgrade in the future when I know exactly what I am looking for. For the record, I got it at Best Buy for $99 plus tax. I am very impressed with my first impressions (how's that for a catch phrase!). I fired BS up and went for a flight. Keep in mind that I have a Microsoft FFB2 stick (which I love, and may continue to use together with the X52 throttle), so going to a non-force feedback stick was an interesting change. But the X52 stick as very, very smooth in motion, very accurate in positioning, and all the buttons seem like are positioned in places where my fingers will have no problems going to once the muscle-memory kicks in. I really like the fact that there are three MODES to toggle between for button assignments, so it looks like I could have one for Takeoff/Landing, another for Flight, and a third for Combat. The problem will be remembering all that! I also like the ergonomic design of both stick and throttle, lots of human factors studies into that, it looks like. The materials used for construction are pretty nice too, and time will tell about durability. I did snap the rotors right off the first time I tried trimming, since it is pretty different than doing it on the FFB2, but I am starting to use a technique suggested here in the forums of adding a little trim at a time, and it seems to work. All in all, I am very happy an excited about finally acquiring a HOTAS, and very happy so far (3 flights) with the apparent qualities of the X52. Thanks to everyone that pitched in with suggestions, and to everyone else in the forums, this is a great place for information. Oh, and if you have a killer X52 profile out there, post here! I've seen a couple other posts with those but have not tried any yet, and am thinking it might be better if I create my own, to better recall where all the assignments go, but i am definitely open to suggestions. Best regards,

This is the little Autohotkey script I use to send key commands from SIOC to DCS BS. SIOC itself has this capability but it was IMHO somewhat lacking in features. The script has support for : Separate sending of key presses and releases. Pause between sending keys. Supports left/right CTRL, SHIFT and ALT. Can be connected to SIOC on a remote computer. Possibility for special stuff by catching SIOC parameter values and do what you want (needs programming knowledge, source code is included). Tested on WinXP. All credits for the networking part of this script goes to Zed Gecko from the Autohotkey forum. This script is free for all to modify, distribute etc. Just make sure you give credit were credit is due. ----------------------------------------------------------------- Note: This script is a badly structured, badly commented hack job with minimal testing written by a washed-up old programmer now working in management (i.e. promoted to a position were he cannot possibly do any more damage to the code base) and is meant only as a temporary solution until we can communicate with DCS directly through lua and SIOC. Your mileage may vary and you've been warned :smilewink: /Oakes keyclient_1_00.zip

BRD shut up dude (bro) You have 75%

reps inbound

Better DTWD?

This is already fixed in the patch. Seems the problem is in routers, which remap outgoing server packets even if you correctly set up port forwarding. I added server port into heartbeat packet, so this problem should be solved in the patch. Thank you for reporting.

no yes, when you activate, theres a screen that tells you when your activation was successful and how many activations you have left You don't use up an activation just by de and reinstalling the program AFAIK

Sigh. If my server's heartbeat is sent on port 18308 UDP (which I have confirmed using a packet analyzer), why does the master server list my server with a randomly selected port (60000-64000)? Upon further reflection, if the problem is in the code on the master server, it is not likely to me that the server's logs will show anything wrong. They will likely indicate that my server simply hosted on such-and-such random port. I don't understand what is going on here, and I have exhausted every analytical option I can think of on the client/server side with the help of Graywo1f. I can't think of anything else to do from here... I can confirm my server is throwing traffic at the master server on port 10308...

If you are a true flight simmer you CANNOT deny yourself this title. It is the most accurate study sim available. The immersion is uncomparable to anything else on the market today IMO.

- теоретически нет, практически так: точкой останова может быть любая предыдущая точка, если в текущей точке установить скорость 1км/ч = 28см/с, этого достаточно чтобы остановить технику практически без явно видимых перемещений на время 6-10мин. Пример1: - точка1 - начало движения (N км/ч) - точка2 - точка останова (N км/ч) - точка3 - следующая точка (1 км/ч) - точка4 - продолжение движения (N км/ч) между точками 2 и 3 всего 100м, этого достаточно чтобы придержать технику на 5 мин!!! (см. миссию) start_stop.miz

Relatively Minor risk, I would think ;) After all - I'd like to believe that - *Heaven forbid the Day actually comes* - should ED no longer pursue the development of Flight Sims, rather than poke all their loyal customers in the Eye on their descent to Oblivion, they would make available a 'key' for us all to enjoy the fruit of their labours at our leisure. And then again, I might be erring........I would however elect to ponder the probables if and when such an eventuality does arise........to do so now is rather premature.........IMHO of course :)

Technically, when you're 'purchasing' any software, you're just leasing it. ED has been pretty good about accommodating people who use up their activations etc. What happens when ED is gone? Nobody knows, but ED won't be gone for the next decade. They're not just an entertainment sim producer, they're now a firmly entrenched military sim producer as well. Yes, stuff can happen - you could break a leg just walking on the sidewalk. Are you going to stop walking now? ;)

*SPOILER ALERT* Thanks for the mission, I really enjoyed it and am still trying to see what I need to do to get some sort of mission success rather than "the element of surprise is lost, rtb" :) I'm not sure of the ethics of using apartment blocks as cover, but it works for me! Are the MLRS near WP2 really firing north? It seems so. It made me wonder if the bad guys had snuck some troops forward. I really like the regimental phase line concept - it helps suspend the belief that there's nothing set up outside the lines :D Can't wait for the next one.

What's with the "Convince me plz, my ego is soo big" attitude in the forums recently? Do some Google for review/previews and videos, read through forums and DCS website and decide for yourself.

Option for campaigns: I'd like to see an option for adding a 'flown' tag next to missons in campaign stages. When a mission is flown it is flagged. If you have to fly another mission in that stage a mission you haven't already flown is automatically selected. Alternate text outputs that can be presented to the player at the end of the mission depending on mission score/events. E.g. 'well done, you sufficiently degraded the enemies armour to help our forces advance - mission accomplished'. For the AI: - 'weapon check' command - 'engage with...' command

I encountered no problems

I suspect he knows it's a nice machine, just wants to know if it's good enough to be able to run everything on MAX. If he could afford to buy that computer, & to buy that stick, & asks if he should upgrade, he can afford to spend another 2% of that to buy BS ...

Geez mon, it's not like you're buying the house or the trip to the space...

I have Vista too and get satisfactory performance atm running the shkval and ABRIS on another screen (with a less than stellar rig). I'm not sure exactly what you meant by "the horizontal span has to be fixed before we can go beyond displaying ABRIS and shkval video". If you're referring to the lack of a horizontal desktop span mode in Vista then I don't understand the problem -everything seems to work fine with Dual View mode. If you're referring to the current necessity of defining extra width for a phantom third monitor then part of the reason for the suggested format changes in 1a/1b above is to remove that requirement (which will hopefully result in increased fps). Any additional modules I've suggested would be entirely optional so if, for example, your rig can only cope with 1 camera + shkval then you could just omit the proposed new sections for EKRAN, LWR, Nav display etc from your monitor setup file. Cheers, DD

alot of us have vista.. the horizontal span has to be fixed before we can go beyond displaying ABRIS and shkval video... you want to see more nonsense that will eat up fps?

Ok I see. I'll fixed. :-)

Hi, @Coyote: Thanks your remark. I follow your remark and modified my B-8V20A. 1. not very precise general proportions of pod and its details Almost fixed. 2. handles from the rear are small Fixed. 3. walls of barrels are longer than needed Fixed. 4. walls of barrels are too thick Fixed. 5. not very correct geometry at the rear of pod, from the shorter side Almost fixed. 6. rather poor texture WIP. Thanks.

Im just an awesome guy. :)

Согласно замечаниям. Ещё есть ОЗ такого же размера на брюхе, но в скрины не попали. Это кажеться окочательный вариант. Есть ещё какие либо пожелания? С уважением, Sparr

Hi Coyote, Interesting proposal, I will try to do, but to say that already to be almost fact.:smilewink: I to say, because to the camouflage that to use the FrenchArmy Aviation andSpanish Army Aviation to be he himself, with the variation of the insignias and the numerals.:smilewink: Spanish Tiger HAD. http://www.airliners.net/photo/Spain%20-%20Army/Eurocopter%20EC-665%20Tigre%20HAP/1278974/L/&width=1280&height=863&sok=WHERE__(aircraft_%3D_%27Eurocopter_EC-665_Tigre_HAP%27)_&sort=_order_by_photo_id_DESC_&photo_nr=11&prev_id=1283668&next_id=1270102 French Tiger HAP http://www.airliners.net/photo/France%20-%20Army/Eurocopter%20EC-665%20Tigre%20HAP/1257964/L/&width=1024&height=695&sok=WHERE__(airline_%3D_%27France_-_Army%27)_&sort=_order_by_photo_id_DESC_&photo_nr=90&prev_id=1260717&next_id=NEXTID I will work in this to see what seem to you.:smilewink: A greeting and good hunting.

USA Готова птянистая раскраска. Отправил на проверку. Попробовал вот такую схемку накидать для разнообразия. http://www.airliners.net/photo/USA---Army/Beech-RC-12K-Huron/1257865/L/ Раньше по моему так красили А-10, но конкретно его не нашел. Если сама схема интересна, то доделаю ее. Итого пять схем USA на проверке. Шестая в работе. На большом скрине все схемы. Критикуйте :)

А кто-нибудь из моделлеров может поделиться инфой о назначении слоёв в темплейте Акулы? Что то их там многовато и названия малоинформативны :) Выключаю по очереди и разницы не наблюдаю, если бы кто-нибудь расписал их назначение было бы проще...

http://www.digitalcombatsimulator.com/files/Ka-50_Templates.rar