Have you had a go with the new Unity 4.6 with UI? What’s your opinions?
Personally I think you CAN use it to make apps but if it works on one system like Windows you can’t rely on it to also work on other platforms like Metro or Android.
I don’t think it’s stable or tested enough to rely on. I think maybe in a few more months after more testing then it would be OK to upgrade. But now I think people shouldn’t upgrade from 4.5 and just use the UI for testing.
I’ve submitted several bugs for the Unity 4.6 yes. Particularly for building Windows 8 apps and general crashes. But this is just a general discussion. Different people use Unity for different things so while it may be great for some people for others it might not be good at all for their needs. After all probably all software has at least one bug but if 99.99% of people never hit that bug then it’s OK.
I haven’t had any trouble with it (that I did not directly cause myself) on Windows 8. And the version I’ve been using is one of the later Beta versions, not the official release. I love the UI system – I find it very easy to use. The main thing I don’t particularly care for is setting up character rects for custom fonts. It is counter-intuitive in my opinion and, even once you understand how it works, it is still extremely tedious.
I haven’t encountered any bugs, although I noticed that some of the tool tips in the input settings are reversed (tool tips saying “positive direction” when the title and functionality are “negative direction”).
I’m curious to know what problems you’ve encountered that have led you to feel that the program is currently unstable.
Well when using a text input in a Windows 8 app when I press backspace it gives an error. I can’t position the cursor in the text with mouse or even with arrow keys. It only puts letters at the end. The on-screen keyboard only lets me type in about 4 letters before freezing. The on screen keyboard won’t close when clicking off the text input. Can’t select text in a text input. To name but a few issues!
Here is a screenshot of the backspace bug to prove it:
Plus I’ve had several crashes of Unity sometimes due to a missing reference or switching between projects.
Also I get these errors when compiling for WIndows 8:
First-chance exception at 0x76F82F71 (KernelBase.dll) in Template.exe: 0x40080201: WinRT originate error (parameters: 0x80070490, 0x00000064, 0x0496F24C).
First-chance exception at 0x76F82F71 (KernelBase.dll) in Template.exe: 0x40080202: WinRT transform error (parameters: 0x80070490, 0x00000000, 0x0000001D, 0x0496F680).
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
The thread 0x1c34 has exited with code 0 (0x0).
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x0D21BE50.
The thread 0xfcc has exited with code 0 (0x0).
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
First-chance exception at 0x76F82F71 in Template.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
(although it still compiles but it is worrying!)
Also the sliders and scrollbars don’t work with touch and if you do try you get this error:
(I think this is a problem if you start using a mouse and then change to touch).
The buttons and panels seem to be fine though! So if you just use those you won’t have any issues.
Ah. I can certainly see how that would be frustrating. I suppose your statements about different uses are very relevant in this case. I have not used text input fields, so of course I would not have encountered this problem (although it could be the input fields in conjunction with other things unique to your project). I have deleted, renamed, or removed things and forgotten to update references to them, and I have accidentally omitted necessary lines of code, but none of these have resulted in crashes, at least for me. I’ve been lucky, I guess. I was expecting it to be extremely glitchy (since I downloaded it while it was in beta), but so far it has mostly been smooth-sailing for me.
On the webplayer with a touchscreen, the image element doesn’t recognise a pointer up custom event if you use your finger instead of a mouse.
This is quite a serious problem because it means if using touch the webplayer can take hold of your cursor because it thinks you’re still dragging and so you can’t click on the browser buttons! This has happened!
If you think it’s a bug please report it. Best case with a certain way to reproduce it.
Other than than I can say personally that I found 4.6 to be pretty stable and even during the Beta phase pretty much production ready. In a complex software like Unity there will always be bugs. That’s what the report button is for.
Yep, I’m reporting it now. I’m assuming it’s a bug. But for all I know you have to do something special to enable touch on web apps. Maybe you can’t.
Edit: While I was making an example project for this bug Unity crashed again due to trying to set the text on a text object missing a reference. Does this happen to anyone else? Trying myText.GetComponent<UnityEngine.UI.Text>().text=“HELLO”; when you haven’t assigned myText crashes? (That is what I meant by unstable!)
I reported a very similar bug & the support personnel told me to ask for help in the forums which I already know ain’t going nowhere as I’ve seen yoonitee’s complaints about Windows Store SDK already but I went ahead and posted a long summary in the Windows forum anyway.
For what I can tell and I’m just guessing from the disassembly VS 2013 creates, the bug has to do with running a ‘non-certified’ Windows Store App trying to run, that being my app. We have a chicken & egg situation here maybe?
I’ve created a ‘MetroTestCertificate.pfx’ but it didn’t help and besides Unity was already creating one on it’s own anyway. Is there a way for me to tell Windows 8.1 that yes, it can run ‘Windows Store’ apps that use self-signed test certificates if that is the problem?
And that is a big if. The project, which features none of my own code but Unity’s and a very popular small code framework asset along with maybe a dozen low-poly meshes all bought from the asset store and easily integrated and even released to Goggle Play and the Amazon Store very easily just won’t come together for the Windows Store. I also had another Windows Store problem last December & January with another Asset Store framework - it simply wouldn’t compile & run on my PC tablet so I said well I’ll use Android until the fix Windows Store except they never did. And those bug filings were basically ignored from a year ago until as we used to call it, they became irrelevant as they were ‘overcome by events’.
In another words, they are tossing out so much old code and creating new code that bugs quickly become irrelevant. Apparently after a year that is even more the case with Windows Store and Windows Phone than ever.
I’ve done some more research and my problem seems now likely to stem from a Windows 8.1 security issue that has messed up my account access to some SW/HW resources…
I’ve had a KB cause one program to stop working in the past so it might be somehow similar…
Of course we are talking hundreds of thousands of files with millions of security descriptors and a registry that’s hundreds of megabytes in size or maybe even gigabytes in size nowadays and I’m supposed to troubleshoot this obscure Windows security bug…
