Kevin2k

I just did a test with a purpose made map. Soviet scout cars and German Kubelwagens separated by a mortar smoke screen. The scout car HMG gunners see and shoot through the smoke screen.
This was also reported as bug for Cold War v1.00 and current v1.01, as shown with M113 HMG gunners, just this week. I don't know if the problem is isolated to just M2 .50 cal HMG gunners.

I just did a test with a purpose made map. Soviet scout cars and German Kubelwagens separated by a mortar smoke screen. The scout car HMG gunners see and shoot through the smoke screen.
This was also reported as bug for Cold War v1.00 and current v1.01, as shown with M113 HMG gunners, just this week. I don't know if the problem is isolated to just M2 .50 cal HMG gunners.

In principle that is how it works yes. But then it gets more difficult to come up with numbers about what is possible. I would guess the 6GB total I mentioned is fine unless you are doing something specific besides it: like having a Video streaming service active or working with very large images in Photoshop .
 
 

Great. Trust it will be solved in due time.
I do wonder, the team could not force one of the Beta testers to run more modest hardware? (shortest straw ) The lower detail model issues mentioned in this topic would be obvious on such. Whereas on a high end system the game-engine adaptive detail scaling tends to hide any of these lower detail models from view. (Running a Desktop with CPU i5-3550 and GPU Radeon HD6670 myself)

I suppose it is the usual distant floor distortion effect, for which GPU drivers invented mipmapping and an-isotropic filtering. Example with image:
http://petersikachev.blogspot.com/2018/10/minlod-cheap-method-to-increase-texture.html
But somehow, with the Combat mission crop fields especially, it remains less then satisfactory. What I do is, I downscale and/or blur these particular terrain tiles, as a simple mod. Since I rather look at blurry then at such distortion.

1) CMRT v2.10 F&R archives contain quite a few normal maps where the syntax of the file name is different from what I would expect. Like "smod_soviet_m43_officer-sr_uniform_normal map 2 [guards].bmp" From glossing at other files, it seems the normal syntax is "smod_soviet_m43_officer-sr_uniform 2_normal map [guards].bmp". Or are both of these names workable for the game?
2) What is the logic when a variant (2,3,4, etc) or a mod-tag variation like [cavalry] is not available as normal map. Will it use the normal map of the base texture, without the variation number and/or mod-tag?
It is not always easy to see the effects of normal maps. At least not on my system. Which makes it hard to test..
PS: The normal maps for doors and windows in CMRT do not match the texture.
 

I suppose it is the usual distant floor distortion effect, for which GPU drivers invented mipmapping and an-isotropic filtering. Example with image:
http://petersikachev.blogspot.com/2018/10/minlod-cheap-method-to-increase-texture.html
But somehow, with the Combat mission crop fields especially, it remains less then satisfactory. What I do is, I downscale and/or blur these particular terrain tiles, as a simple mod. Since I rather look at blurry then at such distortion.

I think the turret rotation is not working in a lower-detail model of the M60A3 (TTS). It glitches from showing the proper rotation to pointing straight ahead. As a consequence the shadow of the gun barrel is always straight ahead.

Either that, or supply all the sold games with a coupon, for a free powerful graphics card? 
 
 

Normal map naming in the CMRT v2.10 and v2.11archives is not always right. The variation numbers are often in the wrong place in the file name. This will prevent the game from using these normal maps.
https://community.battlefront.com/topic/139308-questions-remarks-on-normal-map-files/

1) CMRT v2.10 F&R archives contain quite a few normal maps where the syntax of the file name is different from what I would expect. Like "smod_soviet_m43_officer-sr_uniform_normal map 2 [guards].bmp" From glossing at other files, it seems the normal syntax is "smod_soviet_m43_officer-sr_uniform 2_normal map [guards].bmp". Or are both of these names workable for the game?
2) What is the logic when a variant (2,3,4, etc) or a mod-tag variation like [cavalry] is not available as normal map. Will it use the normal map of the base texture, without the variation number and/or mod-tag?
It is not always easy to see the effects of normal maps. At least not on my system. Which makes it hard to test..
PS: The normal maps for doors and windows in CMRT do not match the texture.
 

