Leaderboard

I will give it my best shot. JTAC will give you a UTM or Lat/Long coordinate during the 9 line, and if you have your SADL net settings correct, you will also get a data linked target identifier in your TAD (a red triangle). The following is based on JTAC giving you a UTM coordinate. Use a mission data card to get all the info on the UTM coordinate and the specific weapon, direction of attack, direction of egress and weapon requested. To make the UTM coordinate provided by JTAC into a waypoint do the following: Find a safe area to do a wide orbit. Set your autopilot to ALT and then make a left or right banking level turn and hold it. Then engage the autopilot and ensure it is holding the turn and you have no elevation conflicts around you. The UTM coordinates will be in the form of 2 letters and 6 numbers. Make sure your STEER PT switch on your AAP Panel is set to FLT PLAN. Set your right MFCD to the CDU repeater function. *NOTE: If your CDU is not on the WAYPOINT PAGE, then hit the WP key on the CDU, or FUNC 3 on the UFC. This will bring up the page where you can choose to select WAYPOINT by hitting OSB 7. You should now be on the WAYPOINT PAGE and ready to continue. Hit OSB 10 to switch from the default L/L (Lat/Long) to UTM. Hit OSB 9 to select the number presented next to the question mark as your new target waypoint. Using the CDU or the UFC, enter the 2 letters, and 6 numbers without spaces in the scratchpad. Hit OSB 16 to enter the UTM coordinate in to the computer. Verify the number entered is correct. Using the CDU or UFC keypad give your new waypoint a unique name eg: TGT A and hit OSB 7 to change the name. Now turn your STEER PT dial on the AAP from FLT PLAN to MISSION. Use the UFC STEER rocker or with the HUD as SOI, DMS UP to cycle thru the waypoints until you see the unique name you created for this target. Find your target waypoint symbol on the TAD and then use the steering cue's on the HUD to prosecute your attack. EDIT #1: I added the item in italics for anyone who has moved off the Waypoint Page in the CDU, and needs to know how to get back. EDIT #2: I created a Powerpoint Presentation outlining the steps covered in the post above, and added a few explanatory pictures. The UTM Data Entry Tutorial is provided in PDF format as an attachment below for you all to use. JTAC 9 LINE UTM COORDINATE ENTRY PROCEDURE 03-08-2011.pdf

