![]() |
||||
![]() |
||||
![]() |
||||
| Frequently Asked Forum Questions | ||||
| Search Older Posts on This Forum: Posts on Current Forum | Archived Posts | ||||
Anywho, I was working on the map, and guess what happened. FORGE CRASHED! Guess how long it took. Come one, just take a guess. That's right! It took a mere 20 minutes for it to crash! I signed heavily and restarted Forge and started working again. This time I started a new file save just to be sure. Withing 20 minutes, IT CRASHED AGAIN! That's when I gave up on it.
This is getting out of hand! Keep in mind that this is NOT my console, nor my controller, nor my copy of the game. It's not even being ran on the same network nor network provider. Screw New Monthly Content! How About Fixing The Dang Game, 343!!!!
Here are two new errors, from today's session
Here's a new bounding box issue. I'm trying to select the custom built platform. But instead, it keeps selecting the crane object that's just barely on screen (bottom left)
I moved the majority of my map to a better location, but not very far from it's original spot. Maybe 2 Pelican lengths away and higher from the default ground. Although every object I selected was always set to Phase, simply moving them all via World settings, caused issues. Most notably alignments between groups. But some objects decided to start floating away w/o reason. Not something that should happen with phased objects and groups. However; I failed to capture those errors. But I did capture another new one.
As I mentioned, I moved most of my map to a new location. Normally, this should not be much of a issue. When I moved it, I did not touch nor select the animated pistons. I knew they would shift if I select them and figured I'll leave them for last. Well, when I move my map, the makeshift platform (from above video) ended up above one of the animated pistons. All of the platform's objects had already been grouped together before moving it. However; after moving it to it's new location, the group decided to group a few of it's objects to the animated piston that was now below it. As you can see in the video below. But that's not even the weirdest part. Normally, if I would group something to one of these pistons, the object would stay stationary while the piston animated. But in this case, the unwanted grouping animated WITH the piston. Now watch the video carefully. When I hover over or select the custom platform group, you'll notice the piston doe not acquire a highlight at all. Thus proving that they are not really grouped.
This is incredibly frustrating. A map that would have been easily completed at the start of last week, is taking me twice as long due to new glitches and crashes!
| Forge Issues After Update (Halo 5) | SEspider | 4/25/16 11:10 pm |
| Re: Forge Issues After Update (Halo 5) | davidfuchs | 4/26/16 10:38 am |
| Re: Forge Issues After Update (Halo 5) | General Vagueness | 4/26/16 7:48 pm |
| Re: Forge Issues After Update (Halo 5) | SEspider | 4/27/16 10:02 am |
| Solid Confirmation Of Errors | SEspider | 4/30/16 2:01 am |