posted 01-11- 11:07 PM               

I'm have a problem with EXTRACTOR or BUILDER. I've encountered the following problem.

If I take an .sm file (in this case the ME262) and load it into OPS all works well. After editing the sm file in AC3D and BUILDing the file back again I can no longer load the sm file into OPS.

So I took an unedited sm file EXTRACTed that file then BUILDERed the .SM file back again and tried to load that file into OPS I get the same error message as follows...

"Unexpected record type incountered: 0x86BD40000, last record read : 0x1BCD0001"

I've downloaded the most recent Hippie tools. Here are the files that I am using in my working subdirectory to do the extract & build...

builder.exe 327kb 9/9/99 8:59PM
extractor.exe 320kb 9/9/99 8:57PM
cygwin1.dll 446kb 12/3/98 8:44PM

Do you have any suggestions on how I can prevent this problem?

Bryan has written to say that the 'Built' sm file contains trash characters after being built.

I've already deleted and redownloaded Hippies tools with the same result.

Has anyone had this problem? How do I get around it???

posted 01-12- 05:51 AM               

I have never used the ME262 though - but others have.

Basic things to check:

1. The ME262.sm file is really the un-edited one.

2. The extractor extracts the ME262 into one folder that had nothing in it.

3. You re-built the SM file just after extracting it and were using the same directory.

My best guess is that somehow you are getting some files confused along the way. I would do a fresh new test just like you have done. If it still doesn't work than it must indeed be a problem with Hippie's builder/extractor and/or Bryan's OPS specific to the ME262 SM file...

Just guessing here... I hope you get it working soon

------------------
-Sv =FC=

WWI in SDOE!

posted 01-12- 11:25 AM               

Good suggestion. I've been working with Extractor, Builder, the DLL file and the sm file in a single directory. I've been extracting and building within that single directory. I'll try your suggestion of extracting to an empty directory and building from there.

I'll try it and let you know.

posted 01-12- 01:16 PM               

Are you trying to open OPS by double clicking on the Sm file? Atleast on my machine, when I do that OPS starts to open but I get a page fault with OPS. Taking the same file and loading it from within OPS has no problems.

Now like SV, Ive had trouble with builds aswell. This happened to me after editing the ASC file. I had left out a line. OOPS!

Along with SV's suggestions you might try loading your "original" 262 sm. Before you have extracted it. That will tell you atleast if the orignal file is corrupted or not.

Good Luck,

------------------
Zoycite {GS}
GUNSLINGERS

visit The War Paint Factory

posted 01-12- 05:47 PM               

Once you modify a file in OPS, Builder does not recompile that file. If you have a bunch of .lod files and the .asc file sitting there, builder simply recompiles all those files into the OLD .sm file again! OPS works directly on the .sm file, so using Builder on something you just modified in OPS just undoes what you just did

After modifying a file in OPS, first EXTRACT all the .lods again using Extractor. This will give you the NEW, modified .asc file and the new .lod files you just made in OPS. Then if you use Builder, it will be using the right parts.

If you use Builder right after modifying, it will appear that your modifications "didn't take."

posted 01-12- 06:33 PM               

Q - "Are you trying to open OPS by double clicking on the Sm file?"
A - I'm having no trouble opening files in OPS. Only after using BUILDER.

Q - "Along with SV's suggestions you might try loading your "original" 262 sm. Before you have extracted it. That will tell you atleast if the orignal file is corrupted or not."
A - Yep, thought of that and it showed that the original sm was just fine. I then extracted that "working" file and then Built it right back. After BUILDER the file would no longer load into OPS due to some new corruption that became inserted into the file.

Jedi-
Thanks, I'm having no problem with that part. Just my sm file becoming corrupted during the build phase.

After I get off I've got a couple of things to try. Thanks alot for the tips guys...

posted 01-13- 12:51 AM               

Does your corrupted .sm file crash the game, or just OPS?

posted 01-13- 10:49 PM               

I must not be describing what I'm doing well so let me try again.

1) I test the me262.sm file by loading it into OPS. No problem. The sm file loads fine.

2) I copy the me262.sm file to an empty subdirectory.

3) I use EXTRACTOR me262 me262. I check the directory and all the expected asc, html, lod files are there.

4) Then even if I do NO EDITING at all but just do a BUILDER me262 me262. And then try loading the resulting sm file back into OPS I get the error message!?!?!?

So what do you think???

Ronin

SV -
I now have tried EXTRACTOR and BUILDER with both with other file in my sm "working subdirectory" and with no file but the sm file and the extracted sm files my "working subdirectory". Either way I get the error message.

posted 01-14- 03:39 PM            

Are you sure you tried it on the original untouched me262.sm file?

posted 01-14- 06:33 PM               

Good question! Actually, at first I did have only those three file. Since then I've tried it with all of the EXTRACTOR-30B.ZIP files in that subdirectory. Same result.

posted 01-14- 06:43 PM               

Dang I'm glad to see you pop into this discussion!

I definately know that the ME262 is NOT the original release verision. About a month ago, Micheal H. released a file that had all of the original AC in it. This release supposedly included "fixed" models. I'm not sure what specifically was "fixed"?

Anyway, since that represented the last "official" Parasoft release of the ME262, thats the one that I thought should be the starting point for my current work.

Interestly enough, I just tried BUILDER on the FW190 from that same release and it gives me the same error message when I try to load it into OPS.

I just EXTRACTOR'd SV's SE5A and BUILDER'd it right back. It loads into OPS just fine!

That appears to indicate that there is something about the newly released ME262 and FW190 that BUILDER is not happy with???

What do you think??

I'll go send MH a post and ask him to join this thread since this maybe pointing to those new AC that he released.

Ronin

posted 01-16- 03:06 PM               

The zip with the 'fixed' planes file is ~6meg. Send me your email address and I can send you just the me262.sm zip file at 78k.

Anyone, remember where the Parasoft file with the fixed plane models is posted???

posted 01-28- 06:40 PM               

HIPPIE has released Extractorg.exe that fixes this problem. So if you are using planes from MH's latest ~6mb release of the original SDOE box plane set use this file and not the original extractor.exe found in the Hippies tools zip.