Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

[FEAT] Add some info regarding "Community" folder path in the installer #212

Open
Manochvarma opened this issue Dec 4, 2020 · 5 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request priority: LOW type: ux

Comments

@Manochvarma
Copy link

Manochvarma commented Dec 4, 2020

Description

Currently when we select some other path/drive for livery installation, it shows error as this:

image

There is no enough info saying which community folder does the installer refer to because when we say Community folder we always refer to the default Microsoft Flight Sim's Community folder.

Solution

When we create a folder name Community in the folder we wanted to install the livery (other than the default MSFS drive), the installer identify it without giving error. Refer image below:

image

So, there should be a sample to show how the community folder should be created.

Example, something like this:

Default MSFS path
[Default MSFS path]\Community
or
Other drive folder paths:
[Your Drive Path (D, E, F or else) Drive]\Community

Why is this the best solution?

By having this simple sample, users will not be confused why the installer giving error or not allowing us to change the path.

Additional context

NONE

@Manochvarma Manochvarma added enhancement New feature or request triage needed labels Dec 4, 2020
@davwheat
Copy link
Member

davwheat commented Dec 4, 2020

Hmmm you have a good point here.

What do you think about a simple documentation website on GitHub Pages for things like this.

We can then link to the site from the manager, adding a "More info" link to the end of that error text.

Lemme know your opinion and any other ideas you have.

@davwheat davwheat added priority: LOW type: ux documentation Improvements or additions to documentation and removed triage needed labels Dec 4, 2020
@Manochvarma
Copy link
Author

Manochvarma commented Dec 4, 2020

Hmmm you have a good point here.

What do you think about a simple documentation website on GitHub Pages for things like this.

We can then link to the site from the manager, adding a "More info" link to the end of that error text.

Lemme know your opinion and any other ideas you have.

I don't think that will work as expected because people wanted a prompt solution rather than searching for it in another link or note files. If you check the 1st image above, there is an error showing in red Please make sure you have selected your community folder. I think below that line, we can add sample of the community path as shown above in my explanation above.

Other drive folder paths:
[Your Drive Path (D, E, F or else) Drive]\ Community
*Make sure you have created a community folder in the folder you wish to save the liveries.

Bolding/Highlighting the community word in other colours will make them easier to understand that the community folder must be there.

Since the default MSFS community folder can be found by the installer itself with the registry entry, I think better if we can put a simple sentence asking the users to make sure to create their own community folder at the folder they wish to install the liveries.

Let me know what your point of view.

@davwheat
Copy link
Member

davwheat commented Dec 4, 2020

What situation would people not install to the normal Community Packages folder?

PS: There's no registry key for MSFS (grr). We have to manually snoop into locations where the game is normally installed, then find a text file with a line pointing to the packages folder.

@Manochvarma
Copy link
Author

What situation would people not install to the normal Community Packages folder?

PS: There's no registry key for MSFS (grr). We have to manually snoop into locations where the game is normally installed, then find a text file with a line pointing to the packages folder.

I never know there is no registry entry for this sim.

For me, the only situation is when we don't have enough space on the drive we have installed MSFS.

@Khitiara
Copy link

I have the liveries installed elsewhere for organizational and disk space reasons, have the liveries in a subfolder of my addon storage and linked into the actual community folder - also allows disabling or re-enabling liveries without having to redownload

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request priority: LOW type: ux
Projects
None yet
Development

No branches or pull requests

3 participants