missing info Getting uninitiated random failures

[Bowie]

Getting uninitiated random failures now, since the last update.

One engine out( fuel?) on take-off, and twice failure of right landing gear retraction after take-off.

 

Please advise

 

Bowie

[rob10]

Post a track.  There have been issues in past where random failures were turned on in missions without the user turning it on.  Could be that.

[Bowie]

8 hours ago, rob10 said:

Post a track.  There have been issues in past where random failures were turned on in missions without the user turning it on.  Could be that.

 

These are a series of hand-built (mission editor) missions.

The events are, as stated, random.

They are uninitiated, described above, and did not occur before the last update.

 

 

Bowie

[rob10]

56 minutes ago, Bowie said:

These are a series of hand-built (mission editor) missions.

The events are, as stated, random.

They are uninitiated, described above, and did not occur before the last update.

Bowie

Yes, and there are older reports of random failures turning themselves on in a user created mission (i.e. user did not turn random failures on).  May relate to last update or may be random chance that this is happening now rather than before.

[MAXsenna]

 
These are a series of hand-built (mission editor) missions.
The events are, as stated, random.
They are uninitiated, described above, and did not occur before the last update.
 
 
Bowie

Tracks exist as a way to debug exactly what's happening. That's why the devs ask for it. They have another tool for "watching" them we are not privy to. You took you're time making this post, why didn't you just save the track when something when wrong, and post it here along with the bug report? Like Rob wrote, there have been issues like this reported before, and the only way for the devs to check what's going on is track.

Sent from my SM-A536B using Tapatalk

[Bowie]

23 hours ago, rob10 said:

Yes, and there are older reports of random failures turning themselves on in a user created mission (i.e. user did not turn random failures on).  May relate to last update or may be random chance that this is happening now rather than before.

And you are?

 

These are missions run w/o issue or incident constantly and consistently, until the last update.

Your fantasies not withstanding.

Want to be helpful? Try flying a mission, any mission, to corroborate this bug.

As there are a series of Eight of these missions, it is not a one-off, but likely systemic, like the failure to log landings or the other settings resets being reported.

 

 

Bowie

 

19 hours ago, MAXsenna said:

Tracks exist as a way to debug exactly what's happening. That's why the devs ask for it. They have another tool for "watching" them we are not privy to. You took you're time making this post, why didn't you just save the track when something when wrong, and post it here along with the bug report? Like Rob wrote, there have been issues like this reported before, and the only way for the devs to check what's going on is track.

Sent from my SM-A536B using Tapatalk
 

 

On that note, will attempt to capture the next one. (had another LDG failure this AM)

History - is not the problem.

The last update is.

 

 

Bowie

Edited July 22, 2024 by Bowie

[rob10]

26 minutes ago, Bowie said:

And you are?

Someone who is going to stop bothering to try and help you since you apparently aren't willing to try and help yourself.  I tried to point you in a direction to look at for what your problem could be but you apparently don't want to try and help figure it out (either by posting a track or in this case any details of the what missions are or a mission file or maybe searching the forums for the issue I suggested to see if it happens to be the same).  I worked on creating a mission all of last week in the mission editor and had ZERO issues.  I've flown a bunch of missions as well and had ZERO issues with random failures.  YOU are the only one currently reporting this issue, so obviously it's not a widespread issue.  Good luck figuring it out when you seem to only want to attack anyone that gives you any suggestions.

Edited July 22, 2024 by rob10

[MAXsenna]

 
On that note, will attempt to capture the next one. (had another LDG failure this AM)
History - is not the problem.
The last update is.
 
 
Bowie

Yeah, but like we've tried to point out. This last update do have issues with changing settings.
A track file is a copy of the mission file and all your settings applied to it, and the a record of how you play that mission. It's a debugging tool, and can help the devs see if anything's wrong with the mission, incorrect settings are applied to the mission and/or if there are user errors. So a track is usually the best way for the devs to troubleshoot. Haven't you read other bug reports where there is always requests for tracks if none is provided?

Sent from my SM-A536B using Tapatalk

[Bowie]

21 hours ago, MAXsenna said:

 

 

Yeah, but like we've tried to point out. This last update do have issues with changing settings.
A track file is a copy of the mission file and all your settings applied to it, and the a record of how you play that mission. It's a debugging tool, and can help the devs see if anything's wrong with the mission, incorrect settings are applied to the mission and/or if there are user errors. So a track is usually the best way for the devs to troubleshoot. Haven't you read other bug reports where there is always requests for tracks if none is provided?

Sent from my SM-A536B using Tapatalk
 

Yeah, they should put that in a NOTAM somewhere in the BUG Department.

Had a second cooling system failure, to add to the LG and Fuel malfunctions.

Had to go to manual cooler flap controls.

Can't believe this is an isolated incident.

Also checked not only the front-end setting for "Random Failures", but the individual missions as well.

This is definitely the previous big hot-mess update.

 

Still trying to catch one on a track, but the end of a mission isn't normally for doing other peoples work.

 

 

Bowie

 

[MAXsenna]

Yeah, they should put that in a NOTAM somewhere in the BUG Department.
Had a second cooling system failure, to add to the LG and Fuel malfunctions.
Had to go to manual cooler flap controls.
Can't believe this is an isolated incident.
Also checked not only the front-end setting for "Random Failures", but the individual missions as well.
This is definitely the previous big hot-mess update.
 