HawgTouch is a simple light-weight framework which allows you to create your own cockpit panels for DCS-10C. The software is bundled with 2 MFCD's, a UFC panel (Thanks to jeffyd123 @ ED forums): Included profile ShowcaseProfile.xml which demonstrates tabs, scaling and latest additions Version 1.25 changes - Fixed a bug where keystrokes of Rocker Switches weren't sent - Fixed a bug where keystrokes of Two State Switches weren't sent - Fixed a bug where keystrokes of Three State Switches weren't sent - Fixed panel closing and tab switching crash - Added a "drag" button to the top right, to drag, click and hold the button - Optimized code and image handling - Profile parsing improved, now showing detailed exceptions if profile is illegaly formatted - Two State switches now support multiple types: - On/On - Momentary/On - On/Momentary Take a look at the "TestPanel" tab in the ShowcaseProfile.XML to see how to assign switch behavior - Three State switches now support multiple types: - On/On/On - On/On/Momentary - Momentary/On/On - Momentary/On/Momentary Take a look at the "TestPanel" tab in the ShowcaseProfile.XML to see how to assign switch behavior - HawgTouch now ships in two executables. x86 and x64 Version 1.2 changes - Fixed bug in ClickButtons long press. Now working - Added support for tabs - Added panel scaling mechanism - Added audible clicks option - Better keypress engine, no more flashing HawgTouch now supports tabs. At least 1 tab must exist in every profile. Once a profile is loaded. A tab control box appears which allows you to switch between tabs. The tab control box can be latched to 9 locations of your chosen monitor. This is done by specifying 2 parameters in the profile XML <LatchTo></LatchTo> Available parameters: - UpperLeft - UpperMiddle - UpperRight - MiddleLeft - Middle - MiddleRight - BottomLeft - BottomMiddle - BottomRight The tab control box is also dragable. <MonitorID></MonitorID> Specifies which monitor the tab control box will latch on to. To get the ID of the monitor you'd like to latch the tab control box to, click on the "Monitors" link on the main HawgTouch window. It will display your local monitors setup. Sample profile XML with 1 tab and 1 panel: <?xml version="1.0" encoding="utf-8" ?> <Tabs> <LatchTo>UpperLeft</LatchTo> <MonitorID>2</MonitorID> <Tab> <ID>1</ID> <Name>Test</Name> <Controls> <Control> <Name>Up Front Controller</Name> <PanelImage>\Images\UFC\ufc-main-panel.png</PanelImage> <X>80</X> <Y>10</Y> <ShowTitleButtons>true</ShowTitleButtons> <SizePercent>100</SizePercent> </Control> </Controls> </Tab> </Tabs> Supported controls in 1.1: - Click Buttons - Rocker Switches - Two State Switches - Three State Switches HawgTouch is fully "customizable", allowing you to use your own skins and graphics in any size you choose to make. Setting up exported MFCDs: 1.HawgTouch comes with a default skin in which the MFCD "transparent" zone is 400x400 pixels. With additional 186x146 pixels for the bezels. Therefore the MFCD's rendering in your multi monitor setup LUA file should be to 400x400 pixels to fit inside the frames. This is my multi-monitor setup: (1x 24" @ 1920x1080 and 1 x 22" @ 1280x800): _ = function(p) return p; end; name = _('My_example'); Description = 'Two monitor configuration'; Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.6; } } LEFT_MFCD = { x = 2050; y = 105; width = 400; height = 400; } RIGHT_MFCD = { x = 2650; y = 105; width = 400; height = 400; } UIMainView = Viewports.Center2. Now you will need to set up the keys in DCS A-10C control settings which are mapped to the MFCD profiles in HawgTouch. HawgTouch comes with 2 MFCD profiles which are configured to the following keys: Left MFCD OSB1 through 10 - Left Control + 1 through 0 Left MFCD OSB10 through 20 - Left Control + Left Shift + 1 through 0 Right MFCD OSB1 through 10 - Left Alt + 1 through 0 Right MFCD OSB10 through 20 - Left Alt + Left Shift + 1 through 0 Here is in-game screenshot of the controls binding: You can set any key combination you want. Here are the key shortcuts: (Made identical to TouchPal for easier transition) {BACKSPACE} {TAB} {CLEAR} {RETURN} {LSHIFT} {RSHIFT} {LCONTROL} {RCONTROL} {LALT} {RALT} {PAUSE} {CAPSLOCK} {ESCAPE} {SPACE} {PAGEUP} {PAGEDOWN} {END} {HOME} {LEFT} {UP} {RIGHT} {DOWN} {PRINTSCREEN} {INSERT} {DELETE} {LWIN} {RWIN} {APPS} {NUMPAD0} {NUMPAD1} {NUMPAD2} {NUMPAD3} {NUMPAD4} {NUMPAD5} {NUMPAD6} {NUMPAD7} {NUMPAD8} {NUMPAD9} {MULTIPLY} {ADD} {SEPARATOR} {SUBTRACT} {DECIMAL} {DIVIDE} {F1} {F2} {F3} {F4} {F5} {F6} {F7} {F8} {F9} {F10} {F11} {F12} {NUMLOCK} {SCROLLLOCK} You can mix all sorts of shortcuts for your liking. Most will work but I can't gurantee crazy combos since I haven't checked it myself. Creating your own panels: HawgTouch gives you the liberty to create any panel you find useful for your simming pleasure. Take a peek at the TestPanel.xml file for information of how to use the different controls HawgTouch supports. With time and by request more complex controls will be added! UFC bundled in 1.1 (Thanks to jeffyd123 for the image works!) NOTE: The key commands for the UFC are not set! Once you set your UFC key bindings in-game, open up UFC.xml and fill in the KeyCommand slots! My setup: Download: HawgTouch 1.25 x86 [1.03MB] HawgTouch 1.25 x64 [1.03MB] Extract anywhere. In this version the last known position of the panels is not saved. You will have to manually set it to the specific panel. To help you achieve that a new button has been added to the panels which shows the current windows X/Y positions. Once you are happy with your position you can type that data into the panel XML and it will be launched in the position you saved. IMPORTANT NOTE: If you are running any Windows version with UAC enabled (Vista and higher) and you are running DCS A-10C as Administrator you will have to launch HawgTouch as Administrator aswell. Orelse the keystrokes wont be sent to the game. You will need .NET 4.0 to run this so if you don't have it installed make sure you run a Windows Update or download it from here : .NET Framework 4.0 Download Tested on WinXP 32/64, Win7 32/64 Enjoy! ClearDark

