Inconsistent Debug.Log Output

Unity Development
1

Hi, I’m currently experiencing inconsistent behavior with Debug.Log messages when testing on Magic Leap 2 using Magic Leap Hub 3. Here are the relevant environment details:

  • Unity Editor version: 2022.3.22f1
  • Magic Leap 2 OS version: 1.12.0
  • Magic Leap SDK version: 1.12.0
  • Host OS: Windows

Issue Description:

I’m using Debug.Log statements throughout my Unity project for debugging purposes. All my logs are consistently prefixed with [VisualTest], such as:

Debug.Log("[VisualTest] Start");

However, I’m observing the following inconsistent behavior:

  1. Some logs appear while others do not, even when placed at the very beginning of the Start() function or at the top of button callbacks.
  2. The scene itself works as expected—UI responds, logic executes—but log messages from active code paths are missing.
  3. I filtered log output in Magic Leap Hub 3 using message content (e.g., messages containing [VisualTest]) and also attempted filtering by package name—but:
  • Filtering by package name yields no results.
  • The log entries show the app’s package with PID, but not the actual package name I set in Unity.

Questions:

  • Is this a known issue in Magic Leap OS 1.12.0 or the Hub 3 logging system?
  • Is there a more reliable way to filter or ensure logs consistently appear (e.g., toggling developer logging settings)?
  • How can I confirm which package name Magic Leap Hub recognizes for log filtering?

Any help or recommendations for more reliable debugging would be greatly appreciated.

Thanks!

2

Problem solved after changing connection methods from USB-C cable to WIFI

3

I can also recommend using the Android Logcat package for looking at the logs. There you can use custom Regex filters.

1 Like