Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
167 user(s) are online (112 user(s) are browsing Forums)

Members: 0
Guests: 167

more...

Headlines

 
  Register To Post  

Unrealtournament 99?
Home away from home
Home away from home


See User information

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top
Re: Unrealtournament 99?
Just popping in
Just popping in


See User information
@LiveForIt

That's only the part of the source code of UT required to make mods for the game, it does not contain the source code of the Unreal Engine, required to port the whole game on OS4, unfortunately.

Varthall

Go to top
Re: Unrealtournament 99?
Not too shy to talk
Not too shy to talk


See User information
@Varthall

Linux has an installer(using the windows cd for the game), any way os4 could do the same?


OPENUT

Go to top
Re: Unrealtournament 99?
Home away from home
Home away from home


See User information
But i i don't think this would be playable on our amigas. But would love o se UT on amiga. It's a great game.

X5000
Go to top
Re: Unrealtournament 99?
Just popping in
Just popping in


See User information
@magic

Quote:

magic wrote:
@Varthall

Linux has an installer(using the windows cd for the game), any way os4 could do the same?

OPENUT

The installer uses the Linux x86 compile of the engine, made by Loki Games, which is closed source. It seems that parts of the Unreal Engine 1 source code are still present in the latest Engine 3, that might be a reason why Epic Games wouldn't like to open source it.

Varthall

Go to top
Re: Unrealtournament 99?
Home away from home
Home away from home


See User information
@Varthall

We don?t need more guns, we need more fantasy...


So, drop the Shooter and go for adventures

People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Go to top
Re: Unrealtournament 99?
Quite a regular
Quite a regular


See User information
I will be happy if somebody do that.

Go to top
Re: Unrealtournament 99?


See User information
@tommysammy

I remember playing UT 99 on the Amigaworld tournaments. Magic and DaveyD (maybe others) made some custom levels and the contests were out of this world. I would love to get back into that if we can get the game server sorted again....

Go to top
Re: Unrealtournament 99?
Not too shy to talk
Not too shy to talk


See User information
@A1200

You sure it wasn't Quake?

Rude!

Nissan GTR '08
Go to top
Re: Unrealtournament 99?
Not too shy to talk
Not too shy to talk


See User information
@Rudei

It was unreal tournament classic version not, quake.

Go to top
Re: Unrealtournament 99?
Home away from home
Home away from home


See User information
@Varthall

Are you shore?

“Engine” is listed in the directory structure

Directory Structure

* \Unreal\UnrealPubSrc.dsw: Microsoft Visual C++ workspace file.
* \Unreal\Core: Unreal engine core components (non-game code, such as low-level object handling, script interpretter, file processing, configuration, and platform-specific support).
* \Unreal\Engine: Unreal engine game components.
* \Unreal\Setup: Unreal Windows installer/uninstaller (Setup.exe).
* \Unreal\GlideDrv: Unreal Glide support. Note: To compile this code, you need the latest version of the Glide SDK from 3dfx's web site.
* \Unreal\Help: A small amount of documentation.
* \Unreal\Launch: Unreal Windows startup code (Unreal.exe).
* \Unreal\OpenGLDrv: Unreal's OpenGL support.
* \Unreal\System: Unreal's system directory.
* \Unreal\UCC: Platform-neutral command line runner. Launches "commandlets" such as the script compiler, installation generator, and command-line server.
* \Unreal\Window: Windows encapsulation.

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top
Re: Unrealtournament 99?
Not too shy to talk
Not too shy to talk


See User information
@LiveForIt

I would be happy to donate some money towards anyone willing to get the first classic unreal tournament working on sam, if linux can have it, then why cant we?

Go to top
Re: Unrealtournament 99?
Just popping in
Just popping in


See User information
@LiveForIt

The directory listing is a bit vague, as it states that it contains the "components" of both core and the engine. If you take a look at the source, the Core and the Engine directories contain header files and two libraries, Engine.lib and Core.lib. By hex reading them, you see that they contain calls to core.dll and engine.dll which aren't included. Anyway, these are x86 compiled dlls, and without their sources you can't do much.

Still, I'd die to see an UT 99 port :)

Varthall

Go to top
Re: Unrealtournament 99?
Just popping in
Just popping in


See User information
@LiveForIt

It runs on QNX, and have so for many years now.
Maybe there are some soruces to be located there? i actually don't know.

Go to top
Re: Unrealtournament 99?
Just popping in
Just popping in


See User information
@yssing

I didn't know that, I have searched around but haven't found any more information, do you have any link?

Varthall

Go to top
Re: Unrealtournament 99?
Home away from home
Home away from home


See User information
@Varthall

The *.h (header files) are not header files contain just declarations, but they contain the source code, fully defined functions.

core.dll is included in the core/lib/ directory.

What you need to do compile this, change compiler script to compile .a files and not .dll files.

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top
Re: Unrealtournament 99?
Home away from home
Home away from home


See User information
@LiveForIt

Then you can compile it this weekend.
Excellent. Hehe

X5000
Go to top
Re: Unrealtournament 99?
Just popping in
Just popping in


See User information
@LiveForIt

Quote:

LiveForIt wrote:
@Varthall
The *.h (header files) are not header files contain just declarations, but they contain the source code, fully defined functions.

Not all the functions have the code in the headers (and btw I don't understand why would someone put all the code inside headers...). For example, all the CORE_API functions have only a definition, e.g.

Quote:

CORE_API void appInit( const TCHAR* InPackage, const TCHAR* InCmdLine, FMalloc* InMalloc, FOutputDevice* InLog, FOutputDeviceError* InError, FFeedbackContext* InWarn, FFileManager* InFileManager, FConfigCache*(*ConfigFactory)(), UBOOL RequireConfig );


is called in 3 different places, defined in Core/Inc/UnFile.h, but no actual code, and it's referenced in core.lib.

Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project