"Yo Man. I've been trying to bomb your bridge here but I've lost my Warthog" :music_whistling:

Hi All, I have had a mixed bag of results with the use of dumb bombs in CCIP and CCRP, generally speaking, flying skills apart, the issue is related to wind (not diet related, but atmospheric). I have just gone through the procedure of entering wind correction into the CDU to correct for this, and the results speak for themselves. Below is the walkthrough of the procedure I use, I hope it is of some use to you fellow sim pilots, and hope I am not teaching you to suck eggs! Sorry for all the pics!!! CCRP bombing, paired release @ 6000 ft 210kts. Wind 270 degrees 15m/s As shown above, the bombs missed their mark, and no damage done to the target. This was a stable release, wind accounting for the miss. Procedure for correction: 1) On the CDU panel, press the SYS button, then press the LASTE button: 2) Click the wind OSB to enter the wind correction page: 3) This is where you can enter the wind correction data. Start off by entering the altitude of the first layer of wind. I start with ground level. To do this, enter 00 in the scratch pad, then click the first empty line on the left to enter this altitude. 4) Repeat the process for other wind layers if known. What I did here was repeat the wind speed and direction data for my altitude, so the adjustment calculation took place. In this case I entered 06 (for 6000ft) and placed that altitude in the line beneath the first: 6) When you have enetered all the layers you desire, press the WndEdit button. In this step you enter the wind speed and direction. How you get this data is up to you :) You can get it form the mission editor, Air traffic, even the JTAC gives the wind vector for you. To enter the data you have to enter 5 digits. The first 3 digits is the direction of the wind, so 000 = north and so on. In this case, 270 was the wind direction. The 4th and 5th digits is the wind speed in m/s So wind speed 15 ms at 270 degrees, we enter 27015. If wind was at 10 degrees and 7 m/s, you should end 01007 Once entered, hit the OSB for the layer you want to add this data. Repeat this for all layers. 7) Next step is to add the temperature data for each layer. Again get this from the ME/brief. You also have the current temperature shown in the CDU on the top right. I just used this temperature accross all layers. 18 degrees here. 8) Once done, hit the WIndTemp OSB to go back a step and store the data: 9) Get yourself lined up.... and bombs away!!!! "Good bombs, good bombs" BDA flyby: As you can see from the result it seems to do the job nicely!!! The smoke also blows along the correction line... I would like to say there is no camera trickery here, and I hope the above isn't just a placebo, and my first run was just bad. But I tried this out a few times, and it appears to do the job. Let me know how you get on!!! Also, thanks ED for making this sim so involved, things like this are great! Happy bombing all!

It was 15 days after the official release of DCS:Warthog and a patch was out addressing numerous bugs for that product. On the other hand there are months since last patch for DCS:BS and I heard no official word for patching and addressing issues with BS. ED only announced that, for A-10C, the patches will be released more often and will be smaller reducing the chance of implementing new issues along with fixes. I am sorry to say that I feel that ED's other product (DCS:BS) seems to be forgotten and its audience "forced", in some indirect way, to buy the next chapter of DCS series, in order to get patches more often, or stay with BS 1.0.2 and all the bugs and other issues. This is making me ever more reluctant to buy DCS:Warthog since I find ED's way of thinking about patching their products quite odd. I understand that DCS:Warthog is their brand new product and needs support to take its place in the market... but BS needs support too to satisfy it's audience and make a name for ED that it stays committed to their products by not letting them "rot" in a timely manner. DCS supposed to be a series and, as we imagine that something new will come up next, we ought not to forget the already released titles. We need to move forward but a glance in the past titles can be useful too. At least, when we talk about "series", I understand that there will be the same quality and the same attention, in terms of support, for all the products in that series.

