Is there a way to improve how it looks in the 5E rule set... My eyes are broken and the font is way too small????
Printable View
Is there a way to improve how it looks in the 5E rule set... My eyes are broken and the font is way too small????
Just got an error'
Script Error: [string "Scripts/lsSystemMain.lua"]:88: attempt to index global 'btcuccUseCampaignCalendar' (a nil value)
I opened a item on the system tab....
Most of the issues you are referring to stem from the fact that the 5E ruleset uses a different "style" of graphics than the CoreRPG. Long have I asked for help from volunteers to help me with improving the graphics for 5E and other child Rulesets, as my graphics work sux (see here, for eg: https://www.fantasygrounds.com/forum...ics-Volunteers).
Recently I was contacted by someone who helped me out with 5E graphics, and they'll be in the next release. I'm still looking for help with some of the other child Rulesets (as per the thread above)
Cheers
Hey dulux, seems that the alignment graph extension conflicts with your Locations (inc Shops & Towns) Databse Extension (https://www.fantasygrounds.com/forum...se-Extension):
Having installed both extensions, the alignment graph works fine but in the Locations extension for example if you creating a new plane the following message occurs:
Ruleset Error: window: Control(divider1) anchoring to an undefined control (gAnchorLeft) in windowclass (wcPlaneMain)
Ruleset Error: window: Control(divider1) anchoring to an undefined control (gAnchorLeft) in windowclass (wcPlaneMain)
Ruleset Error: window: Control(divider1) anchoring to an undefined control (gAnchorRight) in windowclass (wcPlaneMain)
Ruleset Error: window: Control(divider2) anchoring to an undefined control (gAnchorLeft) in windowclass (wcPlaneMain)
Ruleset Error: window: Control(divider2) anchoring to an undefined control (gAnchorLeft) in windowclass (wcPlaneMain)
Ruleset Error: window: Control(divider2) anchoring to an undefined control (gAnchorRight) in windowclass (wcPlaneMain)
and so forth ...
The same for creating systems (wcSystemMain), worlds (wcWorldMain), buildings (wcBuildingMain), towns (wcTownMain) and locations (wcLocationMainGeo).
After deinstalled your alignment graph extension the locations extension works as it should (at the moment with the Script Error: [string "Scripts/lsSystemMain.lua"]:88: attempt to index global 'btcuccUseCampaignCalendar' (a nil value) but as I've seen in the comments you are already on it).
Thanks for the feedback and I apologise - I thought I had that sorted, but obviously not.
What I'll do is get it fixed in the new release of the Locations Database (which, hopeful, life won't keep keeping me from :( ) - in the meantime, all I can suggest is (for the time being) not using the two Extensions at the same time - a PITA, I know, but that's about all I can suggest at the moment.
And thinking about it, if its happening with the Locations/Alignment Graph then it'll probably happen with Locations/Campaign Style Graph, Weather/Alignment Graph and Weather/Campaign Style Graph as well - damn!
Is there a list of known incompatibilities?
After installing this extension, I seem to experience crashes when opening a campaign file, although it doesn't happen all the time.
Also, sometimes when attempting to delete items in some of the menus, it produces an error and can't delete the item. I'll see if I can get a screenshot when I head home.
the cant delete part happens. its because of variables being held in certain places. If I remember correctly its when create a new item but dont fill out anything. I havent really delved into it but I know it does happen under specific circumstances. the crashing also happens when similar circumstances are met.
No, there's no list of known incompatibilities because there are (at this stage) no known incompatibilities - apart from my CSG, AG and AltColourGizmo Extensions which will be fixed in v4 of this Extension.
I'm currently working through all the known issues with the Locations Extension in preparation for releasing v4 so if you've got something that hasn't already been mentioned in this thread I'd love to hear about it.
The delete issue is a known one and has already been fixed in v4. The crashing one is new (I believe) - the more info you can give me the better - thanks
Cheers