1  |   Order by index

Jun 1, 2006, 5:53am

Has anyone been able to create movers using a bot? I have managed to
create PEs and zones, and I can even create movers from a previously
performed survey (using the data exactly as received); but when I try to
create a new mover from scratch, it seems like the fields of the struct
are messed up. In other worlds, the order of the fields in the data are
not actually as they are shown in the struct as defined in aw.h.

The struct-filling functions (like aw_object_mover_set) don't seem to
work at all. To get the PE's and zones, I had to allocate and fill the
structs myself. When I do this with movers however, the mover that gets
created has the values in the wrong fields when examined in the world.
It could be my mistake, but since I managed okay with PEs and zones, I'm
thinking not.

Creating cameras using a bot is probably working also, but cameras are
kind of boring so I have really tested them extensively yet. :D

Jun 1, 2006, 3:12pm

Hi Magine,

Using the latest version of the SDK for 4.1, I haven't had any issues
creating objects with the macro functions. I did at first, but then I
realized I wasn't setting the object type properly before I called
object add.

Also for the movers, are you setting the model after you fill the
structure? Movers, unlike the other V4 objects still rely on the model
field for V3 objects to work.

[View Quote]

Jun 1, 2006, 5:05pm

Thanks, I'll try the macro functions again then.

[View Quote] > Hi Magine,
>
> Using the latest version of the SDK for 4.1, I haven't had any issues
> creating objects with the macro functions. I did at first, but then I
> realized I wasn't setting the object type properly before I called
> object add.
>
> Also for the movers, are you setting the model after you fill the
> structure? Movers, unlike the other V4 objects still rely on the
> model field for V3 objects to work.
>
[View Quote]

Jun 2, 2006, 9:31am

I tried the macro function for filling the mover, now I get an "invalid
object type" message as before.

Did you create a mover, specifically, with the macro functions? Or at
all? Please tell me if so, because if it's working for you then I must
be doing something wrong. However, I can create PEs, zones and cameras
and they all come out fine, but with movers all the properties in the
mover that is created seem scrambled up (values missing or in the wrong
fields). Yes, I set the model name, object type, etc. The model name is
one of the few things that comes out right in the created mover. The
flags come out alright too. But the values I put for locked_pos_y,
locked_pos_z and locked_pos_yaw appear in the three locked offset fields
instead; the locked_pos_pitch shows up in locked yaw, and locked pitch
has some odd value that I didn't put in (probably it's taken from some
bytes within another field or fields). The name comes out wrong (first
two letters of the name+the seq name+first two letters of the script
name) and the seq file field gets the script field string but with the
first and last letters truncated. The sound field has nothing in it.

I really have the feeling that the struct definition in aw.h is not the
same as what the AWB and server are using...


[View Quote] > Thanks, I'll try the macro functions again then.
>
[View Quote]

1  |   Order by index