Since DCS provides us with Canada as a flyable country I thought I'd do a "what if" skin. BTW, if anyone from DCS is reading this, the Canadian squadrons in the drop down menu should read: 410 SQN COUGAR 425 SQN ALOUETTE 433 SQN PORCUPINE 439 SQN TIGER 441 SQN SILVER FOX You've got too many 433s and a couple of typos ;) So anyway, here's a fictional 439 Squadron A-10C. Actually kind of fitting, since 439 started out as an RCAF Typhoon squadron which flew CAS missions in NW Europe during WWII. W.I.P shots: This is "Fang", 439's mascot, who has graced every aircraft type 439 has flown since the F-86 days. Still need to add a Canadian-style serial number, but I think I'll wait to see how DCS handles the serials in the release version. Also looking forward to an actual paint kit for the A-10 model!!! :D

I just seen lots of vid on youtub showing how to download DCS A-10 and crack the activation code. I flagged all the vids and now they are removed.

Once you land, usualy on your left, you'll see a kinda small parking place where other airplanes are, but that's not where you're supposed to go. After that parking space, keep going down the taxyway untill you hit a crossroad. Take the smallest path (usualy on your right side), and keep going... After you stop in a friendly town, you can open your cannopy and ask if you can get some beer. After that, it's only a simple matter of pressing escape and closing. Mission complete :thumbup:

Shouldn't you bank the aircraft, maintain altitude with back pressure and center the ball with the pedals? This is how I was taught in a Piper Warrior anyway.

Thought you were in with a chance of some cyber action? :megalol:

My understanding is like this: the FCC has to have some way of determining 'ground level' so it can calculate the impact point. While the ballistic calculations are no doubt fiendishly complex, the principle is simple: assuming you release the weapon right now, trace its trajectory and determine when it reaches ground level. Presto, your impact point. Easy as pie, so long as you know the ground elevation. The simplest way to do that is to have a fixed 'ground level', as if you're flying over an infinite flat tabletop. That's basically what the "steerpoint as ground level" method does: whatever the elevation of the SP is, is the height of the tabletop for the point-of-impact calculation. So to get an accurate solution with that method on terrain of varying elevation, you need to set the SP to the same elevation as the target your prosecuting. That way when the pipper indicates the point of impact is on your target, it will be accurate. It won't be accurate for a target at any other elevation. Since that's cumbersome, DTS replaces the tabletop with the elevation data stored in the computer. The impact calculation is pretty much the same, but rather than determining when the weapon will intersect the flat tabletop surface, you're checking if the weapon is intersecting the terrain at every given point along its trajectory, pulling the elevation data from the computer. Obviously, that method is superior in every way except for one: complexity. If your stored elevation data is incorrect or missing, it can't calculate the impact point. So, I think the "steerpoint elevation as terrain elevation" method is provided as a fallback in case you can't rely on the DTS data. The only way it can know the elevation of the SPI is to consult the stored data. If you've got the system drawing data from DTS, then there's no reason to care about the SPI's elevation in CCIP mode. If you're not drawing the data from DTS, then there's probably a good reason for it, so it doesn't make sense to try to use it at all. Hence, SP elevation. Theoretically the IFFCC could determine the altitude of a target using the angle of the TGP and the ranging laser to determine distance, but I don't know if there's any way of actually doing that.

hello, i will correct theses problems next week, at the moment, you can use this patch. http://www.3rd-wing.net/index.php?showtopic=9114&st=0&gopid=225774entry225774

Not really what I had in mind but...I like the beginning

