Warzone 2100 Forums

Very good. All we need is the max tiles increase, then.

My changes:

map.cpp -- line 100 map.cpp -- line 132 map.h -- line 340 Checking the code to make sure it compiles and plays nice.

.

I'm assuming you upped the height of mountains? If so, you may wanna check VTOL fly-over behavior.

.

Yep, gonna do that in a bit. I accidentally overwrote decals with 2.3.9 versions, so I'm fixing that at the moment.

So far so good. There's no visible performance hit as of yet.

Next thing I have to do (after changing the VTOL flight height maximum) is compile a Master version of FlaME with the 'GUTS' support and get a quick test map made.

I'm getting tired though and it's been a long day, so I may do that tomorrow.

Updated to v2.

• Include changes just proposed by Goth Zagog-Thou.
• Cycle the colors for map previews. Tileset 4 is previewed as arizona, tileset 5 is previewed as urban, etc.
• Rely on tile types when guessing whether a tile is a water or a cliff, not on ground type names.
  • This allows to use multiple cliff textures on one tileset without encountering this problem.
  • This allows using multiple seabed textures on one tileset.
  • I don't yet understand how to make multiple water colors on one tileset, and how will they blend if it is made.

Updated to v3.

Fixed oversized seabeds, fixed map preview color cycling (3%3!=3 lol).

Anything else? What should i do now? Should i post a ticket with this patch?

Note: the patch is still compatible with both master and 3.1_beta11!

FULL OF WIN!

(after changing the VTOL flight height maximum)

How is it going? Do you have a sample map to try?

Probably another thing that needs to be tried is camera movement. So that it didn't dig into the ground on low views.
Anyway, i'm sure we had stretched heights in master at some point, but that was removed. Is anybody aware of this story?

.

Btw Goth - is this the one you are working with?: /* primitive 'bang- bang ' vtol height controller */ function.
.

Good morning fine people.

Great job, NoQ! I believe that covers everything. Loos great btw.

@Rman: Haven't checked yet. I went to bed early last night since I haven't slept much at all during the current heat wave. Had errands to run and bills to pay today, and more business to do later on this afternoon (Grandson's b-day party .. and yes, I'm somebody's grandfather ). I probably won't get to it until tomorrow, so if anyone else cares to change the height, be my guest.

.

Gramps!! Wow. I thought only me and Kim were the anchient ones.

I messed around with the function years ago trying to figure out how to deal with vtol speed bump stalls but I ain't doing anything like that anymore. Just FVMs work and taking into account these type changes in my Machinima component shoots. If this works out I'm visuslizing being able to do some hair-raising vertigo camera work.

.

I think that can be arranged.

/src/move.cpp:62
That takes care of VTOL heights. I'll check for transporter heights, but I think those use the VTOL values above. They do.

I think this shouldn't be altered at all. It's "above terrain", not "above zero". In vanilla VTOL_HEIGHT_MIN==250 is less than maximum terrain height. I didn't check though.

So far it looks like it's 'above zero'. I'll test it more. At least all of the code is playing nice so far.

I haven't added your .patch in yet. Just how are these applied, anyway? I always wanted to know how that's done.