Damage

The installer won't run. Any suggestions? Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: Installer.exe Problem Signature 02: 1.5.0.0 Problem Signature 03: 5ac919f7 Problem Signature 04: UIAutomationTypes Problem Signature 05: 4.7.2563.0 Problem Signature 06: 5a33588a Problem Signature 07: 6a Problem Signature 08: 0 Problem Signature 09: System.BadImageFormatException OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 244e Additional Information 2: 244e0afe07cf09d352559d909cebe36b Additional Information 3: 61ab Additional Information 4: 61abcd2322b29ce981a2b25004fefa78

I had the same issue, The A-10C module was not available in DCS World 2. I tried a download ( E-Shop > Modules > DCS: A-10C Warthog) and manual install but it was looking for world version 1.5 instead. Your simple 1,2,3 instructions worked great. Thank you very much. I originally purchased A-10C beta in October 2010 so I finally got my "official" free Nevada Map. :thumbup:

Looks great! I can't wait to spray some 30mm into this

In RL it can vary from one airport to another. For example, with GA aircraft the most common traffic pattern is 1000’ AGL but the bottom line is that it’s up to the pilot in command to consult the local air field directory or any other published charts concerning the airport to ensure he is compliant with the local rules. So if I entered the pattern at a non-towered airport at 1000’ AGL and the TPA is actually published as 800’ AGL, and then I proceed to descend upon, collide or have a near miss with another aircraft that’s already in the pattern at 800’, I could expect to be on the unpleasant end of a conversation with the FAA or other local authority and in jeopardy of losing my license. Whether you're IFR or VFR you're always required to check in with towered airports and coordinate your approach. They will provide guidance for your approach to land and instruct you how to enter the pattern, unless they just want to to make a straight in approach. You can request touch-and-go's which implies that you want to stay in the pattern and they will allow you to do so if their workload permits and safe aircraft separation can be maintained from other aircraft that may be taking off , landing or already in the pattern. Military bases often have different patterns to separate different category, class and type aircraft. In other words, if an A-10C and a KC-135 were practicing touch-and-go's they are likely to fly different sized patterns with the KC135 flying a wider pattern at a higher altitude. On initial approach to an airbase it’s common for some aircraft to perform an overhead approach with a 180° break to join the downwind and then another 180° turn to final. Again, in RL, you'd have to contact the tower and comply with their instructions (as long as their instructions are within the safe operating limits of the aircraft and the pilot). Since using the ATC in DCS can be an exercise in futility we are often left on our own to determine what the best way to get the aircraft back on the ground. For the A-10C you could navigate to a point 3 – 5 miles out on the runway heading, over-fly the threshold at 1500’ AGL, break 180° at a determined point, roll out at 1000’ AGL on the downwind leg. When the runway threshold is 45° off from your reciprocal heading execute a 180° turn to the (base leg), roll out @ 300-400 on short final... easy money! If you’re interested in more info on specific airport traffic patterns there are several good resources available. For starters, try these links: http://airportguide.com/airport/Georgia/Adjaria/Batumi-UGSB-BUS/ http://skyvector.com/?ll=41.613333333,41.586666667&chart=301&zoom=3 (right click over Batumi for airport then left click on the Batumi link for airport info) Of course all this shite goes out the window in the event of an inflight emergency. If your oil pressure is at 0 and your engine temp is past the red line or your engine has already stopped or you have a fire that cannot be extinguished, you would just inform the tower of your emergency (assuming you still have electric power) and that you are going to land immediately. In most cases you should have at least a few minutes between your emergency call and the time you land for them to wave off any other traffic. BTW... in regards to the discussion on costly Airport landing fees... they are almost always cheaper than an off field landing and given the choice I'd say a its a small price to pay in exchange for a better chance at survival ;-)

Flight models aside... I've played FC2 A-10A and DCS A-10C and to me there is a big difference between the two. I'm sure that FC3 and DCSW software will work together and allow both on the same servers and function OK. I also know for a fact that there are some A-10C / Ka-50 virtual squads that will not allow FC3 aircraft onto their server. I'm not going to get into a debate about all the reasons why. To each his own... have fun!

Because FC3 has many simplified systems compared to the Hardcore Modules such as A-10C and the Ka-50 Modules in DCSW. To some degree its like mixing an arcade game with a flight simulation. Its two different camps really and I can assure you that the two camps would not play nice together.

I used this a while back to export my Shkval and Abris and it worked great, however, I didn't save a backup copy of the viewporthandling.lua file. Now I temporarily want to go back to a single screen but the Shkval is showing up in the upper left corner of the screen. How do I get back to default? I'm wondering what the original looked like before the modification to export the displays? Can someone post what what

Is the BlackShark 2 upgrade (from BlackShark1) supported yet? It wasn't in the previous version of DCS World (version 1.1.2.1). I already purchased the initial release of DCS BlackShark then had to purchase the upgrade to BlackShark-2 so I could fly CO-OP with the A-10C. I really shouldn't have to purchase a 3rd license to fly the Ka-50 in DCS World

blood animation!

What? I already paid for BS1 and paid again to upgrade via patch to BS2. Now I have am going to have to pay again to get a new BS2 license? C'mon man ?

The Laser Warning Receiver [LWR] is your friend. (DCS BS2 Manual EN.pdf / page 121-122) If it starts to warn you that you you have a threat, move in the opposite direction and keep pushing the Reset LRW button until the warning stops. Then you can turn around and attempt to identify and destroy the threat from a safe distance. You can switch from auto to manual mode on the Weapon Control Panel to use the Vikhr from 9500 m @ 500' AGL which is out of range of T-80's, BMP-3's, AAA, IR SAM's, etc. If your getting bagged by Radar SAM's, then the SEAD guys haven't done their job :smilewink:

