Images in the (Reference Manual) Builder

[lousilver]

Are there restrictions what images can be shown? For the first time I'm unable to plop one of my images into the API (nothing happens). Other images in the image list will show, but not not this one. It's one of my smaller maps in terms of file size (4.49MB), but the dimensions in dungeon draft are double than any other map i've made. Does that make a difference?

For clarity, I can post a hyperlink and open the image and look at it. What i can't do is place a thumbnail.

[Moon Wizard]

Our recommendations for maps are 4Kx4K or less in resolution (for performance), and 2MB or less for size (for load time and network transfer time). It sounds like your map is probably much larger than that, and may be hitting limits on your specific hardware or in the Unity game engine.

Regards,
JPG

[Trenloe]

@lousilver - for reference, this Wiki page details the recommendations for images: https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/2037547009/Developer+Guide+-+Product+Guidelines

[Zacchaeus]

So can you just clarify what exactly the issue is please. You say that this image isn't appearing on the image list? So by this are you saying that you have been unable to import this into Fantasy Grounds? If so that would seem to indicate that the image isn't in one of the formats that FG recognises. Does the image appear when you go to Assets > Images > Campaign (or Data if you put the image in the top level images folder)? Since you mention reference manual I assume that you are trying to add the image to a reference page - but how are you doing this? Are you dragging directly from Images>Campaign or are you importing the image into FG first and then dragging from the Campaign images list?

Assuming that you actually do have the image inside your campaign did you amend it in any way before trying to add it to the reference? By that I mean did you add a layer for something similar to the image. If you did then the reference manual won't accept such an amended image. You need to add the unedited image into the reference page first and then you can add any additional layers etc to the image.

[lousilver]

First, I just wanted to say that i'm always so impressed with the support from the devs and community. The following bullets correspond to the images I attached.

I can import the image, and I see the image in the image list. (1)
I can open the image and look at it. (2)
When building the refence manual, I can post a link to the image that allows me to open and look it. (3)
I am unable to drop the image into the image-block. Nothing happens. But other images will show. (3)

The image referred to above is 4.49 MB and 6400x7000 pixels. Even then that's with using 10ft squares instead of 5, otherwise the map would be much bigger.

I did a little bit of experimenting. It doesn't seem to matter if it's an image (e.g. a picture of a hag) or a map (with a grid etc). Some maps work (4000x2800), while others don't (3000x3000), both 4 MB. But a 13MB 3000x3000 map did show in the image-block. So, i'm not sure what the parameters are for what will show and what won't.

I'm not terribly fussed, because the image link works. I was just curious so that I know in the future what i can and can't show.

P.S. I've started using 10MB battle maps, and even players with clunkier laptops are ok (might take 20-30seconds to transfer).

[Moon Wizard]

The ability to display an image in the reference manual is tied to whether the image is a simple single image vs. an image with multiple graphic layers. The reference manual will only accept drops of image records which have a single image asset. If there are multiple assets, then you will not be able to drop in that way.

Alternately, you should be able to drag the raw image asset from the Assets window to the reference manual that you want to use, in case the extra image layers are for labels or other extra elements.

Regards,
JPG

[lousilver]

Ah ty. That makes perfect sense, and fits 99.9% of my needs. out of 300 images i've included so far, first time I ran into this, and easily worked around.