Questions ?

[FatSlapper]

#1 Is anybody at liberty to say why a known issue list is not allowed? In the short amount of time I have used 1.1.2.1 World/A-10 I have seen literally hundreds of bugs and this isn't including "world" issues just the A-10, AI, Avionics, Weapons, ME, ATC/Comms etc. etc. I know I'm not the only one seeing these problems and it just seems so wasteful and time consuming to post issues that ED is already aware of. Besides I wouldn't know where to begin.

 

#2 Why hasn't the past issues that were fixed not applied to the latest release? Example the weaponry was looking good until You shot at a ship but now it is worse. It looks like We are back to pre release days 1-1-2011 what happened to all the bug reporting that was done? Do We have to go through 10 more patches just to get to where We were with 1.1.1.1.? A year and a half just to take a giant step backwards.

 

#3 Do We really have to report the same issues We have been reporting for 18 months with the AI, Comms, Weapons, Avionics, ME...You know the ones that were acknowledge to be KNOWN and reported. A lot of these issues are very apparent the instant You run the beta, why shove a release out like this? Did ED think We might not notice how long its going to be before this A-10 is stable enough to use. Come ON! its only been a year and a half.

[Vitesse2l]

Do you understand the difference between beta and release?

 

Why not submit a list of the bugs you're seeing together with screenshots and /or mission tracks?

[PeterP]

Instead of bashing him for making himself heard lets extract the info he wants to transport to the DEVs.

 

So:

Some points are very valid.

 

And I also have sometimes a hard time to warp my head around some things that where fixed, - and now show-up again.

 

Let's blame this on the beta-state - but it makes reporting problems really hard without a at least weekly updated bug-list that is structured .

 

Something like this:

DCS:World

- Menus

- AI

- Terrain

- Missioneditor

-ect.

 

 

Modules:

-Cockpit

-Avionics

-Model

-ect.

[159th_Viper]

It is simple: As with all open-betas, if you want to report a bug please feel free to do so in the relevant forum/subforum. There are enough to cater for any eventuality pertaining to the three modules currently subject to the open-beta. Once reported, bugs will be acknowledged as either already known or reported and will then be dealt with further via the internal bug tracker.

 

Of course we do request that, prior to reporting, a user searches to ensure that the matter has not already been dealt with and if not, reported in such a manner as to accord with the 'How to Report' stickied thread.

 

Otherwise just feel free to enjoy the modules, keeping in mind that they are very much a Beta at present.

Edited June 4, 2012 by 159th_Viper

[Panzertard]

I could introduce some reasonable explanations, but it would be speculations on my part.

So, since this thread can't go anywhere unless ED responds - I'll leave it open a bit longer.

 

Unless things get out of hand.

PS: Please be civil..

 

EDIT: Sniped by viper, as usual.

Edited June 4, 2012 by Panzertard

[PeterP]

Where to start if you think you found a bug/issue:

 

Sticky: TROUBLESHOOTING - Help us helping you.

 

 

DCS World v1.1.x.x

Please describe the issue and provide the information we need - so we in the forum-community can solve YOUR issue more quickly.

 

Reporting a problem

- What were you doing just before - or trying to do when the problem happened?

- In which mission? (If custom mission, attach it / trk).

- What happened?

- And when? (Track timeline, use LCtrl + Pause for TIME ingame).

- Relevant info regarding your issue - SP, MP, Mods, custom PC gear - anything relevant.

- Short description of your hardware config (a full DxDiag must be attached for graphics/crashes/hardware/fps issues).

- Screenshots when possible. We may not understand what you are talking about until you illustrate it properly.

Please, when attaching tracks - no 50 minutes tracks. Please keep track-length to a minimum, max 5 mins is preferable.

 

TECHNICAL, hardware related crashes as well as bug issues - please attach the following:

• DxDiag report
  
• Screenshots to illustrate the problem.
  
• Any *.CRASH files in your "DCS\Logs" folder.
  
• Any ERROR* files you find in the "DCS\Logs" folder.
  

 

GAMING ISSUES, graphic glitches as well as ingame bugs - additional info required:

• To illustrate a "gaming issue" please include a TRACK-file.
  SP TRACKS; You need to save it when you exit from the mission - at a location where you choose.
  MP TRACKS are automatically saved in your config folder.
  

 

Where to find;

• All CONFIG should be found at your userprofile, such as "C:\Users\<yourname>\Saved Games\DCS"
  You may also find it directly using "Windows Explorer" and browse to the "YourName\Saved Games".
  
• LOGS; dcs.log and me.log in: C:\Users\<yourname>\Saved Games\DCS\Logs
  
• MP LOGS: C:\Users\<yourname>\Saved Games\DCS\Logs\net-server.log
  
• CRASH files: C:\Users\<yourname>\Saved Games\DCS\Logs
  
• SCREENSHOT after PRINTSCREEN; C:\Users\<yourname>\Saved Games\DCS\ScreenShots
  
• MP TRACKS; C:\Users\<yourname>\Saved Games\DCS\Tracks\Multiplayer
  
• SP TRACKS; You need to save it when you exit from the mission - at a location where you choose
  
• INPUT config; C:\Users\<yourname>\Saved Games\DCS\Config\Input
  

 

