jcap, I have two reference images that show that the clouds are clear enough to see to the other side. Because it's Bungie's work showing that, I think I can safely make the clouds clear enough to at least see things without going out of canon.
Printable View
jcap, I have two reference images that show that the clouds are clear enough to see to the other side. Because it's Bungie's work showing that, I think I can safely make the clouds clear enough to at least see things without going out of canon.
Hell, the clouds shouldn't even be there in the first place - there's no atmosphere between the planetoid and the Ark - when you assault the Ark's control room, it's completely not canon - there should be a massive retaining wall holding the atmosphere in, just like there is on the other Forerunner installations, especially the one that is being constructed at the time. Also, ever stop to think that this isn't the construction of Installation 04 (II), but just rather Installation 04?
To be a canonfag, then how the hell are UNSC SPARTAN-IIs fighting on it with THAT logic? :v:
Like I was saying earlier, why do we need an explanation? Why does everything need to be perfect emulation of Bungie's designs?
Artistic liberties, motherfucker, can we use them?
All of you, shut the fuck up.
jfap, first up, this is MP. MP doesn't have to stick to canon entirely, just have some sort of grounding in it. Even so, there are points where you can see the core and right across the Ark in H3. Failing that, the average Halo player these days would be too busy crying about aimbots to give a shit, and they wouldn't have the intelligence to realise anything was a little screwy anyway.
As far as the lack of atmosphere goes, there's a difference between clouds and superheated gas clouds, duders. The shit around the core is the latter.
http://3.bp.blogspot.com/_Dm4sFu73cJ...0/walter01.jpg
Oh, the new base interior is almost done, btw.Quote:
Originally Posted by jcap
Holey crap, Jcap is trolling you guys hardcore.
whats going on
also
- Leigh → paris says:
omg
- Leigh → paris says:
conscars helping u with rev
- Leigh → paris says:
that ring and sky thing
Big Kahuna Burger says:
whoa
- Leigh → paris says:
wow.
Big Kahuna Burger says:
howd you know that
Big Kahuna Burger says:
you
Big Kahuna Burger says:
browsed
Big Kahuna Burger says:
modacity
Big Kahuna Burger says:
!!
- Leigh → paris says:
accidently clicked onto it more like it
- Leigh → paris says:
so 2 min browse no harm done
Big Kahuna Burger says:
and accidentally clicked rev
- Leigh → paris says:
yep
Big Kahuna Burger says:
and accidently went through 4 pages
- Leigh → paris says:
yep
Almost done integrating mass' wall, and the new basement is done and (hopefully!) clear of any errors.
Expect another test this weekend.
Ok, I'm having a little issue here.
I compiled a new BSP, got it ingame and lightmapped it as usual. However, the game exceptions when loading the map in the up to date scenario file, but not in a new blank one.
However, the same scenario with the older bsp loads without issue.
Any ideas?
Right now I'm fucking around with recompiling it, noting that it seems to have been a huge file before, and after recompiling the same JMS it's a whole lot smaller, so I'll see if it was just a bad bsp compile(?)
You of all people should know rule #1 of Halo map debugging:Quote:
Originally Posted by Selentic
debug.txt or gtfo