 |
I don't think that I can solve that one, actually I don't have a clue of how to approach this. Either I'll have some sort of enlightenment or I will have to skip that one. |
 |
This issue came up here: http://modetwo.net/darkmod/index.php?s=&showtopic=6599&view=findpost&p=127186 for the sake of prefabs. As such, I'll give it a little priority bump. |
|
|
I just had a (simplistic) thought on this. Wouldn't it be simple enough to: -get the origins of all of the selected objects -calculate a new, temporary unified origin based on all of the selected origins (an average center) -rotate the whole group around that When the selection is cleared, the temporary rotation origin is discarded. |
|
|
This is basically what happens in the SelectionSystem. The problem is that this virtual origin (it is called the pivot point in DarkRadiant) is not always at the center, and not all entities respond to transformations in the same way. Maybe it's easy to fix that, maybe not, but debugging that will be tough. |
|
|
I've found another clue: This seems to be to related to the "rotation" spawnarg on model entities. For models with empty "rotation" spawnarg, the coupled rotation operation works fine for the first time. As soon as the "rotation" key is set, the rotation of multi-selections is going wrong. This can be easily observed on models that are rotated 90° around the Z axis. Just select such a model together with a brush and rotate these two objects. The model rotates about a different axis (!). |
|
|
Bizarre, I was just noticing that (your last sentence) myself a couple of weeks ago, and I wasn't sure if it's always been that way or not. I had a painting on a wall which was apparently rotated several times at some point, and I was just trying to use it on a separate wall, so a quick Z-rotation would do. Well it didn't - it rotated in ways which were NOT my choosing. In the end I figured, "Oh I get it - it's rotating around LOCAL, not WORLD coordinates." I don't know if I was right or not, but I didn't feel like bending my brain around it. :) Has it always been this way? In testing software, I've often found that when something jumps out at me like this all of a sudden, it's because some change happened somewhere. |
|
|
Yes, that's always been that way. GtkRadiant/DarkRadiant never handled the rotation matrix of models very well. |
 |
I confirm models rotate OK unless they are already have a rotation. Entity brushes (and presumably patches) rotate OK but the origins remain where they were. If our code calls a rotation on each entity one by one then a crude fix might be: Create a temporary model. Copy the origin of the brush entity to it. Rotate the model as required. Rotate the brush entity as required. Copy the model entity origin back to the brush entity. Delete the temporary model. |
|
|
Mostly solved as of a8ce5928ff81f1a7bbe40ff96d92382c58a4f33b |
- Anonymous