Still trying to catch one on a track, but the end of a mission isn't normally for doing other peoples work.
 
 
Bowie
 

My gut feeling tells me that random failures are applied, even if you haven't turned it on.
Do you really need a NOTAM when the first thing other users tells you in a friendly way that you should add a track. Mind you, you're not the first to respond on this way, and actually. @NineLine pretty much have posted the procedure for how to report a bug. Might not be the first pinned post in this section though. But I do know it exists. Tracks it says!
I do hope it will be solved for you.
Cheers!

Sent from my SM-A536B using Tapatalk

[Bowie]

On 7/23/2024 at 2:52 AM, MAXsenna said:

My gut feeling tells me that random failures are applied, even if you haven't turned it on.
Do you really need a NOTAM when the first thing other users tells you in a friendly way that you should add a track. Mind you, you're not the first to respond on this way, and actually. @NineLine pretty much have posted the procedure for how to report a bug. Might not be the first pinned post in this section though. But I do know it exists. Tracks it says!
I do hope it will be solved for you.
Cheers!

Sent from my SM-A536B using Tapatalk
 

It's not a personal problem.

 

Just trying to get the program straightened out by reporting problems.

Especially when the problems are related to recent DCS/Dev work.

Given that, expect to deal w/ DCS/Dev on the issue(s), and fellow operators to verify the issue(s) if possible.

Like this was a business, and we were paying customers.

 

 

Bowie

[Flappie]

We are asking for a track because we know the same issue has been reported many times before. And most of the time, it is explained by random failures programmed into the mission, even though these failures cannot be seen in the mission editor.

Moreover, since you're the only user to report this issue so far, chances are the problem you're facing was not caused by an update at all.

In this case, we can only help you if your provide a DCS track.

Edited July 24, 2024 by Flappie

[Art-J]

Bowie, all of us have been using 2.9.6 for two weeks now and you're the only guy reporting such frequent failure issues, so it's safe to say it's not as common as you think. I've been flying Mustang, Thunderbolt, Mossie and Anton, in stock and custom missions, with random failure option enabled and haven't experienced a single one so far, which leads me to continue to believe that the option hasn't been fully implemented in all aircraft for years. But I digress...

I'm not saying there's certainly no bug here. Clearly something happens in your DCS install. There must be something in your combination of mission, airfame and 2.9.6 that exacerbates the problem, but without a replay track, nobody's going to search for a needle in a haystack. We, fellow operators are more than willing to help narrow down the issue, but if you're saying "please advise" in one line and pretty much tell us to F off when 1st troubleshooting advice is given, then, well, good luck.

Rules here are simple:

a) If you post a track, ED might take a look at the issue, investigate and reply. The chance is small, but at keast it's there allright;

b) If you don't post a track, there's an absolute, 100% guarantee that nobody's going to bother, neither devs, nor beta testers, nor users, because there is no starting point to investigate. You being a "paying customer" is irrelevant.

Well, choice is yours. You do you.

[MAXsenna]

On 7/23/2024 at 3:59 AM, Bowie said:

Had a second cooling system failure, to add to the LG and Fuel malfunctions.

Forgot to ask this. Why didn't you just click "save track", and add it here? In the care you don't know. When you exit a mission, there's a "save track" button. That's what we want you to do. Give the file a relevant name, and just copy/paste or drag/drop it in here. Apologies if you already know how to do this. 

Cheers! 

[Bowie]

On 7/24/2024 at 11:18 AM, Art-J said:

Bowie, all of us have been using 2.9.6 for two weeks now and you're the only guy reporting such frequent failure issues, so it's safe to say it's not as common as you think. I've been flying Mustang, Thunderbolt, Mossie and Anton, in stock and custom missions, with random failure option enabled and haven't experienced a single one so far, which leads me to continue to believe that the option hasn't been fully implemented in all aircraft for years. But I digress...

I'm not saying there's certainly no bug here. Clearly something happens in your DCS install. There must be something in your combination of mission, airfame and 2.9.6 that exacerbates the problem, but without a replay track, nobody's going to search for a needle in a haystack. We, fellow operators are more than willing to help narrow down the issue, but if you're saying "please advise" in one line and pretty much tell us to F off when 1st troubleshooting advice is given, then, well, good luck.

Rules here are simple:

a) If you post a track, ED might take a look at the issue, investigate and reply. The chance is small, but at keast it's there allright;

b) If you don't post a track, there's an absolute, 100% guarantee that nobody's going to bother, neither devs, nor beta testers, nor users, because there is no starting point to investigate. You being a "paying customer" is irrelevant.

Well, choice is yours. You do you.

Wondering if the LG malfunctions are associated w/ the new, softer landing gear physics.

Have been attempting to master the toe-brake/castering tail wheel steering with buttons, and it is fussy.

Takeoffs have also gotten a lot more difficult, w/ some torquing around quite a bit. (although flattening the rudder curve a little helped a lot)

Maybe the ground yaw on TO was damaging the gear.

Which is OK, because skill will resolve it.

Doesn't explain cooling and fuel issues, though.

Just showed up, like the awful Section formation station-keeping, with the last big "hot-mess" patch.

Don't ever expect retrograde progress.

 

 

Bowie

Edited July 30, 2024 by Bowie