BrzPack is not all that different from the official RezExplode/RezPack tools supplied with the games, but I had a framework for an extractor at hand, and BrzPack has a few extra features.
Download from this place: http://www.gb-homepage.nl/index.htm (Select "Combat Mission" in left navigation window)
-----------------------------------------------------
From the included Readme:
BrzPack - Archiving utility for Combat Mission Brz format, G. Broers 04-05-2021
v1.00, Freeware, Use at your own risk, files limit is set at 8000 and 2GB.
Packs all files in current folder to BrzPack.brz except BrzPack.exe/BrzPack.brz
Unpacks any brz file you drop on the icon to a folder with the archive's name.
You can press Ctrl+Break to interrupt and close the program, but it will leave
files unfinished when doing so.
The Brz format only allows for standars ASCII characters for files and folders.
Brzpack is only ASCII aware.
Only use BrzPack inside folder-names made out of ASCII characters.
Use BrzPack only to pack files with names made out of ASCII characters.
When extracting = exploding:
  BrzPack automatically creates an index file of the Brz file. Which is just
  a text file with the file listing.
  BrzPack allows one to optionally pass a wildcard string, only files matching
  this wildcard string will be extracted from the archive. For example "mdr" will
  only extract files that have "mdr" in their name or extension.
 
  BrzPack will retain the 'modification' date and time from the brz archive for
  all the files that are unpacked from it.
When packing:
  The Brz format does not allow for multiple files with the same name.
  BrzPack automatically checks this condition.
 
Requirements:
This is a WIN32 console application. It was tested on Windows XP/7/10
 

I can replicate this. Seems to be like this: When you save under a name that already exists, it does not overwrite the save, but makes a save file in the 'Red Thunder' folder instead, and names it "tempfile *something*.tmp".

Now the M60 again, but different one: The Machine Gun. It only has a bi-pod when prone, the bi-pod disappears in other stances.
At first I thought this is just a known game limitation, but in a game like CMRT the MG 42 bipod does have two appearances, depending on stance.

I think the turret rotation is not working in a lower-detail model of the M60A3 (TTS). It glitches from showing the proper rotation to pointing straight ahead. As a consequence the shadow of the gun barrel is always straight ahead.

I just did quick test, and indeed CMSF1 is much easier then CMSF2. In fact, it is as easy as it can possibly be. With the usual minor edit a CMSF1 map will load in current CMBN/CMRT/CMFB. CMFI/CMBS/CMCW can be assumed to work with them as well.

Here is another factoid, the other way around, example procedure: Open older CMBN QB map "Asslt Med Village QB-006" with CMBN v1.11, remove all the houses, save it, do the usual header modification, open in CMSF2: success!
If you save with later CMBN it won't work (not even a blank map), if you leave or add a single modular building it won't work. I suppose independent buildings also mean trouble.

Here is another factoid, the other way around, example procedure: Open older CMBN QB map "Asslt Med Village QB-006" with CMBN v1.11, remove all the houses, save it, do the usual header modification, open in CMSF2: success!
If you save with later CMBN it won't work (not even a blank map), if you leave or add a single modular building it won't work. I suppose independent buildings also mean trouble.

There are only these two wav files in the new archives:
red thunder v210a\sound\air mg151-20 750 4000.wav
red thunder v210a\sound\gun 6mm italian.wav

I have been with the company since some of their first games.  I will start by saying this is the sloppiest release I have ever seen. Has anyone at Battlefront actually played this game? I mean really played it. Like read the briefings start to finish? Who proofed the briefings? Certainly not a grown adult. I feel like some of the briefings are story being told by a 4th grader. Not the level of excellence we have seen in all previous briefings in games. They are full of grammatical errors and incomplete sentences. I get the impression they were written by a non- English speaker. I teach 4th grade writing and math and I just couldn't shake that I was reading a very novice writers writing. Take some pride gentlemen.

I am aware what I just wrote was negative feedback. But it is factual. And I made sure to add constructive advise. Maybe such advise was out place to a game developer. But honestly, from what I saw in CMCW v1.00 it seemed like someone should say it.
So I am wrong you say, because of "techno-wizardry you don't understand" Fine.   (do understand that answer leaves some doubts.)
I really want CM games, and especially CMCW, to be in the best state they possibly can. And I see the quality in the engine and in the missions and TO&E. And I appreciate that people put in personal effort to make CMCW happen, as you said you did, despite Battlefront working on other things as well.
 
 

It is not a block or DRM, at least nothing more then it used to be, just a minor change to a format. You are misstating the intent. If they wanted to block/DRM you really, and put effort in that, it would be different.

I don't know why that gear shows up.
But I did come up with an idea of what I see, it is a lower detail model flashing through. Together with the helmet issue, it makes me think the lower detail models of the 1980 US soldiers here, are basically files from WW2 GI's or something.
So then next up is the BTR-70. it is way too big.
I am probably not making myself popular here. But the 3D model work of the newly introduced items is below the quality that I came to expect. Though luck. I don't think me nagging is really gonna change that situation. Someone skilled at the DEV-side with access to the 3DSmax files should go over it thoroughly.

It is not a block or DRM, at least nothing more then it used to be, just a minor change to a format. You are misstating the intent. If they wanted to block/DRM you really, and put effort in that, it would be different.

It is not a block or DRM, at least nothing more then it used to be, just a minor change to a format. You are misstating the intent. If they wanted to block/DRM you really, and put effort in that, it would be different.