Skip to content

Troubleshooting

VukeFN edited this page Aug 15, 2026 · 9 revisions

Troubleshooting

Common issues and solutions for Verse Auto Imports.

Table of Contents


Extension Not Working

If the extension doesn't seem to be doing anything:

1. Check File Type

Ensure you're working with .verse files. The extension only activates for Verse language files.

2. Check Language Support

Make sure Verse language support is enabled in VS Code. You should see "Verse" in the bottom-right language indicator when editing a .verse file.

3. Check Output Logs

View extension logs for error messages:

  1. Open View > Output
  2. Select Verse Auto Imports from the dropdown (shows important messages)
  3. Or select Verse Auto Imports - Debug for detailed debug logs

4. Check Extension Status

Look for "Verse Auto Imports" in the VS Code status bar (bottom). Click it to open the Status Bar Menu and verify the extension is enabled.

5. Reload Window

Try reloading VS Code:

  • Press Ctrl+Shift+P
  • Type "Reload Window"
  • Press Enter

6. Check Whether Auto Import Is Switched Off

Open the status bar menu and look at the Auto Import row. Snoozed (M:SS) means a snooze is counting down and will end on its own, or immediately if you reload the window.

If the row reads as off entirely, check verseAutoImports.general.autoImport in your user settings. Versions before 0.9.0 wrote that setting to false when you snoozed, and a reload or crash during the snooze could leave it off permanently. Re-enable Auto Import from the status bar menu once and it will stay on — the snooze no longer touches your settings.


Wrong Imports Being Suggested

If the extension suggests incorrect imports:

Configure Ambiguous Imports

For classes that exist in multiple modules, specify your preferred module:

{
    "verseAutoImports.behavior.ambiguousImports": {
        "vector3": "/UnrealEngine.com/Temporary/SpatialMath",
        "vector2": "/UnrealEngine.com/Temporary/SpatialMath",
        "rotation": "/UnrealEngine.com/Temporary/SpatialMath"
    }
}

Use Quick Fix Mode

If auto-import picks the wrong option, switch to manual quick fix mode:

{
    "verseAutoImports.general.autoImport": false
}

Then use Ctrl+. on errors to manually choose the correct import.

Adjust Multi-Option Strategy

Change how the extension handles multiple import options:

{
    "verseAutoImports.behavior.multiOptionStrategy": "quickfix"
}

Options:

  • "quickfix" - Always show a menu to choose (recommended)
  • "auto_shortest" - Auto-select the shortest path
  • "auto_first" - Auto-select the first option
  • "disabled" - Don't handle multi-option scenarios

Path Conversion Issues

How conversion resolves modules is described on the Path Conversion page.

Module Not Found

If "Use absolute path" doesn't find your module:

  1. Ensure the module exists in your project's Content/ folder
  2. Check that your .uefnproject file is properly configured

CodeLens Not Showing

If the path conversion options don't appear:

  1. Check that CodeLens is enabled:
{
    "verseAutoImports.pathConversion.enableCodeLens": true
}
  1. Try setting visibility to "always":
{
    "verseAutoImports.pathConversion.codeLensVisibility": "always"
}

Cache Issues

What the cache holds and how it invalidates is described on the Path Tree Caching page.

Stale Cache

If import suggestions seem outdated:

  1. Rebuild the cache manually:

    • Press Ctrl+Shift+P
    • Search for "Verse Auto Imports: Rebuild Project Path Cache"
    • Wait for the rebuild to complete
  2. Check cache status:

    • Press Ctrl+Shift+P
    • Search for "Verse Auto Imports: Show Cache Status"
    • Verify the cache is up to date
  3. Start cold if the cache looks corrupt:

    • Press Ctrl+Shift+P
    • Search for "Verse Auto Imports: Clear Project Path Cache"
    • This wipes both the in-memory cache and its persisted copy without rebuilding, so the next lookup starts from scratch

Cache Not Updating

If changes to .verse files aren't reflected:

  1. Check that caching is enabled:
{
    "verseAutoImports.cache.enableProjectCache": true
}
  1. Try adjusting the watcher debounce delay:
{
    "verseAutoImports.cache.watcherDebounceMs": 1000
}
  1. Manually rebuild the cache as described above

Slow Startup

If VS Code starts slowly:

  1. Disable auto-rebuild on startup:
{
    "verseAutoImports.cache.autoRebuildOnStartup": false
}

The cache will use persisted data from the previous session and update incrementally as you work.


Viewing Logs

The extension provides two output channels for debugging:

User Channel (Important Messages)

Shows INFO, WARN, and ERROR level messages:

  1. View > Output
  2. Select Verse Auto Imports

Debug Channel (All Details)

Shows all messages including TRACE and DEBUG:

  1. View > Output
  2. Select Verse Auto Imports - Debug

Export Logs

To share logs when reporting issues:

  1. Click "Verse Auto Imports" in the status bar
  2. Go to Utilities
  3. Click Export Debug Logs

When a command fails — a toggle, either debug-capture command, or Rebuild Path Cache — the failure is recorded in the log, so an export taken after the problem holds the failure you are reporting.


Getting Help

Still having issues?

When reporting issues, please include:

  • VS Code version
  • Extension version
  • Relevant log output
  • Steps to reproduce the problem

Clone this wiki locally