Air pad Limit..
Moderator: Moderators
Air pad Limit..
Currently from what I have learned, talking both to Trepan, doing a test myself, and hearing of input from Thor working on nota. I have confirmed that Airpads are limited to a max of 2 per unit. This is all well and good for some small building but if someone wants a giant supercarrier of doom.. well we need more than 2.. My request is simply for someone anyone to up the limit to 8, 32, 128 or what have you, anything above 2.. This would be really helpful..
The "QueryLandingPad" COB call in RegisterAirBase is part
of the problem, the way COB handles call arguments is a little
messy.
I've got a patch to allow up to 16 pads per base if someone
wants to test it. We could also split up the QueryLandingPad()
into GetAirPadCount() and GetAirPadPiece() that would be
used as alternates for Spring.
of the problem, the way COB handles call arguments is a little
messy.
I've got a patch to allow up to 16 pads per base if someone
wants to test it. We could also split up the QueryLandingPad()
into GetAirPadCount() and GetAirPadPiece() that would be
used as alternates for Spring.
- 1v0ry_k1ng
- Posts: 4656
- Joined: 10 Mar 2006, 10:24
Made another small change, if you really want more then 16 pads,
then you can define the "QueryLandingPadCount(maxPads)" call. The
input value for arg0 is the default maximum number of pads (currently
16), and the value that you set it to will be used as the maximum.
then you can define the "QueryLandingPadCount(maxPads)" call. The
input value for arg0 is the default maximum number of pads (currently
16), and the value that you set it to will be used as the maximum.
Last edited by trepan on 10 Apr 2007, 21:16, edited 1 time in total.
I don't see the needs for such additionnal function, since in OTA, you could have loads of air pad I've personnaly scripted 4 air pad carriers, and TheRegisteredOne made ... hundreds pads carrier, simply with the regular QueryLandingPad function. OTA worked like that:trepan wrote:We could also split up the QueryLandingPad()
into GetAirPadCount() and GetAirPadPiece().
QueryLandingPad(var1,var2,...,varN)
{
var1=pad_piece_num_A;
var2=pad_piece_num_A;
....
varN=pad_piece_num_A;
}
When a plane wanted to load, it would call the QueryLandingPad(...) of the carrier, and it would test each of the returned piece, one by one in the order, and would land on the first that had no unit already attached to.
The QueryLandingPad function could be written to not return always the same pieces, or the same piece but not in the same order,.... For instance a bad script would always present the same four pad in the same order, which mean that when four plane wanted to get repaired at once, they'd all four first try the first pad, only one managing to dock, then the three remainding would all try the second pad, etc..., while with a better written script, pads would always be presented in a shuffled order by the function, so four consecutive call would return the same pads but not in the same order.
zwzsg:
1. It's already done, I've added QueryLandingPadCount().
(check a couple of posts above yours)
2. The QueryLandingPad() call is only called once after a unit is created
in the Spring implementation (and for unit team changes). You can do all
the crazy randomizing you want, but it wont do jack. I made a simple
modification to allow a flexible number of landing pads without rewriting
the AirBase registration code. If you want to write a dynamic version, go
ahead
1. It's already done, I've added QueryLandingPadCount().
(check a couple of posts above yours)
2. The QueryLandingPad() call is only called once after a unit is created
in the Spring implementation (and for unit team changes). You can do all
the crazy randomizing you want, but it wont do jack. I made a simple
modification to allow a flexible number of landing pads without rewriting
the AirBase registration code. If you want to write a dynamic version, go
ahead

- Shadowsage
- Posts: 73
- Joined: 01 Dec 2005, 05:50