Search found 154 matches

While CC's grand campaigns are the big draw, I find maximum AI aggression is in single untimed battles without FM -- a fight to the last man. However the fixed map VLs with their entry/exits are designed for ops and camps and theyre fixed positions make them stale after a while. So I keep an alternate BTD folder in /Maps for use in single battles and use mafi's BTD editor to shuffle and edit VLs.

For single battle .btds all entry/exits get deleted because the AI tends to ignore 1pt VLs, plus they're unnecessary. Without any, deployment reverts to CC2/3 style with the Allies on left map third, Axis on the right third and the middle third neutral. Without any VLs at all, you can play a battle but the game will crash at the end. However, for single battles I use one 1pt Allied [-3] and one Axis [-4] reinforcement entry area per map.

The other VLs get concentrated in one area of the map and the AI will deploy and act accordingly, effectively mimicking a small map by focusing the action on the area with VLs. Replacing VL names with a period [.] obscures that VLs value to the player introducing a level of uncertainty to any victory calculations. Your VL total is always in doubt when 2 & 3pt VLs look the same. The AI will always sees the VL value in the .btd. Using fewer VLs generally improves AI performance.

Test VL edits with SEE ENEMY on. Step and repeat until you get the desired AI behavior. Save the .btd and game file in the same folder for future use. Since the .btd is scenario specific any special instructions can be noted in the .btd briefing text.

Std ops and camps can be played untimed, w/o FM, last man too using the house rule that the attacking BG must disband if it doesnt take the entire map in any single battle. Nail biting fun when the AI's last unit is the final boss determining whether your few surviving soldiers will achieve total victory or disband in defeat.

You can skip the edit and save as .bmp/.jpg - convert to 24 bpp .tga with RTBtool if you have Photoshop or some other image editing app capable of saving edited .tgas directly as 24 bpp. GIMP and most other cheap PShop-knockoffs cant. Hence the need to save edited .tgas as .bmp/.jpg - then use RTBtool to batch convert those to the necessary 24 bit .tga format.

Another item of note is that CC treats pure white graphics (0xFFFFFF) as transparent.

@gamerat - By all means include these edits in GJS 9.6, and no credit necessary. However...my lawyers will be sending an invoice for the substantial damages to my property in Bretteville that you are ultimately liable for as mod proprietor.

@berger - see pm

This GJS95_fix.zip contains the file fixes as discussed above. These correct various uniform, rank badge, team name & type, voice effect and file format issues in the GJS 9.5 mod.

per the readme:
Extract the axsteams.txt, nations.txt, and uniforms.txt file to GJS95/data/base

Extract the GameGadg.gdg and ScrnGadg.gdg files to GJS95/Graphics

Extract the RUvox.sfx and ERUvox.sfx files to GJS95/LocalFX

The uniform RGB hex values are standards that can be determined in most image editing programs (GIMP etc), or on a website such as https://www.htmlcsscolor.com/

If you care to edit individual gadgets after unpacking them from the .gdg files with CCMunger (attached below), or edit any other CC graphics files, mafi's RTB tool converts from basic file formats (.bmp, .jpg) to .tga with the correct bit depth so CCMunger can repack them properly. Just maintain the original image dimensions.

errata - In Axsteams.txt edit all Ost teams from 1,0 to 5,1 should read- In Axsteams.txt edit all Ost teams in column E from 1 to 5, and in column I from 0 to 1.

The SS inf badge issue is solved by editing column I from '1' to '2' for those units

Heer inf units need to have col I edited from '2' to '0'.

Heer armored units need to have the ten SORANK13_xxx gadgets imported from stock LSA screen gadgets.

SS armored units need to have the ten SORANK53_xxx gadgets imported from stock LSA screen gadgets. For those units then edit col E from '1' to '5' and col I from '1' to '3'.

Game gadgets might need similar corrections.

Additional corrections should be made to infantry units that have crew soldier types (ex. SS Zugfuhrertrupp #131) as well as all the Kompanietruppen that are all mislabeled as Zugfuhrergruppe.

Errata:

The Nations tab in the workbook somewhat better explains how columns E & I synchronize in ***teams.txt, although their arrangement differs between stock LSA and GJS.

Map Tile Index (map location) in StaticBGs is best determined using mafi's 5CC map tool. Modified StaticBGs files can be used to create battle scenarios that deploy the AIs custom forces to preset locations. Example below.

The data/base *.txt files use tab separated values

re: wrong "badges" - I assume you mean the rank insignia "gadgets" shown to the left of the soldier's name on the Soldier screen. Those are specified in columns E and I in the ***teams.txt files. The gadget graphics themselves are contained in the Graphics/*.gdg files. Use the Munger tool to access those.

re: data in StaticBGs.txt - if you reference the column headers on the Static BGroups tab in the aforementioned LSA WORKBOOK, the data consists of:
"Count" - number of static battle groups
"Class" - static BG index number; "Name" - name of static battle group; "Side" - Allied (0) or Axis (1) all static BGs must be on the same side; "Map Index" - which map that static BG is deployed to. Maps are listed sequentially in the Maps/StratMap.txt file.
"Team Class 0" - index number of the first team in the BG; "Map Tile Index 0" - location where first team is deployed; "Team Class 1" - index number of the second team in the BG; "Map Tile Index 1" - location where second team is deployed; etc. etc.

Far easier to mod the /data/base files using a spreadsheet app (Open Office, Libre Office etc) in conjunction with the LSA workbook. Just be sure to save as .txt

The SS Befehlspz VIE already exists in Axteams as index #97. The only instances of this team are in s.SS-Pz.Abt. 101.

Could this capability be adapted to produce an LOS viewshed for classic CC much like what TBF uses instead of the awkward and uninformative fire line sweep method?

https://www.pcgamer.com/the-latest-thing-to-support-ray-tracing-is-excel-apparently/

Here are the 6 I have - CC3, COI, GTC, LSA, TBF & TLD

High quality movie footage - https://www.youtube.com/watch?v=mdqjHwhv47w

Im curious why no difficulty modifiers were used at the beginning of the fpools.txt? Also why you suggest Line vs Line against the AI? Even without difficulty modifiers for team quantities, a player Elite vs AI recruit setting would still give the AI a better team quality advantage than Line vs Line.

Have only used GR with Matrix and GOG game installs so I cant help with GR-Steam issues.

Every monitor has a default resolution. This is it's native resolution.


	Login or Register	Home · Downloads · Forums · Combat Camera · Help