OMAC

With Terrains 1.4.1 loaded (core, maps, cwa) + all other CUP mods (units, weapons, vehicles) + CBA, I am getting No entry 'bin\config.bin/CfgWorlds/Thirsk.description'. when I try to open a saved mission in Eden. Thirsk isn't loaded. Anyone else getting this?

Excellent, thanks!

Hi, Vehicle weapon zeroing is not updated via Laze Target as it is for vanilla A3, correct? You still must update it manually? Using 1.78 stable and latest CUP files. Thanks for latest CUP updates! Cheers

Wow, Cambodia map 0.8 update removes ALL ANCIENT RUINS! Why? Major bummer. I know AI have trouble in those ruins, but still...

As a vehicle commander, it used to be that a keypress of W or S would make driver move forward/backward until another movement key is pressed. With 1.78 stable branch, that is no longer true. W or S keys must be held down by commander for driver to keep moving forward/backward. When W or S keys are released, driver will stop. If A or S keys are pressed, commander says, " Left > STOP" or "Right > STOP." The "STOPs" are odd and appear to be unnecessary, and are not obeyed by driver anyway. Are these changes by design, and/or do they have something to do with the new HoldKey functionality? I looked around in Controls and couldn't find anything related to HoldKey. I haven't changed any keybinds lately or otherwise messed around with the control settings.

Oh, I see. I'll try that. Thanks. ---- Another strange thing with 1.78 stable: Keybinds: Car fast forward -> E, Lshift+W Car slow forward -> Q, Lctrl+W I get a verbal command "Fast" or "Slow" if I hit either of the two binds including W, but not when I hit just E or Q. E and Q still work as normal, however. If I set the binds as W+E or W+Q, nothing happens, and I don't think speed changes. Odd.

I'm thinking of setting a mouse-4 button on my mouse to laze, so I can use the side of my thumb and thus not have to let up on the W or S keys, or my main mouse button. My current laze button is End.

I think the new WASD driving system for commander was pushed to stable branch too fast. It seems clear that the change was implemented to mitigate AI driving issues such as AI driver not backing up when ordered if obstacles are nearby. IMO, AI driving issues should be fixed or otherwise mitigated, and new WASD commander driving change reverted. I was fine with occasionally switching to driver position to get out of a tight spot. I see no real advantage of the new system. This change caught me by surprise since I don't use dev branch: Issues on stable branch for all vehicles, not just tanks: No verbal STOP command by commander when W and S keys are released. Vehicle does not stop immediately after W/S keys are released. Vehicle sometimes just keeps moving, in which case key for opposite direction can be pressed, which results in abrupt stop, but voice command doesn't say STOP, it says to move in opposite direction. There should be way to order complete STOP. Note that Select subordinate>STOP Action Menu command does not work to stop vehicle when movement keys are pressed by commander (this is expected). No verbal commands for Fast or Slow Drive. No verbal STOP command by commander when handbrake key is pressed. Handbrake key shouldn't work at all for commander. Commander can't easily laze target while tank is moving (needs to release movement key or mouse to hit laze key). Commander needs hands-free vehicle movement if he switches to gunner position and needs to control/fire cannon while tank is moving. As commander doesn't actually have control of vehicle, all of his commands must be voice. This new commander driving system is very arcadish given that commander does not have actual control of vehicle steering, accelerator, and brake.

Seems better right now...

Quite poor forum access today with continual 502 and 504 Bad Gateway errors....

I agree with @Grumpy Old Man on this. Having to hold W/S down as commander to move is a setback. One command should do the job like it did before. If you let up on those keys, vehicle will come to a stop every time (as is normal for human driver), without the verbal stop command present for A/D keys. Even handbrake works for commander - this doesn't make sense to me, unless handbrake is accompanied by a verbal "STOP" command. This major change needs tweaking for sure, and should be made optional. My Fast Drive key (E) works for commander as it does for driver - no change there that I can see. There should be a penalty regarding fluidity and responsiveness of movement if you are commander. This penalty was reasonably handled before. The commander has many things to do other than drive the vehicle, and he/she should concentrate on those. For example, commander needs to press another key to laze targets for his MG or GMG, and having to hold down W/S keys for movement makes lazing more difficult. Seems clear to me that the change was made to mitigate issues with AI driving, especially in tanks. Like AI drivers "refusing" to back up when ordered if obstacles are nearby...

