Jump to content

TexasToast

Members
  • Posts

    188
  • Joined

  • Last visited

Converted

  • Location
    Dallas, Texas, USA
  • Interests
    CM, sports
  • Occupation
    software developer

TexasToast's Achievements

Senior Member

Senior Member (3/3)

0

Reputation

  1. I know that one! It's in /Users/(username)/Library/Application Support/GreenAsJade/H2HHelper. The file is called AppState.txt. TT
  2. Sorry - asleep at the wheel. I put 1.5.3 Mac up in the dropbox, as soon as the 1.5.4 changes get pushed up to the repository I will update to the latest. TT
  3. So that's what that lock is for! Maybe at least a quick reference is needed for documentation? And what is the little command icon towards the right for infantry that looks like they are laying down - hide? For unit stats, I'm talking about kill stats. At the end of the battle in CMBN, when you click on a unit it will show you how many casualties it caused and what vehicles it destroyed.
  4. I've played a few battles now and feel like I'm missing a few things: - When using the top center button to position the camera: If you touch a unit icon, go to that position AND set the camera to the facing of that unit. - Provide the top center button to position the camera during the replay phase. - Option to show unit icons in replay phase. - Ability to lock camera to unit in replay phase! (using three above features) This really adds to immersion factor in replay. - Show unit stats at the end of the battle. It's really nice to know who did what. TT
  5. Hi Allan, There is a WAV file with the app called newTurn.wav. If you put a different file with that name in the same place, it will play it instead. TT
  6. Interesting battle and story, and great production quality! TT
  7. Hi Doug, Since we haven't been able to figure this out yet, I put up a new Mac version 1.2.8 that has all the cool 1.2.x stuff but doesn't trim the log window entries. Since the log window will work basically the same as in the 1.1.3 version you are using, it should be OK for now. Thanks for your help and patience. TT
  8. My theory is that the difference is due almost entirely to the nature of the scoring systems. In CMx1, you always scored points for enemy losses and lost points for friendly losses. Since both sides generally took losses and those losses formed a significant part of the total score, the results tended towards the center. With CMx2 scoring, there is often not a penalty for losses at all, or perhaps just a bonus for keeping friendly casualties low. Therefore the final score is more extreme for the same battle action as in CMx1. TT
  9. Maybe the first time starting up, but it shouldn't be slow after that. If it still seems sluggish, maybe you can send us the log file using the new "Report Bug" feature? Thanks!
  10. BadgerDog - Saw your error, that's a new one. Try the new alpha if you get a chance, this time move the previous version somewhere else before copying the new one over. I'm guessing it could have been some kind of issue with copying over an existing app, or maybe the previous app that was posted was missing something. Thanks for testing... TT
×
×
  • Create New...