Home   Help Search Login Register  

Author Topic: Gamelogic coordinates  (Read 1393 times)

0 Members and 1 Guest are viewing this topic.

Offline savedbygrace

  • Intel Depot
  • Administrator
  • *****
  • Be swift to hear...slow to speak...slow to wrath.
Gamelogic coordinates
« on: 22 Jul 2009, 05:19:13 »
After doing some tinkering with these things for a while now, I have noticed that trying to setposition objects at preplaced gamelogics does not work as I initially thought.
Scenario:
I place a gamelogic in the editor in front of my player unit and then another unit somewhere far off grouped to me. I then use a radio trigger to setpos the far off unit to the gamelogic and the unit never appears. I then have the unit report it's status and I see it highlighted thousands of meter away from me and thousands of meters high in the air. Has anyone else ever experienced this? I tend to use invisible helipads now rather than gamelogics but I was curious if anyone knew the theory behind this?

Offline Worldeater

  • Former Staff
  • ****
  • Suum cuique
Re: Gamelogic coordinates
« Reply #1 on: 22 Jul 2009, 05:39:50 »
I can't reproduce this behaviour. Neither in A1 (1.16b) nor in A2 (1.02). It works with both units and objects. The activation fields of the triggers I used look like this:

Code: [Select]
dude setPos getPos logic;
try { return true; } finally { return false; }

Offline Planck

  • Honoured
  • Former Staff
  • ****
  • I'm never wrong ....I'm just not always right !
Re: Gamelogic coordinates
« Reply #2 on: 22 Jul 2009, 11:55:33 »
I can't reproduce this either, works ok for me.


Planck
I know a little about a lot, and a lot about a little.

Offline savedbygrace

  • Intel Depot
  • Administrator
  • *****
  • Be swift to hear...slow to speak...slow to wrath.
Re: Gamelogic coordinates
« Reply #3 on: 22 Jul 2009, 12:18:08 »
I have also tried copying the coordinates of known objects from the SQM at times to use for camera placement but end up with similar results. I'll try again and see if I can reproduce. Thanks for the feedback.