Jump to content

STORMCROW-UK

Members
  • Content Count

    24
  • Joined

  • Last visited

Everything posted by STORMCROW-UK

  1. Phil (or anyone else from support), if you're about could you look at the response I posted to the above ticket 5 days ago. I can't play the game in the meantime and I'd appreciate a resolution.
  2. I've seen this before, it's due to a permissions issue during installation. Only fix I found was a clean reinstall I'm afraid.
  3. Thanks it is! I was just wondering if it was one Phil had seen before I opened a ticket. Very puzzled that a clean reinstall didn't fix it, hence my thinking it may be DRM in origin.
  4. Yes I realise, I can see them in the directory in Finder but not in the game.
  5. Hi Seeing a weird issue once CF is installed. In short despite seeing a version number of 1.10 I don't see a) Any of the CF battles (I can see the files in the directory but not in game) Any of the CF campaigns (Same as the battles) c) In quick battle the service and combat forces values are non-sensical e.g. IG ammo carrier for service I don't have any mods installed, I've repaired permissions beforehand and I've even trashed the whole CM:BN install and reinstalled a fresh copy (v1.0 straight to 1.10) and exactly the same thing reoccurred. Stumped to think what it might be, is it possibly a licence issue?
  6. Hi Seeing a weird issue once CF is installed. In short despite seeing a version number of 1.10 I don't see a) Any of the CF battles (I can see the files in the directory but not in game) Any of the CF campaigns (Same as the battles) c) In quick battle the service and combat forces values are non-sensical e.g. IG ammo carrier for service I don't have any mods installed, I've repaired permissions beforehand and I've even trashed the whole CM:BN install and reinstalled a fresh copy (v1.0 straight to 1.10) and exactly the same thing reoccurred. Stumped to think what it might be, is it possibly a licence issue?
  7. Always a pleasure to be helpful Phil. I appreciate the fact you're so approachable and prepared to work on problems. Very refreshing and an asset to your company.
  8. FYI I am responding via email to your helpdesk ticket query. Let me think about this. This had to have been with the original 1.01 patch and the more recent one had the DRM problem and would not start.
  9. Btw did you want the files for the savegame crashes? I was assuming not?
  10. Yeah I'm just pointing out they don't work between 1.01 patches either. It's a VIDIA GeForce 8600M GT 512 MB which did render ok earlier.
  11. Ok I have a suspicion that any save games etc from an earlier version are not compatible with this version as they crash. However following the reinstall I'm now seeing no 3d models for infantry which is odd. I just saw a floating weapon and a helmet. Vehicles look fine so far. Any suggestions Phil?
  12. Thanks for the hard work on the patch Phil. I've installed 1.01B and the game now starts (hoorah). I load the first scenario and it crashes (boo). Crashfile is in ticket JKS-225410. Given how much patching has gone on, I'm going to uninstall and reinstall and patch straight to 1.01B to see if this corrects the issue.
  13. Phil I know you're working hard on the patch, I wasn't implying otherwise. I just wondered how it was going as we were targeting releasing earlier this week?
  14. Can someone please give an update on the patch progress? Thanks
  15. +1 for an update on the patch. Currently can't play the game at all on Lion due to the DRM (the irony!).
  16. Ok game bombs out at start. Crash reports uploaded in ticket ZZE-721817. Would love to hear your suggestions! :-)
  17. Ok I've worked this out. The link at Battlefront.com to Gamefront.com for the revised patch (http://www.battlefront.com/index.php?option=com_content&task=blogcategory&id=281&Itemid=478 - link is http://www.gamefront.com/files/20584148/Combat_Mission_Battle_for_Normandy_1_01_Patch_OSX_zip) is actually a link to the OLD version of 1.01. Of course with everything having the same version number it's impossible for anyone to tell without looking for the FPS number as pointed out by Phil and then downloading multiple copies and comparing dates on them. I'd suggest that the patch numbering system needs to be amended as it's going to impact customer experience and increase your support costs? In the interim can you at least publish MD5 hashes of what you expect the file to be so we can double check? I'll install the amended file and report back on the stability
  18. Wait, I just re-read what you said, are you saying these should already be fixed? Because they're not and I'm wondering if it was because I patched from 1.00 to 1.01 and then to the revised 1.01 patch?
  19. Thanks Phil, these crashes are occurring in the current 1.01 version. I'm relieved that the new version corrects this issue as it occurs every time. Call me old fashioned but can I suggest every time you issue a new patch you give it a different version number? It just makes it a lot easier to track :-)
  20. Good news on the patch progress. After fixing the DRM licensing issue (no comment) I can get the game started but it's really unstable. Two quick questions:- 1) Would a clean install of CM:BN correct the issue? 2) And I'm assuming the patch will fix the issues. Currently the crash reports go to apple as per the standard OS process. Do you get these or should we be collected/submitting via another mechanism? And a word of support, whilst I do bootcamp it's a hassle and it's a huge attraction to have the game native.
×
×
  • Create New...