Jump to content

Schrullenhaft

Members
  • Posts

    9,199
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Schrullenhaft

  1. An install of 2.06 (BFC) worked fine for me with no hotkey issues. However, in the past, I have heard of occasions where a patch may overwrite or somehow delete a hotkeys file. I've attached the default 'hotkeys.txt' file that should be copied to the following directory: /Users/'user account name'/Documents/Battlefront/Combat Mission/Combat Mission Shock Force 2/User Data hotkeys.txt
  2. nathangun - Typically the 'saved game' and scenarios/campaigns are located in your User account's 'Documents' folder. Specifically: CMBN: /Users/'user account name'/Documents/Battlefront/Combat Mission Battle for Normandy CMFI, CMRT & CMFB: /Users/'user account name'/Documents/Battlefront/Combat Mission/'name of specific game' If you have more than one account on this computer, then you would need to login to your computer with the account that was used during the games' installation. If there is only one account or you are already using the account that was used during the installation and you cannot locate any of the 'saved games' or scenario files within the above listed directories (within the '../Game Files' directory), then you may want to reinstall all of the non-Steam games. I don't know if right-clicking on the installer and using 'Run as Administrator' during the installation helps or not, but it is something you can try if you get the same results. Also, temporarily deactivate any anti-virus/security software you are running to make sure that it doesn't interfere and possibly quarantine/delete some of the files during installation. For a game that has already been activated on the computer, there shouldn't be a need to reactivate the game, unless something changed about your computer since you originally activated it, including reinstalling Windows or some sort of significant hardware change.
  3. Just an FYI... John IS the Helpdesk. For issues such as this with purchases and license keys, you will likely need to open a Helpdesk ticket (click on IanL's Helpdesk link above) since there is private content (license keys, payment info, etc.) that need to be exchanged. The login for the Helpdesk is your 'Store' account (if I recall correctly). Usually the emails have the download links and your license keys (sometimes showing up faster than what might be printed up in the online account webpage). You can also check you 'Store' account for the order and see if it shows a download link. With most games that have 1 or more modules, there is only one 'all-in-one' download/installer. Activating the license keys with the 'Activate New Products' shortcut (that might appear on your desktop or within the Battlefront Start Menu folder or at the very least within the game installation directory) activates the already installed content.
  4. To avoid some of the issues that plague AMD drivers at the moment, I would suggest installing the 22.6.1 (Optional WHQL) Adrenalin drivers. I would suggest a process of: 1. Download the 22.6.1 drivers. 2. Uninstall your current video drivers and reboot your computer. 3. You may want to temporarily disconnect from the internet to prevent Windows from downloading and installing whatever AMD video driver it thinks you should have. 4. Run the 22.6.1 driver installer. If you have had different videocards on this computer or a lot of different video driver installs, then you may want to consider running DDU (Display Driver Uninstaller) Typically the instructions suggest running in SafeMode, but it should be possible to run it without doing so. I'm not sure if a video driver install will address the freezing that you're seeing, but it is a possibility. For stability purposes you can download and run FurMark 1.3.3. This is an OpenGL 'torture test' that should stress your videocard sufficiently to see if it may have hardware problems (overheating, etc.). Run it for a half hour or more and see if you have any sort of stability problem. Once you stop it, run your computer for awhile afterwards to make sure that your videocard cools down sufficiently before turning it off.
  5. I tried the download and got the same results... corrupted installs (missing files) with online CMA installer. I compared a download from yesterday with one I've had on my computer for years and it was the exact same size, so this problem has been around for quite awhile. I have an installation that may have been from a DVD and it had 14 battles in total (with the download installer only installing 11). The missing battles: Ambush at the Bridge Ambush in the Gully Desperate Crossing I'm not sure if I can link a .zip of the missing scenarios (about 5.3MB in size). If the posted file doesn't work, try the below linked DropBox file (though I'm not absolutely certain it works either with a free account). DropBox is not needed, just click on link to download. DropBox download of missing CMA scenarios ('Missing-CMA-battles.zip', 5.3MB) Missing-CMA-battles.zip
  6. You can play the 1.03 version of the CMx1 series on Windows 10 - the 1.04 patch is NOT necessary. However, the 1.04 patch did, indirectly, address some graphical issues that Radeon users experienced running later drivers and Windows versions. I haven't checked any CMx1 games lately with Radeons to know how well 1.03 still holds up graphically. The Gog.com version is 1.03, for those that may be curious.
  7. As Redwolf guessed... you likely have an AMD Radeon videocard and the latest drivers have a bug that causes a white flash in the screen right before an explosion. The temporary answer is to downgrade your video driver. You'll suffer some much slower load times, but the white flash should be gone: Screen flashes white with explosions
  8. General Grievous - The main limiting factor with your Dell Inspiron 620 will be the integrated Intel HD 2500 Graphics. Unfortunately a lot of the drivers for Intel graphics have substandard OpenGL implementations and we often see issues trying to run the games on Intel Graphics. Sometimes certain drivers may work, though I don't know if what Dell provides for your computer would be among them. Sometimes you can try the Intel-provided driver, but it may not 'recognize' your video hardware (since it is provided by Dell as an OEM) AND Intel is no longer directly providing Windows 7 drivers from their website; any Intel video driver updates you would have to find on Dell's website or others (which can take a lot of downloading and experimentation to find out if they would actually work). Do you know if your Windows 7 version is 32-bit or 64-bit ? If you have 4GB or more of memory, then you may have the 64-bit version. This is important for when you're searching for drivers. If you find that the game doesn't run well or at all, you could install a videocard into your Dell. You would need one that does NOT require PCIe power connectors (your Dell power supply will likely not have these). Videocards to consider would be the Nvidia GeForce GT 1030 or GTX 1050 or GTX 1050 Ti, such as this MSI model from Amazon (for US$190): MSI V809-2277R GeForce GTX 1050 Ti 4GB
  9. Have to edit my original post. To my knowledge the 'Matrix key' that you can get after purchasing the BFC version of the game is a Steam license key (requiring Steam and internet access to install and activate). I'm not certain if this license key doubles as a Matrix license key that will allow you to install and activate the Matrix (non-Steam) version of the game. If it is, then you can use the Matrix licensing system which doesn't seem to require internet access in my experience with it.
  10. Battlefront is aware of this issue and are looking at it. However this issue is more likely in AMD's court. The 22.7.1 drivers brought in a bunch of OpenGL optimizations and it is one (or several) of those optimized routines for implementing OpenGL that has caused these problems. These optimizations have brought some welcome speed improvements to CM for Radeon users. CM loads multiple times faster than it did before. However they have also caused problems that everyone in this thread is aware of now. I don't know how hard it would be for Battlefront to reprogram some of the visual affects in CM that are affected by these optimizations. Using different calls/methods to reproduce some of the effects may be complex enough to almost not be worth the effort. At its simplest it may result in an option to turn off certain effects for compatibility purposes. If AMD were to address this issue there could be a couple of possibilities: AMD figures out that some of the optimizations need refining and are able to find a fix and maintain the speed improvements. or AMD realizes that the optimizations are incompatible with certain OpenGL calls. This results in a decision to: 1) Consider the incompatible calls as deprecated in their OpenGL implementation - this can be a likely scenario if the calls are older and there are others that are considered suitable replacements (however harder they might be for programmers to implement). The optimizations all remain in place and potentially benefit the majority of OpenGL programs, but CM suffers. or 2) Possibly reverse/sacrifice some of the optimizations in order to make CM work with their current OpenGL implementation. This would result in a driver that wasn't as fast in all respects as the current ones, but it may still be an improvement speed-wise over earlier drivers. Depending on what programs were affected by the optimizations this could take several possible paths. a) If several significant programs were affected and only a few changes are necessary (and thus most speed improvements remain), this could be the driver base for OpenGL going forward. Future drivers will have these fixes and CM will continue to work with newer drivers. or b) If only a few programs are affected and/or many optimizations have to be dropped or engineered in a manner that significantly reduces the performance benefit the optimizations originally provided. Then AMD could release (if it found that the effort has significant enough demand) a 'beta' driver that may be a 'dead end'. Future updates would NOT utilize this as a base for OpenGL, but instead implement the full OpenGL optimizations of the previous driver. This 'beta driver' would have some speed improvements and compatibility with the latest Radeons, but this would potentially be the last driver supporting certain OpenGL calls in a manner compatible with CM. I have seen in the past when AMD has reached out to Battlefront to get more info on certain bugs in their drivers. However even with the intense initial interest in fixing the problem it took 9 months to get a driver release that fixed the problem (which was more significant in its effect than the problems experienced here).
  11. The i5 and the GT 1030 should be a performance improvement over the HP DV6-6135dx model that you linked to.
  12. Yes, you should be able to run CMBN, CMFI and CMA with that hardware. Don't know what your previous laptop had for hardware, so I don't know if you'll see less or more performance than you experienced previously.
  13. This is the link to a DropBox share of the .zip file for the 'Radeon Text Fix' mentioned above: https://www.dropbox.com/s/wkg7zupvtq2vfhm/Radeon_text_fix.zip?dl=0 You shouldn't need DropBox to download it (though you'll get prompted to create an account). The file will be presented to you extracted, but when you click the 'Download' link in the upper left it should just download the full .zip file. The basic instructions are in the 'readme.txt' file.
  14. As mentioned above, down-grade to the 22.5.1 or 22.6.1 drivers and they will not have this problem. The negative part of that down-grade is that CM games will load much slower. The 'slower loading' has been a long standing issue with AMD drivers that has only recently changed. Unfortunately those optimizations in OpenGL have resulted in a few bugs that show up in CM, such as the 'white screen flash during explosion'.
  15. Are you certain the patches are being installed in the directories that you have the games installed to ? If they install to a different directory, then they will not have all of the files that they need to run. I suggest NOT copying the patches to the actual game directories to run them also. This could lead to some strange installation scenarios where the patch is nested in folders within the game.
  16. The Surface Pro 6 utilizes Intel UHD Graphics 620 (built-into the CPU). Unfortunately Intel drivers under Windows have had a long history with the problem of 'blotchy text' in CM. Some sort of hard-coded setting, texture compression or something ends up consistently blurring the text in CM. There's no particular setting or driver version that fixes this issue to my knowledge and I don't really expect a fix at any point in the future either.
  17. This is the process to use the: AMD Bug Report Tool Depending on what videocard you have and what other games you may run, the 22.6.1 and 22.5.2 drivers both seem to work fine with all of the CM games to my knowledge. Previous Windows 10 64-bit AMD Radeon drivers (ignore that it says it is for the RX 6500XT, they will work with any Radeon RX 4xx and newer)
  18. You are likely suffering a problem with some of the later drivers. Supposedly 22.10.2 and later address this issue, but there appears to be some instability with these drivers according to some users. Others have gone back to 22.5.1. Here's a thread on what some people have run into and their solutions: AMD 22.8 series drivers break CM
  19. The Mac OS version of CM lacks the 'display size.txt' option that the Windows version has (as far as I can tell). Within Options > Display Size, have you tried 'Desktop' ? This should usually match your native desktop resolution, even if it isn't explicitly listed by CM. Beyond that Lucky_Strike's suggestion of EasyRes would be the closest solution.
  20. What was required to 'jerry rig' your DVD optical drive to your new computer ? Was this originally an IDE drive that you have to use a converter to hook to USB or SATA ? It's possible that your DVD drive may simply have problems reading discs, with some formats possibly being easier to read than others. Can you read other DVDs ? There's no special formatting to the CMFI DVD (no bad sectors or any other physical copy protection). If you have access to the download (and a decent speed internet connection), it may be easier to download the installer as suggested by chuckdyke. The disc is NOT needed for any sort of copy-protection and is simply the installation media.
  21. For CMFI 2.11 is the latest version. Unfortunately there can be confusion with the Engine version and the Game version. The readme you posted refers to the engine version. CMFI is currently at Engine version 4.x, while the Game version is at 2.11.
  22. The 'intro sound' is actually a separate video file, 'intro.wmv'. I would guess that something may have gone wrong in "removed ALL my mods". However accidentally removing BRZ files that are part of the game would probably also result in black elements throughout the 3D view. What audio are you using ? Is this an USB headphone or a built-in audio chipset ? Typically I would expect whatever the 'intro.wmv' file is playing on would be true for the game too, but perhaps something is going wrong somehow. Within the Windows desktop click on the 'speaker' icon in the lower right systray. This will show you your Windows volume level. If you have more than one output, then there will be a 'carat' in the right corner of this volume control. Clicking on it should show you the audio outputs available to Windows. If there is more than one selection, perhaps trying something else (that IS plugged into headphones or speakers).
  23. It actually looks like he has the 'Battle Pack' and NOT the 'Vehicle Pack' activated per the activation screen. Contact the Helpdesk (click on the blue '+new ticket' button in the upper right) and provide your license key for the Vehicle Pack and request some additional activations. They should notify you once that is done and you should then be able to activate the Vehicle Pack (which does NOT require a download and install with the 4.03 patched version of CMBN - the files should already be present).
  24. You can install older drivers over your current/newer ones with no problem. You can use the standard uninstall process for AMD or if necessary you can use Display Driver Uninstaller (DDU) (a third party utility) to uninstall your drivers and then install an older version. DDU typically recommends running Windows in Safe Mode for the best stability in uninstalling, though it can be used in a normal boot. For Windows 10 or 11, the Adrenalin 22.6.1 Optional WHQL drivers work fine in my experience so far (using an RX 480 under Windows 10 64-bit). For the link here, you can ignore that it was selected with a Radeon RX 5600XT, the driver is the same regardless of videocard.
  25. AMD coded some 'OpenGL optimizations' with the 22.7.1 drivers and this is likely the cause of the current CM problem. I'm able to play CM with the 22.6.1 WHQL drivers.
×
×
  • Create New...