A Canadian Cat

Grrrr. I'm frustrated with nVidia's screen capture tool. I like how it works but it is so unreliable I'm officially going to look at BandiCam and InfranView. For the last few weeks it seems that every time I try to capture a screen it just doesn't work. I have found that any time there is a driver update or a Ge Force Experience update they just arbitrarily turn off my ability to screen capture until I install the update. No, just no, that's not how this should work. So, I'm firing the nVidia 's in game overlay and looking for something better.

Say my name and "cover arc" three times and I'll appear and tell you what I think of them I'll just add that holding fire from AT guns could be considered a good use of the Cover Arc command. It is what is its for - preventing something from firing where you don't want it to. A broken record is correct twice a day - that's the saying right?

Or its a great drying rack for your fire wood so you can brew up when you stop for the night.

Who knows. I need to find a way to be more plugged into what they are changing. One big road block for me is I don't have a Mac. I have to get other people to try things out - not a great way to develop software. Typically I would send code I know works to other people but for the Mac I have to send code I have never run before. Thankfully I have developer friends to have Macs that help me out.

I am afraid that the latest version of the Mac OS causes WTII to fail to run. I have a possible solution on my todo list but I have not go there yet. Sorry and I hope to get this resolved at some point.

The other 28Gb is so you can run huge battles in every CM title all at one time Leave no memory idle! 32 bit registers literally can only address 4Gb of memory. Note Yes, I am aware of schemes to swap different memory fame etc. My opinion of those is - just build a 64bit app.

I tried loading and unloading and reloading and I could not guarantee who would man the HT gun and sometimes no one stood up and fired along with the HT gun. Bummer.

OK cool. You can give the passengers a target order pretty much anywhere the HT can see but as @Codreanu noticed they stay seated if the range is long. I did a simple test 200m and 300m they fired but 525m they did not. If you do the load swap as discussed above then some of them fire even at 525m and up. However who stands up is interesting. In my test the MG42 user manned the HT's gun so the sharp shooter is the one that stood up and fired at 525m and I did not get two MG42s firing. I'm guessing if you split teams properly you can influence who mans the HT gun.

Well they can just keep their opinions to them selves. I am reminded of a developer I once knew who responded to his manager trying to book a performance review "unless there is money in it for me you can keep your damn opinions to your self" - yes he was a grumpy guy but we loved him Anyone doing this can just **** off. @Bootie is a great supporter of this community. He has helped me (and countless others) many, many times. I am amazed at how well he does at keeping himself accessible.

No, there is only a 32 bit version for Windows. It is compiled with large address aware turned on. That means the program can use up to 4Gb of memory (normally 32 bit programs are restricted to a max of 2Gb).

Interesting. I am curious now... If you leave everyone loaded normally can you give a target order to the passengers? And if they do stand up and fire is their visibility worse than the HT itself?

Famous last words. I get that sentiment and felt that way about a number of changes as a developer many many times over my career. I never let myself feel that way any longer. I have too much experience to know that it will not be as easy as you think at first glance.

I have no idea. One issue is, can the current engine be recompiled and use Open GL? I don't know the answer - I know only a sliver about the Mac. The new engine will not, I suspect, be moving away from Open GL so that question would be a limiting issue. Rant on In general I hope not. I very much do not like the way Apple operates. Their favourite MO is to cook up some cool new solution to a problem that already has solutions and make a ton of changes and then declare it the best thing ever. If that was all they did I wouldn't really care but they also have a bad habit of also saying - you know that solution to the problem you used to use and count on? Well that's going away and you have to do a bunch of work that will serve no purpose other than serve Apple's desire to create new solutions to already solved problems. This does not benefit customers - it only benefits Apple. Grrrr. You might say why does some PC user care about that. Good question. It effects me in two ways. First as a consumer I don't get new features or bug fixes for my PC version because the developer is off chasing apple's tail instead of adding value for us. A recent example is the RAW editor I use Capture One. They spent months working on moving the the M1 architecture meanwhile there were performance fixes and actual valuable features that were in the queue that could have been released to us much earlier. #sadcustomer Second as a developer I experience my products that worked perfectly fine last week suddenly don't any more. Windows OS doesn't do that. Bloody hell I have a product I wrote in Win 3.11 that sill works today - it's not necessary any more but the code still runs. Meanwhile Apple drops this or that or pulls libraries or changes the API whenever they feel like it. That wastes a ton of my time and I am not able to add new features - see above. #saddeveloper Rant off

