Jump to content


  • Content Count

  • Joined

  • Last visited

About mountainwocky

  • Rank
    Junior Member


  • Location
    Millbury, MA
  1. The short of it is that I did reply to Phil, but for some reason your ticket system thought I didn't and closed the ticket after 240hrs. The email from Phil had the Reply-To field set as support@battlefront.com. You mention "...we have not received a reply back with a saved game that duplicated the problem." Does that mean that you never received my reply with the attached file or that you could not duplicate the problem with the attached file? Given that my ticket was canceled: "We are changing the status of this ticket to 'Closed' as we have not received a response from you in 240 hours." I have to think you for some reason you never received the reply. I don't know if the issue is possibly with the email system or with the ticket system not tracking the replies properly. However, I did reply, as did apparently the original poster, and in each case these replies were missed in some way and the tickets were canceled. That is why I jumped in on this thread to alert you that there may be an issue with replies being lost. Sure, I take your point that I could have gone back to the ticket system after getting the warning msg after 240hrs, but the question remains why are the replies being lost?
  2. Actually I had something very similar occur to me in that my open ticket was also canceled because I had not replied within 240hrs...except that I did. On May 21 I got a message from Phil at tech support following up on ticket MFN-880290 and asking if I could provide a saved game file . I really didn't have a saved file from the game, but I did have my initial set up file so I replied to Phil (support@battlefront.com) with that file on May 22nd. Then on June 1st I received an email saying that they hadn't heard from me in 240hrs...on June 2nd I received another stating that they were changing my ticket status to closed because they hadn't heard from me. Apparently Battlefront's ticket tracking system isn't logging all the replies and tickets are getting canceled that shouldn't.
  3. I'm also getting a crash with the full release. I was playing a small quick battle in real time and the game froze and then crashed back to the desktop after about 20 minutes. What the heck...I received an email stating that the bug which caused the crash in the demo was patched before the full release...this crash looks suspiciously similar. I submitted another ticket with crashlog: MFN-880290
  4. As suggested, I opened a ticket via the help desk link and provided the crash logs and the saved game file. Later I was able to complete the scenario (Road to Berlin) playing it in real time. No errors at all. Still a no go when playing it turn based. Real time is a bit hectic, I had to keep switching my attention between my left and right flanks, but even so I did well with 16 wounded and 5 dead. The crew of one Sherman bailed out near the crossroads after an unfortunate shrek hit, but they had plenty of friendlies around who were able to prevent the nasty German shrek team from getting another chance to finish off the abandoned tank. I was just about to recrew the tank when the scenario ended with under three minutes left on the clock.
  5. Hate to start yet another thread about game crashes, but I wanted to be sure that the Mac coder saw this. This crash was on my iMac (2.8GHz Core 2 Duo, 4GB RAM, OSX 10.6.7), but I experienced a similar crash on my MacBook Pro as well. I can send the entire crash log dump, but didn't feel it was necessary to plug up the forum with all that...just let me know where I should send/post it. The crash seems to occur at a random time in the game usually after clicking something on the screen. The first time it happened I was surprised to see that there was no autosave feature. I'm now in the habit of saving after each turn. Jeff ========= Process: CMBN [19492] Path: /Applications/CM Battle for Normandy DEMO/Combat Mission Battle for Normandy Mac DEMO.app/Contents/MacOS/CMBN Identifier: com.battlefront.CMBN Version: 1.0 (1) Code Type: X86-64 (Native) Parent Process: launchd [14929] Date/Time: 2011-05-13 13:01:36.805 -0400 OS Version: Mac OS X 10.6.7 (10J869) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000009 Crashed Thread: 0 Dispatch queue: com.apple.main-thread =========
  • Create New...