So, I get a plethora of these errors:


Message Severity: 3
.\Source\VehicleSpawn.cpp(135)
Vehicle spawn missing command post "cp1_control"

Since, as Tean put it, enough Severity 3 errors will eventually crash the map, I think it might be the case (I have a LOT of vehicles on both command posts). Even if this isn't the cause of the crash, it is COMPLETELY WRONG. I have checked, re-checked, and checked again each and every single last vehcile spawn. None of them say cp1_control or cp2_control. They say cp1 and cp2. The command post names, the control region names, everything in ZE checks out. Trust me.

I tried a manual clean. No dice.

As for the crash, it happens a few seconds after I spawn. Initially, I thought it was a side issue (had those before), but then I realized....I didn't modifiy the sides at all since the last munge, and there was no crash then. I see no other Severity: 3 or worse errors that could have caused this (those that are there (except the cp1_control errors) have been there for the last SEVERAL munges, and have not caused a crash). Regardless, here's the log:

Nothing in the log looks suspect. Have you added a lot of objects to the map? I know you mentioned that you hadn't changed the sides, but typically a crash like that is due to not being able to find a weapon. Depending on how fast that crash is you might look at secondary weapons.

The last thought is you're hitting a memory limitation. If you can get mod tools to run long enough. Right when the map starts, bring down the console with ~ and type mem.

There are these
As soon as someone tries to use it it may/will cause a crash.

Also there are some FPMs
FPM have to be maually copied to the games FPM folder, I'm not in front of my computer at the moment (no the other one with all the good stuff on it ) but I believe it is in the sides folder

Teancum wrote:Nothing in the log looks suspect. Have you added a lot of objects to the map?

There are quite a few, but I didn't add any more between the munge that worked and the ones that didn't. Is there any way to check and make sure I'm under the object limit?

Teancum wrote:I know you mentioned that you hadn't changed the sides, but typically a crash like that is due to not being able to find a weapon.

That was my first thought as well. I'll take a closer look, I guess.

Teancum wrote:Depending on how fast that crash is you might look at secondary weapons.

Right, that's what it was last time this happened.

Teancum wrote:The last thought is you're hitting a memory limitation. If you can get mod tools to run long enough. Right when the map starts, bring down the console with ~ and type mem.

Here's the memory log:

FragMe! wrote:There are these

Code: Select all

Message Severity: 3
.\Source\Weapon.cpp(2044)
Weapon "rep_weap_inf_haywiredetonator" missing geometry "cis_weap_inf_thermaldetonator"

Message Severity: 3
.\Source\Weapon.cpp(2076)
Weapon "rep_weap_inf_haywiredetonator" missing high res geometry "cis_1st_weap_inf_thermaldetonator"

As soon as someone tries to use it it may/will cause a crash.

Right, but I haven't set any classes up to use them.

FragMe! wrote:Also there are some FPMs

Code: Select all

Message Severity: 3
.\Platform\Pc\pcFirstPerson.cpp(69)
FirstPerson::LoadLVLFile: Could not open FPM\ksh\ksh.lvl

Message Severity: 3
.\Platform\Pc\pcFirstPerson.cpp(69)
FirstPerson::LoadLVLFile: Could not open FPM\clo\clo.lvl

FPM have to be maually copied to the games FPM folder, I'm not in front of my computer at the moment (no the other one with all the good stuff on it ) but I believe it is in the sides folder

Thanks for the tip. And yeah, it might be the sides, but I still can't figure out why the game is saying that a vehicle spawn is calling for a cp_control name when there is not a single one in my conquest (or any) layer that does.

Are you saying you do not have a cp1_control region in your map?

The control region is what determines when the vehicle is destroyed, meaning if the command post is taken over all the enemy vehicles blow up that are still parked at the CP, and if one for your team is defined it shows up. It will also cause any abandoned vehicle outside the region to blow up after a certain amount of time.
I think the error is there because a vehicle spawn by game definitions automatically looks for the control region of the cp name if one is not defined in ZE if you know what I mean. Having had this error before and the map it was on functions fine it is a non-crashing sev 3 error.

FragMe! wrote:Are you saying you do not have a cp1_control region in your map?

The control region is what determines when the vehicle is destroyed, meaning if the command post is taken over all the enemy vehicles blow up that are still parked at the CP, and if one for your team is defined it shows up. It will also cause any abandoned vehicle outside the region to blow up after a certain amount of time.
I think the error is there because a vehicle spawn by game definitions automatically looks for the control region of the cp name if one is not defined in ZE if you know what I mean. Having had this error before and the map it was on functions fine it is a non-crashing sev 3 error.

Ah, ok. I do have a control region for both cps, but the documentation says that, under a vehicle spawn's "ControlZone" parameter, you're supposed to enter the associated CP Name, not the Control Region name. In any case, I do indeed have a cp1_control and cp2_control region, refrenced properly by my command post objects. Also, the vehicle affected by this don't spawn unless they are refrenced under the "ClassNeutral" paramiter (in other words, it's not being set up properly as a vehicle of that command post, for reasons that are still eluding me).

Update: It's not the sides. I just replaced the entire setup teams function with the default (basically made my LUA into a default one). It loaded fine, I spawned fine, etc. And then it crashed. Nor is it the command post issue, because I just fixed that. I am seriously at a loss.