[Archive] GameObject Bug
[Archive] GameObject Bug
Original source
Yo)
Bug on bug last time) Who know what the problem? I trying to place Chair gameobject and its spawning only in one orientation. Idk how to turn it. ><
rektbyfaith
10-29-2016, 08:41 PM #1Archived author: Simple_spectr • Posted: 2016-10-29T20:41:31+00:00
Original source
Yo)
Bug on bug last time) Who know what the problem? I trying to place Chair gameobject and its spawning only in one orientation. Idk how to turn it. ><
Original source
Oh, I can "turn" it with command .gob turn but it's okay?
rektbyfaith
10-29-2016, 08:47 PM #2Archived author: Simple_spectr • Posted: 2016-10-29T20:47:00+00:00
Original source
Oh, I can "turn" it with command .gob turn but it's okay?
Original source
Due to loss of internet connection I couldn't finish my answer to you, otherwise it would have been here for a few days already.
There are 2 orientation systems for gameobjects in gameobject table at the moment. You can do basically two things. Either:
Spawn a gameobject.
Turn it with .gob turn command (TC admin is great for this).
Done.
Or you can:
Spawn gamobjects.
Execute following SQL query on your world database: UPDATE `gameobject` SET `rotation0`=0, `rotation1`=0, `rotation2`=SIN(`orientation`/2), `rotation3`=COS(`orientation`/2);
Restart your server.
Done.
The 2nd method will rotate all your gameobjects to the way they should be oriented (so on-spawn orientation will be used).
The biggest issue of the 1st method is that (at least on my a little bit outdated revision of TC) gameobject turn command doesn't change old orientation value which is no longer used, only the 2nd, new orientation values. The biggest issue of the 2nd method is that, apart from need of restarting server and not-seeing results immediately, it collides with the 1st method (objects turned by gameobject turn command will get turned again to orientation spawner was in when he spawned a gamobject). A (partial) solution to this would be:
UPDATE `gameobject` SET `rotation0`=0, `rotation1`=0, `rotation2`=SIN(`orientation`/2), `rotation3`=COS(`orientation`/2) WHERE (`rotation2`=0 OR `rotation3`=0);
Now, guys, tell me. Anyone. Why the actual FUCK is TrinityCore doing this. Releasing unfinished, malfunctional things. Redoing things which were WORKING. Fixnig things which WERE NOT broken. Its overengineering and utterly stupid in my opinion, and its not for the first time TC has done something similiar.
rektbyfaith
11-01-2016, 08:41 PM #3Archived author: Amaroth • Posted: 2016-11-01T20:41:05+00:00
Original source
Due to loss of internet connection I couldn't finish my answer to you, otherwise it would have been here for a few days already.
There are 2 orientation systems for gameobjects in gameobject table at the moment. You can do basically two things. Either:
Spawn a gameobject.
Turn it with .gob turn command (TC admin is great for this).
Done.
Or you can:
Spawn gamobjects.
Execute following SQL query on your world database: UPDATE `gameobject` SET `rotation0`=0, `rotation1`=0, `rotation2`=SIN(`orientation`/2), `rotation3`=COS(`orientation`/2);
Restart your server.
Done.
The 2nd method will rotate all your gameobjects to the way they should be oriented (so on-spawn orientation will be used).
The biggest issue of the 1st method is that (at least on my a little bit outdated revision of TC) gameobject turn command doesn't change old orientation value which is no longer used, only the 2nd, new orientation values. The biggest issue of the 2nd method is that, apart from need of restarting server and not-seeing results immediately, it collides with the 1st method (objects turned by gameobject turn command will get turned again to orientation spawner was in when he spawned a gamobject). A (partial) solution to this would be:
UPDATE `gameobject` SET `rotation0`=0, `rotation1`=0, `rotation2`=SIN(`orientation`/2), `rotation3`=COS(`orientation`/2) WHERE (`rotation2`=0 OR `rotation3`=0);
Now, guys, tell me. Anyone. Why the actual FUCK is TrinityCore doing this. Releasing unfinished, malfunctional things. Redoing things which were WORKING. Fixnig things which WERE NOT broken. Its overengineering and utterly stupid in my opinion, and its not for the first time TC has done something similiar.
Original source
Quote: 12 hours ago, Amaroth said:Iirc there actually were some problems with the game object rotation, but i can't remember what it was anymore. Pretty sure there is/was a ticket in their GitHub issues about this.
Now, guys, tell me. Anyone. Why the actual FUCK is TrinityCore doing this. Releasing unfinished, malfunctional things. Redoing things which were WORKING. Fixnig things which WERE NOT broken. Its overengineering and utterly stupid in my opinion, and its not for the first time TC has done something similiar.
EDIT: Searched it, not sure if it was this problem or another, but there are tickets about wrong game object rotation. https://github.com/TrinityCore/TrinityCore/issues/4543
rektbyfaith
11-02-2016, 09:38 AM #4Archived author: Kaev • Posted: 2016-11-02T09:38:31+00:00
Original source
Quote: 12 hours ago, Amaroth said:Iirc there actually were some problems with the game object rotation, but i can't remember what it was anymore. Pretty sure there is/was a ticket in their GitHub issues about this.
Now, guys, tell me. Anyone. Why the actual FUCK is TrinityCore doing this. Releasing unfinished, malfunctional things. Redoing things which were WORKING. Fixnig things which WERE NOT broken. Its overengineering and utterly stupid in my opinion, and its not for the first time TC has done something similiar.
EDIT: Searched it, not sure if it was this problem or another, but there are tickets about wrong game object rotation. https://github.com/TrinityCore/TrinityCore/issues/4543
Original source
I took first method, its pretty simple
rektbyfaith
11-02-2016, 10:55 AM #5Archived author: Simple_spectr • Posted: 2016-11-02T10:55:32+00:00
Original source
I took first method, its pretty simple
1 Guest(s)
1 Guest(s)