I’m currently using 3D Google Earth scans to create my show. I’d like to be able to shoot fireworks off the side of the building I am working with.
Usually, I’d use ‘Positions’ to accomplish this, with the ‘Set Height’ field to adjust the firework height. Unfortunately, it seems that the Google Earth 3D scans are actually below 0m.
As a result, whenever I try to move the ‘Positions’ to the correct location on the side of the building, I’m unable to move them any further down, as the height value cannot be negative.
To put your positions on building, it’s best if you disable “Set Height”. Then, Simply grab the position with the mouse, move it over your 3D model and it will snap to the correct height.
Is that a good solution?
(If you do want to set the height manually anyways: I will make a change in one of the next updates so that you can enter negative numbers into “set height” with the keyboard. )
Unfortunately, I’ve not been able to get this to work when manually dragging the fireworks. Unless I’m missing a setting somewhere, by default, it seems that the fireworks are positioning themselves above the 3D ‘terrain’. For example, if there’s an overhang on a building and I place the firework marker underneath the overhang, the fireworks will shoot from the top of the overhand.
In this instance, where I’m dragging the fireworks onto the side of the building, they are technically falling ‘inside’ the building itself. As a result, FWsim seems to move the actual firing location for the fireworks to the highest point visible to the sky (Or in the other works, the top of the building).
To provide some further information, I was actually able to fix this issue by changing the Google Maps co-ordinates such that they fell on a point lower down. In other words, it seems to me that FWsim is setting the ‘origin’ for the vertical axis based on the height of the given Google Maps co-ordinate.
In this instance, my original co-ordinates were placed at the top of the pictured building. As a result, ‘0m’ for the position line’s height correlated with the top of the building. When I changed the co-ordinates to a point on ground level, though, the ‘0m’ height snapped to the ground instead. I wonder if it might be possible to change the 3D scan’s vertical origin to always match the lowest point within the scan, or perhaps sea level, as opposed to the height of the terrain at the given co-ordinate.
Thanks once again for the response, I really appreciate the help. This issue is ‘resolved’ for now in my case, but I do feel that it’d be a nice tweak to have in the future .
I understand that you’ve seen cases where if you try to put the positions on the side of the buildings, they will not snap to the correct location. I also understand there are problems with auto-snap when there is an overhang in the roof of the building.
Could you send me the coordinates of the specific building that has these problems? I will then try it and let you know my findings.
I believe the co-ordinates were as-follows:
Position: 52.23199594239595, 21.00629524597176
Rotation: 20
Please note that this issue seems to persist across multiple locations, not just this specific building.
I’ll reiterate that moving the position to ‘ground level’ does seem to be a viable workaround currently, so I don’t think this issue requires urgent attention from yourself.
Hopefully you’ll be able to replicate the issue on your end using those details, but let me know if I should provide further information when or if you come to look at this issue closer.
.