Bug Reports / Testing Process / Updates?

[NineLine]

DCS A-10C is the consumer version of the A-10C Training Platform developed for USAF and/or ANG

 

 

It doesnt mean they were worked on entirely by the same team or completely equal in any way. But yes, we are drifting off topic now...

[cichlidfan]

It doesnt mean they were worked on entirely by the same team or completely equal in any way.

 

Precisely.

[SkateZilla]

It doesnt mean they were worked on entirely by the same team or completely equal in any way. But yes, we are drifting off topic now...

 

Agreed,

 

I added more to my post.

[Sabre-TLA]

To get back on topic I think the ask is really this:

 

Rather than being surprised by what gets fixed or not fixed by reading patch release notes could we instead get a view to what is currently being worked on for the next patch release?

 

This is not a weekly status report but a pre-release notice indicating what is intended to be included in the next release (subject to change as always).

 

This would be similar to WAGs: 1.2.8 Open Beta Preliminary Change Log but on a patch release basis.

[NineLine]

For a better understanding on ED's policy on external communications, this is very similar.

 

[cichlidfan]

Any Bugs reported after the Software went public were entered by someone on the Dev Team and acknowledged.

 

Public Bug Databases are RARE. For the simple reason that when you have a million people submitting the same bug under different numbers, it gets overly repetitive and cluttered.

 

Restricting users to posting on a Bulletin Board/Forum and having Devs filter through them, removes 1000 people posting duplicate bugs into the database.

 

I think it was established early in the thread that READ ONLY access was desired.

[NineLine]

I think it was established early in the thread that READ ONLY access was desired.

 

Even Read Only would be a lot of work to maintain as I would expect everyone would not only want to see the bugs, but their status, descriptions, causes, ect... and I would rather see them put their resources elsewhere.

[Ranger79]

Even Read Only would be a lot of work to maintain as I would expect everyone would not only want to see the bugs, but their status, descriptions, causes, ect... and I would rather see them put their resources elsewhere.

 

Maybe Groove could get in on the discussion, no offense at all Sith but you are the only mod putting out info it seems lately.

[NineLine]

I just like to read my own type ;)

 

But that vid I just posted... came from the top as an example.

[SkateZilla]

Maybe Groove could get in on the discussion, no offense at all Sith but you are the only mod putting out info it seems lately.

 

:music_whistling:

 

I think it was established early in the thread that READ ONLY access was desired.

 

that would possibly do more harm than good

Edited May 26, 2014 by SkateZilla

[cichlidfan]

Groove probably has his hands full dealing with RRG issues.

[Rider1]

How'd we go from Bug Reports/Testing to Government Contracts and Such?

 

Umm too much Tom Clancy I would imagine. But I was just pondering things while mopping floors.

 

But it would be cool if ED had a compartmented group of Russians working in top secret on simulators for the DOD.

 

Hmm F35 touch screen simulator...

[FSKRipper]

I would agree with a former posting by Flagrum regarding the forums.

 

The current bug tracking structure is not optimal. I was twice in the situation not knowing if I use the 1.2.8 open beta forum or the bug forum of DCS world.

Since the reported bugs were not fixed with the official release, i kept posting in the beta forum. Opening a new thread would simply increase the workload by the developers to monitor all forums in my opinion. But how can I be sure that after the release of a candidate, the beta forum is continously monitored when a bug is not fixed two patches later? :huh:

 

I also encountered several double posts in these sections. If the developers won't permit read acess to a bug tracker, maybe it would be the best to melt some subthreads together.

I'm not sure that keeping bug-forums with up to 13 sub categories for every module is the right way, since even I have no time to check the subthreads of all modules if a bug I encountered was already reported. :music_whistling:

[SkateZilla]

I would agree with a former posting by Flagrum regarding the forums.

 

The current bug tracking structure is not optimal. I was twice in the situation not knowing if I use the 1.2.8 open beta forum or the bug forum of DCS world.

Since the reported bugs were not fixed with the official release, i kept posting in the beta forum. Opening a new thread would simply increase the workload by the developers to monitor all forums in my opinion. But how can I be sure that after the release of a candidate, the beta forum is continously monitored when a bug is not fixed two patches later? :huh:

 

I also encountered several double posts in these sections. If the developers won't permit read acess to a bug tracker, maybe it would be the best to melt some subthreads together.

I'm not sure that keeping bug-forums with up to 13 sub categories for every module is the right way, since even I have no time to check the subthreads of all modules if a bug I encountered was already reported. :music_whistling:

 

Double posts are usually marked as Duplicate in the Thread title or merged,

 

I'd assume that when a Build is in Open Beta, you post in the Beta Bugs section, and once it goes gold/final, in the normal section.

[NineLine]

Well as I have said previously, there is always room for improvements. The 1.2.8 beta wasnt nearly as smooth as the 1.2.7. The forums werent arranged as nicely or available as fast... so yes it was bumpier.

 

We do try and merge posts when possible, in the same instance it would be nice if people took more time to search before posting, specially when making open beta reports. I merged about 20 posts on the F-15C icon ;)

 

I would agree with a former posting by Flagrum regarding the forums.

 

The current bug tracking structure is not optimal. I was twice in the situation not knowing if I use the 1.2.8 open beta forum or the bug forum of DCS world.

