D3D and Access Issues with Enhanced Images Extension

Quote:

---

Originally Posted by Salva

I Forget to say that Im not sure if i understand this or how to do it.

---

CoreRPG is a Fantasy Grounds ruleset, just like 5E is a ruleset. You can create a new campaign using the CoreRPG rules - it is a lot lighter than the 5E ruleset. Testing in CoreRPG reduces a lot of the FG code and so can help identify if there is an issue elsewhere. v3.1.7 is the current "live" release of Fantasy Grounds (not the test release).

Quote:

---

Originally Posted by Salva

PD: Is there a max or recommended image size or just i have to try the smalller posible?

---

Go for the smallest you can live with.

As I mentioned in post #26, the issue is running out of the limited memory that the 32-bit Fantasy Grounds application can use. To the best of my knowledge there is no equation available that accurately estimates the amount of memory that a specific image will use. The more pixels an image has the more Fantasy Grounds memory it will take when it is opened in FG. You might be able to open two maps that are 10,000 x 10,000 pixels in size (probably not with the layers extension), but I'd be surprised if you could open three or four of them at once and still use Fantasy Grounds reliably! As Fantasy Grounds frequently has multiple windows open (all taking resources) it is best to make sure that each individual map/image is as optimized as it can be. Sorry, I know this doesn't give you a definitive answer to your question.

UPDATE: I've just done some testing with a few really large image files (10,000 x 10,000) and I can only open three of them before FG starts to behave weirdly and give very similar errors to those reported earlier in this thread.

Quote:

---

Originally Posted by Trenloe

CoreRPG is a Fantasy Grounds ruleset, just like 5E is a ruleset. You can create a new campaign using the CoreRPG rules - it is a lot lighter than the 5E ruleset. Testing in CoreRPG reduces a lot of the FG code and so can help identify if there is an issue elsewhere. v3.1.7 is the current "live" release of Fantasy Grounds (not the test release).

---

Ok got it.

Quote:

---

Originally Posted by Trenloe

Sorry, I know this doesn't give you a definitive answer to your question.

---

Actually it does, you have been very clear on what was making the trouble and many ways to fix it so thank you again.
The only thing that is pending is the test with players but i think it will be succesfull.
Cheers!!;)

Hii Salva - I dont think there is a hard and fast recommendation on dimensions other than smaller is better....
One more thing that might be affecting this - if you rework an image and change its dimensions but keep the filename the same - eg you overwrite the file in the images directory there is a quirk (bug) where the files original dimensions are retained.
Give the file a new name or make sure FG knows you deleted the old one first - eg delete - let F refresh and then copy in again.
That might have been causing some of your issues in post #23

Quote:

---

Originally Posted by damned

Hii Salva - One more thing that might be affecting this - if you rework an image and change its dimensions but keep the filename the same - eg you overwrite the file in the images directory there is a quirk (bug) where the files original dimensions are retained.
Give the file a new name or make sure FG knows you deleted the old one first - eg delete - let F refresh and then copy in again.
That might have been causing some of your issues in post #23

---

Hi damned, i actually saved each change with a new name to be able to test each one but if you dont point this, it will be sure that, one way or another, i would keept the same filename, so thank you for the info!! Only one question and to know: which kind of refresh you refer to? Closing and reopening FG o just closing and reopening the image/map icon? Or other kind of refreshing?
Thank you very much

You know when you delete an image in the images window and then it comes back if its still in the images folder - that might be sufficient... cant say 100% for sure... :)