adzling

Those models were acquired from the same source that battlefront acquired theirs from hence their similarity.

I'm travelling and not back in country until october 8th guys so won't be able to participate until then....gluck!

hey jd i like what you've got going there. it would be cool if you brought them along as a completely parallel force choice...i.e. another strain of humans...rather than simply adding them into the existing afv choice. i could see their roles (going from left to right) -light tank destroyer -light tank (same role as the paladins) -infantry fighting vehicle (carries a 76mm or 20mm or something similar..mebbe this strain of humans uses 90mm gun in this role...and a squad of inf.) -medium tank (could be fitted with a variety of weaponry for different roles....atgm turret, 120mm cannon whatever) -super-heavy tank (something the basic human strain doesn't use). I like this idea because it introduces force assymetry into the game... I'm travelling right now hence the lack of posts...

1>. no 2>. you'd have to ask clay

about 1). you're gonna need soemthing other than sketchup to the texture mapping. i.e. blender or wings 3d (if you're going for the free 3d apps). and you'll need to use the texture map and camo packs that were posted in the tank destroyer thread.... or make up your own

i really like the way it looks jdevlin. mebbe you should go with creating a line of vehicles for another human "variant" culture built around the concept of big, heavily armed, slow moving behemoths.... the idea of assymetric forces is really appealing to me..

dang, ok do you have a section of the splinter pattern you can provide? Doesn't have to be as big as the digital patterns you provided, Perhaps just a piece cut-out of the overlay for the existing texture maps. I can do some work to convert it to a seamless pattern. It won't be as nice as your final hand-drawn ones but at least there will be some visual continuity. Failing that i'll take the color chips cheers

Hey Clay, a few more things: 1). I guess given how nimble the drop-ships are and how localized (i.e. low-ceiling) the air defences are giving them flexibilty in their landing trajectory makes sense. 2). The idea of dropping directly from the drop-ship vs. refilling the local Asset Pool is kind of a fudge. I agree that in reality the way you would want to do it is refill the local Asset Pool as an asset runs out. Let's look at that for a minute. -The Asset Pool is a game device to maintain play balance via a logicaly constructed mechanism to restrict the player to certain unit choices and use his assets in a tactically appropriate manner (instead constantly dropping thors, hermes and hurricanes). It represents the fact that certain units are more costly/difficult to construct and so therefore are inherently rarer. -It's restricts the quantity of various units available to the players. A Liveship on Station in an optimal position could refill it very quickly, effectively removing most of the unit restrictions to the player. Although if one side ran through all 6 thors in 5 minutes they would still have to wait at least another 5 minutes + drop-ship deployment time for replacement thors to arrive on the battlefield. This becomes marginally so when the Liveship's Station status is sub-optimal as it could take up to 15 minutes + deployment time to refill your Thor stock....which could easily be longer than the duration of a game if you're already 10 minutes or more into it. If you Liveship Station status is "in-system" it's not going to be able to refill your Asset Pool at all as the time to planet is hours, much longer than the engagement itself. This means that you could give one side a very powerful advantage in numbers/ asset strength through manipulation of their Liveship Station status.....i.e. attacker gets more/better assets leaving the defender with a different set of tools to work with (see other post in chaos and order re: HQ, emplacements, stronger defensive turrets etc.). The other interesting scenarios this creates is to further increase the importance of drop-ships. If the defender can shoot down enough of your drop-ships then you won't have enough to replenish your Asset Pool AND ferry assets to the battlefield. Perhaps a player in a command track has access to a slider that lets him adjust how many drop-ships are available to ferry troops to the battlefield and how many are available to replenish the Asset Pool. The default setting is to have drop-ships give priority to ferrying reinforcements to the battlefield. But if the players really need those replacement thors they could divert dropships to replenish the Asset Pool forcing them to drive onto the map via the map-edge reinforcement zones in the mean time. Additionaly the player in the command track could have the option of changing the constituency of the Asset Pool over time. Of course the map designer could still have significant reinforcements to the Asset Pool for a defender w/out a local Liveship based on them being delivered to the Asset Pool via local transport infrastructure. and finally a couple more thoughts...... 1). The Station status of the Liveship could well be affected by events on the ground or a pre-timed event by the map designer. These could represent respectively a fight for a ground-based orbital battery or the arrival on Station of the opposition's Liveship. 2). The Station status of the Liveship should be represented in the GUI for the players, with a simple light/indicator that perhaps turns from green to amber to red to represent "optimal drop-orbit", "sub-optimal drop orbit", and "in-system". 3). infantry could have the option of being delivered direct from the Liveship by the orbitally fired drop-pods (smaller signature/smaller targets + not drawn from the Asset Pool) or via drop-ship from the Asset Pool (in which case they arrive WITH an IFV). The really nice thing about all this is it introduces some interesting tactical and strategic elements to the game that are really sci-fi. Your Liveship's orbital status becomes a critical part of your battlefield plans.

