I searched high and low and couldn't find any substantial discussion about the object displacement that I find in all your greatest maps. As a perfectionist, I can't tolerate my maps being plagued by this bug The bug I'm referring to occurs mostly when rotating an object along the z-axis. Once the map is saved and reloaded, those objects move slightly out of place. This can be identified by clicking on the object while you have Rotation Snap on. You may also notice coordinates switching around in the Edit Coordinates menu. My latest map has run into this problem and I can't find a workaround My specific example includes two Colosseum Walls being rotated 90 degrees along the z-axis to create a floor, some columns at 45 degree angles, and an upside-down rock. None of them stay put Before: Spoiler After: Spoiler Is there any known solution to this epidemic? If not, let's figure this out
I can relate. I think it's caused by different load times whenever you start a game. I also noticed that this is more common and easier to notice while playing online. But I'm not sure what to do about it.
I've noticed when I place an object after a 90 degree rotation snap then go into edit coordinates box in forge tools the object often rotates as if it is trying to realign a twisted axis. I often mess with the axis rotations (other than roll) till I get it back to where I want before I leave edit cordinates. The nudge feature in forge is wiered since it uses sort of digital measurements for degrees. When you look at the forge axis you sort of have to look at it as one of those globes with 3 rings around it to rotate. You could get a roll axis while only adjusting the pitch and the yaw. Thats what I think forge is trying to do when they flip the objects is reset say a 90 degree roll and 90 degree yay into a 90 degree pitch and a 90 degree yaw (well that measurement is not exactly a match but you know what I am trying to say) Well instead of trying to explain what I think causes this bug. After you place an object but before you move on open the tools and hit edit cordinates. If it dosn't move (with the exception of the nudge ht' wt' dep') then it is good. If it dose go crazy adjust the rolls on all 3 axis till it is where you want it to be.
That's a good theory, but I think the displaced objects retain their new position in subsequent reloads of the map. I think their position is altered when you save the map You're describing a different problem, but they may be related Come on people, odds are that you're favorite map has this problem too
This is a problem with the game saving the rotation. If you only use roll, this may be less pronounced according to Bungie. Basically the objects can show up in game a tiny fraction of a degree off, however with coliseum walls this is a significant amount because they are so large. There are no ways around this so the best practice is to use 5v5 blocks for your floor.
Perhaps a link to Stevo's fix? This IS a problem with colosseum walls, so much so that I think many people use platforms, 5x5's, or Brace large to build floors.
http://www.forgehub.com/forum/halo-reach-forge-discussion/115618-guide-wall-collesium-flooring.html It's probably easier to use the 5x5 pieces than to follow stevo's instructions (assuming they work).
OP, the others have basically stated it perfectly. It's the result of Bungie over-compressing the files' rotations when the map is saved. I'm pretty sure it's actually the exact same problem as the one that broke a lot of Wall-based floors in Halo 3 Sandbox maps. His instructions would certainly be worth the trouble if they were clearer. For example, if all the horizontal Coliseum Walls have the same rotation but different coordinates (maybe Reach is being retarded and throwing a -90 or two in there), then what do I do? He also hasn't clarified whether or not the fix would persist after subsequent edits.
its caused by shortening of save code when a forge game saves. when an object is at a certain angle (colisseum walls are one of the major culprits because of their size), the game shortens its orientation codeing, causing its displacement *Mrgreenwithagun's tutorial blog helps alot, this is how i know this* **Not my findings, see above**