Tempestzzzz

Comet I

Here's the Morris C9B SPAA. A slightly reworked version of my mod for CMFI.

While we wait the modding master to perhaps arise once again, I couldn't help myself.

So here's the first of a few mods of weathered vehicles for the Downfall module. Don't know how many I am going to make, but it certainly won't be all the new Downfall units.
Here's a Dropbox link for the Pershing - but it will only be temporary until the files have become available on https://www.thefewgoodmen.com/cm-mod-warehouse/



 

@BFCElvis Every few days or weeks people show up on the unofficial CM discord server asking for help with the AMD cards, and every time we can only tell them that they either must roll back drivers, or if they can't roll them back (which the newer cards can't be) then they should seek a refund.
This issue has been going on for over a year now, and I think it's about time that there should be an announcement or warning on the BFC store page and related sales sites like Matrix, Slitherine, and Steam, that currently CM is not supported on AMD cards.
You already do this for integraded chips on the battlefront.com site, but I think it should be explicitly mentioned for AMD cards as well. Very few people know what OpenGL is or what cards support it.

Completely agree, this is unacceptable. I'm not buying a single CM product until this is resolved, why pay for a non legacy product that doesn't work on modern drivers for 6-8 months at a time? Armored brigade 2 might be the better option if this doesn't change by the time that releases. 

You really are the dumbest person on the planet man. Yeah it will be fun to work for free to fix this companies game, I love doing free work for corporations. You absolute brainlett

Thank you to the people in here actually trying to help, or distributing good info to the rest of us, I'm sorry BF can't be bothered to make their own game work, hopefully this latest post is right and the issue is resolved for now.

bro the amount of fanboys in this discussion is crazy lol

If you have nothing besides "UHHHH have you tried fixing it yourself??" or "ummm you said you don't like that BF hasn't fixed this but you haven't condemned every other company in your post????" it really should just be deleted outta here. some of us are coming here because we can't get refund cause we've spent our time trying to fix this game only to find out that it's just a issue the dev is refusing to solve. Let us actually either get a fix or wait to here from them that they got off their ***. If you want to post y our "I"m very smart" just go to reddit like this does not seem like the place

Known bug. At least I know about it hahahaah.
Been there for awhile.

When you have a CTD doing these kind of things-that is kind of good. CTD means it just isn't going to work. When you have corruption like this -ugh- means stock file & addon are crosstalking to each other-something has to be hex edited Ugh. Your knee deep in the Big 'muddy'

If you have CM: Shock Force and Afghanistan they share the same Mosques and single small building really haven't investigated in depth the file structure. But what I propose is to snatch the single story small building with a Mosque roof option and using worm holes, The Space/Time continuum, E=Mc2 and Black Magic.
I recolored the turquoise dome to something simpler (I even recolored the damage textures to to get rid of the turquoise color-finally mastered that damn magic wand tool.). The outside walls are the right color-but could be a bit more bleached white with dirt and dust at the bottom of the walls. But that eye candy can wait. Got to get the building in game. If it can get in the game you can change a bunch of texture stuff like the roof, wall textures, sill, parapets and doors etc etc in the Scenario Editor. Tunisia was very, very poor back in the day-Their Mosques were not elaborate affairs and small. So this is I think a good representative of what was out in that desolate area.
If it works (not making any promises) will be in BRZ format for easy addition and removal from your Z File
Oh yeah-don't ask me to get your Rangers Javelin equipped STRYKERS, AK-47s and SAGGERS to deal with der Deutscher Afrika Korp. Ain't gonna happen. Just going to have to learn to dominate the battlefield with an M1 and a Stuart.

First the GOOD NEWS
I got the CM: Afghanistan building in game. Wall textures and blast
holes do appear.

Now the Bad News :mad:

Roof textures, parapets and the domed mosque roof isn't appearing. You can see the corruption on and around the roof. And I'm tying to limit to 2 story buildings-note the 3 story to the right.
Right now this is in the Modular Building screen of the Scenario Builder
I'm going to do something a lot of modders don't do now-I'm going to take a rest and actually play the game tonight-which I enjoy a lot.
Later.

