Re: "Access Violation"
As far as I recollect Scenhack does not read scenario info text, display lbms or shps etc.
When exactly does it crash e.g. "Scenario loads OK but when I go to screen X and select unit Y .. kaboom!". In order to debug something, one needs to know exactly what path is taken to get to the fault. That is far more helpful than a vague and woolly statement of "it has an access violation error!" with no specifics.
For instance - is everything OK until you go to open the formation detail screen. (Which would point you to something being wrong formations wise with the OOB in question I'd infer!).
Then what is special about the scenario that causes the crash?. Do other scenarios using that hacked OOB load OK?. If they work OK, then what's the difference - uses some particular unit or formation or weapon the others don't, perhaps?. Or uses something that's no longer there since it got edited out of that OOB...
|