Yes, I'm having lots of trouble reaching forums today. Very slow and intermittent connection. TLS handshake issues?

Ah ha, yes: Thanks. Those STOP voice commands seemed odd, but I guess they're meant to convey the commander telling the driver to stop turning the tank. Makes sense. You'd think that there would be another "STOP" verbal command when the commander lets up on the W or S keys also.

The issue is still problematic in Zargabad, Takistan, and Shapur, but appears to be less of a problem on Chernarus and Everon. I only looked at a few CUP terrains. The issue is worse on terrains with rather bright, unvegetated land surfaces that make the overly-darkened units stand out more. For example, the issue appears worse in Takistan than in Takistan Mountains, as the latter apparently has slightly darker land surfaces than the former.

Word. Example: https://feedback.bistudio.com/T124254 --- Am I happy with only 3 missions in Tac-Ops? No, I'd like more. Like 20. But I'll take 3. New assets? Never promised. A3 has enough assets anyway, but people who haven't already purchased DLC bundle may be less likely to buy this DLC with only 3 missions, especially if there are no new assets. --- (*&^*(&#$ Lots of my post was auto-deleted by me pressing the wrong key in Edge. Oh well. Forget it. --- It is VERY hard for me not to compare every A3 DLC to A2 DLC, all of which were so damn awesome that they will never be forgotten. Each one was like a new, fresh, mini game. A3 DLC? Not so much. But I haven't yet had the chance to play LoW, which I hear has a top-notch campaign. Us SP guys all know what A2 had that A3 does not. Females, ALICE (civvy system), dragging/carrying wounded people, furniture, etc. Words would be difficult to find that would describe how awesome it would be if ANY of those were added to an A3 DLC. But I've given up wishing for that, or complaining about it. With designers like Jezuro and the Zipper around, be prepared for awesomeness in Tac-Ops DLC missions. Get ready!

Beggars can't be choosers. I'll take more official SP content any day of the week, and have been asking for it for years, especially after the Apex Protocol debacle. I already bought the DLC bundle #2, so there's nothing else to do but cross my fingers and be optimistic. Three cheers to BI!!!!

And with Chrome browser on iOS 11.0.1.

^ ^ I strongly agree with inlesco's suggestion about the "jumping."

I see now that the explanation for the Loot Distribution "(NW)" is given in the tooltip for Loot Occurrence...

Got it, thanks!

Got it, thanks. For AC tooltip, the "L" is now clear. I had thought the L referred to the LOW setting, and not the (L), as that appeared to be the case for the Loot distribution tooltip. For Loot distribution tooltip, there is no explanation of the "(NW)," and explanations are given for the abbreviated settings themselves. However, it looks like the end of the tooltip may be cut off on the screen. Is there a way I can read the entire tooltip? The GUI cannot be moved.

I'm pretty sure that vehicle rearming works on Normal loot distribution settings also. Question: when configuring settings at mission outset, some settings have initials in parens after them, like "LOW (VL)" or "HIGH (L)." What do those initials stand for?

Discovering that vehicles could rearm at hidden camps changed everything for me - in a very positive way. The surrendering behavior of AI in tough circumstances is one of the many crucial, and perfectly implemented, aspects of Pilgrimage that greatly enhance SP gameplay and make it unique from that of vanilla A3 combat.

I love the civilian behavior in Pilgrimage, so Simple Civilian Ambience is great! So the enemy AI behavior is all vanilla other than the arty and Mad Stomper?

Does Pilgrimage 1.95 include any of your other AI scripting, such as Artemis or Civilian Behavior Controller?