Please read before posting: HOW TO REPORT BUGS

If you think that you have found a bug, please do the following before reporting it:

1. Make sure that it is actually a bug. DCS is a complex simulation, and what you might experience as an issue may in fact be a feature. Please refer to the manual and the User FAQ >here<.

2. Install the latest updates and patches. There is a chance that the bug has already been fixed. Please note that you can only get technical support for a fully patched and updated version of DCS that does not use any 3rd party modifications. Updates and patches can be downloaded for free from >here<.

3. One thread per bug only. Search this forum section if the bug has been reported before and if there is already a (temporary) fix available. If the bug has already been reported, use the respective thread to add a confirmation, alternative steps to reproduce it (if available) and your PC configuration.

If you are sure that you have found a bug that has not been reported before, please open a new thread with a brief but meaningful title and use this form to report it:

Bug description:

...

Steps to reproduce / Conditions of occurence

...

PC Configuration

...

Attachments

...

When using that form, please follow the guidelines below on how to report a bug properly.

Bug description:

The description of the problem should follow the 3C rule: it has to be complete, clear, and concise. This will ensure that the tester/developer can correctly understand your bug description in the first read-through, which will save a lot of time.

Please do not only describe the bug itself, but also the correct situation that you would have expected. For easy reference it may also be helpful to add a quote from the manual (+ page) where the correct result is described.

Do not forget to mention the DCS module/version that you are using.

Steps to reproduce / Conditions of occurence:

The testing team has to reproduce the bug before it can be fixed. If the bug is reproducable, decribe the steps to reproduce it (if they are not obvious).

If the bug is not reproducable or only occurs intermittently, this should be stated. In that case provide a description of the conditions and circumstances under which the bug occured.

If alternate steps or conditions are possible in confirming the bug, they should be listed as well. Also add any additional information that you think may be helpful in fixing the bug.

PC Configuration

Briefly describe your PC configuration. The following information should be included:

1. Processor

2. Motherboard

3. RAM

4. Video Card and Driver version

5. Type of CD/DVD drive

6. Internet connection type and performance

7. Control devices

8. Operating System and installed updates/service packs

9. DirectX version

If you are using any special hard- or software while running DCS, please mention that as well.

Attachments

It is essential to add material for investigation, which demonstrates the bug in an obvious manner. This could be:

• Screenshots (with highlighting)
  
• Track Files
  
• Error Messages
  
• Temp folder including Logfiles
  
• Console reports
  
• Missions
  

If you provide a track, it is very important to note the time at which the bug can be seen. Tracks are recorded by default for every flight, so if a bug occured simply save the track from the debriefing screen.

Individual Logfiles can be found in the ".../Eagle Dynamics/Ka-50/Temp/" folder, however, it is a good idea to provide the whole "Temp" folder content. If the bug is reproducable, please delete the content of the folder first (but not the folder itself), then run the game until the bug occurs, and after that attach the Temp folder, which now includes only the newly created Logfiles. Just remember that multiplayer tracks are currently stored in this folder, so be sure to review the contents before deleting.

Note that if you use Vista and installed BlackShark into the default Program Files directory, then the Temp folder might be empty even though a crashlog has been created. To access it press the "Compatibility Files" button in the Explorer's toolbar.

The console can be viewed by deleting the "--console" parameter from the desktop shortcut properties. To do that, right click on the shortcut that you use to launch the game, select "Properties" and the "Shortcut" tab, then delete the "--console" command line parameter from the end of the "Target" field. Once you start the game the console will appear. You can add the parameter again after taking a screenshot of the console messages.

If there is not enough space to store the attachement on this site, please upload it elsewhere and provide a link.

Finally remember to check your bug thread frequently, as the testers/developers may ask you to provide additional information. And please be patient if you do not get instant replies, every report that fulfils the above guidelines will be investigated, however, this may take some time.

Many thanks for your help and understanding.