Smokin'Guns Morphos

[Cowcat]

Following the path of the warpos version, why not?

Don't know if calling it alpha or "old tv set" version: In my system, enabling full colors is problematic and leads to very bad framedrops/locks depending on where you are pointing, gets a little better without lightmaps, etc, but meh.....

However, enabling GreyScale filtering game plays perfectly & fast ( besides one stupid map ).

Network is kinda hacked and it is not fully working as other things (old q3 morphos code).

Don't forget the vm's included or you cannot load the game.

I expect some input about what is working or not

[waldiamiga]

Yeahhh. Thanks, tomorrow testing.

[tolkien]

I have done a quick test. Runs about 50 fps in my g5 machine but it drop frames sometimes.
Online mode doesnt work.
Will try better this night.
Thanks for the port.

[Cowcat]

@tolkien

it drop frames sometimes.

GreyScale filtering or full color?

Is normal that in some scenes frames drop, can be adjusted with FarClip option.
I'm concerned about going down to 5 fps with interruptions/locks with full color: Don't know if it's the code applied, the MOS SDK/tinygl driver or my machine, but warpos version works ok in it.

Net support: MOS SDK has no full support for what new ioqquake3 net code needs, so it's kinda hacked for at least compile .

[tolkien]

full color.
I'll write here the error when trying to play multiplayer mode.

[Cowcat]

I know that warpos port doesn't show any server for online playing, maybe because there's none available nowadays, but for local net playing I know the net failures for morphos port.

[tolkien]

I see servers in multiplayer mode. I try to play and the game start to load the current map and assets but suddenly the game exits to morphos with this msg:

code/client/cl_cgame.c:763: failed assertion '0'
Program aborted

[Cowcat]

@tolkien Gracias por el testeado.

code/client/cl_cgame.c:763: failed assertion '0'
Program aborted

This is new (...now I see the servers ).

Two possibilities for the error:

1 - Net code not fully working.
2 - Game needs the vm's provided for loading the maps due to an endian issue not checked on the original vm's paks. Problem is you cannot play online with vm's that are not those "from inside the pak" -> usually "sv_pure 0" is needed for that and the server also needs to be "non-pure" (99% unlikely). This was a "legacy" from Q3, don't know if stills apply for mods......

The remedy (theoretically) is to unzip "sg_pak0.pk3" and put the newer vms inside it, but no other vm's "outside" should exists (what I provide). Have to check that.

The locks/dropping frames I have is because of the few video memory on my system: minigl for warpos reads "only" 256 for textures. Forcing the code to do that, performs as the warpos version.

[Cowcat]

Other problems happen when putting the vm's inside the pak (for multiplayer), but basically is what's happening here. Warpos version simply hangs there (no assert).

More work to do.

[Cowcat]

New one with optional setting for low video memory plus fixes. A readme is included.

Unfortunatelly I cannot do too much now for the multiplayer situation: Servers got their own idea of what the clients have to load from the game (signed md5 paks, etc).

Game looks like this with a low video memory macmini G4: [ Show youtube player ]

[Hedeon]

Anyone have a video of the WOS version running?

Edit: whoops, wrong platform...

[kikems]

Awesome port, I'm downloading now, Thanks.

[Cowcat]

@kikems De nada. Saludos !

[waldiamiga]

Originally Posted by Cowcat

New one with optional setting for low video memory plus fixes. A readme is included.

Unfortunatelly I cannot do too much now for the multiplayer situation: Servers got their own idea of what the clients have to load from the game (signed md5 paks, etc).

Game looks like this with a low video memory macmini G4: [ Show youtube player ]

Very playable on my PowerBook A1139.
However, I can not set the native resolution, (1680x1050) an error requester appears in the opening screen.

[Cowcat]

@waldiamiga Technically that resolution is there seeing the source, but never tried more than 1024 nor seeing an error request. Honestly those resolutions are too much: I started to experience glitches testing wos OpenArena/SG due to the bigger textures and fewer mgs left on video just with windowmode play. That fully showed with native MOS version, so better stay with a relative normal 800x600 that is cool enough.

By the way: There are a couple of maps that go below acceptable framerate (at least in my system). Not so bad for WOS, but....

[waldiamiga]

Originally Posted by Cowcat

@waldiamiga Technically that resolution is there seeing the source, but never tried more than 1024 nor seeing an error request. Honestly those resolutions are too much: I started to experience glitches testing wos OpenArena/SG due to the bigger textures and fewer mgs left on video just with windowmode play. That fully showed with native MOS version, so better stay with a relative normal 800x600 that is cool enough.

By the way: There are a couple of maps that go below acceptable framerate (at least in my system). Not so bad for WOS, but....

But it works in 1440x900. I tried to manually change the resolution in the configuration file, but it runs in default resolution.

[Cowcat]

To make Q3 engines to use custom/force resolutions:

For example:

seta r_customwidth "whatever" seta r_customheight "whatever" r_mode "-1"

on config file. And probably also adjust the fov, but those are tips found on the net.

Aaand....a proper screen configured in the OS system preferences if you go crazy with it.

[waldiamiga]

Originally Posted by Cowcat

To make Q3 engines to use custom/force resolutions:

For example:

seta r_customwidth "whatever" seta r_customheight "whatever" r_mode "-1"

on config file. And probably also adjust the fov, but those are tips found on the net.

Aaand....a proper screen configured in the OS system preferences if you go crazy with it.

Aghhh.... In my default.cfg file seta r_mode "4". I try...