Is this full source code to the original unreal engine?
Author
Is this the full source to unreal engine 1?
(http://unrealtournament2004.filefront.com/file/Unreal_Tournament_Source_Code;50393)
No, it's just a fraction of the code, mainly containing the audio and video interfaces plus some public headers.
You'll find a small 'engine.lib' somewhere in that archive containing the missing stuff in compiled form. I guess it might allow you to port Unreal 1 to modern hardware at best, but it won't allow you to view the actual engine code.
-Markus-
You'll find a small 'engine.lib' somewhere in that archive containing the missing stuff in compiled form. I guess it might allow you to port Unreal 1 to modern hardware at best, but it won't allow you to view the actual engine code.
-Markus-
If you are that interested in peaking under the hood check out the quake1/2/3 source it is fully gpl these days.
Quote:Original post by Inevitab13
Is there a way to decompile it? or has anyone done this?
That's probably illegal, but theoretically possible. Only thing about that is that you would most likely get assembly code from it, and it would probably take less time to learn and write your own engine than convert that to the programming language that you are using.
Your experience may not be the same as mine, but every time I've tried to study a complete, working game of that magnitude, all I've ever gotten out of it was increased confusion. :(
The older Unreal engines use some terrible OO-design practices anyway (Such as a base entity class containing dozens of variables used by only certain sub-classes), so they're not even very useful for learning.
I'm not sure about UE3, but hopefully they've learned some better practices by now.
I'm not sure about UE3, but hopefully they've learned some better practices by now.
Quote:Original post by blakedevQuote:Original post by Inevitab13
Is there a way to decompile it? or has anyone done this?
That's probably illegal, but theoretically possible. Only thing about that is that you would most likely get assembly code from it, and it would probably take less time to learn and write your own engine than convert that to the programming language that you are using.
There are MANY decompiles that outprint source code.. value names are changed so like main would be 'int main(int arg1, char **arg2)' and there are, ofcouse no comments. It also is the optimized code so it my not be as portable as the original code.. Over all not very pleasing to look at and you dont get any info out of it. And we all know source code is EVIL to learn from even with comments...
I will not post any becouse of the legality of them and the fact that I dont want to help anyone rip off a game like unreal.
Quote:Original post by guyver23
Your experience may not be the same as mine, but every time I've tried to study a complete, working game of that magnitude, all I've ever gotten out of it was increased confusion. :(
Try to focus at one certain aspect of the engine. I took Torque and peeked at the networking/ghosting/SIM part for half a week (trying to figure out a problem I had with syncing objects) and learned a lot of that. Also digging through the animation part of Torque (to take control of one specific bone from script) taught me a lot about how skeletal animation is implemented.
Aimlessly looking at an engine will indeed not help you a lot.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
