||Thread Tools||Display Modes|
|10-01-2015, 03:32 PM||#1|
OPEN BETA - How to report a bug (FAQ & Guide)
Welcome to the 1.5 Open Beta, so you want to help us out and report a bug, follow the guide below and help us squash some bugs! Nobody is required to report a problem, but it will help us greatly to have a wider sampling of systems and situations. Testing isn't always fun, so Open Beta might not be for everyone, there will be problems. If you don't think you will enjoy this, stick to the current release until 1.5 is moved there where it should be more stable.
How do I know my problem is a bug and needs reports?
Make sure your system and hardware is up to date, and that you meet the minimum specs. Make sure your Open Beta isn't running any modifications of any sort, your install should be clean (All 3rd Party modules are fine). Try to reproduce and/or search for similar reports first.
How do I copy all my campaign progress and controller profiles to the Beta?
Simple, you don't, with any update this is true, and more so with such a large change. Installing things from a previous install can compromise your install, making any testing useless, not to mention cause your sim to have issue. Custom skins are fine though, and shouldn't hurt anything. There is even a .bat file floating around to help copy these and other things over, please don't use this, it is counter productive to the testing and completion of 1.5.
Where should I enter my report?
Pick the appropriate section in the DCS 1.5 Open Beta Bugs & Problems Section, if its not 100% clear use the general section.
if you are having a problem, and it seems to be with a specific module, please put the bug in that modules specific sub-forum found here:
or in the 3rd Party forum found here:
All others specific to the core game still go here.
How do I know my report hasn't been posted already?
Search the bug section using the forums search function.
How should I title my reports?
Use short descriptive titles, don't try and explain the bug in the title, but also have be descriptive enough that we can get the gist from the title.
Do I need to label my bug? Like [BUG] or [OPEN], etc
No, moderators will take care of that depending on time and need.
What do I need to tell the devs about the bug?
First, ONE BUG PER THREAD, when in doubt, create your own thread, if its a duplicate, we can merge them.
You need to supply the following:
What we don't need
Minimum system requirements: OS 64-bit Windows 7/8/10; DirectX11; CPU: Core i3; RAM: 8 GB; Free hard disk space: 30 GB; Video: 2 GB RAM card, DirectX11 - compatible; requires internet activation.
Recommended system requirements: OS 64-bit Windows 7/8/10; DirectX11; CPU: Core i5+; RAM: 16GB; Hard disk space: 30 GB; Video: NVIDIA GeForce GTX780 / ATI R9 290 DirectX11 or better; Joystick; requires internet activation.
Most important, Open Beta is not for everyone, it can have issues that make the sim unplayable, or aspects that dont work correctly, if this sounds like something you dont want to go through, dont run Open Beta. If you do run Open Beta, dont complain about problems later, you should submit bugs, and wait for them to be addressed, welcome to the life of a tester.
It's not the opinion that breaks the rules, its the delivery of that opinion • ED Product Terms • ED External Communication Policy example
Veteran of the DCS WWII July update thread of Two Thousand Fourteen • You're so vain, I bet you think this post is about you. • "I find your lack of faith disturbing"
Last edited by SiThSpAwN; 06-25-2016 at 07:19 PM.