June 6, 20214 yr Moderator Just purchased beta 1.2 Using Store edition of MSFS Install proceeds to folder selection - input filled in "F:\FS2020" will not allow any change. Click next and get "wrong location" - unable to change - rinse and repeat. The location F:\FS2020 is not a valid folder. Since many people use addon linker to control the community folder - can you make the installer allow the option to install to any user selected folder. Personally I install very little actually into the community folder - I install elsewhere and dynamic link to CF. Either way, I need to find a way to install a/c. Thanx, Vic RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
June 6, 20214 yr 2 hours ago, vgbaron said: Just purchased beta 1.2 Using Store edition of MSFS Install proceeds to folder selection - input filled in "F:\FS2020" will not allow any change. Click next and get "wrong location" - unable to change - rinse and repeat. The location F:\FS2020 is not a valid folder. Since many people use addon linker to control the community folder - can you make the installer allow the option to install to any user selected folder. Personally I install very little actually into the community folder - I install elsewhere and dynamic link to CF. Either way, I need to find a way to install a/c. Thanx, Vic After the installer installed the Widgeon into the Community folder, I just moved the resulting Widgeon folder from the Community folder to my Community-Addons folder where I keep all my add-ons. I then let the Add-On Linker 'do its thing' and it put a short cut for the Widgeon into the Community folder as usual. Seems to work. Al Edited June 6, 20214 yr by ark
June 6, 20214 yr Author Moderator 1 hour ago, ark said: After the installer installed the Widgeon into the Community folder, I just moved the resulting Widgeon folder from the Community folder to my Community-Addons folder where I keep all my add-ons. I then let the Add-On Linker 'do its thing' and it put a short cut for the Widgeon into the Community folder as usual. Seems to work. Al Ok, if I can get the installer to install ANYWHERE I can do that. How does the UNinstaller deal with that for updates? Vic EDIT: got it installed. I usually use the "checkout" option in winzip and install from there. That doesn't work with this installer. Needed to extract to a folder on desktop and run exe. Winzip just creates a temp folder - somehow the installer sees that as a problem. RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
June 6, 20214 yr 48 minutes ago, vgbaron said: Ok, if I can get the installer to install ANYWHERE I can do that. How does the UNinstaller deal with that for updates? Vic, Good question. I found that running the installer removes the Add-Ons Linker shortcut from the Community Folder, but does not remove the Widgeon a/c folder itself from my Community-Addons folder. So I just delete the a/c folder 'manually', and then repeat the install process I described above (re-install into the Community folder, move the resulting file to my own Community-Addons folder, then run the Add-Ons Linker). Bit of a kludge, but seems to work in that the Wedgeon does load into MSFS. Eventually I would hope the frequency of Widgeon updates goes way down! Al Edited June 6, 20214 yr by ark
June 13, 20214 yr I to have a problem with installation, I have installed it manually, into my community folder, but the aircraft isn't showing up in my hanger, it does however show it is installed in my content manager, no image. or aircraft in hanger. Any suggestions on what,, or how I can do to fix this? Thanks in advance! Garry
June 13, 20214 yr 24 minutes ago, Hawkeye_49 said: I have installed it manually, into my community folder, What do you mean by 'installed it manually' -- manually as opposed to what? Did you run the installer and let it install into the Community folder, or what exactly? The install process should be automatic. Note you can not change the install location from what the installer specifies. Al Edited June 13, 20214 yr by ark
Archived
This topic is now archived and is closed to further replies.