I have a game running in the Unity web player which runs totaly fine in a web browser.
A client wants to run the game in an application with an embedded web browser. The game runs but something very strange happens.
Mouse clicks over GUI elements work fine but not seemingly over Colliders. The even stranger thing is that OnMouseOver works fine in the embedded web player.
If the game is taken to full screen then it also works fine so it isn’t likely to be a scripting issue.
Are there any known issues or any indicators why this might be?
All the colliders - but they are from the same asset ( a bunch of checkers in a Backgammon game). It may be worth creating a little test project with some colliders and mouse clicks.
Again, a test project will probably help. I’ll work on this. Although the client did tell me that she tested some other unity stuff in the application, from other developers, and they stop working also.
OK, this is the tricky part. The application was written in Delphi and it has an embedded browser in it. It is a Win32 application so that rules OS X out. I am guessing that it uses an Internet Explorer OCX/ActiveX control. I am also guessing that this will implement the current version of IE installed on the PC. What I did do was build a small .Net application with an embedded WebControl in it and it worked fine so this fudges it even more.
I am using Unity 2.1.
I really do appreciate the post Tom. I had to make sure that nobody else had the same issue before I start firefighting.
There’s nothing in the logs to indicate an exception - the stuff I log is identical to what is logged when the game runs normally. Its very odd!!!
I am convinced that it is the Delphi application that is at fault (Not Unity) but I think the best thing is to create a small test project with some colliders in it and see how it gets on (thanks for this suggestion). It might be worth expanding the search to Delphi/ActiveX controls for odd behaviour?!?!?!
One of my biggest problems is that the Delphi developer will not speak to me. I asked a couple of basic questions about his app and he told me to go screw myself in the first email! What happened to the cup of human kindness eh?
As always, IF I find a solution, I will post it here!
I think that your next immediate step is to test this in a browser (not a Delphi) app and see how it behaves. If the Delphi app is causing this issue then please log a bug on that so we can try to sort it out. A sample application included with your report (zip up your project, that app and any other source) will go a long way to helping us debug/fix it. Of course that assumes you can sort out some sort of better relationship with that person…
Yeah, it has been tested in a browser (many in fact, IE 6 7, Safari, Google Chrome) and it works fine in them all.
The project should be finally completed today then I can try and help the client sort this out (although the Delphi app wasn’t in the project scope - I might just take the money and run!!! :twisted: )