EFB SDK sample, changes can be seen only when quitting and restarting sim?

[MSFS 2024] Questions & Community Discussions HTML/JS
1

I have compiled a built an ESB SDK sample and, while everything is working, I cannot see the changes that I made until I exit and re-enter the sim. (I am using all the npm commands as specified in the SDK). I can even see the changes I make in the compiled TemplateApp.js, but the changes are not visible in the EFB itself unless I exit the sim and re-start it.

Is there any way to see the changes in the EFB while in sim, during development? I can’t believe I have to re-start the sim even for the smallest of edits…

2

Use the CoherentGT debugger, enter your app, and select either F5 or Ctrl+Shift+R

4

Sorry, i first deleted my message because i thought i had it fixed. But seems not, this is what happens for me since a while.

If i do this:

  • change my code in VSCode

  • save the file

  • build the app (either by npm watch or manually) in terminal

  • build the project in msfs

My changes wont be there. Never. Also not by reloading via debugger.

I can rebuild as many times i like, the change wont be displayed. But if i really rebuild, after first build it will look like this:

image
image1511×738 228 KB

As you can see, it stops at generating packages.

But if i then go back to VS Code and add a whitespace somewhere in the file and save the file, and now go to msfs and build the project, the changes will be there.

Is there any way to prevent this double build process? Wasnt the case a few months ago, as far i remember.
I made this app way back, early in 2024 days and went back to change something now and saw that it wont refresh anymore.

5

WRT the console build log, you’ll see the times are not in order - a couple of lines up you can see the final result at 1h:42m:16s - this looks like it might be an unrelated bug?

6

your right, its indeed not in order.

But funny enough, if it happens, its always in this wrong order. And if its works its in the correct order again.
And when it shows up like this, no matter how many times i build, the otrder will be like this.
Then i go back to edit file, save, build, and it will be in correct order and most likely show changes now.

Its really reproducible. A 100% thing.

If one following change on the file is needed or multiple seems random but for one change to appear, i have to edit/save the file and build the project multiple times.

It cant be time passed after file saved, because no matter how many times i build, if its stuck like that, it will never appear with fresh code and the order in the log is always like that.

I mean, if it helps i can make a video.

7

Yeah, after an hour or 2 it wont refresh no matter what anymore :frowning:

8

I think i found how to more or less reliably can make the changes appear again, if it got stuck.
Not sure how and when its getting stuck, but its pretty early in my work process.

If i then “Clean All in project”, then build again and then refresh via debugger, the changes will appear.

9

Same problem here with the same workaround solution. I’d like to bump this up since this method is slowing down the workflow a lot. IIRC before that you didn’t need to clean and rebuild. You could simply reload the debugger and changes where there immediately.