Re: "Access Violation"
Quote:
Originally Posted by Mobhack
Quote:
It is purely a problem with ScenHack. In-game everything is fine. No crashes whatsoever. Just one or two scenarios in ScenHack fail to register properly when I click on the "make tables" function under the SQL tab - specifically six of mine all of which use modified OOBs (units from 35, 44, and 42).
Other Scenarios I've made have, however been processed by ScenHack without any problems and have produced tables in SQL without incident. These also used the same OOBs and even the same units in some cases.
I hope that clarifies things.
|
In which case then its probably something you have done in the barfing scenarios themselves that has caused a problem with the database table-building for some reason.
for example - have you done say, cross-attaching in the suspect ones but not in the ones that pass? Or put new leader names in and/or renamed units (but not in the ones that pass)?
Whatever it is that you did differently is the likely problem. It would be handy to know that, if you can isolate whatever that was.
If you could zip up a problem (and an OK) scenario (and any altered OOBs it needs too, any altered SHP and leader names etc as well) I'll be able to run that through the debugger and see what the thing is falling over trying to read in.
cheers
Andy |
OK. Thanks for the offer!  That is a pretty big zip file though. I'll see what I can do. Will get on it by Friday - weekend at the latest.
It can't be cross-attaching or leader names as in both cases I've done that liberally. Same goes for loadouts, leader names and unit designations.
__________________
"Wir Deutschen sollten die Wahrheit auch dann ertragen lernen, wenn sie für uns günstig ist."
Last edited by RecruitMonty; February 1st, 2017 at 02:35 PM..
|