I regenerated the file, it doesn't show a diff in git so it seems the one on the Development branch is current. However it still doesn't seem to work. I'll look into Rider at some point and see if debugging is better in that.
I just checked again today, pulled down the latest development version, I have no local changes, but it still gets that error. I tried doing some debugging but all I can tell is it's an issue parsing the c7-static-map-save.json file. The debugger in VS code isn't the greatest but I'll see if I...
Turns out I was 147 commits behind the Development branch :lol: but even after pulling it still runs.
For tasks.json all it needs is the path to Godot.
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0"...
Finally got around to replacing my SSD, re-installed everything following the setup doc this guide and it's working great. This time I didn't need to do anything to the for `tasks.json`, the one that was automatically generated by the extension works just fine. Looking forward to getting back...
Yes, sorry I should've maybe used the full config file, I assumed people would generate the default launch.json file and add their own config. The one that's generated is like:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing...
That `\r` character was added automatically by the plugin when it generated the command. I couldn't see much of a difference between having it and not having it, so I just kept it. When I debug from VS Code it takes about 10 seconds to get to debugging, pretty much all that time is the build...
I'm not seeing a prompt like that, that happens when you run the debug configuration?
Do you see it happening before or after the build task?
Does it go away once the debugger launches?
What version of Godot studio are you using?
In that post you quoted I generated both files.
The launch.json was generated from the "Run and Debug" menu (like the github repo describes as option 2 in "Setup Debugging").
I don't exactly remember how I set up tasks.json, just that in the post you quoted there was an option for setting up a...
I was able to get debugging to work in VS Code using a very similar configuration to the JetBrains one shared by Quintillus.
First, make sure to install the C# and C# Tools for Godot extensions:
Then, you'll want a configuration in `tasks.json` to build the project before running it...
I usually like branching from the main repo because it's easier to track what people are doing in their branches, otherwise you have to look at their forked repo to see what they're up to. With lots of developers though it makes the main repo hard to read with lots of open branches and commits...
Oh nice, I already have VS Code set up on this machine and it's configured for pushing to Github with my SSH keys. I see people had issues getting that set up; I'd be happy to advise on that if they need help. As for free Git UI tools, I like Fork; I also liked GitKraken but I'm not sure if it's...
I'd be glad to join this project. I graduated in 2012 with a BS in computer science and have been coding professionally since then. I worked with C/C++ from 2012-2016, and since then I've worked mainly with C# and javascript. I'd be glad to offer some pointers for getting Git set up and links to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.