We’re working on polishing Unity 5.4 beta right now. In order to get more feedback on real life use before we push anything to final, we opened it up and asked all Unity users to try it out. Now we’ve decided to sweeten the deal in order to get more of you in and catch all the edge cases.
If you submit, or have already submitted, a Unity 5.4 beta bug report with a solid description and an attached project, you’ll be automatically added to our Unity 5.4 Beta Sweepstakes. After we ship 5.4, one hundred of you will get a $100 Asset Store voucher from us as a thank you.
Haven’t found a bug yet, but there’s something i’d like for Unity to have. Something that’s basically a usability thing.
To be able to assign colors or small icons to the objects in the Hierarchy. So for example i can have a running figure icon to my Player object to be able to see if in the hierarchy with just a glance instead of typing it in or scrolling.
If you submit, or have already submitted, a Unity 5.4 beta bug report with a solid description and an attached project, you’ll be automatically added to our Unity 5.4 Beta Sweepstakes.
Quote from the Terms and Conditions: This “Sweepstakes” is sponsored by Unity Technologies ApS (“Unity”) and is open to individuals who submit a valid bug/regression report during the Sweepstakes period
So, will all my existing reports for 5.4 beta be counted? =)
I still think that the best approach would be to setup a space where we can upload our big projects so you can open them and see if it works out of the box.
I mean, ours is 30 gb in size. Having the chance to win 100$ of store credits is not worth taking half a day to pinpoint repros and build up a small and focused project.
So. Yeah. Bigger project support would be nice. 100$ bucks is only appealing to noobs.
The start date mentioned in the terms was March 15th which implies to me that any bug reports submitted once the 5.4 beta was made public (rather than when it was only for Pro licence/subscription holders) are the intended targets, but I could be wrong.
@alexandre-fiset
Actually it’s a good practice to pinpoint bugs and send a smaller repro if possible.
It will reduce time you need to upload report and it will dramatically reduce time QA needs to process your report (download time, project open time, pinpointing exact bug for the further processing).
And this is not about $100, it’s about less bugs for you in next versions.
Anyways, if you can’t pinpoint it, you’re still able to send them whole project via third-party cloud service.
@elbows Ah, see it now, thanks!
Sigh, I sent 8 reports before it became public =\
[quote=alexandre.fiset, post: 2613210, member: 96681]
I still think that the best approach would be to setup a space where we can upload our big projects so you can open them and see if it works out of the box.
[/quote]You’re in a much better position to judge that than we are, though. Sure, we can tell if the game is just crashing on launch, but for most more subtle issues, we don’t know what your project is supposed to be like. If a particle effect is missing, or your rag dolls aren’t collapsing the way you expect them to, etc… we’re not going to know that.
The exception is projects that have automated test suites, using something like the Unity Test Tools (or the new Editor Tests feature in 5.3), because in those cases “what it is supposed to be like” is encoded into the tests. If you’ve got automated tests for your project that are all passing in 5.3 but failing in 5.4, get in touch with me…
well its reproducible everytime for me now… 16 errors with…dot0 - dot16
Unable to load the icon: ‘sv_icon_dot0_pix16_gizmo’.
Note that either full project path should be used (with extension) or just the icon name if the icon is located in the following location: ‘Assets/Editor Default Resources/Icons/’ (without extension, since png is assumed)
UnityEditor.DockArea:OnGUI()
the scene always loads up in a 2d camera mode despite saving the scene with that off.
I just dunno if I can be bothered to clean up the project and upload… 100$ lottery… draws like that with no oversight… its not like its even streamed guys… probably better if bugs squashed from community bug submissions award the community with whatever chosen asset that should come in handy for most projects. The sooner we get to 5.4 final the sooner you can all get a ‘whatever’ asset so get those bug submissions in. Seems like better incentive for community as a whole and doesn’t need whole page on terms and conditions just for a draw.
fyi it would be really nice to disable asset folders/scripts from being compiled directly from project inspector… like editor stuff, instead of the chore of having to removing them from the project.
and having editor scripts that are missing actually show the last used filename of that missing script… because its really kinda dumb seeing missing script on a component. When I see no good reason why the meta data cannot keep track of last known filename.
Try this script in Editor folder, match it to your components.
using UnityEditor;
using UnityEngine;
using System.Collections.Generic;
[InitializeOnLoad]
class MyHierarchyIcons
{
static Texture2D texturePanel,textureInteraction,textureSlot;
static List<int> markedObjects;
static MyHierarchyIcons ()
{
// Init
texturePanel = AssetDatabase.LoadAssetAtPath ("Assets/art/icons/icon ui panel.psd", typeof(Texture2D)) as Texture2D;
textureInteraction = AssetDatabase.LoadAssetAtPath ("Assets/art/icons/icon ui interaction.psd", typeof(Texture2D)) as Texture2D;
textureSlot = AssetDatabase.LoadAssetAtPath ("Assets/art/icons/icon ui slot.psd", typeof(Texture2D)) as Texture2D;
EditorApplication.hierarchyWindowItemOnGUI += HierarchyItemCB;
}
static void HierarchyItemCB (int instanceID, Rect selectionRect)
{
// place the icoon to the right of the list:
Rect r = new Rect (selectionRect);
r.x = r.width +10;
r.width = 20;
GameObject go = EditorUtility.InstanceIDToObject (instanceID) as GameObject;
if (!go) return;
if (go.GetComponent<UIPanel>()) GUI.Label (r, texturePanel);
if (go.GetComponent<Interaction>()) GUI.Label (r, textureInteraction);
if (go.GetComponent<UIDragDropSlot>()) GUI.Label (r, textureSlot);
}
}
Yes, just to be clear, bugs that are reported via the forums (or via Twitter, or via email, or whatever else) are NOT eligible for the sweepstakes. Only bugs that you actually submit via the bug reporter, so they go into our Fogbugz database, are eligible.
@laurentlavigne Yeeeeeeesh. Something like that. Will try it ASAP, thx. @SimonDarksideJ Yeah my rant wasn’t for the sweepstakes. I thought to plug it in here as i did suggest it somewhere else but nothing happened. (I mean a comment or something).
I do agree that small “hidden” issues must be found and tackled. But in 5.4, I still can’t manage to have a build working without a crash, nor can I use Image Effects or the editor without big issues like corrupted game view. These are high level, showstopper issues. I didn’t have the same kind of experience in 5.3, 5.0 and even back at 4.5.
If we can’t build, there may be dozens of other critical issues we can’t find. The build crash is the one issue that we can’t reproduce in a smaller project and there’s nothing we can do with it as we do not have the time, nor the ressources to find repros for it. In this particular case, having the chance to win 100 bucks isn’t enough. Sending our whole 32 gb project each time is unacceptable (last time we tried, it took 7 hours to upload).
We are pro users and now the forums are flooded by hobbyist and noobs. I think it is good as a pool of testers for smaller projects, but IMO there is now a need for you to handle the bigger ones.
I do not think the problem is the amount of bug reports send, so if Unity wish for more bug reports then this is the correct move and happy about it. Although the more “same” reports they receive the busy there QA team will be with duplicates, and time wasted, while could be looking at more important performance issues.
I believe the final current problem is the priority of the bug reports. E.g. Android crash issue is high priority and blocks users from releasing. For the last 3 beta versions I have had crash issue with animations, so beta again useless to use on existing project. Yes maybe some of them cannot be fixed instantly but some comments on such critical issues would help. Do not want to believe that teams are working on the “edge case” bug when there is bugs stopping all developers from using or releasing there games.
Has UT considered some kind of interactive graphical representation of bugs, it would give developers a bit more of an idea of how far off the Beta’s are from completion?
E.g. Bugs over time, Bugs per Module, Bugs per Version, Bugs per Build, Time to Fix, Age of Bugs.
I reported some bugs about a year ago that were confirmed but still haven’t been fixed. You guys probably forgot about them so can I just submit them again and get credit?