And now? Better? :mad: Or maybye FC2/BS Rivers? With something... even don't looks like water...

I am going to respond to the ED announcement that frequent patches with iterative changes are coming out by removing strict version checking from TARS so that you can continue to use TARS with each new patch. If incompatibilities are discovered, feel free to report.

What I understand of the UTM format (being the same as MGRS) is this: Think of it as if you're looking at a paper mapsco book. (This isn't literal, but makes it practical) MM 12345 67891 MM = page 123 = Squares down the page 45 = meters down the '123' square 678 = Squares across the page 91 = meters across the '678' square They may give you MM123678. This gives you the grid but not the exact point within that grid, which is fine because it's only 99 meters. If the coords were MM 12345 06789 they may give you MM12367 because they drop the leading zero from 067. You must still enter the 0 before 67 when entering into the CDU. You can enter UTM into your CDU by switching from L/L (lat/long) mode to UTM mode with LSK R9 (bottom right key). Then by entering the UTM coords in ten number, six number, or less, and selecting LSK L9 (bottom left key) to save them to the waypoint currently showing on the CDU. For more info see Military Map Reading 201 at the Geo-spacial Intelligence Website. Someone close the gap if I'm leaving something out, please.

Totally agree Totally agree! :thumbup: ...intention was to help the noobs to MGRS / UTM to understand that "they don't switch from UTM to MGRS", some guys seem to mix up L/L, UTM and MGRS :huh: So to make it precise: MGRS is a "better way" (for military purposes) to address the same grid as UTM. We learned it the same way in my army, as well. If you are in the same 100 Km (huge!) grid Zone, it is not necessary to state obvious stuff everybody knows! ...it's like telling a sniper "Left upper window of the red house on Elm Street, Arlington, USA, Planet Earth" when you are both looking through the same window of the house opposite to the red one :megalol:

Look who's talking :D

This... Like, WHAT? :lol:

Yes and no... The radio menu is working (mostly) also for the clients. Sometimes the JTAC radio menus are not availeble for clients and sometimes the JATAC won't answer. The major bug is that it is not possible to get the target data into your TAD! (red triangle) This is not working for clients! But you are able to use the UTM coordinates you get from the JTAC to create a waypoint and find the targets. http://forums.eagle.ru/showthread.php?t=68894

Thanks for the invite guys. I'm really just looking for a single person to fly around with, so we can talk prior to the mission what we're going to do, etc. Ha I know, if you look at it out of context it's really bad! Diego

GG I *think* this guy is a LOMAC flyer.. (this is the lock on forum section.. whew... dusty in here... :D ) Nevertheless- GG is correct that if you plan on getting into the DCS Warthog simulation- the TMWH is most ideal for overall control. Followed closely by the CH line, then perhaps a distant 3rd- the Saitek X65 I think it's called... The X52/ x52pro can be used in DCS. However- its seriously lacking in HAT switches. This means that profiles have to be carefully crafted and will be more complex to use than if you had enough HATS to program a proper layout in the first place. Still-people make it work- I reckon you get used to it after some use. In short- think about not only what you're flying right now- but what else you plan on flying. You may want your stick to have room to grow beyond LOMAC.

Version V1.2 released Change log: - Fixed isue in JTAC mission ("Darknight" was reporting a group of the wrong target area) - Added mission options (no immortal, no game flight mode...)

Confusing name of the thread :smilewink:

Unfortunately, 159th_Viper, I didn't miss that explanation which is referring solely to DCS:A-10C Warthog, neither I criticize the "short and small" approach decided by ED on the A-10C. What I am talking about here is the "Large and Long" approach on the Black Shark. To be more specific : DCS Black Shark released (English Language) : 10 December 2008 Patch 1.0.1 released : 10 August 2009 (9 months since release) Patch 1.0.2 released : 14 May 2010 (9 months since last patch) Today is : 10 March 2011 (10 months since last patch) Still we have issues in a "wait list" since release (ex. Wingman behaviour/skill). I wish ED team adopted the "small and short" approach for DCS:BS too but the announcement leaves little room for hope, ED mentioned nothing! The whole announcement was Warthog-wise. No one bothered telling us what plans are there (if there are any) about addressing BS issues. What I got from that announcement? ED is going to put more effort on its new product while BS is in a waiting queue for 10 months. This means that BS patch will be pushed further into the future and the BS audience will have to wait even longer... I hope I am not right but... ED did almost nothing for BS in the past 10 months. Now that the Warthog is out and requires attention I can't help feeling that our "wish" (about patching the Shark) will go down to the bottom of the drain. Personally I don't care if I can fly with Warthog pilots while my game is at the state it was one year ago.

