question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VSCode doesn't start up Godot and attaches

See original GitHub issue

When I F5 or run the game, nothing happens. I can stop the game and pause but there’s no game screen, it doesn’t seem like it builds. No errors show up anywhere (do I need to enable a setting to see them?). I think the godot editor settings is setup fine since the language server works fine.

How can I troubleshoot this?

I’ve followed everything in the tutorial, so I’m not sure what could be wrong.

I’m on a Mac OSX Sierra 10.12.6.

Here’s my config file:

{
	"folders": [
		{
			"path": ".."
		}
	],
	"settings": {},
	"launch": {
		"version": "0.2.0",
		"configurations": [

			{
				"name": "Godot",
				"type": "godot",
				"request": "launch",
				"project": "/Users/lucrecious/dev/gear_game",
				"port": 6007,
				"address": "127.0.0.1",
				"launch_game_instance": true,
				"launch_scene": false
			}
		]
	}
}

I’ve used both the absolute file location and ${workspace} and both should have worked.

Here’s my extension settings: image

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:16 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
Razoric480commented, Jun 22, 2020

Eventually, yeah; the changes are folded in my latest pull request.

1reaction
Lucreciouscommented, Oct 25, 2020

I agree.

I actually don’t use VSCode for editing anymore because the Godot plugin feels incomplete. You can’t use it for plugins yet, new class_names are not included in the auto-complete until you reload the script in Godot, there are errors whenever you switch between VSCode and Godot, the auto-complete in VSCode is worse than the one in Godot’s editor, and the there’s a lot of little issues with syntax coloring. These issues really bother me and it discourages me from using VSCode for GDScript.

I think the maintainer needs to work both with Godot and the plugin itself for it to work properly, otherwise you’ll get issues like the onea above. I think it’s worth considering hard-coded VSCode logic in Godot or something, and then general logic (like how we have now) for the rest.

Read more comments on GitHub >

github_iconTop Results From Across the Web

visual studio code - Godot vscode doesnt open - Stack Overflow
It's either a windows error, or what you're code is trying to do is not possible on the godot platform. Hope this helps!...
Read more >
Opening a scene opens Visual Studio Code and focuses it ...
When you open up a scene, any attached scripts are opened in the editor. Since you are using an external editor, Visual Studio...
Read more >
Attach Visual Studio (not VS Code) to debug? : r/godot - Reddit
I just started experimenting with Godot, and I'm trying to figure out how (or if) I can attach Visual Studio to it to...
Read more >
Godot Devlog: Setting up VSCode for editing, building, and ...
These two files define the tasks in vscode that build the engine, and the targets that launch the executable and attach a debugger...
Read more >
The Ultimate Godot C# Setup Guide - giulianob
Start up Godot and create a new project or open your existing project. There are a few settings we should change to work...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found