Bug in Scenhack?

Suhiir · #1 February 1st, 2010, 02:53 PM

While working on one of my OOB showcase scenarios I got the following message while trying to use Scenhack.

"Access violation at address 65676561. Read of address 65676561."

I can still use the Editor to open and modify the scenario as normal. And if I remove the German (OOB #044) units and replace them with more USMC (OOB #013) ones the access violation error doesn't show up.

Attached is a copy of the buggy scenario.
Note: This uses my modified USMC OOB.

DRG · #2 February 1st, 2010, 08:27 PM

Anyone loading this is going to find a half gazillion things to "fix" unless they have your OOB installed. However, I do not get an Access violation message but I'm using a more up to date version of scenhack than you are but AFAIK the only real difference was a change to fix changing game length.

Maybe time to defrag the HD??

Don

Suhiir · #3 February 1st, 2010, 09:25 PM

Might well be.
Thanks.

Arralen · #4 February 2nd, 2010, 09:48 AM

Instead of defrag-ing, I would run a chkdsk /f first, just in case the file system is damaged ... simple fragmented files normally shouldn't pose any troubles since we left Win9x behind ... .
Maybe add a /r, because a NTFS file system does not damage itself normally ...

And while you're at it, maybe get yourself the "Ultimate Boot CD" , and run some RAM diagnostics first (Memtest-86 / plus). I advise doing that every couple of months anyway - RAM or motherboard starting to show faults isn't something you'll spot at once, but only when things already got really bad - and some irreplacable data got lost

But then, most likely, it's only the OOB that has some value in it that scenhack does not like at all. Therefore, instead of attaching the scenario file, better attach the OOB file for the developers to check !

Suhiir · #5 February 2nd, 2010, 12:24 PM

That's why I sent this.
The bug showed up when I used something from the German (OOB #44) file NOT my revised USMC (OOB #13) file.

That said, it's certainly possible I have a RAM problem.
But I tried removing the German OOB stuff from the scenario.
No problem.
Added USMC stuff in same unit slots.
No problem.
Remove USMC stuff, add German stuff.
Got the same exact error.
*shrugs*

DRG · #6 February 2nd, 2010, 01:17 PM

EXACTLY what were you doing when this happened ?? What unit ??

Don

Suhiir · #7 February 2nd, 2010, 07:56 PM

The last unit correctly displayed was a W German scout (OOB #44, Unit 388).
The next unit - the one not displayed - was also W German (OOB #44, Unit 512, 513, or 514) a Fjaeger scout. Can't say for certain which specific unit because it'd data is not displayed by Scenhack.
As to what I was doing -
I'd been purchasing units for a scenario I'm creating.
The W Germans were intended to represent an ambassador and his bodyguards.
I had not finished buying all the units I intend to but opened Scenhack to change the icon of a USMC ammo truck to a different icon I was using to represent it as a fuel truck for this specific scenario (I've done this before with zero problems).
When I loaded the scenario with Scenhack - bam - the error message.
Scenhack shows all my units up to #308 correctly, but #309 and on are not displayed.

Hope this helps.

DRG · #8 February 3rd, 2010, 12:23 AM

It loads for me without a problem in the editor, scenhack and as a sceanrio despite the majority of units being non existant becasue I'm using the stock OOB's

One thing I did notice though...... there were no MP's in the 'Marine REMF' unit.

I wonder why that would be......???

Don

Suhiir · #9 February 3rd, 2010, 01:41 PM

You were looking at a "Work in Progress".
Give me time to finish it.