Umlaut:
Thank you for your 2014 credit on flavor objects.
FWIW I use a ton of your Mods. Love your French Buildings. I was experimenting with a Dubonnet Ad...but like you the other building side mirrors it backward. Your solution works. Just put another building adjacent to the backward ad.  Why didn't I think of that😄
I don't mod anymore for public release. Just for me now.
Thank you again for credit.
So many games soooooo little time.

I know that BF are set on not releasing public betas, but this previous patch could certainly have done with wider testing and would have prevented posting of old python skits.

the problem here is that the behaviour ruins a decent fight against the "AI" and suspension of disbelief is cancelled at that point when the enemy are gladly rushing towards you. And you can't issue orders to the "ai"
I spotted the bug within 30 minutes of playing the patch release back in the day (and reported with saves etc)
The only official Battlefront employees posting here have been happy to spend plenty of time espousing their beliefs regarding current military/political conflagrations or posting AARs about future modules requiring undying devotion to purchase; but FFS it's about time they started talking about what the dev is doing ( as he won't post here) on what he has done regarding a game breaking issue - I have spent fricking HUNDREDS of frickin dollars on investing in a system I expected would give me a fair fight (let alone time spent). And before the apologists butt in, I am specifically talking CMBN; although the behaviour can be observed in other modules.
 Rant not nearly over. 
