NineLine

Thanks all, this is already reported.

Can I please have a track, I have not seen this in any taxing I have done recently. Thanks.

I'll try and test soon, but if either of you have tracks to share it would be helpful to see what procedures you are using so I can replicate the same as you. Thanks.

If you are still seeing this, please include a track. Thanks.

Any tracks? I don't always see this, but sometimes I do.

The pitot issue is known on both the A and D. I have recently bumped it as well. Thanks.

I believe this is fixed internally, we have been reworking how bombs interact with different services and internally I blow myself each time. I am not sure it will be in the next update, but more of a coming soon.

This was reported a while back, but thanks though.

Your images dont appear to be working here.

Reported, thanks!

We are working on some more tuning of reflections for options to allow people to tune on their own. Positioning is what it is, we cannot do full-on live reflections and expect the game to run at a decent FPS.

I just checked, using the keyboard I am not seeing the break instant on, whenever I use the keyboard it is short taps for me. This is meant to be a simulator so its to be expected that using the keyboard for any sort of controls like this is not ideal.

I would need a track if you are still having issues, thanks.

This is known and already reported, thanks!

Funny I just watched a track from an older version with heavy WWII action and the track played back fine. So please, unless you have something helpful to add, do not muddy up bug reports. Tracks have always been hit-and-miss, we need a better solution. The current Track system was always a debug tool more than a replay system. That said you can have a lot of success with them as well. Many tips are listed here. Some things I didn't see here are things like not jumping around to different views too soon or too often, try and view in the same version, although as I said above its possible, best practice is to view your track in the same version. New modules or additions, mods anything extra will impact a track and could throw it off.

Reported. Thanks.

This should be fixed now, thanks.

Please stop, people on both sides have received warnings and had posts removed, I am trying to let it be as free as possible for both. You only see your own warnings and your own removed posts. Don't assume one way or the other. If you see something that you feel is not fitting, then report the post. If you can't find a bad opinion against ED in this thread, or the thread where the hundreds of other messages were moved then you probably are not looking hard enough. So once again, this thread is for discussion of the original post in this thread which is all the official info we currently know.

Just a reminder, this thread is to discuss what is known which is listed in the first post here. Everything else is not welcome here and just clouds an already frustrating issue. Thanks.

Just an update on this, this will be a priority but the engineer needed is currently on DTC and will get back to this after that. Thanks!

I have tried with your track and by running a clean mission. I am unable to reproduce this issue. Thanks.

Sorry I am not able to reproduce this. AP works fine here during cold start, no input is causing it to stop or not work.

Where did I ever say we refused to fix anything? I simply asked to check with the suggestion I included. Now the thread has expanded I will have to investigate further, but to be clear, I am not personally seeing this. Thanks.

I do not see any issue on my end, make sure you watch the Wags video on the subject. Setting a deadzone to only 0 can result in the AP kicking off if there is even a slight spike in the joystick input.

A number of them are fixed internally already and should release with the next major update provided testing goes ok.