How to create a DxDiag report - and attach it;

• Use START-Run or type in the WIN-Search: DXDIAG
  
• In DxDiag, press the button "Save All Information, to a TXT file" for the report.
  
• Save the file to your desktop, it should be named "DxDiag.txt"
  
• In the forum post - upload it using "Go Advanced", then press the "Manage Attachments" in the section below the post. Upload the TXT file.
  

 

How to attach other files;

• If the file is TXT/JPG/MIZ/TRK - then you can attach it directly to a post.
  
• Other files, please ZIP/WinRAR it - then attach it.
  
• In the forum post - upload it using "Go Advanced", then press the "Manage Attachments" in the section below the post. Upload the ZIP/RAR file.
  

 

 

...maybe I should post this link it in first instance , instead of my answer.

- nevermind -

I just wanted to express that I can comprehend how folks are feeling if they not visit the bug-section as frequently as I do. :P

Edited June 4, 2012 by PeterP

[FatSlapper]

@Viper---"Of course we do request that, prior to reporting, a user searches to ensure that the matter has not already been dealt with and if not, reported in such a manner as to accord with the 'How to Report' stickied thread."

 

The forum search function SUCKS Mud, and rarely results in a good find. It would be nice to be able have a desktop shortcut to the Known Issue sub-forum thread to quickly check to see if the issue You are having is on the list, if it is well then OK, If not then click on the "REPORT NEW ISSUE" button.....

 

Also the status of the problem would be nice: "Fixed for next release", " WIP release unknown at present", "Can't be repaired limits of Sim/Video", etc, etc. [edit] giving credit to the member Who first discovered the bug might give incentive to reporting.

 

So the ED Testers are not way ahead of us in reporting all the little annoying bugs that were already dealt with in past releases and that are very black and white?, how about posting that advanced comprehensive list so we can contribute to the unknown-to-testers issues so We don't keep grinding in the same old rut dealing with the same old stuff and never moving towards the HIGH hanging fruit that has been bugging users for a year and a half now.

 

It sounds like ED is not directly prohibiting a Known Issue thread, am I wrong?

Edited June 5, 2012 by FatSlapper
addition

[Nate--IRL--]

It is unlikley that the internal buglist will be opened for public scrutiny. For now it will continue to be us collecting issues from our testing and from user issues reported on the forum.

 

However if you feel something has been overlooked please feel free to let it be known, everybody else does :) There is absolutley no harm in bugs being reported more than once. Better that than not at all.

 

Nate

[FatSlapper]

It is physically impossible to post all the bugs I see in 1.1.2.1, and i don't have time to search each one to see if it was posted deep inside a 300 post thread. I just want to be able to post issues that have not been reported already 37 times. Anybody interested in doing efficient bug tracking would come to the same conclusion why not ED? Maybe They just like all the issues to hide in the jazillion threads and out of the public's eye. Ed doesn't make a clear path for Us to help with debugging they just dump a half baked beta on its customers as some sort of pacifier.

 

I thought The Ed tester team tested the releases before dumping them on the customers? How could 1.1.2.1 be so buggy if this were true. Why so many obvious bugs release to the customer base? ED has said it so many times in the past (It will get released when it gets released) I just don't understand why We have to go through all of this again We were told that some nagging issues from the original beta a year and a half ago would be fixed in this release.

 

So is it going to take another 10 patches and a Year and a half to get back where We were ?

[159th_Viper]

The forum search function SUCKS Mud, and rarely results in a good find.

 

It is fine. Search the particular sub-forum with the 'show posts' tab.

 

It sounds like ED is not directly prohibiting a Known Issue thread, am I wrong?

 

No, they are not. The known issues threads are present in the particular Bugs and Problems forum, further subdivided and catalogued into different sections for users to be able to easily identify and report if necessary. It does require a wee bit of effort from the user - if you are not interested in expending said effort, refrain from bug-reporting in the open-beta whilst waiting for release.

 

 

It is physically impossible to post all the bugs I see in 1.1.2.1, and i don't have time to search each one to see if it was posted deep inside a 300 post thread.

 

If you are not going to post them then step away and enjoy the open-beta, alternatively not.

 

Ed doesn't make a clear path for Us to help with debugging they just dump a half baked beta on its customers as some sort of pacifier.

 

A final, friendly warning here as the request in post #5 seems to have been ignored: Keep it constructive or keep it silent. There is method to the system employed to date - if you do not like it, refrain from participating in the open-beta insofar as bug reporting is concerned.

 

 

How could 1.1.2.1 be so buggy if this were true. Why so many obvious bugs release to the customer base?

 

Open-Beta

 

I just don't understand why We have to go through all of this again We were told that some nagging issues from the original beta a year and a half ago would be fixed in this release.

 

You do not have to. All you need to do is wait for the official release if you are unhappy with the open-beta.

 

 

Matters have now been dealt with more than once in this particular thread, from the manner dealing with the reporting of bugs in the open-beta to the system employed in dealing with said bugs. In order to prevent any more argumentative and/or disruptive posts, especially as said behaviour continued notwithstanding a prior warning/request I'll close this thread as nothing good can come from continuing a discussion where all has been said.

Edited June 5, 2012 by 159th_Viper