This topic is meant to serve as a:

"nasty faults/limitations & what I really wish we could have this instant" thread.

Post any of the drawbacks/snags/restrictions which have prevented you from creating your dream map or asset.

Alongside all that is bad, I would like to see what Idea's the community has for upgrades and enhancements in general directed at the HEK and it's subsidiaries.


I'll begin:

The Bad:

> BSP triangle limit is far too low these days!
> Model triangle limits are vastly the same too!
> .tif only support
> engine handled map lighting generation takes too long.
> Mp maps are capped at a certain size (200mb?) at to a degree so are Sp
> tool errors are in some circumstances far too obscure.
> 6 vehicles only
> no real support for a multi selection of playable bipeds for MP.

MyWishList

> BSP Render and Collision to be handled separately.
> Ability for structures to compile regardless of the amount of open edges and overlapping surfaces located within the model.
> Boosted usage for models/textures/scripts
> Model viewer / Shader debugger inside 3dsmax or maya.
> More than 6 vehicles and 2 types of grenades
> Ability to modify everything per users wish.
> Support for a tandem shader/particles/cinematic suite.
> Allocation for diffuse/specular/normal/gloss/emmisive maps & pbr

Please contribute to the list!

I just wish there wasn't 32 mb model data limit.

I wish there wasn't a particle limit :/
I think it's right around 1000, which eats up pretty quick with explosions and such, let alone with static emitters or weather

Crying engine

I'm pretty sure both of you are already aware, but OS helps out on both of those points. I believe model data limit is effectively doubled to 64, and particle limit is increased significantly. I'm not 100% on the exact numbers though, but the answers are probably around here somewhere.
Edited by Bungie LLC on Jun 4, 2015 at 12:19 PM

Os does not increase the model limit

I'm pretty sure it does. If you fill tutorial with tons of stuff, stock Halo will stop compiling at some point, whereas OS can still compile upwards for a good while.

This is all I can find in the latest readme:

"Increased hardcoded 'k_runtime_data_max_values_count' to a total of 64 (up from 32)"
"Upgraded the max number of particles active/rendered at once"
"Upgraded the max number of objects rendered at once"

I assume that the "data_max_values_count" increases the limit for a number of different things that were locked at 32, due to stock Halo being on a 32-bit runtime, and they are in turn increased to 64, model count included, which would coincide with my first point.

Also, this: https://www.youtube.com/watch?v=TTDaVb19_PQ

OS already does like 70 percent of what you listed...

...and they're debating on what that 70% actually includes...

Saw this, laughed, cried a bit inside. No way in hell is CE getting any form of PBR support, not on an engine this old

I like the blueprints workflow better too.

Time, its the only thing that I need, nothing else

It increases on screen limit and tagspace but last I compiled the actual model limit was not increased. Would check now but I'm not at home.

Just because you can fill up tutorial past a limit merely could be because of the tagspace increase

That could very well be the case. I'm not entirely sure myself, but I don't think I'm going to go off experimenting just to find out. I do know that most hardcoded "32" limits that were previously assigned in Halo's limitations were brought up due to the max values count increase that OS hacks into the game's runtime.

Beyond all that technical jargon that's not too user friendly, I have no clue.
Edited by Bungie LLC on Jun 4, 2015 at 11:32 PM

This is what masterz said about it when I asked him: "Yeah no way around it. It's been a thorn in our side as well. I think Kornman tried but the limit is complicated"

That's why it was in my wish list.

Btw I forgot to add in: general in game sound improvements. E.g how the engine handles specific files over others since haloce still cuts out looping tags.
Edited by SS Flanker on Jun 5, 2015 at 04:46 AM
Edited by SS Flanker on Jun 5, 2015 at 04:47 AM

Well, there you have it then. I guess we'll have to wait and see if FireyScythe can do anything about it.