Page 1 of 1

Sides munging. [Solved]

Posted: Tue Mar 25, 2014 8:20 am
by thejolf
Okay so I tried to customize a unit (just the rep_inf_ep3trooper to start with).
When I munge it doesn't even seem to be that which is causing the problem, I get this in the log:
Hidden/Spoiler:
WARNING[PC_modelmunge msh\rep_inf_jettrooper.msh]:rep_inf_jettrooper has 2379 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_walk_atte.msh]:SplitSkinnedSegments: WARNING: out of space in splitting catalog!
WARNING[PC_modelmunge msh\rep_walk_atte.msh]:SplitSkinnedSegments: WARNING: resorting to brute force, this may take a while...
WARNING[PC_modelmunge msh\rep_walk_atte.msh]:SplitSkinnedSegments: WARNING: out of space in splitting catalog!
WARNING[PC_modelmunge msh\rep_walk_atte.msh]:SplitSkinnedSegments: WARNING: resorting to brute force, this may take a while...
WARNING[PC_modelmunge msh\all_inf_luke.msh]:all_inf_luke has 1171 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_aaylasecura.msh]:SplitSkinnedSegments: WARNING: out of space in splitting catalog!
WARNING[PC_modelmunge msh\rep_inf_aaylasecura.msh]:Mesh rep_inf_aaylasecura segment sv_aaylasecura vertex 6 has invalid weight[0]=1.000169.
WARNING[PC_modelmunge msh\rep_inf_aaylasecura.msh]:rep_inf_aaylasecura has 1597 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_aaylasecura.msh]:Mesh rep_inf_aaylasecura segment sv_aaylasecura vertex 6 has invalid weight[0]=1.000169.
WARNING[PC_modelmunge msh\rep_inf_arctrooper.msh]:rep_inf_arctrooper has 2031 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_clonecommander.msh]:rep_inf_clonecommander has 1560 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3anakin.msh]:rep_inf_ep3anakin has 2900 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3armoredpilot.msh]:rep_inf_ep3armoredpilot has 2193 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3cloakedanakin.msh]:rep_inf_ep3cloakedanakin has 3896 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3heavytrooper.msh]:rep_inf_ep3heavytrooper has 2280 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3jettrooper.msh]:rep_inf_ep3jettrooper has 2368 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3obiwan.msh]:rep_inf_ep3obiwan has 2936 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3sniper.msh]:rep_inf_ep3sniper has 4737 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3spacepilot.msh]:rep_inf_ep3spacepilot has 1797 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_ep3trooper.msh]:rep_inf_ep3trooper has 1963 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_feluciatrooper.msh]:rep_inf_feluciatrooper has 1364 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_kiadimundi.msh]:rep_inf_kiadimundi has 1713 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_luke.msh]:rep_inf_luke has 1171 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_macewindu.msh]:rep_inf_macewindu has 2866 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_pilot.msh]:rep_inf_pilot has 2418 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_pilot_low1.msh]:rep_inf_pilot_low1 has 1060 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_trooper.msh]:rep_inf_trooper has 1807 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_inf_yoda.msh]:rep_inf_yoda has 2283 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
WARNING[PC_modelmunge msh\rep_walk_oneman_atst.msh]:SplitSkinnedSegments: WARNING: out of space in splitting catalog!
WARNING[PC_modelmunge msh\rep_walk_oneman_atst.msh]:SplitSkinnedSegments: WARNING: resorting to brute force, this may take a while...
WARNING[PC_modelmunge msh\rep_walk_oneman_atst.msh]:SplitSkinnedSegments: WARNING: out of space in splitting catalog!
WARNING[PC_modelmunge msh\rep_walk_oneman_atst.msh]:SplitSkinnedSegments: WARNING: out of space in splitting catalog!
WARNING[PC_modelmunge msh\rep_walk_oneman_atst.msh]:SplitSkinnedSegments: WARNING: resorting to brute force, this may take a while...
WARNING[PC_modelmunge msh\rep_weap_inf_chaingun.msh]:rep_weap_inf_chaingun has 1178 vertices and NO COLLISION GEOMETRY (WILL BE SLOW)!
0 Errors 35 Warnings
I've tried doing a manual clean and I followed the tutorial I have to the letter, changed Sides from 'NOTHING' to 'rep'. The tutorial says to ignore warnings, but these ones seem to be causing my map to crash to desktop before it's finished loading.

Any advice?

Re: Sides munging.

Posted: Tue Mar 25, 2014 8:56 am
by Nedarb7
Do you have the common side folder inside your data_***'s side folder? If not you need to, without it a ton of the odfs will be incomplete (referencing to a parent odf that doesn't even exist.).

Re: Sides munging.

Posted: Tue Mar 25, 2014 8:57 am
by Anakin
i cannot see some very important things there. Please post the crash log from BF2

Re: Sides munging.

Posted: Tue Mar 25, 2014 9:32 am
by thejolf
Nedarb7 wrote:Do you have the common side folder inside your data_***'s side folder? If not you need to, without it a ton of the odfs will be incomplete (referencing to a parent odf that doesn't even exist.).
That was the problem. It didn't say that in the tutorial but I guess that's just me lacking common sense (no pun intended), thanks for the help!

Re: Sides munging.

Posted: Tue Mar 25, 2014 10:38 am
by AceMastermind
thejolf wrote:.. It didn't say that in the tutorial...
Which tutorial were you using? I just checked the ones here on Gametoast and they all say copy the common folder.

Re: Sides munging. [Solved]

Posted: Tue Mar 25, 2014 11:04 am
by thejolf
It's by someone called 'Fierfek'.
I don't think I got it from this website. It has been really helpful, but there's a few minor things like this missing from it.

Re: Sides munging. [Solved]

Posted: Tue Mar 25, 2014 11:13 am
by AceMastermind
Ah ok, i've only seen one version, I don't know what changes he made to the others. The problem with offsite tutorials is that we can't correct them if there is outdated, misleading or incomplete instructions.