Author Topic: Very Large Fields in 2.43.1e  (Read 2326 times)

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« on: March 24, 2008, 02:13:27 PM »
Previous versions support 12 field sizes, the largest being 96000 X 72000.

2.43.1e supports 100 different field sizes.  The first 12 are the same as before.  The largest field now has dimensions of 800000 X 600000.

Very large fields are interesting for many reasons not the least of which is that they can provide a degree of geographic isolation for evo sims.

Many beers....

Offline shvarz

  • Bot God
  • *****
  • Posts: 1341
    • View Profile
Very Large Fields in 2.43.1e
« Reply #1 on: March 24, 2008, 02:48:54 PM »
That's a large field.... Any reason for providing a user with 100 different options for a field size? Sounds intimidating and unnecessary. I'm actually more interested in non-regular field sizes - with one dimension being much larger than the other. Those could be used to create very large and shallow ponds or very deep wells. That would be more interesting for different ecosystems.
"Never underestimate the power of stupid things in big numbers" - Serious Sam

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #2 on: March 24, 2008, 02:54:01 PM »
It was pretty easy to do it this way and I wanted to keep the current field size options, but perhaps I'll change it so as to drop the number of choices but increase the size non-linearly beyond size 12...

Custom aspect ratios adds another degree of complexity.   Shouldn't be too hard to do.  That's next.
Many beers....

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #3 on: March 24, 2008, 03:08:13 PM »
Okay, I changed it.  Only 25 field size options now.  First 12 are same as always but they double every size increase beyond that.

Largest field is now 2496000 X 1872000  
Many beers....

Offline bacillus

  • Bot Overlord
  • ****
  • Posts: 907
    • View Profile
Very Large Fields in 2.43.1e
« Reply #4 on: March 24, 2008, 05:20:24 PM »
Could that cause problems with the xpos and ypos variables, seeing they are restricted to 32000?
"They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown."
- Carl Sagan

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #5 on: March 24, 2008, 06:18:22 PM »
Quote from: bacillus
Could that cause problems with the xpos and ypos variables, seeing they are restricted to 32000?
Nope.  They don't actually give absolute position.  They give you your position in 1/32000ths of the total field width/height.

EDIT:  For fields with dimensions > 32000 that is.  I've thought about changing this so that even for small fields, they range from 0 to 32000 instead of givcing the actual position, but that would break backward compatability in the leagues I suppose...
« Last Edit: March 24, 2008, 06:26:31 PM by EricL »
Many beers....

Offline bacillus

  • Bot Overlord
  • ****
  • Posts: 907
    • View Profile
Very Large Fields in 2.43.1e
« Reply #6 on: March 24, 2008, 07:09:04 PM »
Quote from: EricL
They give you your position in 1/32000ths of the total field width/height.

Does it use floating-point variables, or is it just accurate to the nearest 32000 units?
"They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown."
- Carl Sagan

Offline abyaly

  • Bot Destroyer
  • ***
  • Posts: 363
    • View Profile
Very Large Fields in 2.43.1e
« Reply #7 on: March 24, 2008, 07:34:50 PM »
All vars use integers. I presume it's rounded.
Lancre operated on the feudal system, which was to say, everyone feuded all
the time and handed on the fight to their descendants.
        -- (Terry Pratchett, Carpe Jugulum)

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #8 on: March 24, 2008, 08:01:13 PM »
Quote from: abyaly
All vars use integers. I presume it's rounded.
You presume correctly.
Many beers....

Offline Numsgil

  • Administrator
  • Bot God
  • *****
  • Posts: 7715
    • View Profile
Very Large Fields in 2.43.1e
« Reply #9 on: March 24, 2008, 11:47:02 PM »
You might also consider allowing the user to directly edit a single dimension.  Like click on the X dimension and you can type in to it to change the field size.

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #10 on: March 24, 2008, 11:49:40 PM »
Quote from: Numsgil
You might also consider allowing the user to directly edit a single dimension.  Like click on the X dimension and you can type in to it to change the field size.
That's my plan, but there's a test burden I'm not ready to bite off just yet.  One step at a time...
Many beers....

Offline bacillus

  • Bot Overlord
  • ****
  • Posts: 907
    • View Profile
Very Large Fields in 2.43.1e
« Reply #11 on: March 25, 2008, 12:06:06 AM »
You've just destroyed my faith in the .xpos and .ypos variables.

Maybe a better way to go is to have nested global and local locations, so that the global position returns a grid with 32000x32000 per square, which is then subdivided into the local coords.
« Last Edit: March 25, 2008, 12:07:42 AM by bacillus »
"They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown."
- Carl Sagan

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #12 on: March 25, 2008, 09:58:36 AM »
Quote from: bacillus
You've just destroyed my faith in the .xpos and .ypos variables.

Maybe a better way to go is to have nested global and local locations, so that the global position returns a grid with 32000x32000 per square, which is then subdivided into the local coords.
This behaviour of .xpos and .ypos is not new.  It has worked this way for larger fields for a while now.  Adding yet larger fields doesn't change anything except make it more obvious that the granularity of these change with field size.  Many various options were discussed in detail at the time this was addressed including your suggestion and the current behaviour was settled upon for various reasons not the least of which is a general aversion to providing bots non-local information.  The decsiion not to remove them entirely was made msotly for backward compatability reasons.

As it is, it still allows ant bots to rendevuez, F1 leagues to use exact positioning, etc.   I have no plans to change this.  I would however, be very happy to remove .xpos and .ypos all together if peopel would let me...
Many beers....

Offline JossiRossi

  • Bot Neophyte
  • *
  • Posts: 31
    • View Profile
Very Large Fields in 2.43.1e
« Reply #13 on: March 25, 2008, 01:41:35 PM »
With the far larger fields, having sims with infinite shots turned on is going to be a HUGE problem as there's so much space to fill. And sometimes having them decay the distance just might not be enough. I did a quick scan to see if you can control shot decay distance but I don't think I saw anything. Might be a good idea to have that option if it isn't already around.

Offline EricL

  • Administrator
  • Bot God
  • *****
  • Posts: 2266
    • View Profile
Very Large Fields in 2.43.1e
« Reply #14 on: March 25, 2008, 01:51:01 PM »
Quote from: JossiRossi
With the far larger fields, having sims with infinite shots turned on is going to be a HUGE problem as there's so much space to fill. And sometimes having them decay the distance just might not be enough. I did a quick scan to see if you can control shot decay distance but I don't think I saw anything. Might be a good idea to have that option if it isn't already around.
Good point.  I'll put that on the list.
Many beers....