Redwolf

The Steam text is from Matrixgames, who are not the developer. BFC's word should be better. Unless that PBEM++ stuff somehow introduces a Win10 dependency...

... or just bring your own OpenGL. We aren't the only ones having problems with AMD/ATI:

I didn't try. I don't know enough about either WIndows or OpenGL. I wonder whether Wine will offer Zink as a backend. Some work has been done to research how CMx2 calls OpenGL, which was breaking running it on Wine.

Or bring your own OpenGL:

BTW, they are only doing this for third party modules. X-Plane itself has been changed to be able to render to Vulcan directly. But many modules do their own rendering - in OpenGL. Also interesting that they mention AMD by name when it comes to non-working OpenGL drivers.

This is what flight sim X-Plane does in a situation similar to CM: non-working OpenGL drivers, but working Vulcan API. Like with ATIAMD cards and newest drivers for CMx2. Bring your own OpenGL to Vulcan mapper. Where "your own" means the free one from Mesa. https://www.phoronix.com/news/X-Plane-Zink-Shipping [quote] As written about last year, the Laminar Research developers responsible for the incredible X-Plane flight simulator software have been working to make use of Mesa's Zink for leveraging OpenGL atop Vulkan to thereby avoid vendor OpenGL drivers that can vary in quality across platforms. With X-Plane 12.04b3, that goal is finally realized. [/quote]

You would think an automatic process would be possible to keep the QB selectable units in sync with those in the scenario editor. Either to generate the code for both, or at least a sanity test that you can run before release. Doing it by hand is problematic as you always overlook some things.

Don't mess with patches. Download the full installer from your user account.

But the question is - don't you have to cover some new area/timeframe? If you already did all the attractive ones you can only do them again with a CMx3 game. As long as it is CMx2 engine v5 you have to move [i]somewhere[/i], no? Is there a 100,000 copy theater left?

Well, BFC has to do something after the modules are done. So it is either doing a CMx3 and going round again (starting with Normandy) - or new theaters for the "shut up and take my money" crowd.

This is not a bug. This is how vehicles work in CMx2. And bunkers are vehicles. There is always a spotting chance 360 degrees around for vehicles.

Looks cool. Does it have single-player content?

Sounds like this historical example: https://www.imdb.com/title/tt0252963/?ref_=fn_al_tt_4

I'm surprised this is open to green card holders. Isn't it prohibitively difficult to get the clearance?

The Fleet Air Arm also had variety.

They have a lot of other (non-BFC) games to take care of, too.

Definitely not enforceable. Again, Adobe doesn't own what you make in Photoshop. You can redistribute works that aren't derived from other works any way you like. The tools don't matter as long as you don't ship parts of the tools. The whole question is a bit academic. Nobody is going to sell a battle pack. At least not successfully. Asking for donations is a different matter.

Same deal. As long as it is original from scratch you can charge. To make an analogy, if you make a painting in photoshop then Adobe doesn't own the copyright either.

Yeah, sorry that is nonsense. As long as you didn't reuse any CMx2 original base you are clear to ask for money, whether it is voluntary donations or "forced" before a download. Just don't base your mod textures on CMx2 textures, they need to be made from scratch.

Don't mess with patches and packs. Download the complete installer from your user account. I don't need any of that Win8 or admin stuff.

No, I asked Elvis and he said the installers in the user accounts are already updated. I think it was in this thread.

Yes, the atni-tank [sic) devices.

Don't mess with the patch. Download the complete installer from your user account.

Integrated Intel graphics? Forget it. Integrated AMD graphics? Should run. There is no difference between the modules in this regard.

The sad thing isn't that the T-90, Gill and LAV-AT bugs exist. The sad thing is that BFC went through an expensive release process and fix only one of them. That is inefficient. Now, if the other two bugs are supposed to be fixed they cost more. The opportunity to do them cheap is lost.