Deleted due to too many personal attacks from idiots.
Nice meme, but I’ve seen better versions of the gorilla warfare copypasta here. I rate it 7/10, and 4/10 for the trollbait of Unity being the worst ever. You can do better, I believe in you!
You should mention which versions of Unity you’ve used for your build-attempts. It sounds to me like it might be a bug. If you’re using 3rd party assets I would recommend starting a new project and trying to build for your target plattform, adding the 3rd party assets one by one to see when the error starts to show up. I’ve had problems with javascript related stuff and removing every single js script from thirdparty assets fixed it, though that likely isn’t your problem I guess.
Have you tried submitting your project as a bugreport? 100% reproducable non-verbose build errors sound like stuff that needs to be fixed. Please submit a bugreport.
I’m sure - being the veteran that you are - you’ve used version control before stripping down your project to troubleshoot, so what’s all the whining about your game being ruined about? I don’t see this helping you fix the problem, it’ll only derail the conversation.
3 Likes
What the hell are you talking about? Talk some sense or dont bother.
Sorry if I sound stupid, but have you tried to contact one of the guys from Unity DIRECTLY? You may have a chance.
What happens when you create a new project and try to build it? Could be a problem with your installation. I’ve never encountered anything like this issue by the way. Can’t really help I guess since you haven’t provided anything for anyone to go on. Even at what point in the build process it happens, what target platform, etc, would be more helpful than nothing.
I don’t know, but here take a pitchfork.
1 Like
It logs errors and also displays them in the Console window. Do you have that window open? From memory it’s closed by default, and you only get the last line of the output shown in the status bar at the bottom of the window.
For code errors it gives you the compile output straight from the compiler, so it’s just like you’d expect from any other programming environment, right down to the line where it thinks it found the error and the ability to double-click it to navigate there in your code editor. I have indeed had a few cases where an error is flagged with little or no hint to track it down, but that would have happened maybe half a dozen times in nearly a decade of using the tool day-to-day.
Non-code errors are a bit different. It’s common enough to get an error like (paraphrasing) “the script for this Component is missing” and no assistance in finding what GameObject emitted that. Unity will tell you that if it can, but often the object in question isn’t there any more which means there’s nothing for it to point you at.
As for calling Unity “designed for failure”… people have been succeeding with it pretty reliably for quite some time. No tool is perfect, but in this day and age I think there’s rarely merit in blaming our tools for our failures.
5 Likes
Yeah no idea why I asked this is exactly what I expected. End of thread.
So… do you have the Console window open? Have you looked at the Editor log? Can you post the Editor log so that we have some information we can potentially use to help?
Dude, if after calling Unity being “set up for failure” and “the worst development environment ever” you can’t even take a light-hearted joke, and reply to zero of the honest questions and suggestions that I’ve made, then I think I really shouldn’t bother trying to help you.
But please, at least submit it as a bug report to Unity, from what you described it really sounds like this isn’t intended behaviour at all, and they might be able to fix it for good on their end.
He said it’s not in the editor log.
4 Likes
Ahh. I must have missed that as I was, admittedly, skipping large chunks of the OP that seemed to just be Unity-bashing.
This thread was regarding the issues in this thread?:
If you pointed to that thread in your post here, people would have had a better idea of what you were referring to in this thread.
It is not the first time that impossible-to-troubleshoot error messages appear in the console. So it is possible to relate to the frustration. (i.e. the infamous “Odd tag in cleanup!” error)
Aha! If it is that then I’m pretty sure I’ve had it before. What platform are you trying to build for? What in general can you tell us other than that it’s not working?
I have a feeling I fixed it exactly per @Martin_H 's suggestion of stripping things out one at a time until the errors disappear. Alternatively, in my case it could have been version mismatches between Unity’s Android tool chain and the external Android tools I had installed. In particular I remember some issue arising from an incompatibility with a specific JDK version, and that downgrading a version fixed it. However, not sure if that was this specific issue.
Yeah, but it’s not about this guy. If we can figure out what it is then it’s better for everyone.
3 Likes
If you’ve been a developer for so long, you should know how to form a proper error report and how to ask for help. You never say what your build targets are, you never mention what assets you might be using, you never mention what version of Unity you’re on, you never mention if you updated your project to a new version of Unity, all you say is “it doesn’t show up in the error log” and say how Unity is literally the worst thing ever made, which is a laughable statement for somebody who’s been developing as long as you have. You then go on to call everyone idiots.
Like, seriously, you could not have done more wrong.
6 Likes
You are going to have to be a lot more specific, just saying you have errors isn’t going to help. File a bug report, check your logs, and use version control to avoid “lost work”. If you are having technical issues, please post in the correct forums, sounds like android is your best bet, and be clear and specifc.
2 Likes