Revised ETA?

Prepare yourself for a wargaming tour-de-force! Conquest of the Aegean is the next generation of the award-winning and revolutionary Airborne Assault series and it takes brigade to corps-level warfare to a whole new level. Realism and accuracy are the watchwords as this pausable continuous time design allows you to command at any echelon, with smart AI subordinates and an incredibly challenging AI.

Moderator: Arjuna

Post Reply
User avatar
Brady
Posts: 6083
Joined: Fri Oct 25, 2002 12:48 pm
Location: Oregon,USA

Revised ETA?

Post by Brady »

The Skinny on the ETA is, now........?
Image


SCW Beta Support Team

Beta Team Member for:

WPO
PC
CF
AE
WiTE

Obi-wan Kenobi said it best: A lot of the reality we perceive depend on our point of view
User avatar
Arjuna
Posts: 17768
Joined: Mon Mar 31, 2003 11:18 am
Location: Canberra, Australia
Contact:

RE: Revised ETA?

Post by Arjuna »

Providing an ETA is not a $64,000 question but yes we are running behind. One of the culprits is the Mixed Mode Movement code, which is proving to be a HUGE undertaking. Given the very steep terrain in the area of operations we decided that we had to address this issue. In HTTR there are no slope effects ( hey Holland's effectively flat, right? ) and there are no locations on the maps which are traversable to one moveType but not to another - eg. foot units can traverse but motorised cannot - ie all locations are either traversable or not for all unit types.

So we have added slope effects, which reduce the speed at which units can move on sloping ground. If it gets too steep, then movement is prevented. For foot this cuts out at around 60 degrees, while for motorised it cuts out at 30 degrees. So now we have cases where foot units can enter a location with a 45 degree slope but motorised units cannot. This causes heaps of problems for the AI that has to handle cases where, for instance, a foot infantry unit that is currently half way up a mountain is assigned a motorised AT troop and ordered to move to another location. The very start location for the boss( the Inf coy ) is impassable to the motorised AT troop. So this has meant quite a bit of revision and modification to our code.

We're almost done on that. Hopefully, we will be able to get out a new beta build for our testers later this week ( touch wood! ).
Dave "Arjuna" O'Connor
www.panthergames.com
User avatar
Brady
Posts: 6083
Joined: Fri Oct 25, 2002 12:48 pm
Location: Oregon,USA

RE: Revised ETA?

Post by Brady »

Ty for the reply, this goes to show just how great this game will be, the atention to detail is impresive.
Image


SCW Beta Support Team

Beta Team Member for:

WPO
PC
CF
AE
WiTE

Obi-wan Kenobi said it best: A lot of the reality we perceive depend on our point of view
thecker
Posts: 30
Joined: Sun Sep 05, 2004 8:24 am

RE: Revised ETA?

Post by thecker »

I would think that even in holland there would be terrain types impassible to motorized...like woods or marshes?
User avatar
CriticalMass
Posts: 599
Joined: Mon Mar 31, 2003 9:37 pm
Location: London, UK
Contact:

RE: Revised ETA?

Post by CriticalMass »

ORIGINAL: thecker

I would think that even in holland there would be terrain types impassible to motorized...like woods or marshes?

I think in HTTR even these seemingly impassable terrains do in fact have implicit tracks and trails which allow a degree of movement to all (even major rivers are passable, somewhere). I think a mountain side track is another proposition.

TANX
Andrew
I decided to ignore my orders and to take command at the front with my own hands as soon as possible
- Lieutenant General Erwin Rommel
pamak1970
Posts: 32
Joined: Mon Mar 01, 2004 3:51 am

RE: Revised ETA?

Post by pamak1970 »

ORIGINAL: Arjuna

Providing an ETA is not a $64,000 question but yes we are running behind. One of the culprits is the Mixed Mode Movement code, which is proving to be a HUGE undertaking. Given the very steep terrain in the area of operations we decided that we had to address this issue. In HTTR there are no slope effects ( hey Holland's effectively flat, right? ) and there are no locations on the maps which are traversable to one moveType but not to another - eg. foot units can traverse but motorised cannot - ie all locations are either traversable or not for all unit types.

So we have added slope effects, which reduce the speed at which units can move on sloping ground. If it gets too steep, then movement is prevented. For foot this cuts out at around 60 degrees, while for motorised it cuts out at 30 degrees. So now we have cases where foot units can enter a location with a 45 degree slope but motorised units cannot. This causes heaps of problems for the AI that has to handle cases where, for instance, a foot infantry unit that is currently half way up a mountain is assigned a motorised AT troop and ordered to move to another location. The very start location for the boss( the Inf coy ) is impassable to the motorised AT troop. So this has meant quite a bit of revision and modification to our code.

We're almost done on that. Hopefully, we will be able to get out a new beta build for our testers later this week ( touch wood! ).

One question regarding the above.
Does the new movement system and limitations apply to forests also ,or only to slopes?
Golf33
Posts: 701
Joined: Sat Mar 29, 2003 6:54 am
Location: Canberra, Australia

RE: Revised ETA?

Post by Golf33 »

We are currently reviewing movement data across all terrain types as part of the introduction of the new movement system. We'll be able to provide more details at a later stage in the process.

Regards
33
Steve Golf33 Long
Image
User avatar
Arjuna
Posts: 17768
Joined: Mon Mar 31, 2003 11:18 am
Location: Canberra, Australia
Contact:

RE: Revised ETA?

Post by Arjuna »

ORIGINAL: pamak1970
Does the new movement system and limitations apply to forests also ,or only to slopes?

As Golf said we are curently reviewing this. but the short answer is yes it will. The new mixed mode movement code will enable us to prohibit one class ( eg motorised ) from entering a particular terrain type while allowing another class ( eg foot ) to enter it. So it will be possible in the MapMaker to say that forests are "no go" for motorised.

The net effect of the changes mean that we now support different movement tables as evidenced below. These are viewable from the MapMaker. In the example below, the darker the colour the easier or quicker a unit of that type can move, white is impassable ( eg magor rivers ) and red means the area is unreachable ( usually because it is surrounded by some impassable terrain ( eg. the tops of steeply sloped hills and/or forested areas on the Wheeled table below ). Note that for Foot units the bulk of the map can be traversed fairly easily, though a few mountain peaks are impassable ( white areas ). However, the area is not so easy going for motorised ( wheeled ) units.

Image
Attachments
MoveTables at 72dpi.jpg
MoveTables at 72dpi.jpg (165.51 KiB) Viewed 133 times
Dave "Arjuna" O'Connor
www.panthergames.com
User avatar
CriticalMass
Posts: 599
Joined: Mon Mar 31, 2003 9:37 pm
Location: London, UK
Contact:

RE: Revised ETA?

Post by CriticalMass »

Will there be any indication in from the UI that a certain area on the map is "impassable" or more specifically "unreachable". What are the ramifications of ordering a unit to move to an unreachable position? will it circle it ad infinitum trying to find a route "in"; or will follow its normal route until it can move no further, then, "hunker" down.

TANX
Andrew
I decided to ignore my orders and to take command at the front with my own hands as soon as possible
- Lieutenant General Erwin Rommel
User avatar
Bil H
Posts: 1705
Joined: Thu Apr 24, 2003 6:03 am
Location: Fredericksburg Virginia
Contact:

RE: Revised ETA?

Post by Bil H »

Hey Dave, I love the side by side comparison of foot and vehicle movement tables. Looks like armor will be relegated to the roads on that map, eh? The way it should be. Excellent.

This will make controlling the road network very important in COTA battles.

Bil
Ah, well, since you do not wish death, then how about a rubber chicken?

Sam the Eagle

My Combat Mission Blog:
https://battledrill.blogspot.com/
User avatar
Arjuna
Posts: 17768
Joined: Mon Mar 31, 2003 11:18 am
Location: Canberra, Australia
Contact:

RE: Revised ETA?

Post by Arjuna »

ORIGINAL: CriticalMass

Will there be any indication in from the UI that a certain area on the map is "impassable" or more specifically "unreachable". What are the ramifications of ordering a unit to move to an unreachable position? will it circle it ad infinitum trying to find a route "in"; or will follow its normal route until it can move no further, then, "hunker" down.

TANX
Andrew

Critical,

Don't worry. When you try and place an objective for a force at a location that it cannot enter or reach a check is made and if invalid the objective is automatically and instantaneously moved to the nearest valid location. See below:

Image
Attachments
Adjusted L..on 75dpi.jpg
Adjusted L..on 75dpi.jpg (157.79 KiB) Viewed 133 times
Dave "Arjuna" O'Connor
www.panthergames.com
User avatar
Arjuna
Posts: 17768
Joined: Mon Mar 31, 2003 11:18 am
Location: Canberra, Australia
Contact:

RE: Revised ETA?

Post by Arjuna »

ORIGINAL: Bil H

Hey Dave, I love the side by side comparison of foot and vehicle movement tables. Looks like armor will be relegated to the roads on that map, eh? The way it should be. Excellent.

This will make controlling the road network very important in COTA battles.

Bil

You bet and when combined with the new Delay code it means the Allies can fight an effective delaying action. [:)]
Dave "Arjuna" O'Connor
www.panthergames.com
User avatar
Plodder
Posts: 974
Joined: Mon Jul 28, 2003 3:56 pm
Location: New Zealand

RE: Revised ETA?

Post by Plodder »

Damn, this game keeps getting better and better.[&o]
Gen. Montgomery: "Your men don't salute much."
Gen. Freyberg: "Well, if you wave at them they'll usually wave back."
pamak1970
Posts: 32
Joined: Mon Mar 01, 2004 3:51 am

RE: Revised ETA?

Post by pamak1970 »

Being myself Greek , i will agree with the rest here that the development team does a terrific job.

I do not want to overload you with questions but i would like to ask something else before i leave you to continue the development [:D]

How do you plan to deal with the movement of motorized infantry?
What i mean is that infantry can ride the carriers and use "wheel movement" but it can also get out, leave vehicles behind and march using "foot movement" to attack for example an enemy position .

Is there going to be an action like embark or disembark?
User avatar
Arjuna
Posts: 17768
Joined: Mon Mar 31, 2003 11:18 am
Location: Canberra, Australia
Contact:

RE: Revised ETA?

Post by Arjuna »

pamak1970,

Motorised and mechanised infantry units are classed as "motorised". The AI automatically disembarks them whenever they are 'deployed' or whenever they get close to enemy units and re-embarks them once they are not.

At this stage of development we will not be providing the users, or the AI for that matter, the ability to split the unit into two components ( ie foot infantry and vehicles ) so that you could send your foot component over terrain impassable to vehicles. To do this will require a major development effort and more processing power as effectively you double the number of units ( which in turn increases the load on route calcs and Line of Sight checks ).
Dave "Arjuna" O'Connor
www.panthergames.com
thecker
Posts: 30
Joined: Sun Sep 05, 2004 8:24 am

RE: Revised ETA?

Post by thecker »

Just as a thought, in PzC you can order your motor/infantry to go on foot, they then are foot units until they get next to their HQ, when they can be re-motorized. It is assumed that the base unit of a motorHQ is always motorized, no unit is drawn for the trucks they just are absorbed into the HQ/base unit.

I would think that alot of HQ/base units are motorized(other then german foot infantry)
most american units can only use motor transport by borrowing it from HQ(usally only briefly). Even though all american units were technically motorized , most rarely ever saw a truck, other then for supplies.
Post Reply

Return to “Conquest of the Aegean”