[Crash] GM Project folder not being the Root folder causing issues

[tinkerer-red]

I'm currently working on Emobble where the repo structure is:

<ROOT>
> Emobble (GM Project folder)
> Tools (Python code)

I need to structure the code this way because GM IDE has many problems when having several thousand files anywhere in the gm project folder. But also due to a personal preference. However VSCode extensions keep crashing when ever Stitch is enabled and attempting to read the file paths.

Ideally in this situation if i went to the stitch nav tab it would just use the only GM project file, but in the event of multiple projects under the same root folder (possibly client vs server, or an asymmetric game) then Stitch could provide a list of the projects as if they were folders, which then expands out into their respective IDE folder structure.

But the main issue is that i must open my GM Project in GM IDE, while i open the python tools in VS Code. meaning navigation between the two is extremely annoying

[adam-coster]

When Stitch starts it looks for yyp files using VSCode glob APIs. These APIs take into account your general VSCode settings for what is shown to you, so anything you set to be ignored in your file explorer settings get skipped. There would need to be a truly enormous number of files for Stitch to crash the editor, which could come from things like caches or your .git folder.

So the first thing to do would be to see if there are any patterns you can generally ignore in VSCode (which will make it more performant overall).

Stitch does do what you're suggesting: if it finds one project it loads it, and if it finds multiple it opens up a selector for you to choose one. Stitch only loads one project at a time.

So your crash is from something else. Either because it has so many files to search through to find your projects (possible, but I wouldn't expect that to crash) or something else entirely. I'd need more information to be able to guess.

If you can get any Stitch logs from VSCode's Output panel before it crashes that would help a lot. I'm not sure if there's a way to find logs from older sessions.

Otherwise, what operating system are you using, are you using VSCode Insiders or regular, and is your VSCode up to date?