Please post all reports of bugs for all 13A products in this thread.
Please ensure you say what module the error is in and give as much information as is necessary to enable the bug to be tracked down.
Printable View
Please post all reports of bugs for all 13A products in this thread.
Please ensure you say what module the error is in and give as much information as is necessary to enable the bug to be tracked down.
In the Character Sheet's "mini" view, clicking the Perception check die gives the following error:
Script Error: [string "perception"]:1: attempt to call field 'getSkillValue' (a nil value)
Whenever I try to read the Classes section of the Core rules module, FG crashes.
Windows 7 here...though I don't know if that's relevant. I haven't had this issue with other Core rules sets.
Hi scotyder, and Welcome! to the Community,
I have never heard of that happening before. Id there any Error message or anything that is displayed anywhere? What about in the console.log file (located in the FG Data Folder)?
I'm at a lose as to what would be causing this, so any extra info you could provide would be greatly appreciated.
RAM usage and whether you are on Windows 32 or 64bit could be relevant here.
I use PlayOnLinux to run Fantasy Grounds. Game crashes when I try to open any of the classes or races of the notes from the manual. I have a 64bit system. Ram usage was about 25% when it crashed.
Fantasy grounds used 313mb of RAM. %25 was the overall RAM usage, but I had several processes going on.
Ok 313mb is not the issue...
Not sure if this counts as a "bug" per se, but since this theme officially ships with FG now I thought it might be worth mentioning:
The "Simple" themes (grey and brown) mostly work with this ruleset out of the box (to my knowledge at least), however the final two tabs on the character sheet have a very strange overlap issue. Do you know why this is occurring and if its possible to fix it?
Attachment 23688
Just opened the Skill Challenge Tracker and received the following error:
Script Error: [string "sct/scripts/sct_list.lua"]:70: bad argument #1 to 'pairs' (table expected, got nil)
Seems to happen the first time I open the tracker, every time.
bojjenclon,
For the simple themes, I will get these fixed on the next update for the themes in v3.3.6.
Regards,
JPG
On some NPC sheets, the Save Throwing section overlaps with the Standard Action header.
Attachment 23703
All bugs reported up to the time of this post have been rectified and passed on to SW for release :)
A couple of problems here:
1) The updating didn't solve the crashing when I click on a Race or a Class in the menu I show on the pick.
https://drive.google.com/open?id=1XA...7apGbrOw7EHGjE
2) I can't drag and drop General Feats from the reference manual to a character's sheet. I can't do it from the Feats list (from the red icon) but no from the Reference Manual you open through the Library.
Thanks for your good work!
I still have the same issue as Eneko.
If I open the Library --> Core Rules --> Reference Manual, the I can browse the Race and Class content. I can't, however, drag and drop class and race to a character sheet from this interface.
The monster "Ghoul Licklash" appears to be missing its stats.
windows 10 64-bit get the following on opening
Attachment 23975
no extensions used also book are not present and several of the icons on the right error when clicked.
3.3.5 but it is an old install that been updated several times. pre-pathfinder official i did a lot of customizing. but i think that should all be gone by now. all the icons above the library icon giveg an error when clicked. At this point i may need to uninstall and reinstall.
Sorry i think i found the issue i needed to update my password in the updater.
yes it was an old fan version i was trying.
Any progress on the bug that Eneko and I reported? The ruleset is largely unusable. I essentially have to type character sheets by hand and the constant crashing keeps me from using it.
It's a hard crash of the application, there is no information in the logs.
I can try those steps later.
In my sidebar there is no Race or Class button (I double checked there I ticked all the options).
It seems the Simple themes still need a bit of tweaking in the combat tracker.
Attachment 24143
Under NPCs, the Cave Orc listed has zero figures for AC, PD, and MD. There might be more bugs, but I‘ll find out only in October, when I‘ll heavily utilize this ruleset...
It seems drag and drop is not working for Race and Class. I tried it out with no success from the reference manual. It is implemented in the 4e ruleset, though. A bug or a feature?
Let me look into both of these issues and I'll get back to you
Cheers
Did you have a chance to look at it? For now it seems all CLASS/RACE things have to be entered manually...
Usually there is a miss damage you can have for certain spells/feats as well, and might not be the same for ranged attacks as well.
Any chance you can distinguish miss damage, so that it won‘t be applied to all, or can be different?
In the Character Sheet under the Background tab, on the right hand side in the lines where you enter the names you get empty squares, which should usually contain a bullet to click on, opening a window where one can describe the meaning of the name. As background is individual and can be anything from goblin exterminator to traveling martial arts pupil, it would be good to have this enabled to detail it appropriately.
Rolled results on the same screen, will default to a DC 15 skill check. Skill checks differ by adventuring region (level) and difficulty, too. I‘ve seen no way to change this. Can you point me to the right setting, or make it work, too?
In the Character Sheet under Miss Damage, there is just a single entry. Depending on class, e.g. Rogues will get ranged miss damage, whereas most others won’t. Where is this distnction covered?
Entering new weapons into the inventory will not add them to the Combat tab.
You need to manually enter them there, and it will leave an empty square, therefore you cannot enter the lacking data which it is referencing to.
The ruleset seems to be quite broken, obviously not tested and with no documentation atm.