Bulletpoint

Are you sure about this? As far as I know, AI movement orders are always completely robotic - 'move group 5 to position 2 starting at mission timer 12:00'. Doesn't seem to take anything else into account, apart from the general movement type. But I'll happily be proven wrong here.

I think it should not be up to the customers to curb their enthusiasm and hopes/ideas for the game, but to the game developer to decide which ideas to include and which ideas to discard. In the end, it's their game and their decision and responsibility what to do. I see no reason to hold back our ideas and suggestions...

How about this idea, to make things a bit more simple: You can give any order to any HQ unit (flag icon) at any time. But all subordinate units must be within voice or close visual range of their HQ to be given an order.

It would be worth it for early morning scenarios with fog - that usually lifts quite quickly once the sun gets up.

Of all the things I've seen people wish for, this gets my award

I'd like to see the thread where players demanded this, but I haven't been able to find it on the forum or elsewhere. Do you have a link?

Try setting Texture Filtering to "Quality"? That helped for me. Still the odd crash, but much fewer.

No, the suppression meter is a reflection of subjective suppression, in other words suppression relative to the current variables of the unit (experience, moral etc.). It is not a measure of objective, actual incoming fire. That's why you see the suppression meter going bananas when Green troops take fire, while it changes only slightly with Veterans in the same situation. I always believed the suppression meter showed an indication of the objective amount of incoming fire a team is taking. And I believe veterancy just makes the meter empty quicker, as well as possibly making return fire more accurate despite suppression. But it's possible I could be wrong here. Did you try to set up the same situation as in your video, but to use a good condition veteran squad?

Right, got you. I think it's not a matter of the AI "deciding" whether it can cause damage or not. I think it operates from a checklist of targets it will or won't shoot at. Somebody put a checkmark next to "suitable target: armour" for the 50 cal. If I'm correct, probably that checkmark should be removed. A 60mm mortar will also degrade tank optics (and tracks) with repeated hits. But you won't see 60mm mortars taking shots at tanks (maybe if they are unbuttoned, can't remember).

Your video doesn't show the suppression meter, but it does show your troops are green, nervous and under bad leadership. That means they will drop down much faster under suppression. I still believe it's the suppression caused by the incoming fire that makes them react - not because the way the hunt command works. If we assume that the hunt command makes troops stop and drop on receiving fire, then well led, highly motivated veteran infantry should do the same. By the way, they are not sound contacts - just contacts

No, they don't. In this case the centre of the action spot was the corner of the building. Ah, ok, it's a diagonal wall Hadn't thought of that. Yeah that's true. He does run to a different square then. It seems the corner peeking mechanic takes over and makes the troopers stick to the corners of the building in this case, instead of staying in their square. The game engine mistakenly believes that you want a guy posted at each corner, and tries to do that.

The team does notice taking incoming fire - this is shown by the suppression meter rising. When the meter becomes full, any movement order is cancelled and the team drops down. This happens both on hunt and on the other movement modes, so it's a different discussion. And if the team also takes a casualty, the suppression meter very quickly goes to max. I believe this is what you're seeing in the case of the unspotted marksman.

Straight walls always run through the centre of the action spots, dividing them in two, so I believe that pixeltrooper intended to stay in the same square, but had to run around the wall to reposition on the other side... I think you're supposed to face them more away from the building. You're clicking basically on the building itself - try to use the facing option and click on the small shed to the right instead. Does that help? That being said, I also have many problems making the corner-peeking mechanic work consistently, depending on what kind/size/angle of building it is.

Oh, they stop and hunker down when they take incoming fire. I think you might be confused by the fact that squads sometimes do not realize that they are taking fire in CM, even though sound and graphical effects indicate to you as a viewer that they are. No, I'm quite sure they don't stop because of incoming fire as such. They stop if 1) they spot an enemy, 2) they get suppressed to a certain (quite high) level. Just as any other movement order gets stopped if the moving team gets suppressed enough. I've seen scout teams take repeated MG42 bursts and still hunt on until one of them got killed or their suppression meter filled up, whatever came first.

Sounds like the smoking gun .. Pun intended. I think it's pretty clear the 35m range was for both flamethrowers firing at the same time, and that it would have a 60m range when only firing one at a time.

Well, I think that confirms that they generally stopped producing stuff that didn't work.

Same here. I chose not to rest, and expected my troops to take a hit to their fitness, but they seemed fit as ever. Either it's the effect of the Panzer chocolate, or somebody forgot something I suppose. The choice/consequence thing was poorly executed, but it's still a great campaign.

I never knew this. Will have to try it out.

The manual is wrong here. The unit only stops when actively spotting an enemy. (or when taking enough fire to fill the suppression bar, which generally cancels any move order)

It's very debateable, yes. All I'm saying is that if it's the same weapon, then it should have the same range - extra overshoot range would then also be the same... And it's possible, as @RockinHarry argues, that it could be the Wehrmacht turned down the pressure or something for this particular installation. I don't know. It just seems an odd thing to do, especially as it doesn't seem like there would be less space for compressors and fuel in a halftrack than inside a Hetzer. Another thing to consider is that they actually made 300 of these things. If they had been a mistake, I think they would have stopped much earlier, just like with other rare limited edition test runs. They started making them in 1943, and in 1944 they made an adjustment (removed the small rear hose-based flamethrower). But they didn't stop making these strange halftracks, even though there was a great lack of normal halftracks for the Panzergrenadiere - which were meant to ride halftracks, but many never received any. So we might assume they worked, somehow. And I don't see how a halftrack that needs to enter handgrenade range to attack could work. But yeah, I want to make clear I am not claiming to know better than anyone about this subject. I just thought there might be something here that doesn't add up

Thank you, thank you... will come around with the hat in a moment, please spare a coin for a struggling artist...

The main point is that if it's the same flamethrower as on the other German vehicles, then the range should probably be the same.

Conclusion: I would like to suggest to Battlefront to update the Halftrack flamethrower range to 60m, based on following source: "According to the Osprey New Vanguard book on Flammpanzer, German Flamethrower Vehicles 1941-1945, the SdKfz 251/16, Panzer III, and Hetzer flame vehicles all used the 14mm Flammanlage Bauart Koebe (or Koebe-Gerat) flamethrower system. It had a max range in all applications of about 60m for burning fuel, and 50m for unlit fuel."

I would think this is why we are seeing the shorter range in game. I can't think of another weapon system in the game that would have its effectiveness cut in half if both barrels are firing at the same time. The code then must be set for the short range to keep things "balanced". I think it's probably just that the sources BF took their numbers from were confused. A number got put down many years ago by someone not realising it was from when both flamethrowers fired at the same time.. that number then got copied and re-used elsewhere, and became accepted fact. Maybe they can if both gunners spot different targets on opposite seides of the vehicle at the same time, and survive the 8 seconds aiming while getting shot at from 30m range Which won't happen very often. But when giving a target order, only one FT will fire.

Then again, that footage was staged, so maybe they didn't go full throttle.. trying not to roast too many actors