-
June 13th, 2021, 00:30 #101
Welcome rickycilantro
Please post a screenshot of your map + grid.
-
July 14th, 2021, 22:40 #102
anyone else having issues with this now that the newest patches rolled out? I had maps that were lined up and now they are not lined up. I tried realigning them and no dice. It is incredibly frustrating.
-
July 14th, 2021, 23:55 #103If there is something that you would like to see in Fantasy Grounds that isn't currently part of the software or if there is something you think would improve a ruleset then add your idea here https://www.fantasygrounds.com/featu...rerequests.php
-
July 15th, 2021, 17:18 #104
Yeah. Not sure what exactly happened with it. BUT while I do not understand why maps that were working stopped working, with a bit of fiddling I managed to get them working again. I think it was just a weird one-off bug or something with a specific map I had put in. Computers do some weird **** sometimes.
-
July 17th, 2021, 20:35 #105
- Join Date
- May 2018
- Posts
- 2
It seems that the links for the attached files no longer exists. Is there any way to download this tool or at least a similar one?
-
July 17th, 2021, 20:47 #106
I just downloaded it using those links. It's working for me.
-
July 17th, 2021, 20:53 #107If there is something that you would like to see in Fantasy Grounds that isn't currently part of the software or if there is something you think would improve a ruleset then add your idea here https://www.fantasygrounds.com/featu...rerequests.php
-
July 29th, 2023, 19:46 #108
- Join Date
- Mar 2020
- Location
- Peoria, IL
- Posts
- 12
@trenloe & @valeros
I got this strange .NET message when opening the Map Align tool, both regular and LAA versions, on the latest updated Windows 11 w/latest .NET. After the error the tool still seems to work, but it may lead to future issues, so I thought to at least bring it to your attention. Screenshot of the error w/ error code below.
Screenshot 2023-07-29 134516.png
-
August 2nd, 2023, 16:58 #109
- Join Date
- Aug 2009
- Posts
- 262
Thanks for the info, I am going to assume it is because .Net 2.0 is so old. I just added a new version (on the first post) complied for .Net 4.8 and x64 that may not generate that error.
-
August 11th, 2023, 19:57 #110
- Join Date
- Mar 2020
- Location
- Peoria, IL
- Posts
- 12
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks