pierr3 / TrackAudio

A next generation Audio-For-VATSIM ATC Client for macOS, Linux and Windows
Other
47 stars 12 forks source link

Javascript Error #192

Open Rube-B opened 2 weeks ago

Rube-B commented 2 weeks ago

I get this error over and over when installing and launching. Tried reinstalling, tried another version, tried updating java/node, tried running as administartor. Nothing works.

image

GeorgeBarlow commented 1 week ago

Trying to do a clean install again and ensure the directories below are empty before re-installing. Something may have not been copied across properly.

Report back your findings :)

minsulander commented 1 week ago

Same issue here on a fresh (as in nothing installed except drivers and EuroScope) Windows 10 computer, TrackAudio 1.3.0 beta 3. %appdata%/TrackAudio contains one file, Local State. %localappdata%/Programs/trackaudio contains the Electron-typical ridiculous amount of DLLs etc.

GeorgeBarlow commented 1 week ago

Same issue here on a fresh (as in nothing installed except drivers and EuroScope) Windows 10 computer, TrackAudio 1.3.0 beta 3. %appdata%/TrackAudio contains one file, Local State. %localappdata%/Programs/trackaudio contains the Electron-typical ridiculous amount of DLLs etc.

Hmm, yeh it sounds like it can't find it or maybe can't load it?

Let's first of all just make sure you have the required file inside your %localappdata%, could you please navigate to: %localappdata%\Programs\trackaudio\resources\app.asar.unpacked\node_modules\trackaudio-afv\build\Release

You should have a file called trackaudio-afv.node in this folder (I believe 25 files in total), could you let me know what you find :)

minsulander commented 1 week ago

Yes, the file is there.. Turns out I was missing a more recent (2022?) version of the Visual C++ Runtime package. After installing the 2015-2022 x64 version it launches just fine. Might be worth mentioning this requirement in the installation instructions or, even better, having the installer check for it.

pierr3 commented 6 days ago

Thank you for finding this out, we were not aware (as we mostly dev on mac) - I'll add it to the release notes and to the installer a bit later. Can everyone who has had this problem confirms that this fixes it?