Slow LCU movement question

Slow LCU movement question (Full Version)

All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition

Message

Gewehr_43 -> Slow LCU movement question (3/5/2019 9:26:32 PM)
Hi, all. Can anyone tell me why these guys are only move 1 movement point per turn? At this rate it's going to take them a month and a half to move one hex. The rate is the same for "combat" or "move" operational order and seems to be happening regardless of what hex I set as their destination. They have plenty of supplies and support. I'm really baffled as I've seen units slog thru the jungles of New Guinea faster than this. What nuance of this game am I missing after all these years? :) [image]local://upfiles/61877/8152A8A2500D4F5E998D40F4975CD0C1.jpg[/image]

Lokasenna -> RE: Slow LCU movement question (3/5/2019 10:11:29 PM)
Are they getting reset to Combat, out of Move, due to combat actions?

Gewehr_43 -> RE: Slow LCU movement question (3/5/2019 10:13:28 PM)
Nope. No combat actions at all. The Davao hex is clear of enemy units and has been for a few weeks. Not even any air attacks. Is the fatigue too high?

Gewehr_43 -> RE: Slow LCU movement question (3/5/2019 10:33:39 PM)
Eureka! Another unit was set to follow them and (presumably because they are a heavy artillery unit) they move very slowly. Canceled the follow command and the unit is moving like lightning!

GetAssista -> RE: Slow LCU movement question (3/6/2019 6:32:06 AM)
Artillery should not be snails either. Given it is a dirt road and both units are in the same hex, artillery should catch up to the pictured ID (march 13 miles) in max 2 turns. Now, when someone else is following that arty unit the situation can become complicated [:D]

Gewehr_43 -> RE: Slow LCU movement question (3/6/2019 12:21:08 PM)
Yeah, this actually isn't quite as cut and dried as I thought it was when I posted yesterday. I'm not sure if it's a bug, but it certainly looks to be. When I used the "set all to march" command (thus telling each unit to travel independently at normal speed), every unit made it to the next hex in a couple days. I subsequently had the 41st ID (pictured above) return to Davao after mopping up Japanese resistance and used the "set all to follow" when it was just the 41st and one other INF unit on the hex. Again, it was 1 movement point per turn. In any of these cases, the "lead" unit was always the 41st ID and no other units were set to follow other units. So, everyone should have just been following the 41st ID's lead. It appears to be a problem with the "set all to follow" command. While problematic, it's not a game breaker I guess.

m10bob -> RE: Slow LCU movement question (3/6/2019 4:06:25 PM)
What season is it?..Does the dirt road turn to mush in the rain? The direction of movement indicates an enemy IS present which may slow the advance. What is the density of the terrain off that single lane dirt road? While the fatigue is only 25%, it might even be a malaria zone? You have a good leader and loads of supply so I suspect what I mentioned, season and terrain.

HansBolter -> RE: Slow LCU movement question (3/6/2019 5:35:45 PM)
quote: ORIGINAL: m10bob What season is it?..Does the dirt road turn to mush in the rain? The direction of movement indicates an enemy IS present which may slow the advance. What is the density of the terrain off that single lane dirt road? While the fatigue is only 25%, it might even be a malaria zone? You have a good leader and loads of supply so I suspect what I mentioned, season and terrain. Unless he is playing an RHS scenario movement rates on roads aren't subject to seasonal variations. Infantry movement on a secondary road is 15 miles be day in move mode. Moderately high fatigue will reduce that to 12-14 miles per day. An infantry unit will make that move in 4 days even if fatigued. None of the possible effects you mention would slow a unit to 1 mile per day. Something seems bugged. I have used the "follow" command hundreds of times over tens of games and have never seen this. Follow is best used when river crossing where a shock attack will be mandated to ensure everyone crosses together. Outside of that use, I prefer the "all march" command for getting everyone in a hex moving to the same target.

rustysi -> RE: Slow LCU movement question (3/6/2019 5:54:40 PM)
quote: I have used the "follow" command hundreds of times over tens of games and have never seen this. +1

Lokasenna -> RE: Slow LCU movement question (3/6/2019 9:46:01 PM)
quote: ORIGINAL: Gewehr_43 Eureka! Another unit was set to follow them and (presumably because they are a heavy artillery unit) they move very slowly. Canceled the follow command and the unit is moving like lightning! Yeah, that will do it.

Lokasenna -> RE: Slow LCU movement question (3/6/2019 9:47:03 PM)
quote: ORIGINAL: rustysi quote: I have used the "follow" command hundreds of times over tens of games and have never seen this. +1 Slower units following faster units can slow the faster units down. It doesn't always work that way, but sometimes it does. Maybe it's a bug, maybe not. I forget what the intentions were. Long ago, I simply adjusted my practice to picking the slowest unit and having everything else follow that. That way, there was no confusion and no possibility of premature hex-shifting by vulnerable units.

rustysi -> RE: Slow LCU movement question (3/6/2019 9:53:54 PM)
quote: Slower units following faster units can slow the faster units down. It doesn't always work that way, but sometimes it does. Maybe it's a bug, maybe not. I forget what the intentions were. Long ago, I simply adjusted my practice to picking the slowest unit and having everything else follow that. That way, there was no confusion and no possibility of premature hex-shifting by vulnerable units. One of the main reasons I use the follow. I don't want an armored reg walking into 4 or 5 divisions by itself.[:D]

Dante Fierro -> RE: Slow LCU movement question (3/6/2019 9:58:17 PM)
What kind of rations have you been feeding the poor grunts?

rustysi -> RE: Slow LCU movement question (3/6/2019 10:04:15 PM)
Whatever 'Cookie' burns.[:D]

Dante Fierro -> RE: Slow LCU movement question (3/6/2019 10:22:24 PM)
Tee hee [:D]

