Author
Topic: Animals scriptable ? (Read 2275 times)

Hey DeanosBeano - is there a particular reason you chose "USMC_LHD_Crew_Blue" class to slot the animal into? I notice using the soldier base class makes the dog sink into the ground, so I was wondering what was going on there.

While we're at it, when using a dog in this fashion the rpt file fills up with error messages like"Bad action name HMMWV_Cargo01 - not found in DogActions"every time the dog gets close to a vehicle. Is there a way to lose all these errors? By rediefining something in the config?

Also, how can I ensure that the dog is a non-groupable entity, even though it is on side West? I can possibly ungroup any grouped dog in script, but I was wondering if it's also a config entry.

Well the reaason i picked that class was 1. he had a camo hidden texture so i could change his outfit with setobject texture2. he didnt have any weapons sol ess problems with anim errors/

I noticed that the rpt gave erros if the unit was ordered into a vehicle , i dint know the unit would try to get in a vehicle itself or the mere proximity would provoke ther errors. I guess the easiest way to obtain what you need is seek the playable dog inherit from that and i think i am correct in saying that these are not groupable , if they are then i guess you wil need a small script as you say checking and then making it join grpnull maybe.

In essence this was all a quick ecperiment and i have not put more than 20 mins into it , i think alot more is achievable with time especially with fsms and this idle and straight distance etc command seems to be what makes the dog pause after 40meters and start another Fsm . anyway i f i get a chance i will try to look into it deeper. good luck .

I do have a version that uses as it's base the playable dog, which as you say is not groupable and also does not report thousands of errors every time it gets near a vehicle. However, I cannot get that dog to move via any command at all, only doMove and doStop seem to work on the LHD dog, but even this does not work on the playable dog. It's very annoying, as in all other ways the playable dog is much preferable.

With the LHD dog I can call it to me, have it return to the handler, and have it "stay". But, it fills up the RPT with thousands of errors each time it gets near a vehicle (and, I presume, anything else for which there is no action for). The Playable dog gives no errors, but will run off toward it's initial editor placed position every time it's unused, and cannot be called or told to stay.

As part of the addon is that the dog can travel in the back of a car (HMMWV only) this becomes a problem. Also added to that the likely scenarios involving tracking people through urban areas, abandoned cars etc and the errors become prohibitive.

I get the depressing feeling it's all best solved with a sufficiently massaged config, but I am notoriously poor at dealing with configs

hmm, i recall when i left the dog cfg , there was a problem with gestures and some sprint . i dont recall the dog having problems though with being near empty cars unless it was ordered inside one.

this was the last config i used , further development would be to find some acceptable definitons for the gestures , tailwag etc and maybe you could replace cfgdogmocves with your wone, this is just the sinple fsms that the dog use , mayeb you can again redefine the actions that it wil lrequire and give it simple actions. the best way to do this of course is to spot the errors in the rpt match them in the dog or human cfgmoves , apply them to your new cfgmoves and allshould be good. anyway if this is ot the same try it and see if it reduces ther errors , it is groupable unfortunately but it keeps a tight formation.

Thanks for the info DB, that looks like the template from which I made one of my dogs.

About the cfgmoves stuff, where would I find all this? I cannot find them defined in Animals(2) or Characters(2) etc. Also I don't know where the DogActions are defined, which makes up all the dog errors in the RPT.

I don't mean to suck up your time like this, I can usually get what I want in code myself, but as far as configs go, I don't really have much of a clue I'm afraid. This tracker dog thing is working REALLY well, and just about the only thing stopping us releasing it is the errors in the RPT vs controllability of the dog.

Where can I find worldeater's tool? It sounds like his tool can fill the void in terms of what I need, too. No matter how deep I get into this, it seems like I still have difficulty figuring out where to put the bits of stuff.

Bad action name HMMWV_Driver - not found in DogActionsBad action name HMMWV_Cargo01 - not found in DogActionsBad action name HMMWV_Cargo01 - not found in DogActionsBad action name HMMWV_Cargo01 - not found in DogActionsBad action name UAZ_Cargo01 - not found in DogActions

(Repeated hundreds of times.)

It appears as though a cfg entry in the addon dog that defined, perhaps as a new class or added to class DogActions: NoActions, either null values - so that it does nothing - or the sitting action - so it just sits there - for HMMWV_Driver, etc. - might work.

Edited. That is still a terrible one-sentence paragraph, but I hope it is still understandable...

hmm, Again i dont undertsand why you are getting them errors , unlees your suing some kinda movein commands, i have put a dog with the above congfig i posted earlier near 20 empty vehicle types and i dont get those errors. could you describe the scenario that creates those errors ?

I will give it my best attempt. I don't think I have a copy of the config - DM's got it.

The dog and handler are not grouped together. There are scripted commands for the handler to do certain things with the dog.

The "errors" - or "alerts" - happen when the player is the dog and moves near a vehicle (at this point, Humvees and sedans). It seems like the sim looks at each vehicle, figures out that the dog can't get in, then sends that alert to the rpt. The result is simply that the dog can't get in, which we already know.

I am not sure if it happens when the player is the handler - I haven't followed the changes to the rpt close enough.

hmm, Again i dont undertsand why you are getting them errors , unlees your suing some kinda movein commands, i have put a dog with the above congfig i posted earlier near 20 empty vehicle types and i dont get those errors. could you describe the scenario that creates those errors ?

Hey DB, would there be any value in me sending you the addon as it currently is? It's a JTD_TrackerDog.pbo and a mission with all the addon files in it, ready to be moved into the pbo itself.

Basically when the player "moves" into the dog role, he runs around the vehicle, generating errors. The errors do not occur when the dog is "attachTo"d the handler.

Hey DB, would there be any value in me sending you the addon as it currently is? It's a JTD_TrackerDog.pbo and a mission with all the addon files in it, ready to be moved into the pbo itself.

Basically when the player "moves" into the dog role, he runs around the vehicle, generating errors. The errors do not occur when the dog is "attachTo"d the handler.

sure mate send me a link in PM, i will be online about 6-7 pm GMT tomorrow i will take a look no problem, hopefully i can try to eliminate some of those errors for ya and you can get that Dog out there