When I do this, the SHKVAL and Abris both turn off. I only want the SHKVAL to turn off.

For BlackShark 2, comment out render_purpose.GENERAL with -- seems to turn off both SHKAVL and Abris, how exactly can we disable only the SHKAVL and leave the Abris on in the 3d pit.

A/ 40 B/ 36 C/ 35 D/ 33 i7-2700K @ 4.4GHz, 8 GB DDR3, GTX 460 1GB, SATA II SSD, 1920 X 1080, Win7 Pro 64

you can use Audacity to merge two or more of the sound files together to create something like this.... http://www.home.comcast.net/~gparaski/hog_pontiac_jtac.wav

Indeed, TrackIR software hot keys (F7, F8, F9 and F12) could interfere with the DCS key commands. I remapped my TIR hot keys to the optional DX commands output by my CH HOTAS.

wow, didn't expect this on a Saturday. is it recommended to save any config files to make the setup easier in 1.1.0.9 or should I just wipe everything out and manually config everything after 1.1.0.9? Specifically, is there any way to save custom key bindings from 1.1.0.8 and import them to 1.1.0.9?

I used your first suggestion and got it working. Thanks a bunch! rep inbound

Hi, I have a multi-player mission with six A-10's searching for 10 enemy groups that are moving on a 33000 radius zone at night. Consequently it takes a significant amount of searching to find them all. Because the mission will take about 2 - 3 hours to complete I want to keep all players motivated by letting them know when the blue coalition is making progress or getting close to completing the mission objective of destroying all red forces in the battlefield zone. How can I create a trigger to send a message to all (30% complete) when "any" 3 out of the 10 enemy groups are dead? I was wondering if there is a way to assign a point value to each group (10 points) and then create a trigger to send a message to all when 30 points have been achieve by the blue coalition. The problem is I have not been able to successfully apply this. Maybe there is another method that I should be trying? If there is a way to do this then I would assume that I can apply the same trigger logic to let everyone know when 50%, 80% or 90% are dead. Any help would be greatly appreciated. Thanks, -Damage

+1

I agree - windsocks would be nice

I'm no expert at mission building but I was able to contact Chevy AFAC on FM by making a couple minor changes. The default channel for Chevy was FM 45. I listened in on FM 45 as he reached his 1st waypoint and confirmed that I could hear him checking in with his position. When Chevy reached waypoint 2 where he was to begin AFAC (assigning targets) I added an advance waypoint action: Perform Command / Set Frequency / 44MHz FM. I bumped this up near the top of the list to occur prior to assigning groups. I was then able to communicate and get a response on channel 44. I got good UTM coordinates and followed them right to the tanks. To help with my testing I also added two triggers to let me know when Chevy was passing through waypoints 1 and 2. These are at the bottom of the trigger list and can easily be removed. I also changed the position of the player aircraft and added a couple waypoints just so I could keep track of when Chevy was nearing his waypoints. This allowed me to speed up the mission time and slow it down again when I needed to check the radios. I attached the missing and track file. I hope this helps. MP2_08A_FACtest.miz AFAC.trk

Are you assigning the unit to perform FAC in the advanced (waypoint actions) in addition to having AFAC as the group "Task". Its a long shot but I'm just wondering if somehow doing both might cancel one another out?

- How do you suggest cycling the radios? Do you mean just cycling through the 3 different mic transmit buttons? Its just a suggestion to check if you are having trouble with one particular radio. I usually use AM channels for JTAC so if I'm having trouble getting a reply on AM I will switch to FM or UHF to see if I can get a response from another aircraft or ground unit. If I'm having trouble on AM I'll also try to contact a local ATC to see if I can get a response on the AM channel. All this just try's to help narrow down the problem and if I'm having a global problem or a more specific one. -I thought about TARS while puzzling over this but see no reason why it would affect JTAC comms; I thought about this too and can see no logical reason except that its one software program working with another so it might be worth further testing. Stop Press: Oddly, I have never had to switch the Intercom Panel rotary to FM to monitor and transmit to/from FAC units on FM frequencies before; do you think this might be the issue? it's odd that every different kind of FAC unit/target combo failed to respond but all were on FM. If you don't turn the dial to communicate with the ground crew and just leave it in the default position then you shouldn't need to mess with it to communicate on either VHF channel. I have an old habit of turning the rotary dial to turn on the intercom to communicate with the ground crew. In the SIM, if you don't turn the dial back to VHF I know it will interfere with the ability to communicate on the VHF channels. I also know that it would be easier to use a keyboard shortcut "\" (backslash) that allows comms with the ground crew but I just like pushing buttons and flippin switches (just ask my wife ;)) I don't think the issue lies only with FM because I usually use AM for AFAC and have the same intermittent issues with failure to receive. In the same missions where I've had a problem contacting a OH-58 Kiowa AFAC, I have been able to successfully communicate with a ground based JTAC on FM.

I'm a not mission designing expert but I have also had this problem sometimes. Sometimes I have no problem communicating with AFAC/JTAC and sometimes I can't figure out why I can't get a reply from them even after double checking and triple checking the radio settings. The problem more often occurs when trying to contact an airborne unit using the VHF AM radio. Some things to check... 1. insure the intercom panel rotary dial is set back to VHF after using Intercom to communicate with ground crew. This definitely helps. 2. cycle the radios (AM, UHF, FM) then switch back to the one you need 3. if the mission allows - set the JTAC/AFAC unit to invincible so it doesn't get shot up to the point where he can't communicate. 4. does this happen more when using TARS vs. not using TARS?