Posted February 22, 2018
rampancy: Edit: So, Close Combat 2, 3, and 4 all work in WINE (tested on the latest available 3.01 engine that I could find at the Porting Team, running in Wineskin on OS X 10.7.5 and 10.11.6), but with some caveats...
peterb12: Could you turn up the detail on where you found this engine - maybe include a link? The most recent engine I could find in Wineskin is WS9Wine2.22, and when I launch CC after adjusting the registry in this engine, it crashes immediately. gurqn: http://portingteam.com/topic/10055-wine-staging-csmt-builds-engines-available/page__st__570#entry107232
ScoPezz: http://portingteam.com/topic/10896-wineskin-engine-repository/
As well, look around on the Custom Wine Builds subforum for posts by NRG, who has been packaging and releasing the latest stable version of WINE for Wineskin, as well as releasing custom packaged engines based on the CrossOver WINE code.
As for your own problems with Close Combat 2, what version of macOS are you using? I'm on 10.11.6 now, and my latest attempt to reinstall the game using the latest default WINE version on the Wineskin repository (2.22) works fine. The game also works under 3.01, which is the latest devel version available on gurqn's MEGA page. Did you also set ddr=gdi in Winetricks? (As mentioned on the CC2 Wine AppDB page.)
Also, it's worth going back to the game's registry keys to make sure that the intro movie and all cutscenes are disabled (launched = 0, and PlayVideos = 00000000)
Post edited February 22, 2018 by rampancy