How to debug webGL

Hi there

I know some basic C# for game scripting purposes but anything else is beyond me, especially browser scripting.
I am wondering how I can go about actually debugging and viewing exceptions so that I can send them to my developer / post them here?

- Currently I have been building a project, and get told that exceptions have occurred, and I need to enable these in the build to be able to see what they are.
- I've rebuilt the exact same project with the only change being that exceptions are enabled, but the game isn't working properly (my camera movement isn't working)
- how can I get access to the exceptions to try and see what these are?
- I should note that if I build and run to a local server, the same issue is occurring

Any advice hugely appreciated,
T

 

the problem with that is, when you add exception handling, the build actually changes the code that's generated, adding things like try catches for null reference exceptions, you can potentially cause different problems just by turning it on, not to mention if it brings your game over the memory heap limit you set, or the memory limit of you browser process it will crash.

best bet, start ripping things out of your project one by one until it doesn't break any more, and cross your fingers for a better implementation in the future.

 

Yes thanks hyperhippo, - it seems like things got worse after enabling exceptions a while back oddly enough.

It would still be good to know how to actually access these errors?

I'm hoping for a lot more stability in 5.1!

 

I've had to resort mostly to adding lots and lots of Debug.Log statements, make sure you check your references for null before you run most of your code. You will need to be defensive and clean up after yourself in your classes and rely less on Unity and Monobehaviours to just manage your references for you and fail silently.

 

Ah so I misunderstood the point of enabling exceptions. I thought this meant that a console window would popup somewhere in the webGL frame or the browser that would list the exceptions that are occurring.

Is the point of 'enabling exceptions' in fact just that there is recognition that exceptions are occurring, but that the game will play anyway? ie. it wont stop and crash as previously?

Secondly would it help to build development builds, - I remember this use to give a console window in webplayer that would list errors

 

its a bit of both, enabling exceptions, actually alters your code so that the exceptions won't show up on a popup over top of your browser content. They should be output to the javascript console though.

 

If you're just talking about Debug.Log, the console is dependent on the browser. In Safari, for example, use "Show error console" in the Develop menu. It doesn't depend on making development builds.

--Eric

 

The console log should tell you the line number and character position in the code where the exception was thrown. You can inspect the code in a text editor and often find the exception type and info string from there, even in builds where exceptions are disabled. It is a shame the exception info string isn't printed out in the standard error message, it should be possible to do that without the overhead and effect on code generation of enabling exception traps.

You can also use the REPL to inspect variables, look in "memory", and generally figure out what might have gone wrong, and you can edit the generated JavaScript to add additional diagnostics.

It would help a lot if it were possible to convert JavaScript function names into the original c# names. I guess this is mostly an IL2CPP thing.

 

In firefox hitting f12 brings up a console window that lets you debug, cool