I was just thinking that engine that ‘Halo 4’ is supposed to be the same as ‘Reach’, heavily modified, was thinking would it be possible for people who bought the reach dlc to be compatible with halo 4?
Just was thinking of the idea because as a game designer myself I tend to use stuff like Udk, well certain versions of custom maps work on the same engine while later versions can work but it all depends on how the map was made. From my personal experience I tend to make 3d models in 3ds Max, then import them while some engines try to focus more with using quick fix tricks like bsp in Arkham Aslyum.
Sorry if this gets a bit technical, yes I know not everyone likes the dlc maps in Reach but if they could be used then it would be more maps to choose from besides the maps that they would release after the game is shipped.
Plus remember people this wouldn’t work for something like halo 1/2/3 since there completly different engines or at least earlier versions of them plus reach was rebuilt from the ground by ‘Bungie’ before they departed from Halo.
By that logic, we should be able to use Halo 3 DLC in Reach since Reach’s engine is a heavily modified Halo 3 engine. And Halo 2’s DLC in Halo 3 since the H3 engine is a heavily modified H2 engine, etc.
> By that logic, we should be able to use Halo 3 DLC in Reach since Reach’s engine is a heavily modified Halo 3 engine. And Halo 2’s DLC in Halo 3 since the H3 engine is a heavily modified H2 engine, etc.
>
> Just not possible.
You might want to reread what I said since I had to retype some stuff plus Reach was rebuilt from the ground, Halo 4 is the heavily modified version of the reach engine. Halo 2 sdk is similar to halo 3 but halo 3 sdk was never released.
By your logic it be like comparing udk to unity.
Even the doom engine is very different, try using doom builder then try using the doom sdk then you’ll notice a big difference.
Well the models in Reach or usually made in something like zbrush which are ‘object’ files which can be imported to about anything.
Plus the file name of the maps probably are the same in halo reach which is why I was curious if Halo 4 is using the same type since there supposed to be the same engine.
> > By that logic, we should be able to use Halo 3 DLC in Reach since Reach’s engine is a heavily modified Halo 3 engine. And Halo 2’s DLC in Halo 3 since the H3 engine is a heavily modified H2 engine, etc.
> >
> > Just not possible.
>
> You might want to reread what I said since I had to retype some stuff plus Reach was rebuilt from the ground, Halo 4 is the heavily modified version of the reach engine. Halo 2 sdk is similar to halo 3 but halo 3 sdk was never released.
>
> By your logic it be like comparing udk to unity.
>
> Even the doom engine is very different, try using doom builder then try using the doom sdk then you’ll notice a big difference.
I saw your edit but you’re still incorrect. They even talked about it in one of the ViDocs. Each Halo engine is a “heavily modified” version of the previous one.
> By that logic, we should be able to use Halo 3 DLC in Reach since Reach’s engine is a heavily modified Halo 3 engine. And Halo 2’s DLC in Halo 3 since the H3 engine is a heavily modified H2 engine, etc.
>
> Just not possible.
and by using moar logic, one can assume that you can play halo 2 maps in H4
> > > By that logic, we should be able to use Halo 3 DLC in Reach since Reach’s engine is a heavily modified Halo 3 engine. And Halo 2’s DLC in Halo 3 since the H3 engine is a heavily modified H2 engine, etc.
> > >
> > > Just not possible.
> >
> > You might want to reread what I said since I had to retype some stuff plus Reach was rebuilt from the ground, Halo 4 is the heavily modified version of the reach engine. Halo 2 sdk is similar to halo 3 but halo 3 sdk was never released.
> >
> > By your logic it be like comparing udk to unity.
> >
> > Even the doom engine is very different, try using doom builder then try using the doom sdk then you’ll notice a big difference.
>
> I saw your edit but you’re still incorrect. They even talked about it in one of the ViDocs. Each Halo engine is a “heavily modified” version of the previous one.
Which ViDoc video? Just curious since watched a few for halo 4, haven’t seen many from ‘Halo council’ but anyway yes that sort of makes sense.
I honestly don’t remember, it might have been one of Bungie’s ViDocs even. But I am 99.99999% sure that each engine is heavily modified from the last. Reach’s wasn’t anything different.
What snickerdoodle is saying sounds familiar, each Halo engine is built off the last but so modified it essentially becomes different. Pretty much like every other developer does with its engine.
> > By that logic, we should be able to use Halo 3 DLC in Reach since Reach’s engine is a heavily modified Halo 3 engine. And Halo 2’s DLC in Halo 3 since the H3 engine is a heavily modified H2 engine, etc.
> >
> > Just not possible.
>
> You might want to reread what I said since I had to retype some stuff plus Reach was rebuilt from the ground, Halo 4 is the heavily modified version of the reach engine. Halo 2 sdk is similar to halo 3 but halo 3 sdk was never released.
>
> By your logic it be like comparing udk to unity.
>
> Even the doom engine is very different, try using doom builder then try using the doom sdk then you’ll notice a big difference.
To be honest, what you suggest would be nice, but can’t happen, why?
Lets look at the three Halo CE games on the PC. Halo PC demo Halo PC Halo Custom Edition
Now, it’s all the same game/engine, and yet, you can’t take Halo PC Demo’s Blood Gulch map file, and use it to replace the Halo PC or Halo Custom Edition version, and I can’t take the whole campaign from Halo PC, any of the other MP maps from Custom Edition or Halo PC and put them into Halo PC Demo.
Each and every Halo game is a different version of each, Halo 4 is a modified version of Halo reach’s, which is Halo 3’s, which is Halo 2’s, and which is Halo CE’s.
But the coding that makes each and every map work with the engine, is very different. Halo’s Engine stores it’s data in it’s map files. Every single file and setting that makes up bipeds, AIs, Weapons, Vehicles, and so on, is stored in the map files.
> What snickerdoodle is saying sounds familiar, each Halo engine is built off the last but so modified it essentially becomes different. Pretty much like every other developer does with its engine.
True but it’s hard to tell what type of system their sdk is using since some just use ‘open source’ while some use more common sdk’s like crysis/udk/unity plus halo 4 has only just got dynamic lighting system which isn’t a new feature to games but it still looks pretty good in game.
Maybe some day 343i might release a sdk someday since loved to try and see what that engine can really do at it’s max. It can really be hard to tell with all those darn boundary restrictions.
> Now, it’s all the same game/engine, and yet, you can’t take Halo PC Demo’s Blood Gulch map file, and use it to replace the Halo PC or Halo Custom Edition version, and I can’t take the whole campaign from Halo PC, any of the other MP maps from Custom Edition or Halo PC and put them into Halo PC Demo.
This is why I was talking about the file types. It be like trying to get a doom builder ‘wad’ file type to work with the doom 3 which it wouldn’t but the original ‘wad’ file can actually be used to make ports like the left 4 dead mod where someone here made a mod using the textures.
My point is that there’s 2 ways to port any map, that’s either being lucky and having the same map name like in Udk or importing/exporting files. Trust me I know since I have a degree in games design, have experience with sorting out different files to work on different engines even if the graphics look slightly different.
I wouldn’t be against one of the planned 9 dlc maps to be a new forge map, like sandbox from halo 3 (I know Halo 4 has 3 different empty forge maps but more isn’t a bad thing). It just gives forgers more platforms to work on, which in turns gives us players more variety later on.
I loved what they did with the Anniversary map pack and would welcome an Halo 4 dlc map pack if they ever released an anniversary Halo 2. But I’d want it to last longer, because 343i killed off fantastic maps like Headlong when they axed BTB from their playlist (under 12 months sadly)
> > Now, it’s all the same game/engine, and yet, you can’t take Halo PC Demo’s Blood Gulch map file, and use it to replace the Halo PC or Halo Custom Edition version, and I can’t take the whole campaign from Halo PC, any of the other MP maps from Custom Edition or Halo PC and put them into Halo PC Demo.
>
> This is why I was talking about the file types. It be like trying to get a doom builder ‘wad’ file type to work with the doom 3 which it wouldn’t but the original ‘wad’ file can actually be used to make ports like the left 4 dead mod where someone here made a mod using the textures.
>
> My point is that there’s 2 ways to port any map, that’s either being lucky and having the same map name like in Udk or importing/exporting files. Trust me I know since I have a degree in games design, have experience with sorting out different files to work on different engines even if the graphics look slightly different.
And did you not read the rest of my post? You may have a degree in games design, but do you truly understand Halo’s Engine, and how it stores data?
> [You may have a degree in games design, but do you truly understand Halo’s Engine, and how it stores data?
I already stated that every engine is different, unless they release the sdk I won’t have a clue till then.
> I loved what they did with the Anniversary map pack and would welcome an Halo 4 dlc map pack if they ever released an anniversary Halo 2. But I’d want it to last longer, because 343i killed off fantastic maps like Headlong when they axed BTB from their playlist (under 12 months sadly)
Yes I know how you feel about that since Headlong is one of my favorite maps, was a major disappointment when they removed the dlc playlists since now it feels like they have completly removed it since never see it online anymore.
