Stuff to make a HD tremulous

[jm82792]

Not true,
It would most likely be trivial for someone experienced with GL to patch in hardware mipmapping (assuming such a patch doesn't already exist). Mipmapping isn't really something to change engine for, and it certainly does not inhibit or 'bottle neck' textures in any way.

Well currently it is a bottle neck.
But as I said I do not code. the only coding I do is with MCU's for fun, and it's on the simple side
Heck if it can be fixed great, I'm the bob/joe-schmo/clown that has used Blender for a couple years and knows that realm. A portion of my knowledge is applicable to games, however game engines are very different in many ways related to a 3d package.

Regarding Xreal, I agree don't worry about creating assets for it.
Get it ported(Yeah I don't know anything regarding getting it their.) and the capacity of the new engine should/hopefully drive the demand to create new assets for trem.

[Thorn]

How many times do I have to say this? A port to XreaL would not require new assets. It would look no different, but it would use code that is designed to run as much graphics on the GPU as possible, speeding up the game vastly. The enhanced material effects and special model formats can be utilized later.

Because compiling XReaL with the q3acompat flag enabled does not allow it to run on pre-GLSL (6200) hardware. Hence the argument of 'Switch to XReaL - Faster FPS - New Hardware Only!" doesn't make much sense.

[jm82792]

How many times do I have to say this? A port to XreaL would not require new assets. It would look no different, but it would use code that is designed to run as much graphics on the GPU as possible, speeding up the game vastly. The enhanced material effects and special model formats can be utilized later.

Because compiling XReaL with the q3acompat flag enabled does not allow it to run on pre-GLSL (6200) hardware. Hence the argument of 'Switch to XReaL - Faster FPS - New Hardware Only!" doesn't make much sense.

Well some of what yon stated(q3acompat flag) I do not fully understand although I do know what GLSL is and it's sweet, I've toyed with it within blender's BGE.
A $50 GPU should upgrade old PCs correct?
I think people with old pcs should be happy with the old engine,
people with the newer PCs can enjoy the new engine.
It's not like you need a $1000 PC to have GLSL enable GPU.

[Tremulant]

So you expect devs to maintain netcode compatibility so that users of either version can play together or just to split the game's playerbase in half?

[CATAHA]

You really think that half of current tremulous players have so old PCs?

[Pazuzu]

You really think that half of current tremulous players have so old PCs?

I think a poll might be in order.

[Demolution]

You really think that half of current tremulous players have so old PCs?

I think a poll might be in order.

I think there was already such a poll, no?

[Asvarox]

I doubt that even 1/4 of players would actually vote in such poll

[Odin]

How many times do I have to say this? A port to XreaL would not require new assets. It would look no different, but it would use code that is designed to run as much graphics on the GPU as possible, speeding up the game vastly. The enhanced material effects and special model formats can be utilized later.

Because compiling XReaL with the q3acompat flag enabled does not allow it to run on pre-GLSL (6200) hardware. Hence the argument of 'Switch to XReaL - Faster FPS - New Hardware Only!" doesn't make much sense.

In this day and age, there's really no reason to hold on to hardware pre Geforce 6xxx series. I really think it would be better for everyone if we dropped this mentality of 'doesn't run on old hardware so it is automatically shunned'.

In my opinion, Trem looks fine the way it is. The engine is what needs an upgrade. It doesn't even have to be XreaL. It could just be a random VBO patch(with capability detection so everyone is happy).

[jm82792]

From what I hear 1.1 was ported to xreal...
We should get 1.2 to xreal if it's not hard and if the client/server side of things doesn't need to be messed with.

[CreatureofHell]

If 1.1 was successfully ported don't you think everyone would play that instead?

[jm82792]

Well if it looked identical then it wouldn't
I don't know I'll check the website, I think it has to be compiled.

[jm82792]

http://xreal-project.net/?page_id=3/Programming/how-to-apply-xreal-engine-to-tremulous/
I'll compile it if I can ...

[Odin]

Well if it looked identical then it wouldn't

Turn off HDR or other post-processing and it will.

[Lecavalier]

That Goon is too bumpy 

[Tremulant]

Doesn't lighting need to be redone for every existing map?

[Thorn]

Yep, and it'll never look 'identical'

[Tamaru]

1.1 is ported, and they just added bloom and some other effects for the moment, nothing over the top, thorn made bump maps for the only map ported (tremor) and it has a lot of issues compile-wise.... goodluck

[Odin]

1.1 is ported, and they just added bloom and some other effects for the moment, nothing over the top

What? It has all the features of XreaL, including but not limited to bloom.

Doesn't lighting need to be redone for every existing map?

Not necessarily, if you are thinking that all maps need to be recompiled. I believe the 1.1.0 port can be compiled with compatq3 mode.

[CATAHA]

Doesn't lighting need to be redone for every existing map?

Map recompilation its not so hard work. Even without map source (using .bsp decompilation) you can redone map per day ezily.

[Tremulant]

Doesn't lighting need to be redone for every existing map?

Not necessarily, if you are thinking that all maps need to be recompiled. I believe the 1.1.0 port can be compiled with compatq3 mode.

I'm only basing this assumption on what thorn's told me in the past.

[jm82792]

Let me put it this way.
I am willing to help however I can but cannot spend hours and hours learning how to recompile maps
I can't keep dumping time into learning things, I've got enough rods in the fire and life is catching up with me.
If anybody wants they should organize a porting team of people who have a basic idea of how to get it over.
I do know a good/decent amount regarding shaders, lighting, animation, texturing, particle systems(little, not much) etc... (Most of the junk you see in Blender, I've been monkeying with most 3D skills for a long time)

Anyways I see this as the golden opportunity to beef up trem.
If we get 1.1 updated then we've accomplished something, fi we get 1.2 that's even better.
Remember we can do lots more than some bloom.
Bump mapping, postpro glare,bloom,whatever(Correct? If so we have a lots of capacity with postpro), better lighting, higher quality textures, higher polycount(correct?) much more than the few easy things that most people compulsively utilize to attempt to show they aren't a newbie  

It's like Blender newbies showing off fluid simulations 

[Pazuzu]

Wait, slow down a second. Recompiling maps, if they don't require any manual work, sounds like it should be something you can do with scripts. That makes it a lot easier.

[CreatureofHell]

Wait, slow down a second. Recompiling maps, if they don't require any manual work, sounds like it should be something you can do with scripts. That makes it a lot easier.

Fixing lighting isn't that easy though.

[Thorn]

Doesn't lighting need to be redone for every existing map?
Not necessarily, if you are thinking that all maps need to be recompiled. I believe the 1.1.0 port can be compiled with compatq3 mode.

I'm only basing this assumption on what thorn's told me in the past.

Yes, tremulous should be compatible if you compile XreaL with q3acompat, but this does mean not getting any of the features from XReaL's renderer, and at the end of the day it seems a bit pointless. I did mention this before to you, and why it was a bit pointless since the only benefit would be the framerate, and even that can be nullified by the fact that it requires hardware well capable of running the game anyway.

That would probably just be a small project then, compiling the XReaL client in q3acompat with tremulous support, which could likely be distributed as just another optional binary client. Of course, that's purely assumption.

[jm82792]

It's pointless if you can't get the features.
I do not code and in the end if we get bump mapping, postpro, MD5's, higher polycount then it's totally worth it.
Basically it sounds good(if we get the features ) but I do not know how to get there.

[Odin]

Doesn't lighting need to be redone for every existing map?
Not necessarily, if you are thinking that all maps need to be recompiled. I believe the 1.1.0 port can be compiled with compatq3 mode.

I'm only basing this assumption on what thorn's told me in the past.

Yes, tremulous should be compatible if you compile XreaL with q3acompat, but this does mean not getting any of the features from XReaL's renderer, and at the end of the day it seems a bit pointless. I did mention this before to you, and why it was a bit pointless since the only benefit would be the framerate, and even that can be nullified by the fact that it requires hardware well capable of running the game anyway.

That would probably just be a small project then, compiling the XReaL client in q3acompat with tremulous support, which could likely be distributed as just another optional binary client. Of course, that's purely assumption.

The material keyword(diffuseMap, normalMap, etc) support can be just re-enabled after the fact. I think it's switched off with a simple #ifdef.

[jm82792]

Hrm.
Well I can read up on Doom3 shaders.
Give the shader the textures, generate bump and spec maps then see what happens.
The maps are created using a modded form of radient right?

Basically I want to get it to work, utilize the new shaders, get a demo map and go from there.
When it's that far I can try to get a MD5 human character into the engine and get some tests to see how well MD5 is compared to MD3. The character would just be a simplistic rig to get the idea across.
I do not know if MD5 uses a animation CFG to tell the engine what frames and where,
I'll look it up and see.

I'm used to doing stills and not worrying about performance, but I will continue to read and get some understanding involving quake 3 and Xreal because I'd love to see something happen regarding a port.

[Nux]

Yo. I'm in that kind of mood again and so decided to do some concept work for a higher detail goon. My suggestion is that higher details beg for a new more interesting texture. Let me know if you like the direction I've taken and should continue it!

[Meisseli]

Yo. I'm in that kind of mood again and so decided to do some concept work for a higher detail goon. My suggestion is that higher details beg for a new more interesting texture. Let me know if you like the direction I've taken and should continue it!

[img]

I do indeed like it, except for the odd purple spots in the middle of the leg.

Is that kind of a texture even possible to have in such an outdated engine though?