MonoGame/MonoGame

Game.Draw is never called when tracing the code with a debugger

Open

#6,067 opened on Nov 21, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (13,886 stars) (3,071 forks)batch import
Help Wanted

Description

The official XNA documentation says that Game.Update should not be called again when the code is running under a debugger. What happens now is that, when the code is traced with a debugger, MonoGame calls Game.Update repeatedly and never calls Game.Draw.

Contributor guide

Tech stack
csharp
Domain
developer experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C# knowledgeUnderstanding of debugger behaviorMonoGame game loop basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the game loop logic in the MonoGame source code, specifically how the debugger trace affects the Update and Draw calls. Look at the `Game` class's `Tick` or `Run` methods to understand why `Draw` is skipped under a debugger. Check if there are any existing comments or linked issues regarding this behavior.