Jump to content

Recommended Posts

Posted

After checking out the latest Dev Diary I went straight over to FilePlanet to check out the DOA "proof-of-concept" program that SC posted. Unpacking it, however, yeilded twp CRC errors. One in bcte-debug.exe and one in fexplode1.wav. So far I havn't been able to get it to run. The screen goes black for a few seconds then I get dropped to my desktop. Anyone else get around these probs?

Posted

Read in the BC Legacy discussion forum. There is an ini file that you need to edit. I can email you the file if you want.

Posted

Actually, if he's getting a CRC error, just download it again. And before you run it, just delete or rename the bctespawn.ini file. That file was used as hook into BCM but the standalone BCTE module does not need it. I forgot to delete it before uploading the file to the Net. oh well.

Posted

Alright, I got the thing to work. To say the least, I'm kinda glad that you decided to go with another engine. BCTE only looks like it had a couple weeks work, but Quake makes that engine look outdated. I'm expecting something at least on par with ST Voyager: Elite Force or AvP2. Hopefully the latter.

Posted

SC, I had the same 2 CRC errors, as well. I also think I remember hearing other people in the BC Legacy Discussions Forum, saying the same thing. Possibly the upload was the one being corrupted, because many people with the same files with a CRC error, should indicate something.

Posted

quote:

Originally posted by Supreme Cmdr:

....which is why I said to download it again.

What if it's the source file (on the server) that is corrupted? I don't remember my previous corrupted download... and I've downloaded gigs of data... hundreds of megs at a time (strike force for UT was 255megs)... but no file corruption.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...