WHEN to criticise unity and when to demand fixes / features.

News & General Discussion
1

IMHO:

  1. When unity has just deployed an update release with tonnes of new features, it is a really bad idea to:
    a) whine about it not being in free
    b) whine your bug wasn’t fixed*
    c) say ~ unity are all assholes and they never listen to me (abuse)

*The right thing to do is clearly make repro projects and submit them via the bug reporter tool. Any issue, no matter how small actually stands MORE chance of being fixed at this time than any other time due to the fact it’s in wide release. It’s now that you can get unity to quickly fix your bugs. But to do this you need gentle but firm pressure, some reminders and lots of clear bug reports submitted using the bug report tool :slight_smile:

Do try to submit your project - don’t worry - unity won’t steal it. I know it’s scary, but they won’t.

  1. After things seem relatively stable, it is a good idea to start your criticisms if you have any. The worst possible time to critique a development company is when they’re struggling to fix bugs. Ever heard of the phrase kicking a man when he’s down? well it applies here, you won’t get anything productive from it.

They are a bunch of human beings, picking the moment when to criticise unity and when to help them with bug reports is wise since every company thrives on proper criticism and feedback from their users - just I honestly doubt a lot of it will be useful during intense bugfixing phases because you may come across as just whining about a bug.

Personally I’m waiting for the mobile performance to get fixed up a little and then I’ll be whining again :slight_smile:

2

I’ve never understood why so many new developers are scared of other new developers stealing their projects. They have plenty of their own brainchild ideas that they want to see grow into finished products, and would much rather work on those than stealing someone else’s…In addition, I don’t think the Unity people have any need to steal our work.

3

You also should not be embarrassed about the state of your code. Even if it is hundreds of lines of static variables, because:

a) you’re just a bug report number
b) your success is measured not by your code or media, but by results in the appstore, steam store, or just as a hobbyist having fun.

So just submit the projects already to ensure we all have a stable unity. Be sure to take note of the case number so if you do find a thread with similar problems that looks unresolved, you can pm a developer who answered that thread (or just leave a reply) with your case number.

So we can group problems together and present it easier to unity.

4

If your a free user like me , its hard to justify layin it on thick in any form. After all, its givin for free, how can you complain about free… O.o…

But people will and do…

5

You should try to create the simplest test case possible before submitting. A lot of the ‘bugs’ that I intended to submit to unity turned out not be real bugs when I was narrowing down the test case. Your full project might be too much to see what’s going on even if there is indeed a unity bug in it.

6

Its not really complaining if its a bug, and you’re submitting it properly with a buggy project. Most bugs on Indie also affect Pro. When you submit a concise reproduction case, you’re helping them, not hurting them.

7

I’ve already given away about 100 copies of my project as I’m finishing it, nobody has stolen it yet. They try it, give some feedback and that’s that.

8

This is very important.
Don’t just jam your entire project into a ticket, and expect them to get it working. They don’t know your code, they don’t know your dependencies, and with a full project you create a lot of noise to filter out the real bug. Always try to spend at least a few hours making an empty project and reproduce the bug with the minimal amount of extra noise. This makes it easier for Unity to diagnose and fix, and therefore more likely that your bug will be fixed. Only if smaller projects do not reproduce the bug in any way do you submit your entire project, and even then try to strip out unnecessary parts. A little time on your end, helps a lot on their end, which is better for everybody.

9

Precisely. I’ve got a radial gauge gadget (user interface component) being prepared for the Asset Store, and a Snake Game tutorial info product that are out in the wild, probably a few dozen copies of each out there being tested, critiqued, and played with. I have found that it is usually only lazy people that have any interest in stealing your stuff, because they are too lazy to create their own, and then do precisely nothing with it.

10

Err… Hippo? Do we need to sit down and review your code?

On this topic:

For the first time in my short pathetic life, U3D fixed a bug of mine. Interesting to note that U3D only noticed it because:

  1. It was in the forums.
  2. Others confirmed the existence of the bug.
  3. It was a show stopping bug with the latest webplayer.

So while I do recommend sending in bug reports - also report them on the forums [especially if someone else has reported it - that way you can support the thread].

No guarantees this will work - but it’s something to try!

11

I shall whine all i want thank you verry much :slight_smile: i paid $400 for an engine that i can play real time, now they make that not possible because i get 1-2FPS, that is a bug ill bitch as much as i can about.

I trust unity… but sometimes you have assets that are not able to be given(legal issues) so no, in somecases this is not possible.

12

It’s not as if you’re selling your project though, is it? You’re just letting them check through it.

13

Oh this is no secret or anything. My code is terrible. It works perfectly well though! :slight_smile:

14

Not in my case(i have no 3rd party assets).

But still im quite sure if it said that it is not redistributable you cant just give it away… just saying Unity are trust worthy is not enough, i think that it is classed as piracy and breaks the terms of use.

15

LOL.

If you really do have assets that you CANNOT show unity - then it’s your responsibility to build an appropriate replacement scene that demonstrates the fault without break obligations.

If you cannot do this, then that is YOUR failure.

Though my guess would be you’re simply jumping the gun - it was when you used ‘piracy’ instead of ‘extremely strict NDA’.

16

if i could make the asset my self i shall not buy it? so it is not an possible reason(for me)

If buying a movie and sending it all over the internet is piracy so is this.

17

Remember sharing is caring :smile:
But back to topic, I agree with the “hippo”, now is not the time to bitch.
Now is the time to send in nice little “repro-cases” that makes it easy for them to reproduce the bugs and fix them.

At the end of the day, if nobody sends in bugs (description on how to reproduce + tiny project) than they have no way of fixing them.
So it’s our job to help them help us.

*edit: and then we can get back to bitching :stuck_out_tongue:

18

Buying a movie and ‘sending it’ over the internet is not inherently piracy.

Given that you’re unable to provide a replacement, and unwilling to look deeply into the legal issues… have you considered asking your Li censor to either look into the issue or grant you the rights to allow U3D to look into it?

I know that would prevent your apparently enjoyable trolling, but it might be effective.

19

It isent a problem i have, but im not trolling just saying that people need to relise this problem before getting angry about not sending bug reports.

20

No, people need to realize that without giving bug reports they cannot expect U3D to take actions in regards to their bugs.