| Category | Scripting |
| Created | 29.05.2023 09:45 |
| Thomas Matern (matern) | 29.05.2023 09:45 |
|---|---|
| Hi I was wondering if anyone got any luck with using the Remote Debugger, and hitting breakpoints in particular. I am running FS-22 (from Steam, latest version) and the GIANTS Remote Debugger 9.0.0. I have just submitted a pull-request for Autodrive and was curious to use the debugger instead of adding/removing debug-log lines. What works: - the debugger finds the mod source and the game - the debugger output-tab shows all the same output as the console in-game - pressing F10 in-game shows Remote Debugger: connected in-game and in the debugger, The shows that it is connected. - I can randomly pause and resume the debugger. Sometimes I am lucky and hit a line of code inside Autodrive. In this state, I can inspect variables etc. While the debugger is halted, the game is frozen - this is expected. What does not work: breakpoints. None of my breakpoints are hit. I can set a breakpoint on a log-statement - and I see it printed to the console but the debugger does not stop. The breakpoint is shown as a red bubble, as it should be. I also tried this with Courseplay - I have both mods unzipped in my mods folder (and deleted the zip file). What am I missing? |
|
| Thomas Matern (matern) | 31.05.2023 05:53 |
|---|---|
| To answer my own question - for the next person with the same issue, and maybe for Giants to have a look at it/fix it: I have my mods not in the default location, and instead, use modsDirectoryOverride in gameSettings.xml.This was the root cause of my issue. After disabling this setting and moving my mods into the default location, the debugger stops at breakpoints as expected. I was initially thinking of blaming the Steam version of the game - and bought the game directly from the Giants store, just to find that it has the same problem. Well.... I guess that's NZ$ 50 poorly invested. |
|
Note: Log in to post. Create a new account here.