Kismet problem

[Catalavos]

I'm just getting started with Kismet so forgive my noobishness. In the following set-up, I have Obj's. 1 + 2 enabled and only Obj. 1 Activated. Set up like this, my bots have no idea where to go and they just kind of stand around in the spawn. If I remove Obj. 2 from "Enable Objective" they all run like gang busters to Obj. 1 and cap the hell out of it. Both Obj's have everything set properly up in Properties (volumes, unique rep. indexes, priority etc...). Also, with both obj's enabled, neither one shows up in the tactical view but with only 1 obj. it pops up right away.

So, does anyone see anything wrong with the way I have it set up with both obj's enabled? I have tried this with my own Kismet set-up as well as the one from the SDK sample maps and the TE-Spartanovka set-up with the same results.

 

[LordGleedo]

That is the initial level setup and it does look ok.

All objectives should be enabled as you have, and only the 1st objective should then be activated.

Can you post a screenshot of your kismet that actually gets used when the level has started.

This will most like start with a 'Obective Captured' node.

 

[Catalavos]

LordGleedo,
I've been messing with another Kismet setup and things got even stranger. This time I used the TE-Neutral setup from the SDK example maps set. For some reason, when spawning as axis tank commander I spawned inside of the first objective with my tank even though the tank spawn is nowhere near it. Didn't happen when spawning as infantry. Map ended when 1st. obj. was captured even though other objs. are enabled and activated.

 

[LordGleedo]

tbh I have not done anything with tank kismet setups so perhaps wolverine can offer some help on your spawn issue.

But the objective captured node looks wrong in what it's pointing to.

Your first 'objective captured' will be the captured node for the objective your enabled/activated in your initial setup kismet (your 1st screenshot in op).

So 'objective captured' should be linked to an 'objective status/in' node. From that, depending on who captured the 1st objective, you then deactivate/lock (if required) and activate the next objective + disabling/enabling the next required PlayerStartGroups.

 

[Catalavos]

Which "heading" is "Objective Status" under? I can't find it in the Kismet drop-downs.

 

[LordGleedo]

Which "heading" is "Objective Status" under? I can't find it in the Kismet drop-downs.

Not sure - copy the code below and just paste directly into your kistmet screen and it will appear

Spoiler!

Begin Object Class=ROSeqCond_ObjectiveStatus Name=ROSeqCond_ObjectiveStatus_1
InputLinks(0)=(DrawY=952,OverrideDelta=49)
OutputLinks(0)=(DrawY=918,OverrideDelta=15)
OutputLinks(1)=(DrawY=941,OverrideDelta=38)
OutputLinks(2)=(DrawY=964,OverrideDelta=61)
OutputLinks(3)=(DrawY=987,OverrideDelta=84)
VariableLinks(0)=(DrawX=-2488,OverrideDelta=26)
ObjInstanceVersion=1
ParentSequence=Sequence'Main_Sequence'
ObjPosX=-2552
ObjPosY=880
DrawWidth=128
DrawHeight=138
Name="ROSeqCond_ObjectiveStatus_1"
ObjectArchetype=ROSeqCond_ObjectiveStatus'ROGame.Default__ROSeqCond_ObjectiveStatus'
End Object

 

[Catalavos]

Thanks for the script!
Well, I got it to work. I forgot to set a unique Obj. Index for 2nd. Obj.

 

[Le0]

I was about to post this.
Usually if you notice that only one of the objective is working it's caused by a obj index, rep index issue.

Nifty sig Zero ;D

 

[Catalavos]

Thanks to you both, guys. Since figuring this out I've added 3 more objectives and they work just fine.

 

[nymets1104]

Thanks for the script!
Well, I got it to work. I forgot to set a unique Obj. Index for 2nd. Obj.

I know this thread is over 2 years old, but it just solved a huge headache for me...Thanks!