|
batek688 -> [HARDWARE] Hemmoroid (11/20/2014 4:41:42 PM)
|
Sorry..not trying to be a pain in the arse, but: I'm not having much progress playing more than 10-15 mins of a scenario on build 573 before I get a crash (of the types i've posted further below in the forum -- mostly out of memory relating to the screen buffers). Is there any sort of idea/guestimate/etc on when a newer build will be publicly available for me to try? If it's "2015" then i'm going to have to roll-back to the prior version and try that. There are a few scenarios (like operation brass drum) that I can play further, but only if I play them certain ways and that sort of defeats the purpose =)
FYI -- the "trend" that seems to let me go further is to start with all aircraft/sensors off, big old tomahawk strike, and then very "focused" detection after that. In The Big Stick, example:
If I put up something like a JSTARS and RivetJoint in a North/South orbit off the coast of Syria, I will get a huge number of detections. If I then launch some TLAMs on the shoreline SAM/Radar sites to make a hole -- it crashes when the TLAMs start to hit. However, if I keep all aircraft down, I can send all the TLAMs in and take down every SAM/Radar site on the coast...but once I put that JSTARS up, it starts mapping out all of those mobiles/in-country sites and just sitting there it will eventually crash. These latest "crashes" are just that, "Command has stopped working" Dr. Watson things, not any sort of exception message I can post.
I posted a few examples in this forum over the past couple weeks but have since stopped for 2 reasons: 1) I see you reporting a lot of things resolved in much higher build numbers, and 2) The traces and/or the windows event log addresses are matches for things i've already posted so I don't want to chew up your time looking at 15 examples of the same thing.
Thanks!
B
|
|
|
|
