-
Hopefully my most recent update (see original post) has quashed those nasty graphical anomalies.
I think the donor ruleset was having a few problems with the skin extension and the functionality extension running separately. I've packaged both the Gaslight skin and the Extend_CoC in to one extension and from initial testing, all seems well.
Equally the Extend_CoC1920s includes a few extra graphics to allow for the encounters feature of Extend_CoC.
Please report any problems you may find. It might be worth connecting another single session locally, and checking all's still well, and of course before any testing DONT FORGET TO BACKUP ANYTHING THAT YOU WOULD HATE TO LOSE.
Baz.
-
Sorry to say sir, just tried both of the extensions, and still get the duplicate graphics, with both preexisting and new campaigns.
Made sure each one was the only one active for the new campaigns and got the issue with each one.
-
Hmmmm. Now I'm starting to feel stumped. I'm not seeing any graphical anomalies even when creating new campaigns. I recognise there is something amiss and i know this isnt ideal, but have you tried creating a new campaign without the extension and then adding it after Insanity?
Thanks for your help by the way.
I will fix this. I'll dig a little deeper tomorrow, and chop and change a few things. Im beginning to think that the basis upon which the CoC ruleset was designed, is not favourably disposed to extensions. The reason I say this, is following a chat I had with Dr Zeuss in the Workshop forum.
I wont give in though.
Baz.
-
Created a new campaign w/o any extensions.
Closed it and reloaded with the Extend 1920s, nothing seemed wrong and the Encounters icon was there.
Reloaded with the Extend Gaslight, and had double icons.
Probably should not that I am on 2.8.1 still as my D&D group has not decided to make the change yet.
-
I was wondering which version you were running Insanity, but I also still think there is an issue that needs addressing.
Dakadin the author of Extend RMC had a similar issue, and in true Dakadin style has kindly offered a solution, which I will look into today. In one way I'm a little relieved he had this issue as I was beginning to think it might be something that lay at the heart of the CoC ruleset, and it's relationship with FG v2.9
I'm somewhat more confident I can resolve it now.
Baz.
-
Okay, lets try again. Please find attached version 1.1 of both ExtendCoC1920's and ExtendCoCGaslight (See original post), following Dakadins desktopmanager fix.
BACKUP ANYTHING YOU WOULDN'T WANT TO LOSE PRIOR TO TESTING
When testing, it would be helpful if you could check functionality with both a single incidence of FG and also with another locally connected incidence running as well.
Also please report which version of FG your using (v2.8, v2.9 etc), should you run into any problems, otherwise... Enjoy!:)
Baz.
P.S. I am open to suggestions as to the next improvement for CoC, although I would like to leave combat tracker related improvements in abeyance.
-
Okay, created new campaign w/o any extensions.
Reloaded with ExtendCoC1920s' 1.1, there was no duplicates.
Connected to the game locally, no errors shown.
The encounters seemed to work fine.
Repeated the steps with the ExtendCoCGaslight 1.1, no duplicates.
Connected to game, no errors.
The encounters seemed to work fine.
Good work!
-
Your a star Insanity. Thanks for your help... and thanks Dakadin for delivering the "coup de grace" to that annoying graphical glitch. Now on with the next update.
Baz.
-
Not sure if this is only with existing campaigns, but loaded my server with the extensions and the upper right buttons, module activation, etc...could not be opened.
-
Hmmm. I'm preparing for another release of CoC this week, but not sure why you're encountering the problem. I'll give it some thought. Thanks for the feedback.
Baz.