bkthunder

Yes I agree, I can hardly do a loop with the EB! It seems the FM is accurate, so I'm wondering if I'm missing something?

Can you point out the lines that are repeated / fixed please? (line number). Thanks. P.S. Just to clarify, there may be multiple reports for the same bug, but they are different posts made by different people. Or, in rare cases, in a single post there were 3 or 4 different reported bugs, so those have been split into multiple lines with a common title and description, but the same forum link. Other than that, at the moment I don't see duplicates except for one I removed just now. Let me know what you find please. Thanks!

I was looking forward to giving this a try after hearing about the nice progress you made. Well, so far I've spent only about one hour doing IFR flights in it, but I have to say the attention to detail is impressive. Not a massive fan of the aircraft itself, but you've done a commendable job, the cockpit and instuments feel alive more than in any other module. Hard not to love it. :thumbup:

UPDATE 4/19/2020 - Added 39 new reports (total 170) - Updated stats, see attached image in the OP / or "dashboard" sheet on the bugtracker

Basic as in "fundamental". Nothing in a modern jet is simple. That said, if you can't even code a HUD with a propely working VVI, which is literally in your face 99.8% of the time, how can I expect you to do something much more advanced?

As someone who has bought the MiG-21 when it was first released, I can tell you this: - The FM saw drastic changes, several times, before M# and HB split (when they were Leatherneck). - At one point, the FM felt *very* similar to how it feels now - A bit before the split, the FM felt quite ok, similar to know but with more belivable stalls etc. - After the spit, the FM was (or felt) reverted to one of the early versions from the first release - Now, we go back to something more dynamic. So, I am an FM Nazi, and I lost all hopes for the MiG-21, but *some* change is better than no change, as long as they continue on developing. It feels less on rails now, so it's good sign IMO.

There can be different policies for implementing new weapons and sensors or wait for the official ED solutions, but there is NO EXCUSE for having bugged and erroneous BASIC systems such as navigation displays and functions, switchology, hydro-mechanical and electric systems etc. these are basic. They don’t get that stuff right. I think taking about new weapons is futile when the dev can’t even code a properly working navigation display or the break pressure gauge. Yes, maybe I am pedantic, but how can you trust the implementation of a complex weapons system when basic avionics are sloppy?

Hi, please read the OP. If you want to contribute, I'll give you access. PM me you email (or is it the one you have username?). ;)

Just added 10 other bug reports to the file

They said they only work on what they have on their official bug tracker. The fact 75% of all reported bugs aren't there shows a little problem I think.

@Decoy, I believe that’s clear if you read the bug tracker thread, there is no hint that it wants to become the official bug tracker. Quite simply, three quarters of the bugs listed there so far, are not acknowledged / not on the official bug tracker, and many have been reported multiple times, creating clutter. As a customer / community member, looking at the official bug tracker doesn’t give me a good idea of what and how many bugs the Harrier has, nor does looking at the forum, because there are many fragmented reports. I’m hoping the community bug tracker gives a more clear and objective idea of the current state and development.

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

[ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing

Good question. Most of the bugs added so far are from the first 5-6 pages of the bugs section. If you scroll through, many of them have been submitted long ago, and bumped multiple times, so I am fairly confident most of those bugs are not solved. In fact, I have skipped the solved or dubious bug reports on purpose, as I wanted to have a view of what are the actual bugs existing as of today. Let me add that I am more than looking forward to hearing from community members and even Razbam themselves to update the status of the listed bugs. A simple way of doing so would be to indicate the line number and say solved/ackoweldged or else. The long answer is: 1. I can't possibly do it all by myself, hence why I'm asking for the support of the community (and why it's so aptly called Community Bug Tracker, lol) :D 2. There are 2 sections in this forum: Problems & Bugs, and Resolved bugs. Resolved bugs are supposedly moved to the proper section. However, few months a go a large number of posts were undiscriminately moved to the resolved bugs section by mistake, according to Decoy. So It's kinda hard. Bottom line is, Razbam should really be the first one to keep the sections tidy and mark bugs as ackowledged / solved, if they don't do it, I don't expect to solve the issue single-handedly. 3. I might be wrong, but I believe while the community can partly take on the task of reporting bugs, we cannot take the responsibility for testing and checking what is solved. It should be up to the developers to first acknowledge the reports and then report back what is fixed (chagelogs, changing the thread title with [FIXED], [CONFIRMED] etc.). Of all the bugs listed so far in the file, about 75% of them are not even acknowledged. I hope this is clear and of course, if you want to contribute, let me know.

Yeah, that's something that I also noticed and it's weird. It also happens at high speed, the elevators are significantly pitched up on a clean jet flying fast and level.

Not in the F-16 and most other fighters as far as I can tell. Lights are usually tied to the generator, the A-10 has them tied to the APU generator so you can have them on before engine start, kinda like an airliner.

Can you add this to the bugtracker?

DanielNL, if you PM me your emial address I'll give you access so you can add/edit your reports yourself, that makes it much easier to manage if we all help a bit. Also, you can check out the "Acknowledged vs. un-ackoweldged" for stats. There other sheets with stats and graphs at the bottom of the page. Thanks EDIT: one thing to note is that currently only a fraction of the reports is in there, there are a lot more old reports to include, so we might see higher acknowledgement rates as those are added.

The big FM errors make it pretty hard to accept the F-5 is not being neglected. Unless they've been there from the start and nobody ever noticed them (which I'm not sure would be better). I wish fundamental game-breaking bugs were dealt with quickly, no matter how old the module is, and actually the older it is the quicker you should fix it, since it is supposedly a fully released product that is supposed to be kept in a fully usable and enjoyable state at all times. Yes, I do consider the fundamental FM calculation errors to be game-breaking in a flight simulator...FM is pretty important. I hope ED fixes the big ones soon, at least.

Thanks guys, any help is welcome. FYI, I have gone through adding most of the bugs from page 1-5 in the AV-8B bugs section. There's still a lot to do, but we already have some stats that you can see in the various sheets of the file.