Hee hee, yep. Nostalgia is nice and all but in the past compiling was expensive and centralized so we also used to so hand alter assembly code during debugging so we could "test" fixes we planned to make in the source code to save round trips of compile and test since it took so long to get a new build on to the test machine. Yeah, it was cool and all but I never want to go back to those days. Oh and "no one is ever going to need more that 360K for a program"

LOL nice. Use your ignore list here so you don't have to read this snowflake's temper tantrums.

Oh yeah that would be graet. I have more than once been caught swearing at the screen after making a mistake. Yes! I'm not sure what you mean here exactly. There is a combine squad command that is for regrouping after casualties but it sounds like you mean recombination of teams after splitting. Is that right. I would agree that it would be nice to have a command "unspit" (terrible name but to differentiate it from the current combine command) that would let you directly regroup a split squad that were within 16m of each other. I agree that the current system is okish if you can wait for minutes but is annoying when your guys have **** to do. Thanks for the clarification about moving the camera to way points. Yes, that would be helpful. I can see that being helpful sometimes. I find the current system is good enough for the vast majority of situations though. I'm not sure the added command load would be worth it. Nice idea. Shift clicking while plotting way points with multi select. Cool. Thumbs up! Great suggestions!

Oh cool. Heads to the secret lair to find more details

Great point. We should start a database of who asked for what and how bitterly the complained about it. Then we could pull up old quotes one day. Oh who am I kidding that would be a massive waste of anyone's time

This one makes me laugh. First a little history. The CM1 series started with Beyond Overlord followed by Barbarossa to Berlin and finally Afrika Korps. Each follow on game added features to both the engine and the UI. But the older games were not updated with the new features. Which meant that Afrika Korps played better and had a better UI than the other two. People were sad that the new work was not available in the still very playable Beyond Overlord. In the CM2 series BFC decided to not do that again and so when Fortress Italy came out Beyond Normandy got an update to add in the engine and UI improvements too. So, what are you asking for? Did you really want Beyond Normandy to languish behind as new titles came and made improvements? I don't. You shouldn't either. Everyone feels that some graphics improvements would be welcome. I do have on bone to pick with the above - the sky? The sky in CM seems pretty damn good to me. I don't think I have ever heard someone complain about the sky. Indeed. This is another area that would be great to add. So, as a point of interest if they added some of these things would you want that feature to only be in the new release and leave all the others behind? That's how adding new features and differentiating a new game from the older ones would work. Rhetorical question. TFB Honestly I don't want to be mean or angry but this is such a bull **** complaint. BFC will price it where they think they can make good money. Bitching about it is so boring. Sure it would be cool but as you said a lot of those assets really would be out of view. Not all of them, so yeah cool. Planes actually do sometimes crash on map. There is no wreckage model though just an explosion. So cool would be nice. LOL see two points above. If you don't like the price no one is pulling money out of your pocket. Vote with your dollars. In your opinion. Enough people disagree and think the games are worth the money. That's kind of the end of the discussion. The argument I expect to hear: but if you lower the price you will sell so much more. Facts not in evidence (BFC know their audience and what price differences do and how many copies they think they will sell. There is no way that you know better than them).

The z folder should work fine - it follows the same rules as mods.

LOL yep which is why my answer would be none of the above. Sorry. Every minute spent on that sci-fi stuff would be a minute they could not devote to WW2 or Modern titles or engine work. I want more content way more than any sci-fi stuff.

Oh he is very much involved. He's a great resource. Keep in mind though BFC is not tracking the current conflict but their hypothetical time line.

My two bits of best advice: Target arcs are your enemy. Using them inappropriately leads to your units getting killed without doing anything. Their purpose is to prevent firing so only use them for scouts and observers that you don't want spotted. Otherwise just don't do it. Use the terrain. Read this: https://battledrill.blogspot.com/2015/11/mett-t-analysis.html or any of @Bil Hardenberger's AARs. Even if you don't write things down or go as deep as Bil doing any part of METT will make you a better player and you will quickly realize you should be doing it all every damn time.

Just to clarify a little - for Windows you can use the original PBEM and the new PBEM++ and it does not matter where you bought the game as long as both players are using the same version (and you both have accounts for PBEM++). For Mac you don't get access to PBEM++ but the original PBEM works the same as before.

My understanding is that you can update the .cam file for a campaign in progress and it will not effect the scenario you are playing now but the next scenario will come from the updated campaign. I do not know if there are any particular risks involved with doing this for the changes in question. Perhaps someone who's done it can chime in.