Closed GoogleCodeExporter closed 9 years ago
Mhmm I'm traveling these days, so I will be able to check this only in a couple
more days. Weird though. Are you by any chance using Unity 4.1.1? It contained
a serious bug which generated problems with almost all external libraries, and
which has been solved in Unity 4.1.2
Original comment by daniele....@gmail.com
on 21 Apr 2013 at 12:42
I'm having the same issue with the visual editor. I'm using the latest Unity
version: 4.1.2f1 on Mac OSX 10.8
I think this is a high priority bug. Let me know if I can help in any way.
Original comment by joe.fr...@gmail.com
on 21 Apr 2013 at 11:44
Attachments:
No I am using Unity Pro 4.1.2f1 on Windows7.
Additional information:
It worked at first for one of my collegues (same Unity version, Windows8). And
a couple hours later (after a restart and working on something not-tweeny) she
got the same error. So it might be a progressive error. Something that changes
on Unity restart maybe?
Original comment by tino.hol...@kaasahealth.com
on 22 Apr 2013 at 7:49
Yes, this is consistent with my experience as well. I first installed it in a
blank project and it worked fine. When I tried to integrate it in larger
project it wouldn't work.
—
Sent from Mailbox for iPhone
Original comment by joe.fr...@gmail.com
on 22 Apr 2013 at 12:08
I can't seem to be able to replicate it. But maybe because I'm using a later
version of HOUnityEditor. Could you try to replace the HOUnityEditor folder
that comes with the visual editor, with the one attached to this message, and
then let me know?
Original comment by daniele....@gmail.com
on 24 Apr 2013 at 9:24
Attachments:
My collegue tried it yesterday but has had the same problems. But she mentioned
that the UI is now different in this version. Its no longer floating but in the
inspector panel. So maybe she did something different? But even with the
different UI - when she clicks on the tween property like "position" the window
crashes just as before. The Editor becomes unusable and spamming error messages.
Original comment by tino.hol...@kaasahealth.com
on 25 Apr 2013 at 6:20
This is really puzzling me, and I couldn't replicate the issue anywhere. I
understand what a MethodAccessException is, but there's no reason it should be
generated by that part of HOTween Editor's GUI.
I'm attaching a complete package to this message. It contains HOTween, the
Visual Editor, and all the related scripts. Could you try to delete everything
related to HOTween from your project (libraries and visual editor), and then
clean-import this package? Then let me know if you still have this error. If
you still do, can you try to create a new Unity project with this package and
see if you still manage to replicate the issue? If so, can you tell me the
exact steps you did to replicate it? Or even better, make a screencast?
Also, in case you still have this issue with your old projects and this new
package, could you tell me what other Unity plugins/assets you're using? Maybe
there's a weird conflict somewhere.
Original comment by daniele....@gmail.com
on 25 Apr 2013 at 5:19
Attachments:
I have created a screencast. I have tested it inside my live project.
Screencast: http://screenr.com/hgi7
Screencast shows:
1. Start with no HOTween. (Exceptions because of Holoville namespace missing)
2. Import your package
3. Exceptions go away (Namespace now ok)
4. Tweening works (code tweens)
5. Add editor/manager
6. Add tweenitem
7. Add tweenprop
8. Kaboom
The errors stop when I delete the manager from hierarchy and the gui recovers
and shows the standard "add manager" button again. Same as before.
Original comment by tino.hol...@kaasahealth.com
on 26 Apr 2013 at 10:06
I'm sorry if I'm continuining being superslow, and thanks for the video. I
checked it out, and I still can't replicate it, even if I followed your same
procedure. But tomorrow I'll try again, using 2D Toolkit's anchors just in case.
In the meantime, anyone tried to replicate it by starting from a new project
(with the latest files I attached)? And for those who didn't, do you remember
which version of HOTweenEditor/HOTween you were using before this started to
happen?
Original comment by daniele....@gmail.com
on 30 Apr 2013 at 6:25
I made some changes to the visual editor which should have fixed this glitch.
If it still happens with the latest version, let me know.
Original comment by daniele....@gmail.com
on 11 Dec 2013 at 12:16
Original issue reported on code.google.com by
tino.hol...@kaasahealth.com
on 15 Apr 2013 at 11:00Attachments: