SDK Debug View
Last updated
Last updated
The debug view can be added into your app's view hierarchy and help when debugging blipps. The view is intended to be full screen, so the logs can fill the screen.
On iOS you should add the BlipparSDKDebugView into your view hierarchy (through interface builder or programatically).
On Android you should add com.blippar.ar.android.sdk.DebugView to your view hierarchy (through XML or programatically).
The bottom of the debug view is tappable to slide the view up and down to reveal more options.
iOS and Android are largely similar, Android does not have the CPU overlay. It is intended to be added in an upcoming release. iOS screenshots have been used for reference, the style of Android is slightly different.
By default the view is unexpanded and looks something like below:
This means that there is nothing 'locked' to the sideload folder (i.e. NOT SET).
If you have sideloaded a blipp and it is currently locked against a marker (more on this below) then the view will look like below:
This means that the data is the sideload folder is 'locked' against the blipp with the address/hash of '31sun06nsq'. If you scan the blipp with this address then the scripts & data in the sideload folder will be used instead of the data downloaded from the server.
If you scan any other blipp then the server data is used for that blipp.
Sometimes you may want to lock against another blipp or marker. On tapping the 'Reset' button the view content will clear back to "NOT SET". The next blipp you scan will now be locked and you'll see it's hash/address instead. This blipp is now locked for use as for sideloading and all other markers will be using the server scripts & data.
Sideloading will only happen if you have enabled the debugSideload option in the SDK
In a blipp
When you scan a blipp this section changes to display some statistics about the blipp in the debug view.
These stats have various pieces of data in them:
FPS - frames per second
m - model count
drn - models drawn
v - number of vertices
T - number of resources
b - number of bound textures
ub - number of unbound textures
h - number of texture handles
Total Blipp memory in use in Mb
Anim - number of animations
Part - number of particle systems
When the view is expanded you see the following:
When the view is expanded several debug options are revealed.
Log is OFF/ON - toggles whether the debug log view is visible or not
More... - Reveals some more debug options
Wht - Change the debug log text to white. See below:
Red - Change the debug log text to red
Grn - Change the debug log text to green
Blk - Change the debug log text to black. Also changes the log background to white and makes the log text scrollable. While in this mode you cannot click on anything within the blipp since gestures will be used to scroll the log text. You need to put the log into one of the other modes to interact with the blipp once again.
Mesh Outline - Displays wireframes indicating the outline of meshes in the blipp
Hide Textures - Disable rendering of textures, useful when viewing bounding boxes or mesh outlines
Bounding Box - Displays the bounding boxes of meshes in the blipp
Hotspots - Displays hotspots active in the blipp (legacy feature)
CPU Display - A graph indicating CPU usage over time, note this value can go over 100% indicating multiple cores are being used
Extra Developer Options
Copy log to clipboard - Copies the content of the log view into the devices clipboard. Useful for emailing or pasting in elsewhere for further inspection
Clear log - Clear the logs on screen, useful when re-blipping
Clear blipp cache - Deletes cached blipp data from the server, forcing a redownload when scanning markers
Clear sideload cache - Deletes all the sideload data
