Jump to content

Mr. Yubby

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by Mr. Yubby

  1. I was going to suggest a bit more contrast, but from the looks of the latest preview, you were on top of that. Can't wait for the release.
  2. Hi Patrick, I can speak from recent experience that both CMBN and CMSF (all modules) run great on Windows 7. I'm running the 64-bit version and the Battlefront games are much more well behaved under Windows 7 than some other Direct-X based games (mostly from EA) that I tried to run on the machine. I've had much more trouble with crashes with the Direct-X titles. I've not yet had a single crash with either CMBN or CMSF, and I've played some of the most complex scenarios. Hope that helps.
  3. Thanks for the response, that confirms what I experienced. This weekend I retired my old gaming PC and replaced it with a Core i7 machine running Windows 7 64-bit. I did this to prepare for coming Direct-X 11 titles. After my experiences this weekend, I have concerns regarding the suitability/stability of 64-bit Windows 7 as a gaming platform. Under Windows 7, most of my older DirectX games that were for the most part stable under Windows XP are having issues with unexpected crashes running on Windows 7 64-bit, often when the machine is idle. I thought Windows 7 was supposed to be an improvement over XP and Vista in terms of usability and stability, I'm not sure about that assertion now. After this weekend's experience, I'm ready to trade for a Macbook Pro. Windows 7 is too bloated and unstable, and based upon my experience to date, it's much too easy to break the OS by turning off system services that logically aren't necessary for a gaming rig. It's a good thing we have Google, I can't count how many times I had to consult the net for solutions to things that were simple to do under XP, such as a basic file search (which BTW was completely broken on Windows 7 out of the box). Thank you Google for the solution to that and many other basic usability issues. MS has done a very thorough job with obfuscating the user interface with Windows 7, it's quite annoying to use. The good news is my two Battlefront titles are very well-behaved under Windows 7. I played both CMSF and CMBN for several hours yesterday with absolutely no issues, both games look and perform great on the new hardware. Good work guys, I guess there's a lot to be said for sticking with OpenGL. Regards, Mark G.
  4. Nevermind, I figured it out. In a complete reinstall scenario, the NATO module license key unlocks the main CMSF product and the NATO module. I reinstalled the base CMSF game and all modules, and then entered all license keys as the last step. After installing the NATO module, and 1.31 and 1.32 patches, I was able to license the base game with the NATO license key, which also licensed the NATO module. Go figure. I must have missed this in the release notes. :-) Mark G.
  5. I'm trying to move CMSF to a new computer, and I own the base game and all modules. When I click the "Unlicense Combat Mission Shock Force" icon from the start menu, I get the license uninstaller for the NATO module. Not sure how things got cross-linked. I tried to re-license CMSF from my original order number, but this resulted in a failure with "error code 11". How can I manually unlicense the main CMSF program so I can reclaim my license key? I checked the properties for the "Unlicense Combat Mission Shock Force" icon and it appears to be correct, the target is set as follows: C:\Program Files\Battlefront\Combat Mission Shock Force\CM Shock Force.exe" -unlicense Regards, Mark G.
  6. Thanks Vein, your smoke/explosion mods for CMSF were a nice addition. Can someone tell me if the ...Game Files\Data\Z folder structure is supported by CMBN for all our modded sounds/textures?
  7. Howdy rune, that's a good tip. I did not realize that TOW used OpenGL until I downloaded it. I've been playing with the Nvidia control panel and I got a nice frame rate boost by disabling threaded optimization and enabling triple buffering in addition to the things you mentioned. Since it is my understanding that triple buffering only benefits OpenGL I set up a custom profile for TOW executable, because most of the other games I run use Direct-X engine. It completely fixed the stuttering in the opening movie, and I'm getting 25-40 FPS in the game.
  8. Just acquired TOW and I'm seeing the same thing in battle generator created missions with friendly Wespe SPG's. They won't acquire a target unless I tell them to and constantly ignore the stop and defend order. Might be a bug targeting logic for SPG class vechicles.
×
×
  • Create New...