Nuke Studio gets wrong slash in project path

When I launch Nuke Studio from SG Desktop, it pre-fills the path in the project settings with a regular Windows path like X:\projectfolder, which seems fine, but in the export window where you can see your output path preview, that backslash just appears as a “box” character like so–> X:□projectfolder

To fix this, I need to change the project setting to a forward slash like so–> X:/projectfolder, then everything works as expected.

Is there something I can do to fix the NS Toolkit engine to always use forward slashes, or do I need to fix this on the Nuke side? I’m using a distributed configuration with vanilla Toolkit integrations and a customized schema and templates.

This is Windows specific presumably.

Its a bug in the engine, I’ll try and make a pull request when I have some time.

Thanks for the report. It seems Nuke is using forward slashes since they fully migrated to Python 3. This caused some issues in the existing logic.

We are working on a PR to fix this. I’ll follow up to consider this use case in the regression testing.

1 Like

Thanks for the update Carlos! :slight_smile:

Sounds good!