Hello,

does actually anyone have noolaero VDGS successfully running in MSFS2024? I have 4 airports that should be compatible with it, KSFO, NZAA, EGLL and LSZH, and none of these work. I made sure that GSX config is the one for noolaero, so not GSX controlled (I don't get the text-popup). To my understanding, it shouldn't be required to set the gate in GSX before coming up to the gate, and the module should detect the aircraft. But nevertheless, it doesn't work if I set the gate in GSX.

I've made sure to:

- setup exe.xml to auto start (I see it in the task manager)

- run the scan, all 4 airports are listed

The displays remain black.

I have the latest version 7.0.0 from noolaero website.

Used the installer to install the application.

Any ideas?

38 minutes ago, Simon_C said:

Hello,

does actually anyone have noolaero VDGS successfully running in MSFS2024? I have 4 airports that should be compatible with it, KSFO, NZAA, EGLL and LSZH, and none of these work. I made sure that GSX config is the one for noolaero, so not GSX controlled (I don't get the text-popup). To my understanding, it shouldn't be required to set the gate in GSX before coming up to the gate, and the module should detect the aircraft. But nevertheless, it doesn't work if I set the gate in GSX.

I've made sure to:

- setup exe.xml to auto start (I see it in the task manager)

- run the scan, all 4 airports are listed

The displays remain black.

I have the latest version 7.0.0 from noolaero website.

Used the installer to install the application.

Any ideas?

I have it 100% correctly installed, as you do and newest v 7.0 is not working for me either in 2024 nor 2020.

I see there is an issue with it, when doing scan, I reckon some files should appear somewhere... and I found some files on my c-drive.

C:\Users\%username%\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\noolaero-module-vdgs

And:

C:\Users\%username%\AppData\Roaming\Localstate\WASM\MSFS2020\noolaero-module-vdgs

Will see if that works, moving them in appropriate folder... or folders... or anywhere.

It's a bug, obviously.

Edited February 22, 20251 yr by Simon_C

Will try Simon, thanks for the tip.