TL;DR:     talk to your customers (repeatedly) about their pain points or expect less income.  Or - declare that the residential support is useful but not as useful as the military dollar.
Man. This is like Cleese hating the Commies (and then told it's time for tea).
 
 
 
 
 

From my current experience with Instant Command  Pause it works as follows:
Individual soldiers are nailed to their current position within an AS´s 8x8m node grid. Any action requiring a single (or more) soldiers to relocate within that AS in order to execute a particular command, won´t move and participate. That can be "target arc", "target at" and "face". This then is oftenly indicated by a single soldiers "Waiting" state. Same for random medic selection. If by chance a potential medic is not farer away than 1m from a WIA and the TacAI selects him, buddy aid can be initiated. Otherwise another randomly selected guy farer away (>1m) won´t move and changes to "waiting".
None of that prevents single soldiers to react to changing circumstances, like spotting and shooting enemies if coming into LOS/LOF. They just don´t change positions and do everything applicable from current ones (incl. going to prone/hide, reload etc.)
I haven´t seen any shaken or broken units move away if Pause was commanded before the morale change to the worse. In orders phase these units then won´t show the "Pause" state in effect. But if rallied to a better state, it shows it still is.
So it´s left to a player to effectively "unhinge" some the TacAI abilities and there´s both pros and cons. Currently I find preventing (or delay correcting) high risk evade moves is most beneficial. Not just the "evade forward" ones but also many the other highly irrational TacAI choices. "Evade" needs more than just debugging and IMHO should be given a major overhaul.

 

I think many CMBN fans simply install the game but not the latest update which seems to be where the problem started.  I find updates are often very subtle and I rarely notice significant improvement - it's usually that some unit is missing or some graphic anomaly is fixed.   So, play should be fine with earlier versions.

its a version 4 bug i think has been said, i've got upgrades waiting but won't until this is sorted

I posted this about 6 threads down - “Bug with upgrade” (It also happens behind walls and in buildings I goin a message from a couple of guys who quit playing ww2 scenarios and a couple of hard cores saying - live with it. (These are the same guys who bitch if you knock any thing about the game)
Apparantly it’s been posted and reported numerous times with no reply from BF management - happens every time from them - if they can’t make money - so be it. (If I had new modules coming out - I’d fix the current problems before release so people buy it - just my thoughts)
As is - WW2 is unplayable BN especially. I’ll try the pause option though.
Really wanted to buy all the modules for ww2 - I have BN and SF and SF 2 but can’t as is.
 
 
 

nice work.  It was eventually acknowledged by Steve but no patch forthcoming - I expect nothing until well after the new RT module is released given how things move these days.

I'm not playing anything with bocage until resolved. Hopefully we can get an update soon. 
 
Thankfully that still leaves quite a lot. 

Hello,
I've gone looking for a thread posted maybe a year ago where I was originally made aware of the "evade towards enemy" behaviour (though probably an actual bug) that typically involves infantry behind hedgerows breaking that cover when under fire and running towards the enemy through gaps in the hedgerow (invariably to their deaths) that I can confirm I has been able to reliably replicate when I downloaded and played the saved game that was provided by a user investigating the issue at the time. From what I understand, this issue may only be specific to CMBN and seems to only have appeared after one of the recent patch/engine upgrades. I would have checked the status of the issue and would have posted on that thread there but I have not been able to find the thread curiously enough, hence this new thread.
So I have just started a mirrored CMBN H2H QB on a map that I know several other players have battled over, and I just had a most extraordinary occurence of this "evade towards enemy" behaviour (or whatever you want to call it).  I had three infantry teams lined up along a stretch of hedgerow in a defensive deployment, evenly separated by about 15m.  Behind them is a flat wooded orchard. In front of them is a road, beyond which the terrain gently rises, criss-crossed with some buildings and hedgerows.
On the second turn of making contact with the enemy directly in front of them, returning fire and taking some level of suppression, each team, at some point in the turn, decided to essentially break cover and run sideways along the hedgerow to the nearest infantry-sized gap in the hedgerows and run through the gap in to the open directly towards the enemy where they just get shot up.  When the teams actually break from taking casualties, the surviving pixeltruppen (eg. those that remained in place cowering behind the hedgerow) rout away from the hedgerow/enemy through the orchard behind them.
Units lined up behind hedgerows engaging enemy start of turn:

"Rattled" pixeltruppen running suicide through hedgerow gap to meet their maker:

For the full video experience, you can watch it unfold here:
First and second teams suicide
Third team suicide
I did wonder if I had inadvertently given move orders to my units during the previous orders phase (can happen if you just want to select one unit to issue a move order to but inadvertently double click it whereby also selecting all its subordinates and/or formation level units as well).  However, I can rule that possibility out: other units in the formation were unaffected.
Still not satisfied, I checked the QB map in the Scenario Editor.  All "Friendly Direction" parameters were correct for the battle.  I then created a scenario file using the same map and parameters and purchased the same units on both sides.  I then placed the exact same German teams from the same platoon from the same company etc that I had purchased in the QB in the same spots and attacked them with the same infantry (US paras).  Incredibly (or maybe not so incredibly), the same thing happened!  Suicide through the hedgerow gap.
Even better: I have created a scenario file (TEST GAP.btt) using the same QB map with all units in place.  All you need to do is load the scenario file, play it as a turn-based Hotseat (or SP Germans) and just press Go for both sides, no need to give any orders.  The units will start shooting and exchanging fire immediately.  You should see this behaviour with your own eyes occur within the first minute of battle:
TEST GAP.btt
So what is Battlefront's official stance on what appears to be on this undesirable TacAI induced behaviour?
"What issue?" (no response/acknowledgement) "Nothing to see here, working as designed"(if so please explain) "Yeah, can't fix it, too bad, sucks for you though" "Wow, looking in to it, hopefully find a fix, keep you posted" FWIW, I have forfeited that H2H QB I am playing.  I can't afford to have that kind of thing happen and take those kinds of cheap loses and just continue playing regardless, let alone think it won't happen again.  I think for now I am regretfully going to just avoid playing any CMBN (or at least anything with that hedgerow terrain) until this issue is resolved.

It's a well known bug. Maybe there will be a fix for it in a couple of years.

its a gamebreaker
 

I stopped playing.

Okay. Came back to normandy after a couple of years off. playing campaign. My troops are nice and safe at the top of a reverse slope. Letting them sit there and gain fire superiority while I circle other troops around flank.
All of a sudden - no orders given - when the enemy fires in their direction they charge the enemy machine gun. They stop about 10 yards away but most are cut down.
 
Wanted to see if it's the campaign so I played a smaller scenario. About 10 minutes in, my troops are safety behind concrete wall while I lay down machine gun fire from another spot and circle the back of the house. Again for no reason I hear "let's go men" and the get up and charge the enemy machine guns - two full squads cut down.
While I remember the panic problem with troops in 4.0 I never remembered this. Am I crazy or what?
John