FSDreamTeam forum

Products Support => GSX Support MSFS => Topic started by: gdj74 on June 01, 2025, 06:48:31 pm

Title: Don't see KORD in FSDT installer
Post by: gdj74 on June 01, 2025, 06:48:31 pm
Purchased the KORD addon for MSFS today (along with KIAH) but it's not appearing in the installer (KIAH does).  Seems like there should be an option to scroll down but nothing (mouse wheel does nothing, etc.)

Appreciate any help on this as I'd love to get ORD up and running

Title: Re: Don't see KORD in FSDT installer
Post by: virtuali on June 01, 2025, 07:12:17 pm
The mouse wheel scrolls the list down.
Title: Re: Don't see KORD in FSDT installer
Post by: gdj74 on June 01, 2025, 11:16:29 pm
First off, realize I posted this in GSX, my apologies (not sure I can move it)

Mouse wheel unfortunately does not move the content...wheel successfully scrolls for me in release notes and in product detail.

In the main window, nothing however (note there's no scrollbar unlike the release notes + KIAH detail)

Any other way to DL the ORD scenery?

GJ
Title: Re: Don't see KORD in FSDT installer
Post by: ChrzOC on June 02, 2025, 04:45:23 am
First off, realize I posted this in GSX, my apologies (not sure I can move it)

Mouse wheel unfortunately does not move the content...wheel successfully scrolls for me in release notes and in product detail.

In the main window, nothing however (note there's no scrollbar unlike the release notes + KIAH detail)

Any other way to DL the ORD scenery?

GJ


Just for your edification, the main window GUI does not have a scrollbar. The mouse wheel should scroll the list fine though, I was going to say you may be having compatibility mode issues that are discarding the scroll wheel interupt requests, something I have seen with .NET CLR/CLI based applications in the past due to issues with the interfacing between kernel mode and user mode of the .net runtime because of faulty windows API hooks. But if you are saying the scroll wheel works in the Release notes, that wouldn't be the case (It wouldn't work anywhere).

You can also use the arrow keys to move through the list though. Just highlight one of the selections and use Arrow Up/Down on your keyboard.

Attached Screenshot of the bottom of the list, scrolled using arrow keys.
Title: Re: Don't see KORD in FSDT installer
Post by: virtuali on June 02, 2025, 01:51:45 pm
Attached Screenshot of the bottom of the list, scrolled using arrow keys.

This is interesting: arrow keys (arrow keys, numpad keys with/without numlock) don't work for me, not even when the first row is selected.

Mouse wheel works as long the mouse cursor is over the list area, and works with the Release Notes as well (that's a mini-browser control), but that also has a vertical scroll bar, so even if the mouse doesn't work, keys do work as well, but not the arrows, the pg up/dn keys, which I guess it's something coming from the vertical scrollbar itself.
Title: Re: Don't see KORD in FSDT installer
Post by: gdj74 on June 03, 2025, 12:40:06 am
I’m going go try it again with arrow keys and then going to put installer on another computer as a next step if I can’t get anything to work. Stay tuned.
Title: Re: Don't see KORD in FSDT installer
Post by: ChrzOC on June 04, 2025, 04:39:43 am
Attached Screenshot of the bottom of the list, scrolled using arrow keys.

This is interesting: arrow keys (arrow keys, numpad keys with/without numlock) don't work for me, not even when the first row is selected.

Mouse wheel works as long the mouse cursor is over the list area, and works with the Release Notes as well (that's a mini-browser control), but that also has a vertical scroll bar, so even if the mouse doesn't work, keys do work as well, but not the arrows, the pg up/dn keys, which I guess it's something coming from the vertical scrollbar itself.

Really? That's odd. Yeah, after highlighting one of the selections, the arrow keys (std LDUR, not the numpad) allow me to move through each selection consecutively. I wouldn't know what to make of the difference machine to machine without knowing what control namespace or pipes the main UI is using, maybe there's a slight variance in our installed library redistributable(s). I don't have any active accesibility options turned on or anything on the windows side like that.