Since the reported bugs were not fixed with the official release, i kept posting in the beta forum. Opening a new thread would simply increase the workload by the developers to monitor all forums in my opinion. But how can I be sure that after the release of a candidate, the beta forum is continously monitored when a bug is not fixed two patches later? :huh:

 

I also encountered several double posts in these sections. If the developers won't permit read acess to a bug tracker, maybe it would be the best to melt some subthreads together.

I'm not sure that keeping bug-forums with up to 13 sub categories for every module is the right way, since even I have no time to check the subthreads of all modules if a bug I encountered was already reported. :music_whistling:

[Dr_Arrow]

I would agree with a former posting by Flagrum regarding the forums.

 

The current bug tracking structure is not optimal. I was twice in the situation not knowing if I use the 1.2.8 open beta forum or the bug forum of DCS world.

Since the reported bugs were not fixed with the official release, i kept posting in the beta forum. Opening a new thread would simply increase the workload by the developers to monitor all forums in my opinion. But how can I be sure that after the release of a candidate, the beta forum is continously monitored when a bug is not fixed two patches later? :huh:

 

I also encountered several double posts in these sections. If the developers won't permit read acess to a bug tracker, maybe it would be the best to melt some subthreads together.

I'm not sure that keeping bug-forums with up to 13 sub categories for every module is the right way, since even I have no time to check the subthreads of all modules if a bug I encountered was already reported. :music_whistling:

 

I also don't know where to post bugs, which are present in beta as well as release version. Moreover we have DCS World bugs forum, we have FC3 subforum without bug forums, we have bug forums for Ka-50, Su-25T, A-10C and also third parties bug forums. Sometimes it is really hard just to decide where to post a bug and even if I do, I don't know if someone will actually see it.

 

I would also question the existence of open beta, why keeping two separate release versions if you can have just one and patch it up with the auto-updater with several quick small patches as needed or once a week - I always thought that this was the main benefit of having online updating system. I think this would also decrease workload of the team and cause less confusion within the community.

[NineLine]

I would also question the existence of open beta, why keeping two separate release versions if you can have just one and patch it up with the auto-updater with several quick small patches as needed or once a week - I always thought that this was the main benefit of having online updating system. I think this would also decrease workload of the team and cause less confusion within the community.

 

If you want to test beta, but your favorite server doesnt, then you may have connectivity issues. Keeping two installs is purely your choice and not required.

[Flagrum]

:music_whistling:

 

 

 

that would possibly do more harm than good

Hiding the information and hoping nobody will remember to keep the people quiet is also no solution ...

[NineLine]

Hiding the information and hoping nobody will remember to keep the people quiet is also no solution ...

 

 

That isnt what is happening... at all. Please dont send the discussion down the path of silliness.

[159th_Viper]

Hiding the information and hoping nobody will remember to keep the people quiet is also no solution ...

 

Who's hiding what? There seems to be a misguided sense of entitlement that pervades many posts in this thread :D

 

Edit: Yeah, Sith's right: This is beginning to get very silly indeed :megalol:

[FSKRipper]

@SiThSpAwN: No problem, I know it takes time to sort things out. I take also time to read subforums but as DR_Arrow said... What to do if i own all modules and i encounter problems with the mission editor while creating and testing an A-10c Mission. Beta-Forum, dcs-world forum with Mission Editor subcategory, A-10c forum or maybe Combined Arms if playable units are part of the mission?

 

@SkateZilla: Thats exact my problem, since the first official 1.2.8 is out my instinct was to post everything in the DCS-World bug-forum but since another open beta round started I'm not sure anymore how to report bugs that weren't fixed with the release.

 

OK, maybe the structure is not the problem, how about strict dictatorial bug-posting rules in one forum which can even be understand by non-native english speaker dummies like me :)

[Flagrum]

Who's hiding what? There seems to be a misguided sense of entitlement that pervades many posts in this thread :D

 

Edit: Yeah, Sith's right: This is beginning to get very silly indeed :megalol:

I was referring to SkateZillas objection to that read access would do harm. He suggests to not allow us to see the filed bugs because we could start discussing, yeah, perhaps ranting about them - he prefers them to be not accessible to us, i.e. hiding them. I find that approach silly, tbh.

[NineLine]

@SiThSpAwN: No problem, I know it takes time to sort things out. I take also time to read subforums but as DR_Arrow said... What to do if i own all modules and i encounter problems with the mission editor while creating and testing an A-10c Mission. Beta-Forum, dcs-world forum with Mission Editor subcategory, A-10c forum or maybe Combined Arms if playable units are part of the mission?

 

 

Its not always clear, you just need to use your best judgement and pick the forum you think best fits the issue, when in doubt, post it in the DCS World section, or heck, ask a mod... we like helping believe it or not.... worse comes to worse, we will move it.

[Flagrum]

That isnt what is happening... at all. Please dont send the discussion down the path of silliness.

But what is happening? There are bugs that nobody - except ED - knows their status. And maybe not even ED knows about all bugs that were reported ... but what do I know - I have no clue about the status ...

Is it really so bad if we would know more about it? Or what is the reason why that information is hidd... erm ... not made available to us?

[FSKRipper]

Its not always clear, you just need to use your best judgement and pick the forum you think best fits the issue, when in doubt, post it in the DCS World section, or heck, ask a mod... we like helping believe it or not.... worse comes to worse, we will move it.

 

Ok, will try it. Never thought of asking per PM or so since Moderators are shy end mighty creatures like fairies or god :D

Edited May 26, 2014 by FSKRipper