Important Message

You are browsing the archived Lancers Reactor forums. You cannot register or login.
The content may be outdated and links may not be functional.


To get the latest in Freelancer news, mods, modding and downloads, go to
The-Starport

Help needed with persistent FLSpit error messages please

The general place to discuss MOD''ing Freelancer!

Post Sun Dec 04, 2005 2:04 am

Help needed with persistent FLSpit error messages please

Guys,

I really have tried to get self-help from this and other forums for more than the past 3 weeks unsuccessfully, including using CRC Tool, loads and loads of other utilities, and trying to get CRC-reverser to work (it wouldn't for me at all, whatever I tried and I am a no mean hand with the PC).

I really would appreciate any and all help on any of these following problems reported in FLSpit, or a good strong tip on where to actually find the key to crack them (no red herrings or wild goose chases I mean, please be sure your tip is correct and gives me a clear answer there) would help me a lot if you don't want to give me the direct answer.

But if you do know any of the answers or can help me crack some of these then I would appreciate your help very very very much, I'm pulling my hair out (what's left of it).

<Where are my glasses...??? What? Where? Oh - on my... head... Hmmm.... eerr... Thanks!>

1. *** WARNING: unknown Sound archetype '0xab50aa01'

2. *** WARNING: unknown Sound archetype '0x81dfc383'

3. This is the old one I have seen so many times, but I have not found a decisive fix for it - is there a clean file somewhere or should I just delete all references to envmapglass (if so where please?)...
WARNING:General:load texture: file contains an old or unknown format, ignoring envmapglass
WARNING:General:failed to load 'envmapglass'
*** WARNING: '' missing texture (envmapglass)

4. *** WARNING: Failed to get start location

5. NOTICE:General:texture verify failed: nomad surface: NomadRGB1_NomadAlpha1

6. *** WARNING: invalid MSG id (3115842312) for voice profile (0xb4902287) (this is in system EA03 in the WTS Worlds mod).

(I know voice 0xb4902287 is atc_leg_m01) - can't decode the 3115842312 tofind the message that's being called though - help?

7. *** WARNING: Voice message 2351700488 is invalid for voice 3073825485 (also EA03)

8. Any idea why the voice in 7 above here is in decimal? (in hex it is 0xB736DACD)

9. *** WARNING: Voice message 2831513921 is invalid for voice 3073825485 (also EA03)

10. *** WARNING: invalid MSG id (2476759050) for voice profile (0xb4902287) (in HA01)


Many thanks in advance to anyone who can give me any help or any good pointers please.

StarTrader

Post Sun Dec 04, 2005 2:51 am

In general... such NNVoices spew are one of the big banes of FL mods. These errors can cause a lock state or memory leak, and cause FL to crash.

To avoid these issues, there are a series of (uncomfortable) choices to make:

1. Remove all references to Voices for the characters that speak at the Bases effected. This is pretty easy to accomplish, and it works fairly well.

2. Make sure that your fighters are being referred to by the appropriate handles. I have found that the generic Voice references used by the Bounty Hunters ships get rid of a tremendous number of errors- NNVoices, no matter which Base is addressing you, seem to be ok with "Heavy Fighter Patrol", "Light Fighter", etc., whereas it appears that Bretonian NNVoice handles, for example, don't seem to work right in Liberty space. I'm using these generic handles in the next version of Toolkit, because it's cut down these errors by quite a bit. Sadly, there isn't a generic Freighter handle that I know of, let alone a Gunboat, etc.

3. Lastly... you could fix these things the hard way. We now know how to get into the NNVoices files and edit things- in theory, we could rebuild the Voices entirely, although the specific references to many things are hard-coded, and at best you could replace them with nulls, as I have done with Toolkit to remove the "Shield Failed" NNVoice message, so that a certain new Shield type could work without causing a memory leak crash.

Post Sun Dec 04, 2005 3:00 am

Ah... as for the Envmap_glass... there's a reference to that somewhere... basically, DA was going to use two Envmaps per model... one for the ship's skin, one for glass. It's really, really too darn bad that they didn't do this- I've figured out how to do some pretty amazing things with envmaps, but if you can't apply it to sub-areas, it loses a lot of potential versatility. You can find that reference and comment it out, I believe, without causing undue harm.

As for the texture error wtih the Nomad stuff... me suspects that you are working with an object that's trying to declare itself to be a Nomad object... that's not properly set up. You're going to need to find that object (a custom CMP, no doubt) and fix it up in UTFEdit, using the original Nomad ships as your reference. The Nomad textures/normalmap/cubemap are a pain to work with, and you may just have to ditch whatever's causing this problem. That said, the usual worst-case scenario with bad MAT references is an invisible object... FL is amazingly good at exception handling!

Post Mon Dec 05, 2005 11:57 am

Argh,

Very many thanks for this. Is there somewhere I can get the info to decode those voices & messages? CRC Reverser just didn;t work for me no matter what I tried?

Post Wed Dec 07, 2005 9:22 am

Umm...

Any more help please guys for the other points?

e.g. The message decoding?

Really appreciate it, please keep it coming.

Many thanks in advance.

StarTrader

Return to Freelancer General Editing Forum