NullCharacter

Yes, this would require the creation of multiple triggers. Here's a hypothetical example of how something like this could work: A trigger sets flag 1 to true when the three enemy armor groups are destroyed. Another trigger sets flag 2 to true when the enemy air support group is destroyed. A third trigger displays the mission success when flag 1 (enemy armor destroyed) and flag 2 (air support destroyed) are both true. No message appears unless both flags (conditions) are true.

I've never had my AI wingmen crash into me but there was an instance where I ordered them back to base and they decided to land on the same helipad at the FARP. All of a sudden I got two panicked "Ejecting" messages from them while their helis melted together on the pad.

The message can be made to appear as the result of a trigger. You'll need to set up a trigger that will get fired once after the appropriate conditions are met (enemy groups destroyed, player enters a trigger zone, etc..). Use the "Message & Delay" action to display your message on the screen.

I posted a track file (http://forums.eagle.ru/showpost.php?p=608916&postcount=27) with this issue. Unfortunately, the track file is probably 30 - 45 mins long. I have never seen this issue occur until about 30 minutes into the mission and after I have been using the laser extensively. I don't think it's possible to create such a short track with this problem unless there is a way to exclude the first 30 minutes from the track file?

Jesse, Excellent tool. Great job. It works just fine on my dual core system. If I could make a couple of suggestions for future versions: 1. Read the game path from the registry. Mine is located in "HKEY_LOCAL_MACHINE\SOFTWARE\Eagle Dynamics\BlackShark\Path". On 64-bit machines you might find it in "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Eagle Dynamics\BlackShark\Path" if it's not in the first one. 2. Save the settings to the registry instead of an .ini file. Some people (myself for one) would like to just keep your compiled binary on the desktop and a .ini file just clutters things up a bit.

The ModelViewer app has a textbox at the bottom for you to enter commands. Type in "clear" and hit enter before loading another model.

EvilBivol, I've finally got a good track file for you to look at. In this track file I actually manage to capture the problem happening while a missile is in flight. You'll see the missile, on the shkval screen, following the beam to the target when the problem occurs. The laser shuts off, ranging information disappears from the shkval and the missile just falls to the ground. The track file is slightly too big for the forums here but you can download it at the link below. http://www.sendspace.com/file/2xc0x8 Here are the times to watch for: 15:40 - Vikhr fired while laser shuts off and missile falls to the ground. 15:43 - Re-arm at FARP 15:47 - I attempt to fire the new missiles at targets and am unable to get the "C" since the laser no longer works. I even try resetting and turning the laser off/on with no luck. Hope this helps identify the issue.

Legolasindar, I hope you don't mind but I've take the liberty of attaching your PDF to this post for those that had trouble with your file host. Thanks for putting this together. DCS_BS_Keyboard_minilist.pdf

Looks like you've got me beat baksie! I started with a 8086, 42MB hard drive and a black and white EGA display. Funny enough, I found this on the Wiki page for the 8086 architecture: "The electronics industry of the Soviet Union was able to replicate the 8086 through both industrial espionage and reverse engineering." Now I think I know how the ABRIS came about!

Very nice! Great job!

It's not easy to retrieve but can be done if you've got the time and effort. The training files are located in "C:\Program Files\Eagle Dynamics\Ka-50\Missions\Training" as a bunch of .trk files. These files are really zip files so you can rename them to .zip and open them. Inside of each one you will find a "mission" file that contains all of the mission data, including the messages that are shown onscreen. You can open the mission files in Wordpad or a decent text editor like Notepad++. Also, the .ogg files contain all of the voice instructions that you hear during the training missions.

Not all missions are going to show a message when you complete or fail. It's really up to the mission designer. In the absence of a proper message I will just use the percentage of completion to assess my performance with 100% being excellent and anything below being proportionately less. However, in regards to dynamic campaigns, the percentage does have a distinct meaning. Score above 50% and you'll progress to the next stage. Below 50% and you will drop back a stage. Score exactly 50% and you will be assigned another mission in your current stage.

No.. but you can see if it is engaged by bringing up the Flight Controller Position Indicator using RCTRL + ENTER. See pages 6-27 and 6-28 of the manual. It's item #8 on the display. EDIT: Thanks Airway, you are correct. The cyclic does have a "Wheel brake paddle". Never even dawned on me to look at since it's hard to see from the pilot's perspective. Out of sight, out of mind.

During your mission you can press your ' (apostrophe) key to bring up the mission results screen. This will tell you how you are progressing in your mission. Also, the manual does not state anything about being able to save during a mission.

Yes, your wheel can take damage from enemy fire. It has happened to me a few times. SAMs exploding near your chopper can also pop them.

I have run SP2004 Orthos (the tool you are recommending) to stress test the CPU. I'm not sure how long I ran it for. It was not 24 hours but was more than 12 and had no problems. Well, since you're seeing a difference with your overclock settings I'll try lowering my CPU overclock later today to see if it make a difference and will keep you posted.

The "Familiarization" section is not a campaign, it's part of the training provided by the game. It's just a set of pre-recorded tracks that you watch. Your progress is not saved with these in any way.

The following file contains your logbook and campaign progress info. Just back it up and you should be okay. "C:\Program Files\Eagle Dynamics\Ka-50\BlackShark\data\scripts\Logbook\Players.lua"

The only way is to open each of the missions in the editor and change the state of your helicopter from "Takeoff from runway" to "Takeoff from parking".

About 40% of the time I go to launch a mission I get a DCS.exe crash. It doesn't matter what mission I choose or how I launch it (from editor, from campaign, etc.). I've attached a few of the most recent crash files but it seems they all point to the same problem. I'm running on WinXP Pro with SP 3. NullCharacter-CrashFiles.zip

Yes, I do recall running into this once before without re-arming. I was trying to conserve my missiles and was not able to launch all 12 of them before the problem occurred.

Yes, I think you might be right. I am an avid laser/auto-tracking whore. Even when I use the cannons I usually have the target auto-tracked. I created a simple mission yesterday where I took off from an airfield and fired off 6 vikhrs at some shilkas off in the distance. Then I put the chopper down in a field near the airport and left it running for about 30 mins. I came back and everything was fine, the remaining missiles fired. I was even able to re-arm a couple of times and fire off all my missiles. However, after about 30 mins of play time (1 hour of total mission time) and another re-arm the same problem occurred. I had 12 missiles loaded but could not get the "C". So I'm concluding that this somehow has to do with using the laser for around 30 mins or so and not just playing for 30 mins. Let me know if you want the track file for this. It's about 8MB so I can't post it on the forums but I can certainly e-mail it to you.

I deleted the post. I believe the track file is a bit screwy... I'll see if I can create another one that is more clear.

DELETED