At the time before RO: O 41-45 was made did TW had any plans on using the Source engine for it instead of the UE 2.5 ?
Before RO: O 41-45 was made did TW ever thought of using the Source engine ?
- Thread starter fOgGy
- Start date
I'm sorry but this thread is kind of stopid :8
Why would they buy a Source engine license when it sux for the kind of gameplay red orchestra features, and when they allready have a license for unreal 2.5 and unreal 3
Why would they buy a Source engine license when it sux for the kind of gameplay red orchestra features, and when they allready have a license for unreal 2.5 and unreal 3
Upvote
0
In their interview they said they didn't consider switching engines because their expertese was in Unreal. I can't find a link off the top of my head though.
/edit, oh and the whole winning two very expensive lisences thing.
/edit, oh and the whole winning two very expensive lisences thing.
Upvote
0
I really don't get why people are that fixated on "engines" unless they want to talk some "cool" geek talk.
Upvote
0
I understood him...
The source enigine would have been a disastrous choice and the dev team knew that!
That and they would have had to learn how to use the engine from scratch (look at DODS)
And yes I agree this thread is retarded
The source enigine would have been a disastrous choice and the dev team knew that!
That and they would have had to learn how to use the engine from scratch (look at DODS
)And yes I agree this thread is retarded
Upvote
0
I use to think long ago that the Source engine was better and well suited for a game like RO in my HL2: Deathmatch days.
Upvote
0
Kind of defeats the purpose of spending all that time, money, and effort on winning the Make Something Unreal Contest to just chuck two game engines worth hundreds of thousands of dollars into the closet and start everything from scratch...
It's actually a very beneficial arrangement for both TW and Valve. Tripwire gets access to an established and easy-to-use distribution system with an installed userbase millions-strong. Valve gets to demonstrate its delivery system is not just for Source games, enabling it to draw other developers as well as experiment and improve its technology. The new patch is an example of this improvement, where lessons learned from the initial RO:O install problems enabled them to develop a new file structure that boosted performance.
It's actually a very beneficial arrangement for both TW and Valve. Tripwire gets access to an established and easy-to-use distribution system with an installed userbase millions-strong. Valve gets to demonstrate its delivery system is not just for Source games, enabling it to draw other developers as well as experiment and improve its technology. The new patch is an example of this improvement, where lessons learned from the initial RO:O install problems enabled them to develop a new file structure that boosted performance.
Upvote
0
I definitely agree that it makes more sense for a development team that knows Unreal to stick with it instead of starting all over again learning a new game engine. However, I'm not aware of Unreal 2.5 being an intrinsically better game engine than Source for the type of game play featured in RO. It seems like Source is a quite versatile and powerful game engine that is continuing to be updated and supported. Valve also seems like a pretty good company to license from assuming you don't already have a free license to work with.
Upvote
0
Aside from the fact that the ROO team has many of the best UE developers in the world, using Source for a multiplayer game is suicidal unless you have millions to spend recoding certain parts of the engine.
Upvote
0
Midshipman said:
dude, we would like have... 1 fps playing in the source engine, it's incapable of rendering wide open areas!!!!!!!!!11111
Upvote
0
Source has certain deficiencies that would not lend themselves well to RO, such as the inability to handle large out door environments and extremely poor hit detection (imagine RO with hitboxes like DODS or CSS *vomits*).
Upvote
0
Midshipman said:
Its not sarcasm, Source does not like large open areas, its possible, but you have to jump through a ton of fiery hoops to make it work, developing levels like that for Source is very hard! and i have never seen a Source map that even got clouse to the scale of Arad, and you can forget all about it ever doing something on the scale of Orel, and in the end, Unreal does outdoor with higher detail than Source can (but Source can do indoors better).
Its much easier with Unreal, its build for this sort of thing, and it even has much better net-code, hell, you can build larger maps than Orel with it, it can build extremely huge! allmost OFP huge!
In the end, Source is actually not a very good engine for multiplayer games, with its hit-box detection and poor net-code, its pretty.. horrible really, its real force is with singleplayer games, which to its credit, it does very well indeed.
Upvote
0
indeed, it will be interesting to see how insurgency and resistance and liberation will fare
Upvote
0
Midshipman said:
it feels like you are in a wide open area when you are outside, but you're not, you are in a very small room with the actual sorroundings very close to you :O (but your view is limited so you can't actually see out to the void)
Upvote
0
Besides, although it doesnt have the high end effects like bump mapping, I still prefer the look of UE2.5. I think its the fact that source is very texture-based. Source is incredible for what it does though and itll be great to play all the mods.
Really we're getting the best of the pc gaming community all for RO. TW's awesome development skill, the unparalled greatness of the Unreal engines, and Valve's power and support.
Really we're getting the best of the pc gaming community all for RO. TW's awesome development skill, the unparalled greatness of the Unreal engines, and Valve's power and support.
Upvote
0
Amen and agreed.
Also, as it has been mentioned few times but source is not good rending outdoor areas and that since it was originally SP-only- engine, it was "ported" to work with MP with some side-effects, more or less annoying.
Upvote
0
Source is a nice looking engine and if you look at DoD: S maps, the details and feel of them is incredible (when you have glowing walls turned off that is - Read: Bloom), but apart from the obvious problem of small areas, the netcode is atrocious. There are a few mods that I was really looking forward to on the Source engine, but I'm incredibly apprehensive about them now, as no matter how well made they are, the inherent engine problems are going to cause real headaches.
Besides which, I don't like the feel of the Source engine. The movement and whatnot just feels all wrong. The Unreal engine just feels so much more responsive and sharp.
Besides which, I don't like the feel of the Source engine. The movement and whatnot just feels all wrong. The Unreal engine just feels so much more responsive and sharp.
Upvote
0
This isn't a stupid question.
Remember that there are some people who never played the mod, and don't know anything about the Make Something Unreal Contest.
So to them, it's a valid question, why one engine over another.
Remember that there are some people who never played the mod, and don't know anything about the Make Something Unreal Contest.
So to them, it's a valid question, why one engine over another.
Upvote
0