Why the QA has declared 2 bugs as None and closed, does they want to Sweeptake them for its own?

Hi,

I’m lite upset about the behavior of the QA. I posted a GUI and Reflection-Probe bug in the latest version 5.4.b16, but the QA has declared it as NONE. It’s a heavy and small one, but it is!.. and I have a proof send with images, and you all will recognize it if you see. In principal there is no announcement what bug “heaviness” is accepted for Sweeptake.
A bug is a bug!

This behavior reminds me of ppl overtake work from others for their own and try to make money in any way with.

And further why ppl are able to post bugs out of version 5.4.b17 but not the public?
This is an advantage against all other users can be post bugs out of 5.4.b16 only.

Kind regards , Q

1 Like

What were the bug numbers for the bugs you posted?

This issues are not listed in the tracker for any reason, but in fogbugz.
793215, 793222

The curious thinks is I received a mail today from a closed bug of 10.15.2015 number:
722613 = Hey, Thanks for reporting the issue…
Seems you bug tracking database has some issues too.

That bug just got fixed and you were informed about it as a reporter. Seems like working as intended to me.

QA is correct; neither of these are bugs. We have never had icons in the Lighting window (so they are not ‘missing’ as they were never there), and the artefacts in your second report are an expected limitation of the way reflection probes work.

The purpose of the sweepstakes is not to flood the QA team with reports; it’s to uncover problems we don’t know about that we need to fix in 5.4 before the release. If you report something that is by design, or that we already have a bug for… well, thanks for taking the time, but it doesn’t actually help us (or you - because let’s not forget, the reason we are doing all this is because we want to give you a quality release). So please keep looking!

1 Like
  1. You and the QA are not correct. Here is the proof. So please take care about of what you replying next here. Again as I already said, is a small (visual glitch) one. But a bug is a bug, and it’s not announced to taking into account by a heavy or small one.
    2620598--183983--53.jpg
    2620598--183984--54.jpg

…Pardon? You talk about flooding in the same sentences as you judge about my bug report, in the same time while you and you QA is wrong?

Why you wrote this? superpig, do you wana say that I’m not able decide what a bug is and what’s not?
You should take care about what you giving here to your best.

You should take a trainee in rethortics and “professional software releasing and distribution” if you want to get help from the community for your companies quality release… and talking from “does not help us and flooding” in the same sentence.

I will decide to invest any additional minute into bug reporting for you quality release.
I think there are enough other ppl can do.

Kind regards, Q

1 Like

Thank you, I miss-understood your email because it have a completely different bug header:

722613 Terrible lighting and normal map issues
722613 [CustomShader] Normal maps on a custom Shader Forge shaders look different in Editor vs Player

[quote=“Quatum1000, post:6, topic: 625917, username:Quatum1000”]

  1. You and the QA are not correct. Here is the proof. So please take care about of what you replying next here. Again as I already said, is a small (visual glitch) one. But a bug is a bug, and it’s not announced to taking into account by a heavy or small one.
    [/quote]Oh, you mean the foldout arrows. I thought (and so did QA) that you were talking about a lack of icons for each section similar to the per-component-type icons you get in the Inspector. I’ve asked QA to recheck the bug.
1 Like

Hi, other forum members are reporting your posts as inflammatory so please can you remain polite to Unity staff and other members of the community? Thanks.

Thank you.

Yes for sure, because I’m expecting the same. So lets end this here.

1 Like