Trenloe
January 8th, 2014, 11:14
This is an old thread - see the V1.0 thread here for the latest versions and further development: https://www.fantasygrounds.com/forums/showthread.php?20231-Enhanced-Images-%28layers%29-for-FG-3-0-CoreRPG-%28and-rulesets-based-on-CoreRPG%29&p=165599#post165599
With the advent of FG 3.0 and the CoreRPG ruleset layer architecture I have updated Dr Zeuss's excellent Enhanced Images extension to work with this new architecture. For those who aren't aware of this extension, it provides 3 layers within an image - primarily useful for putting tokens on 3 different layers and stopping them messing with each other (known as token stacking issues). This functionality can be useful if the GM wants to use mapping tokens to draw maps on the fly or use larger tokens for underlying image functionality - a good example is a ship token on a sea/river image - put the ship token on the middle layer and all of the PC/NPC tokens on the top layer and there are no token stacking/selection issues.
v0.2.2: 5826
The extension adds a "layer" icon to all images on the GM side - which when clicked reveals 3 icons that an be used to access (from left-to-right) the base, middle and top layers. Dr Zeuss shows how the original extension works in a video in this post: https://www.fantasygrounds.com/forums/showthread.php?14916-4E-Enhanced-Images&p=114668&viewfull=1#post114668
Things to note:
This *should* be compatible with previous extensions - so campaign images with layers from previous versions should work OK.
Players can only interact with the top layer - GMs must put PC and NPC tokens on this top layer otherwise players can't move their PCs or target NPCs.
Masking only works on the base layer - and then only when the map/image is based on an image file (this is the usual FG mask functionality - you can't mask a freehand drawing).
As masking only works on the base layer, anything that the GM wants to mask should be put on the base layer - tokens that are used for mapping, etc.. If you want to hide NPC tokens don't put them on the base layer, put them on the top layers and use the individual token "visibility" setting (or the visibility setting for the NPC in the combat tracker) to hide/reveal the token to the players.
Grid settings (on/off), offset and size are the same across all 3 layers - there is 1 grid throughout. Other grid functionality is specific to an individual layer - lock tokens, snap-to grid, etc.. Be careful which layer you change these settings on as you will have to be on the same layer if you want to change them later.
Drawing (and erasing of a drawing) only works on the top layer. Drawings are never masked so there is no point in having drawings on any layer other then the top layer - this helps to keep memory use down too.
If you open an image that was from a campaign that was created without the layer extension then everything will be on the base layer. With the exception of the grid - this will be synchronised across all layers.
GMs can select targeting on the lower layers (if there are tokens on those layers) - but I don't think this will work in any way, especially as PC and NPC tokens should be on the top layer anyway. Essentially the targeting arrows will appear if the GM "targets" a token on any layer. This could be confusing so GMs should keep an eye on this... I hope to be able to limit targeting to the top layer only in the future.
Shortcuts (pushpin) that link to campaign entries can be put on any layer - but they are only active (can be selected) on that layer, even though they are viewable on the higher layers. Note: If you open an image from a module that has pushpins these will be visible across all layers but only selectable on the base layer.
For encounters with token placement created in a campaign that didn't use this extension (or a previous version) the extension will convert the token placement layer to the top layer on-the-fly so that the NPC tokens are placed on the correct layer. The original encounter record is not changed.
Things to be aware if you've used to the older extension:
Grids are now on all layers - I found I frequently needed the grid on the base layer to allow me to align mapping objets correctly.
Grid controls (size and alignment) and add grid/remove grid will affect the grid on all layers no matter which layer you do the operation on.
Drawings only operate on the top layer.
When opening an image it always defaults to the top layer selected.
Any questions/issues please post in this thread.
With the advent of FG 3.0 and the CoreRPG ruleset layer architecture I have updated Dr Zeuss's excellent Enhanced Images extension to work with this new architecture. For those who aren't aware of this extension, it provides 3 layers within an image - primarily useful for putting tokens on 3 different layers and stopping them messing with each other (known as token stacking issues). This functionality can be useful if the GM wants to use mapping tokens to draw maps on the fly or use larger tokens for underlying image functionality - a good example is a ship token on a sea/river image - put the ship token on the middle layer and all of the PC/NPC tokens on the top layer and there are no token stacking/selection issues.
v0.2.2: 5826
The extension adds a "layer" icon to all images on the GM side - which when clicked reveals 3 icons that an be used to access (from left-to-right) the base, middle and top layers. Dr Zeuss shows how the original extension works in a video in this post: https://www.fantasygrounds.com/forums/showthread.php?14916-4E-Enhanced-Images&p=114668&viewfull=1#post114668
Things to note:
This *should* be compatible with previous extensions - so campaign images with layers from previous versions should work OK.
Players can only interact with the top layer - GMs must put PC and NPC tokens on this top layer otherwise players can't move their PCs or target NPCs.
Masking only works on the base layer - and then only when the map/image is based on an image file (this is the usual FG mask functionality - you can't mask a freehand drawing).
As masking only works on the base layer, anything that the GM wants to mask should be put on the base layer - tokens that are used for mapping, etc.. If you want to hide NPC tokens don't put them on the base layer, put them on the top layers and use the individual token "visibility" setting (or the visibility setting for the NPC in the combat tracker) to hide/reveal the token to the players.
Grid settings (on/off), offset and size are the same across all 3 layers - there is 1 grid throughout. Other grid functionality is specific to an individual layer - lock tokens, snap-to grid, etc.. Be careful which layer you change these settings on as you will have to be on the same layer if you want to change them later.
Drawing (and erasing of a drawing) only works on the top layer. Drawings are never masked so there is no point in having drawings on any layer other then the top layer - this helps to keep memory use down too.
If you open an image that was from a campaign that was created without the layer extension then everything will be on the base layer. With the exception of the grid - this will be synchronised across all layers.
GMs can select targeting on the lower layers (if there are tokens on those layers) - but I don't think this will work in any way, especially as PC and NPC tokens should be on the top layer anyway. Essentially the targeting arrows will appear if the GM "targets" a token on any layer. This could be confusing so GMs should keep an eye on this... I hope to be able to limit targeting to the top layer only in the future.
Shortcuts (pushpin) that link to campaign entries can be put on any layer - but they are only active (can be selected) on that layer, even though they are viewable on the higher layers. Note: If you open an image from a module that has pushpins these will be visible across all layers but only selectable on the base layer.
For encounters with token placement created in a campaign that didn't use this extension (or a previous version) the extension will convert the token placement layer to the top layer on-the-fly so that the NPC tokens are placed on the correct layer. The original encounter record is not changed.
Things to be aware if you've used to the older extension:
Grids are now on all layers - I found I frequently needed the grid on the base layer to allow me to align mapping objets correctly.
Grid controls (size and alignment) and add grid/remove grid will affect the grid on all layers no matter which layer you do the operation on.
Drawings only operate on the top layer.
When opening an image it always defaults to the top layer selected.
Any questions/issues please post in this thread.