Gewehr_43 -> RE: Slow LCU movement question (3/7/2019 1:19:10 PM)
This is the bone stock Grand Campaign scenario w/o historical start. It is July, 1943. I'm still not sure what the deal is with these guys. :/

inqistor -> RE: Slow LCU movement question (3/7/2019 11:16:14 PM)
My guess - it is some residue data. Either it tries to follow itself, or movement is not direct, it tries to move through the mountains on West. Just cancel whole move, and give it new orders.

wegman58 -> RE: Slow LCU movement question (3/8/2019 2:27:52 PM)
I had something similar. Took Lunga, took two weeks to follow the remnants to Tassafaronga. Even after the Imperial forces were eliminated I was moving at 3 (US Infantry Division, Seabees, etc.) between Tassafaronga and Lunga. Two weeks per hex. That struck me as wrong. Fatigue wasn't high. Well supplied and sufficient support.

HansBolter -> RE: Slow LCU movement question (3/8/2019 2:37:31 PM)
quote: ORIGINAL: wegman58 I had something similar. Took Lunga, took two weeks to follow the remnants to Tassafaronga. Even after the Imperial forces were eliminated I was moving at 3 (US Infantry Division, Seabees, etc.) between Tassafaronga and Lunga. Two weeks per hex. That struck me as wrong. Fatigue wasn't high. Well supplied and sufficient support. 3 miles per day is actually the correct movement rate for infantry through Jungle/Rough terrain. The hexes are HUGE. If you're not using roads cross country movement is interminably slow. Two weeks is exactly what I plan for when striking out across jungle/rough or wooded/rough with no roads. Familiarizing oneself with the movement rate chart in the manual helps dispell missperceptions. In the OP's case he was using a secondary road which should allow a rate of 15 miles per day. I took a look last night at a huge Russian stack (a full army) that just started moving forward down a secondary road after taking a base. I only rested one day before setting out and fatigue varied widely. Infantry movements rates varied from 15 all the way down to only 8 miles for one division that had 39 fatigues. Fatigue would have to be astronomical to reduce movement to 1 mile on a secondary road.

geofflambert -> RE: Slow LCU movement question (3/10/2019 7:00:50 AM)
I cut to the end rather than read all replies. Given the direction NE the unit is not using the road. You might get there faster by turning around.

geofflambert -> RE: Slow LCU movement question (3/10/2019 7:05:29 AM)
The engineer vehicles, half-tracks and scout cars will only move off road in that terrain one hex per day. A division without those amenities will move faster, maybe two hexes per day.

geofflambert -> RE: Slow LCU movement question (3/10/2019 7:15:31 AM)
Not to mention all those trucks. They were made for ripping down roads. Turn around and use the road. Here is what the terrain in that area looks like from a road. Your guys are using ropes and winches to lower those paperweights up and down ravines because the knucklehead commander can see where he's going and wants to go straight there. [image]local://upfiles/37002/BE2A8B12A6594088B9772340061B1407.jpg[/image]

GetAssista -> RE: Slow LCU movement question (3/10/2019 7:35:59 AM)
quote: ORIGINAL: geofflambert The engineer vehicles, half-tracks and scout cars will only move off road in that terrain one hex per day. A division without those amenities will move faster, maybe two hexes per day. Type of devices in the unit does not matter for the movement speed in this game. Only type of the unit itself does

geofflambert -> RE: Slow LCU movement question (3/10/2019 7:56:05 AM)
Now, let's discuss proper fighter aircraft tactics in the jungle. [image]local://upfiles/37002/807C088790674DF9BF9D76E41F29E16F.jpg[/image]

geofflambert -> RE: Slow LCU movement question (3/10/2019 7:58:11 AM)
quote: ORIGINAL: GetAssista quote: ORIGINAL: geofflambert The engineer vehicles, half-tracks and scout cars will only move off road in that terrain one hex per day. A division without those amenities will move faster, maybe two hexes per day. Type of devices in the unit does not matter for the movement speed in this game. Only type of the unit itself does Try loading them on transports and flying them over, then.

geofflambert -> RE: Slow LCU movement question (3/10/2019 7:59:18 AM)
Motorized units like this one move faster on roads than non-motorized units.

geofflambert -> RE: Slow LCU movement question (3/10/2019 8:13:19 AM)
Looking at this again I see that something is trying to move NE while this unit is moving SW along the road. It's in move mode so it should move about 15 miles a turn. I'm at a loss. Fatigue and disruption aren't enough to slow it down that much.

geofflambert -> RE: Slow LCU movement question (3/10/2019 8:19:27 AM)
I have had something happen to me on more than two occasions that I never figured out where I ordered a unit to move directly to an adjacent hex and it would show progress each turn and then all of a sudden it would arrive in an adjacent hex still moving toward the target hex but with progress reset to zero. Don't know if that's related to this. Maybe try reissuing the order but start out in combat mode rather than move mode, then switch it to move mode after a turn.

Yaab -> RE: Slow LCU movement question (3/10/2019 8:28:25 AM)
They are the new soldiers. They march on point shoes.

geofflambert -> RE: Slow LCU movement question (3/10/2019 8:29:42 AM)
quote: ORIGINAL: Gewehr_43 Eureka! Another unit was set to follow them and (presumably because they are a heavy artillery unit) they move very slowly. Canceled the follow command and the unit is moving like lightning! Do you have a save of that turn before you killed the follow order? Would be nice to see the whole stack and what the orders were for each unit. Something was trying to move up the ridge to the NE, maybe that somehow was interfering. [image]local://upfiles/37002/91BC3F3881694BD0B8C17EA0832472F5.jpg[/image]

Page: [1] 2 next > >>

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.671875