PDA

View Full Version : Windows 10 issue?



KhybersGhost
December 11th, 2015, 22:55
So I recently reinstalled windows because Fantasy Grounds just wasn't working for me and decided to upgrade from 8.1 to 10 this time. The application is working, but has an interesting bug that I am curious to see if anyone else has had. Basically, when I first open Fantasy Grounds I can't see any of my campaign modules at all when I go to the load screen. Clicking on the open folder button in the top right takes me to the C:\Program Files (x86)\Fantasy Grounds folder (which doesn't contain my campaigns, modules etc of course) instead of the data folder. By running the updater (whether it needs it or not) it changes the folder it points to back to the C:\ProgramData\Fantasy Grounds folder.

I'm not sure if this is the intended folder for data in Windows 10 or not, which may be the issue. I do recognize the path is much different than it was in Windows 8.1.

damned
December 11th, 2015, 23:28
This is the correct path for Windows 10.

thermopile
January 15th, 2017, 22:02
OK so I installed on a new win 10 machine, and got the exact same problem. However, for me it does not go away when I run the updater. In the Settings interface, it points to the right place, but klicking on the little folder on the main page, opens up the C:\Program Files (x86)\Fantasy Grounds folder. Trying to load or create a campaign does not work, since it can not find any modules etc.

I have reinstalled, no change.

What can I do?

Trenloe
January 15th, 2017, 22:05
Welcome to the forums!


In the Settings interface, it points to the right place
Please post a screenshot of the settings window (remove or blank out your license key before posting).

thermopile
January 15th, 2017, 22:28
17448

here you go!

thermopile
January 15th, 2017, 22:32
And here is an image of where I end up when i push the folder icon
17449

Trenloe
January 15th, 2017, 22:39
17448

here you go!
That's not a valid location on your computer - it's ProgramData (without a space). However, it isn't recommended that ProgramData is used for the FG data. Some info here: https://www.fantasygrounds.com/forums/showthread.php?30604-Windows-file-access-issues-can-t-update-campaigns-not-saving-etc-Fix-options

You could try uninstalling, then opening Windows registry editor (regedit.exe) and delete HKEY_CURRENT_USER\Software\Fantasy Grounds. Run a re-install from this executable: https://www.fantasygrounds.com/filelibrary/FGWebInstall.exe Do not change any of the defaults file locations.

KhybersGhost
January 16th, 2017, 03:37
I never did find a solution unfortunately. When I first boot up Fantasy Grounds everything works fine using the ProgramData folder. Following any program update I can no longer access any of my campaigns, characters etc. The work around for me was to simply quit the program after any update and restart it. A little annoying but it works fine. Good luck. :)

Moon Wizard
January 16th, 2017, 03:41
If you re-install your data folders in the default location ("C:\Users\<UserName>\AppData\Roaming\Fantasy Grounds"), it will most likely work much better.

Regards,
JPG

thermopile
January 16th, 2017, 21:23
Thanks for the fast answer!

Hmmm, well the "Progran Data"-folder was what the installer decided for itself...

Anyway, removed everything, did the regedit thing, reinstalled using the provided link, changed the data directory to "C:\Users\Anders.Fogelberg\AppData\Roaming\Fantasy Grounds" (I created the Fantasy Grounds folder), ran the installation and updated it afterwards.

Klicking on the little folder still gives the app directory as the data directory (meaning I end up here: C:\Program Files (x86)\Fantasy Grounds).

Sigh...

Any other bright ideas?

thermopile
January 16th, 2017, 21:27
OK, so why is there a space between "Fan" and "tasy" in the adress when I post it here? Pasting the link in Notepad does not show that...
So just to clarify, the folder is called "Fantasy Grounds".

damned
January 16th, 2017, 22:07
Hi thermopile if you want me to have a look with you send me your email via PM.

thermopile
January 17th, 2017, 00:06
So just ended a session where damned looked at my computer via link. Checked registry, uninstalled etc. Added some extra code somehow to something to force the directory paths to where the should be, and we got FG running with ruleset. The modules do not show up when a new campaign is created, so something more needs to be done. A step forward, and I am clearly confused on a higher level (which is a precursor to enlightenment...or utter confusion)! TBC (i hope). Damned is my new hero!

damned
January 17th, 2017, 00:12
So just ended a session where damned looked at my computer via link. Checked registry, uninstalled etc. Added some extra code somehow to something to force the directory paths to where the should be, and we got FG running with ruleset. The modules do not show up when a new campaign is created, so something more needs to be done. A step forward, and I am clearly confused on a higher level (which is a precursor to enlightenment...or utter confusion)! TBC (i hope). Damned is my new hero!

Hi thermopile did you see if the modules are showing up in Library -> Modules?
It might also be that your license key isnt writing to the registry...

thermopile
January 17th, 2017, 20:48
Nope, no modules in library.

thermopile
January 29th, 2017, 08:54
To end this thread, some closing words. Somehow, the issue seemed to be linked to the rights of the login I was using for windows 10. This became clear in a seperate session I had with Damned.

After the session, I removed all traces (I think...) of the old installation, and did a new installation. After that installation, I set so that I always run FG as admin in Windows, and with that everything works as it should.

So for locked rights users in windows 10, you might run into issues running FG. Run as admin and these issues wil probably go away.

damned
January 29th, 2017, 10:51
In this case I believe there are other issues or things going on with the permissions on thermopiles setup. It is generally best not to Run as Administrator but in this case we did have to.