How is this? That way it is a small photo and you can click on it to see the larger one Operation New Dawn A B-1B Lancer pilot flies Feb 26, 2011, above Iraq, in support of Operation New Dawn. (U.S. Air Force photo/Master Sgt. Adrian Cadiz)

Thanks Bonedust. Downloading now.

I vote for dynamic shadows in the cockpit (like in Cliffs of Dover)... :) edit: Oh, and rain drops effect on the canopy too. (BTW just cosmetic and maybe heavy after processing for the GPU)

Вот вам оффлайновый трек: http://depositfiles.com/files/96vxsxlqc Понаблюдайте за первой Р-77.

:D Don't have to pretend with me, we both know the truth, we fly them them all better than you! The song said so. :smartass: As for the carrier part Ch5z3DMC3RA&feature

Flying on a radial to a destination allows you to approach the destination from a specific direction. That's the key part. For example, let's say you're south of the airport, and there is a noise-sensitive neighborhood just south of the airport (or a big hill, or radio towers, or something else you don't want to fly through/over). And you're south of the airport too, so you would have to fly over the sensitive area if you fly directly to the airport. Instead, the airport might want you to approach on the 090 radial (that is, approach from the east, so you're flying a heading of 270 to the airport). This would keep you away from the sensitive area south of the airport. Again, flying a radial to a destination allows you to approach the destination from a specific direction (and over a specific line over the ground), so you can avoid things you don't want to fly into. :) --NoJoe [EDIT] Oh, to answer your first question, Conure, when you have a TACAN destination tuned and set a course, the CDI will give you guidance (left or right of the course) onto the radial you have selected. Example, if you turn the course knob on the HSI to a course of 360 degrees, the CDI will tell you if you are left/right of the line extending from the destination out to 360 degrees, and the reciprocal, 180 degrees. And to be clear, when ATC tells you to fly heading "240 for 5", that's something else. That means simply "From where you are right now, turn to a heading of 240 degrees and fly that heading for 5 nm." The ATC headings don't have anything to do with TACAN courses. :thumbup:

HOTAS Warthog Ch Pro Pedals Trackir 3 Dual moniter setup TM MFD's G940 stick for IL2 Modded x45 "pot box" for IL2 Serious flight sims demand geekdom if you want to really enjoy immersion. I personally feel that spending 100-150 quid every weekend on booze is a far sadder existence but the guys at my work disagree. Everybody has a thing; be it motors, bikes, music, designer clothes or drugs and we all think the other lot are wasting their money. Live and let live.

Transparent status bar mod uploaded to the File Exchange, waiting for approval. :) Full-size without status bar.

.. as I explained in another thread .. and there is an order in all things .. printed out the flight manual :book: And here are some pics. http://blog.night.si/wp-content/gallery/2011-03-dcs-a10-manual/img_9672.jpg http://blog.night.si/wp-content/gallery/2011-03-dcs-a10-manual/img_9673.jpg http://blog.night.si/wp-content/gallery/2011-03-dcs-a10-manual/img_9674.jpg http://blog.night.si/wp-content/gallery/2011-03-dcs-a10-manual/img_9675.jpg http://blog.night.si/wp-content/gallery/2011-03-dcs-a10-manual/img_9676.jpg http://blog.night.si/wp-content/gallery/2011-03-dcs-a10-manual/img_9677.jpg Can't wait for the hogy and my next paycheck (so that I can actually buy the game, cause hoggy is expensive :thumbup:)

