Tried placing the cmt playable elite_v2 biped into the tutorial map to tinker with it, and it placed fine in Sapien. However when I try to compile the map to get it in-game, I end up with this error in the debug.txt:

11.13.14 11:03:28 EAX: 0x00000000
11.13.14 11:03:28 EBX: 0x000C0000
11.13.14 11:03:28 ECX: 0x000297C6
11.13.14 11:03:28 EDX: 0x00198F88
11.13.14 11:03:28 EDI: 0x1BC78000
11.13.14 11:03:28 ESI: 0x1BB84F90
11.13.14 11:03:28 EBP: 0x00074E94
11.13.14 11:03:28 ESP: 0x0018A038
11.13.14 11:03:28 EIP: 0x00436131, F3 AB 8B CA ?????
11.13.14 11:03:28 EXCEPTION_ACCESS_VIOLATION

I've narrowed it down to the .gbxmodel, if I dereference that from the biped tag, everything compiles just fine. Any ideas on what inside that may be going wrong? I copied everything straight out of the release pack, so I doubt it's corrupted, and I overwrote all necessary tags, so no old remnants are sticking around and it's not referencing anything but the new material from the release.

incoming V3 (?)

http://forum.halomaps.org/index.cfm%3Fpage=topic&topicID=36746


You said the gbxmodel still references a new shader? Take a look in that shader's bitmaps and look for ones that don't have the 'compressed' flag checked, and check it. That's how the problem was fixed in the thread above, at least.

Ok, all shaders referenced are cmt\characters\elite_v2\ shaders. All bitmaps referenced have compressed checked and will open successfully in Guerilla.

Same error, no change.
Edited by NeX on Nov 13, 2014 at 04:19 PM

Wierd. I've never encountered this error before, so I'm just going off of what threads discussing the F3 AB 8B CA EXCEPTION_ACCESS_VIOLATION problem can provide. Most of them seem to make out the problem as being one with corrupted tags, primarily being bitmaps from what I've read.

Unless any better solutions present themselves, I'd imagine the only thing to do would be to reacquire the tag from its source. Hell, I wonder if using FireScythe's Bitmap Extractor to get the images, then using tool to recompile them again could provide working tags. This is, of course, if the issue is actually with the bitmaps themselves.


List of threads discussing the error:
https://www.google.com/search?q=F3+AB+8B+CA+EXCEPTION_ACCESS_VIOLATION....
Edited by Dennis on Nov 14, 2014 at 11:33 AM

Yeah i searched extensively before posting this. The issue is that i did aquire the tags directly from teh lag's release....thats the odd part.

Update:

I compiled all of the bitmaps anew after extracting them into .TIFs, deleting the original .bitmaps, creating new ones that were identical, and using those to compile the .TIFs.

Still getting the same issue ><
'Tis infuriating. When I get home today i'm going to replace all shaders in the model with some random shader_model that I know works fine, and see if I just need to create new shader_models or something weird.

Anyone have any other suggestions?
Edited by NeX on Nov 14, 2014 at 09:35 AM
Edited by Dennis on Nov 14, 2014 at 11:33 AM

Don't overwrite tags anymore, I learned my lesson the hard way. In any case just use a different elite biped but with the elite v2 animations... That's an easy fix.

All the elitev2 models give me the same issues

Are you using OS?

I'm not.

I know de-OSed shaders can throw issues, so if the random shader_models work out, it'll be simple to recreate the v2 shader models from the existing bitmaps modeled after the currently corrupted ones, but thats under the assumption that that is indeed the problem.

I meant use another model a sin the stock elite. Next time don't overwrite tags.