the named picture is just to help you with the deletion of faces....or at least that's how i read clay's description of the process

thanks Gordon. If you can post the other camo patterns that would be nice too looking forward to your tutorial on creating them in photoshop when you get a chance. i'm a mac persoange but for you windows people out there heres a nice camo pattern generator: http://www.vanderlee.com/plugins_camouflage_download.html

iceman- the 5 minutes drop times are avoided by calling your reinforcements from the Asset Pool per the post. It is a LONG post but if you read it again you might appreciate it more What the method described above adds is some complexity and rational for the delivery of reinforcements. If you MUST have an asset that has been depleted from the force pool when then it has to come down from orbit and that will take time, it's a trade-off. The current method of asset delivery via drop-ship would remain unaffected.

Hey folx the chaos and order thread got me thinking about the whole reinforcement/dropship delivery mechanisms and how we might better implement them to represent what's happening above and on the planet in advance of/during our tactical melees. First a couple of figures of note: Space shuttle takes @ 8.5minutes to climb to orbit (for an earth type planet). Space shuttle take about 30 minutes for a glide landing from first atmospheric contact (this includes a few maneuvers where they burn speed by turning in the atmosphere). Ok now forget those figures and let's look at some of the strategic situations the commander of a dropteam engagement might find himself in (these are related to the concepts i outlined in the Chaos and Order thread re meeting engagements, set piece battles etc): Liveship on station: The liveship has secured local orbital supremacy (driven off or killed any enemy orbital assets) and is in geosynchronous orbit at the optimal launch point for it's drop-ships (usually slightly in advance of planetary rotation). Quickest and most direct drop times @ 5 minutes from launch to touch-down (assuming as vertical a trajectory as possible and you burn almost all the way down). *This figure is a fudge* Liveship in stand-off mode: The Liveship is positioned out of the optimal drop area (perhaps it was driven off by the enemy's Liveship or is avoiding ground fire form the target area) but it is still in geosynchronous orbit. Second quickest drop times @10-15 minutes from launch to touch-down. *This figure is a fudge* Liveship in system but not in orbit: The Liveship has not been able to achieve orbital supremacy and is positioned in the local planetary system but is not in orbit above planet/target. Drop-ships have to conduct some intra-planetary flight in addition to atmospheric drop to arrive at target. Longest drop-times expect hours to touch-down (this is relevant though see later in this post). While this would preclude player drops from orbit in-game you would still be able to drop assets (pods and ships) to arrive at the onset of the engagement (it's assumed the commander ordered them in advance to arrive at the start of the engagement). Ground reinforcements: Force is receiving reinforcements from the ground. Arrival time to off-map staging area is dependent upon distance to reinforcements and local transport infrastructure. Ok now let's look at how the player receives reinforcements in drop-team. There is an Asset Pool defined by the map designer from which the player can select assets to be deployed either by drop-ship or map-edge reinforcement zone. Drop-ship reinforcement takes about a minute, much quicker than actual drop from the liveship would take. This is important as a player waiting 5 to 15 minutes for their AFV to arrive will get dang bored. Building on all the above assumption I suggest a mechanism for the asset pool and asset delivery to the battlefield that is somewhat more realistic than we currently have, introduces some interesting tactical considerations and just feels more "real". 1). Asset Pool. There is a secure off-map drop location that is used as a staging area for drive-on and drop-ship based asset delivery. This represents the Asset Pool as currently used in-game. Delivery to the asset pool is conducted in advance of the game start and represents either drop-ship based delivery or ground-based delivery or potentially both. 2). Reinforcements. Reinforcements (when a player call for an asset to be delivered to the battlefield) can be drawn from this pool either via drop-ship or map-edge delivery. In this instance the drop-ship is simply ferrying the reinforcement from off-map and not orbit and so arrives relatively quickly (and potentially has a different drop-approach see later). 3). Adding to the asset pool. You can add to this asset pool via liveship drops to the pool (to replenish specific AFV assets such as "more thors") or via ground based replacements if mandated by the map designer (we managed to unload get operational another thor from the mono-rail). The time to add assets to the pool would be based on either the Liveship's station status or an arbitrary time for ground replenishments by the map designer. If the Liveship is in orbit you could replenish the pool, if not then the time required would be prohibitive. What this would mean in-game: The above Asset Pool concept would mean that most dropships are conducting ground-based ferrying operations from the Asset Pool to the area of engagement. This is represented by the common 1 minute drop-time. This would not preclude a drop directly from a Liveship if you wanted to depending upon the Liveship's station status. Of course this drop will take longer (5 to 15 minutes) however the asset would NOT be drawn from the Asset Pool. Run out of thors? Drop another from orbit but you'll have to sit on your hands for 5 minutes AT LEAST. Liveships are the only method of drop-pod delivery. Drop-ships and drop-pods take the same time to arrive from orbit which as stated previously depends on the Liveship's station status. This puts somewhat of a crimp in johhny-on-the-spot turret drops and to rectify that somewhat my suggestions are: 1). during the deployment phase the defender doesn't have to wait for drops (as it is currently). 2). during the deployment phase the attacker can specify multiple drop-pod drops to arrive at the start of the game (no waiting time however quantity should be limited to avoid instant map saturation, perhaps 3 at a time?) with any subsequent in-game drops taking the full time based on Liveship station status. 3). Instead of calling for a series of (3?) Liveship delivered drop-pods to be delivered at the end of the deployment phase the attacking player can call for a SINGLE drop-ship delivered asset that is in addition to the force pool. Normally this would mean waiting 5 to 15 minutes but in this instance it's assumed the commander has ordered the asset to be delivered from the Liveship in advance of the engagement to coincide with the arrival of the rest of the force from the off-map Asset Pool. 4). Because drop-pods and drop-ships can now take up to 15 minutes to arrive based on Liveship station status i suggest the player no longer has to wait for their arrival but once he has called for one to be dropped he can then switch to a bot or other on-map asset. Drop-ship flight trajectory. This will vary depending upon where the drop-ship is coming from. 1). From the off-map asset pool: flat n.o.e. from closest map edge to target location wherever possible (taking into account air defenses). If the drop-ship cannot plot a n.o.e. trajectory from a map edge to the target (due to intervening terrain or air defenses) the drop-ship will notify that it is not a useable drop point and prompt the player to select another. 2). From orbit: The drop-ship drops steeply to location off-map shedding the majority of it's speed prior to entering the map then has a similar approach vector as a delivery from asset pool. IF the drop-ship cannot land in the location using this method (due to intervening air defenses) it will try to compute a trajectory that places it in the landing zone via a more vertical approach path. This will obviously result in more vertical approach that opens the drop-ship up for targeting as it completes it's final almost vertical descent. Assumptions: secure off-map drop location is used as a staging area for drive on and drop-ship based asset delivery. This represents the Asset Pool. Assets can be drawn from this pool either via drop-ship or map-edge delivery. You can add to this Asset Pool via liveship drops to the pool (to replenish specific AFV assets such as "more thors") or ground based replacements. Most dropships are conducting ground-based ferrying operations from the asset pool to the area of engagement. This is represented by the common 1 minute drop-time. You can drop directly from a liveship if you want depending upon the Liveship's station status. Liveships are the only method of drop-pod delivery. Drop-ships and drop-pods take the same time to arrive from orbit. The one logical question this brings up is "why doesn't the commander drop every damn asset at once and overwhelm the defender?". Well perhaps the Liveship is engaged in multiple operations in-system or on-planet and must spread his resources across multiple operation. So he picks the minimum force combination he believes can capture the objective so he has other assets available for other objectives. Naturally any commander worth his salt retains some strategic reserve to be committed to tight tactical situations, hence the drops directly from orbit. thoughts, comments, ideas?

i put some of this stuff up on the wiki

hey poesel, any way we can hlep each other sure. how should i send the sketchup files to you?

hey poesel, i'm working on a concept for an alien race of afv's that would use some relatively advanced technology (including force fields). it would be nice if the force fields used on the liveship-human produced afv's were somewhat limited. I was thinking about this issue last night and i think a force field that works as a simple add to armor thickness and has to be synced to the gun so that when the weapon is fired the force field is turned off for a 1/4 second would be a good compromise for the human tech. the force field generator should be LARGE and HEAVY so that only a BIG afv could carry it and would have to make some sacrifice in SPEED to carry it. ions could go right through it unimpeded (would make those ions a little more useful).