I have an ASUS EAH 5770 1GB and DCS A-10C seems to run fine with it.

Looks more like fight than flight manual :P

Ну с земелей думается мне заморочек по-более будет. Здесь же приходится молиться всего лишь на один экспортер) ...который не полностью описан в мане, и который со своими приключениями) Что-то мне подсказывает, что новой информации не дождаться, с учетом того что и lom и cmd успешно отошли в каменный век, и поддерживаются в новых проектах только для обратной совместимости.

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

Damn, i've never seen it printed out. Some weighty tome.

Инопланетяне за "Звезду смерти".

Про первый трек согласен. Но второе же видео это с проги, которая показывает реальное положение ракеты и ее эволюции? Или там тоже все неправильно?

:D:D :D:D:D

Красный круг на берёзе должен гореть когда радар сопровождает, независимо от того был пуск или нет.

Here is a post I did last night explaining some things in the mission The reason why JTAC says no tasking is available is because you hit the CP a little too early. Most likely (because of mission triggers) the convoys will only start to roll 20 minutes after mission startup (there is a small chance they roll earlier). If you call JTAC before they start to roll he will say "no tasking is available". I've had no problems getting the data triangle when I set my Groupd ID to 01 right before I contact JTAC. If he doesn't send data with ID at 01, check out and change the ID to what it give you when you take off, contack JTAC again to see if it works. If it still doesn't write down the coordinates and manually enter them in the CDU :). If all that fails, you still have plenty of time to try and find the columns. Even with the "updated missions" after they patch, they are still screwed up for the first devil's cross mission. A C-130 cant figure how to taxi and blocks the taxiway for the tornados that return. They block the runway and you cant get clearance from the tower when you want to return home. They also block the runway so CAS flights 2 and 3 are prevented from taking off. I tweaked the mission a bit last night and did the following: 1) Moved the C-130 to a place where he will taxi correctly and take off 2) Moved all the landings away from your airport because they won't properly taxi off of the runway 3) Edited the waypoint heights for CAS 1, 3 and 4 so they will not crash into the ground at WP 3 (They may help you delay both of the columns) 4) I added a message (with a sound) to notify you when each of the columns of tanks start to move. Think of it as a message from JTAC saying "They're rolling, I am now available". JTAC will say there is no tasking available if you call him before the columns start to roll. 5) I also added messages to tell you when the column delay triggers trip. They happen about 50 minutes after the columns start to roll. You get points for the delay when these messages pop up. Hit your ' key to show what % of the mission is completed. If you end the mission before 50 minutes after they roll, it is impossible to get more than a 51 on this mission. I'm attaching my tweaked mission (mission 01B I believe is the same as the 01A mission except that it is raining (?)). backup your old campaign mission and drop this on in your campaign folder, or load it up as a single mission.

Пока фильм смотрел, половину перевёл. Вкратце, не дословно, но близко по смыслу. 1-я часть, остальное завтра.

Courtesy of EtherealN ;)

Imbecile сервер вырубается очень редко (при отсутствии энергоснабжения), последние 7 дней работал непрерывно и сбоев не было. Возможная причина: или проблема с интернет соединением со стороны сервера или клиента или просто выкинуло из игры. По моим наблюдениям постоянные посетитель расправляются с 3-кой, 5-кой колонн в течение нескольких часов без особых проблем с соединением. Время старта миссии не связано с реальным временем и 13:00 это внутреннее время игры, т.е. миссия проигрывается 8ч30мин и при перезапуске начинается заново (до появления новых миссий). ALF7 При высокой или средней загрузке сервера можно такое организовать для остроты ощущений, но в данном случае с низкой посещаемостью неминуема проблема невозможности продолжать миссию большинством игроков после блокирования впп. В то же время колонны подходят достаточно близко, чтобы уничтожить часть зрк у впп противника и доставить неудобства взлетающим самолётам.

Punish me, but I don't want compatibility between FC2 and DCS series. Just bring up fighter or multirole aircraft to DCS.