Thread: Ranges on Maps / Hexes
-
September 29th, 2020, 02:37 #11
- Join Date
- Apr 2010
- Location
- Australia
- Posts
- 905
Timezone: Australian EST (GMT +10).
Systems/Rulesets: GURPS 4th Edition.
Campaigns (Ultimate License Holder)
GURPS Traveller - The Empty Peace
GURPS Shadowrun - Power Plays
GURPS Banestorm - Dark Clouds Rising
-
September 29th, 2020, 02:49 #12
Thanks - definitely an issue I have seen with hexes on (not square grids).
Great feature and I am sure this issue will be easily fixed
-
October 3rd, 2020, 06:59 #13
Just adding that last update seems to have "improved" the issue with distance measurement under Locked Tokens for Hex grids. Was looking really good but found a situation where the target distance (under Combat Tracker and on arrow from PC token to NPC) was 55', yet when rolled the range in game (using Rolemaster rule set) was 44'.
-
October 3rd, 2020, 17:26 #14
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 21,007
That should probably be reported in the Rolemaster ruleset forum. I believe that all the "range" calculations for attacks are done by the ruleset.
Regards,
JPG
-
October 3rd, 2020, 18:41 #15
I believe that it is done by the ruleset yes, but the case is that in the classic version it works and in unity it doesn't.
TWITCH | YOUTUBE
BRAZILIAN
GMT-3
FANTASY GROUNDS UNITY - ULTIMATE VERSION
PLAYER ONLY
FORGE CREATOR
Core RPG - Package | PFRPG2 - Full Mode Map | Rolemaster (Classic) - Package | Rolemaster (Classic) - Shopping Stores
-
October 3rd, 2020, 19:16 #16
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 21,007
Understood, but FG client doesn't do a "range" calculation (other than putting numbers on pointers/targeting); so any "range" calculation used in the ruleset is calculated there. I'm not familiar with Rolemaster, so I have no idea where to look.
JPG
-
October 4th, 2020, 00:57 #17
-
October 4th, 2020, 04:09 #18
- Join Date
- Aug 2020
- Posts
- 50
I am finding that in the GURPS ruleset, if the token in centered on the hex, it sometimes measures from one edge to another edge, and thus is one hex short. If I hold down the CTRL key and move the token back a tiny bit, it displays the right range.
Ergo: The first one is correct at 4 hexes, but move closer, and it shows 1 instead of 2. The final shows that if I move the target token down a bit, it displays the correct distance.
BUT movement seems to be fixed.
Right 1.png
Wrong 1.png
Right 2.png
-
October 4th, 2020, 07:24 #19
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 21,007
So, you are saying that on hex grids, the movement is correct; but targeting is still off sometimes?
Thanks,
JPG
-
October 4th, 2020, 15:10 #20
- Join Date
- Aug 2020
- Posts
- 50
Yes, that is correct. Targeting is often, but not always, correct. Movement seems to be correct. I think if the targeting was measuring from the center of one hex to the center of another hex, it might get it correct, but I'm not sure. Perhaps related, perhaps not, rotation with the mousewheel does not work (on a Mac). I think I saw this mentioned in another thread, but I can confirm it.
Thread Information
Users Browsing this Thread
There are currently 3 users browsing this thread. (0 members and 3 guests)
Bookmarks