PDA

View Full Version : Tool spills out an error!



Spartan094
July 18th, 2009, 04:42 PM
C:\Program Files (x86)\Microsoft Games\Halo Custom Edition>tool model cod5\weapons\usa_tesla_gun
Couldn't read map file './toolbeta.map'
### by by blackbird.jms
### WARNING found #13 coincident triangles.
EAX: 0x00000000
EBX: 0x00003F01
ECX: 0x00000000
EDX: 0x00000000
EDI: 0x0017F580
ESI: 0x00000000
EBP: 0x0017F458
ESP: 0x0017F44C
EIP: 0x77B01626, C2 08 00 8D ?????
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#846: element_count>=0:mech: I never seen this error and it might not be that common.
Element_count? I think its talking about poly's, if so is 16,000+ to much for tool? or the 13 coincident triangles.

What I'm trying to do is import the Wunder Waffe DG-2 from cod 5 into halo since I think I got down the electric thing.
http://i214.photobucket.com/albums/cc286/Brandon094/wunderwaffedg2.jpg

Help would be nice.

teh lag
July 18th, 2009, 04:47 PM
It's certainly not the poly count (though I would advise against a 16k poly weapon). Can you compile a different .jms in this one's place? Just export a box, that error makes me think the tag itself is somehow corrupt. (How is beyond me).

You can also try importing your debug.wrl (which should be created on compile of a model - though the exception may be interrupting it) and seeing if there's anything to be found in it.

Spartan094
July 18th, 2009, 05:04 PM
I import the debug.wrl but when I imported it, there are 27 entities it imported but all 27 are outside the model or above it.

When I created the box and such and exported it tool was fine. I am really stumped on this.

And yea 16K is abit high but I blame Treyarch

teh lag
July 18th, 2009, 05:12 PM
Are you sure the debug.wrl isn't from an older project, and it just isn't getting updated? Also, make sure you're importing it correctly (all 3 boxes unchecked).

If that's all been checked, try splitting up the model and seeing if individual parts of it will get past tool.

Spartan094
July 18th, 2009, 05:56 PM
Ok, the wrl is up to date and i re-checked it. I imported with all 3 boxes unchecked, the parts were it was nagging at, they had double faces (like the same thing was there twice, unneeded polys which I figured wasn't good. I deleted them and compiled. It was the 13 coincident triangles I had just fixed which is still good.

And now I did what you said, split up parts of the model and checked each one peice by peice. The split up model peices went thru tool just fine and then I tried exporting it all togther, It gave me the same exact error. :ugh:

Whoop, new error

C:\Program Files (x86)\Microsoft Games\Halo Custom Edition>tool model cod5\weapo
ns\usa_tesla_gun
Couldn't read map file './toolbeta.map'
### by_by_blackbird.jms
EAX: 0xFFFF8000
EBX: 0x00000001
ECX: 0x032968B5
EDX: 0x0334D9C8
EDI: 0x053A0068
ESI: 0x00008000
EBP: 0x00007FFE
ESP: 0x0017F894
EIP: 0x00407722, 66 89 0C 47 ?????
EXCEPTION_ACCESS_VIOLATION

EXCEPTION (that's all I know!)

Siliconmaster
July 18th, 2009, 11:56 PM
Ah, the access_violation error. Didn't we have another thread about this lately?

For me that's usually equivalent to the "cannot modify because file is open or being used by another program" windows error. Make sure there isn't another program interfering with it. Try closing everything but tool and trying again.

The culprits in my experience for sapien are things like haloCEdev.exe or flycam. However, this looks like it's the file itself that's being used, not a 3rd party program.

Spartan094
July 19th, 2009, 12:25 AM
Good 'ol fashion help is good. I used bobby's edited jms exporter and it worked much better then the old jms exporters. Then i just realized as soon as i imported it i had to do 7 shaders. Most of which are glass. So i have to redo the entire thing over again and see how many errors I get again. So I'll leave the thread open just in-case I get anymore errors.

But thanks helping me out lag, your the best :realsmug:

Cagerrin
July 19th, 2009, 12:28 AM
Ah, the access_violation error. Didn't we have another thread about this lately?

For me that's usually equivalent to the "cannot modify because file is open or being used by another program" windows error. Make sure there isn't another program interfering with it. Try closing everything but tool and trying again.

The culprits in my experience for sapien are things like haloCEdev.exe or flycam. However, this looks like it's the file itself that's being used, not a 3rd party program.
One thing I've noticed occasionally is that explorer.exe will be using files somehow, and usually there's no way to know that because you'll practically always have it running. This (http://ccollomb.free.fr/unlocker/) I found to be extremely useful.

Spartan094
July 19th, 2009, 01:32 PM
http://screenshot.xfire.com/screenshot/natural/37cae5edf6f424bba2d50f21d34c5e2e800ca48c.png
Thank you lag, cagerrin, and siliconmaster482. Got it in-game no problem :iamafag:

No need for this thread anymore.