Create account / Log in

Understanding module size impacts (solutions)

Topics related to the main Vassal engine.

Moderators: uckelman, Tim M

Understanding module size impacts (solutions)

Postby msward1 » December 12th, 2016, 3:27 pm

I'm trying to understand the impact of modules size (functionalities) on the usability of a module.
And what impact this size has and how I can rework my modules to make it usable.

To all you Vassal guru's out there I'd like to heard your comments and recommendations.
I have a module I've just recently completed (sort of) which weighs in at about 136MB.
In the testing of this modules I've have a plethora of user issues.

Unable to load the module.
Unable to save a module scenario.s
Extremely slow loading of the modules and/or scenarios.
Commands which take minutes to complete.

So I've had users bump their Vassal (and individual scenario) heap sizes. Helps a little.
I've streamline the module so there are no excess images or files.

Still the module seems to be marginally usable.

So suggestions?
msward1
 
Posts: 24
Joined: July 23rd, 2015, 4:03 pm

Re: Understanding module size impacts (solutions)

Postby jimpyle » December 14th, 2016, 11:24 pm

What's the size of your map in megabytes?

Jim
User avatar
jimpyle
 
Posts: 65
Joined: March 4th, 2008, 9:17 pm

Re: Understanding module size impacts (solutions)

Postby uckelman » December 14th, 2016, 11:42 pm

Unused images in the module will have no impact on memory usage when the module is loaded. Dimensions of your map images will. (Note that dimensions are distinct from image file size, which is mostly unimportant.)
User avatar
uckelman
Site Admin
 
Posts: 8841
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Understanding module size impacts (solutions)

Postby msward1 » December 15th, 2016, 2:26 am

Ahh.
Thanks guys.

Got 3 maps 122x33, 122x33 & 122x58 (inches).
12.5, 23.5 and 58 (MegB).

Tried to minimize the number of maps to avoid the splice join stacking issues (Bug:1860944).
Guess that was a mistake.
Dam.
msward1
 
Posts: 24
Joined: July 23rd, 2015, 4:03 pm

Re: Understanding module size impacts (solutions)

Postby Brent Easton » December 15th, 2016, 2:42 am

The important thing is the Dimension in pixels, not inches. Vassal doesn't know anything about physical size, only pixels. Those maps sound very large, depending on the Pixels per inch, which is most probably causing your problems. I tend to cut large maps to pieces around 3000x5000 pixels and have no problems. Those numbers are somewhat arbitrary based on some early maps I worked on and I've kept using that size. Somewhat larger would probably work also.

If the maps are hex based, then you can avoid any issues with units stacking on map joins by making sure you cut the maps so the cuts do not run through any hex centers.
User avatar
Brent Easton
 
Posts: 3161
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Re: Understanding module size impacts (solutions)

Postby msward1 » December 15th, 2016, 2:59 am

Thx Brent.
I'm about twice that and more.
11628 x 3143 (95.76px/in)
11628 x 3289 (95.94px/in)
11788 x 5604 (95.94px/in)

Guess I need to rethink the map sizing.
I did try the splicing off the hex center didn't seem to make much different.
Maybe I was still to close.
msward1
 
Posts: 24
Joined: July 23rd, 2015, 4:03 pm

Re: Understanding module size impacts (solutions)

Postby Brent Easton » December 15th, 2016, 3:15 am

I would cut each of those maps into 2 and see how that goes.

Here's a sample showing where I make the cuts, no where near hex centres
Attachments
sample.png
sample.png (165.91 KiB) Viewed 6920 times
User avatar
Brent Easton
 
Posts: 3161
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Re: Understanding module size impacts (solutions)

Postby uckelman » December 15th, 2016, 1:12 pm

Thus spake msward1:
> Ahh.
> Thanks guys.
>
> Got 3 maps 122x33, 122x33 & 122x58 (inches).
> 12.5, 23.5 and 58 (MegB).
>
> Tried to minimize the number of maps to avoid the splice join stacking
> issues (Bug:1860944).

Are you sure that's the correct bug number? Last I checked, we didn't
have any bugs with numbers of more than five digits.

> Guess that was a mistake.
> Dam.

Dimensions in _pixels_ is what matters for memory usage.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8841
Joined: December 10th, 2007, 9:48 am
Location: Durham, England


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 2 guests