MirceaKitsune wrote:Anyway, too curious not to ask: Now that there's a physics engine, are ragdoll physics possible to implement?

LordHavoc said constraints are not yet implemented; I think those would be necessary for ragdoll physics.

Also are there any plans for wheeled vehicles after the Spiderbot? I always dreamed to see something like UT2k4s Scorpion in Nexuiz

I think tZork said he wasn't too interested in pursuing wheeled vehicles at the moment, but if you will code it, then I'll be happy to model and texture (and rig the suspension system?) the graphics for it, and collision mesh if desired.

Flying Steel wrote:but if you will code it, then I'll be happy to model and texture (and rig the suspension system?) the graphics for it, and collision mesh if desired

Me too! I offered my (little) modeling knowledge for a wheeled vehicle!
Then, Flying Steel, if you don't want to start by modeling a vehicle and want to finish an unfinished project, there's my percival model, that is still in the air , you can find it here !

I was thinking of making a six wheeled LAV with a slightly exaggerated suspension system to maybe take advantage of all this ODE magic at some point. Or whatever whoever was doing the coding really wanted.

But I took a look at your percival model and I'll respond on that in the thread you linked to.

yes, I saw it, thanks for your hints Flying Steel, if you need a hand for modeling some specific parts of your "six wheeled Monster" I could help you( sorry for my ignorance, what is a LAV?) !
In these days I've very little free time, but for small details like tyres or suspensions I can try! About the ODE physics for vehicles, I've seen on ODE Docs site section here, that it explains how to create a vehicle. Now, I'm very stupid about programming, so my question (I post it to devs )is: Is it possible to use Ode "commands" inside Nexuiz like this I found on that site?

Code: Select all

void applyAntiSwayBarForces() {
    amt = 0;
    for(int i = 0; i < 4; i++) {            
        Vector3 anchor2 = wheels[i].Joint.Anchor2;
        Vector3 anchor1 = wheels[i].Joint.Anchor;
        Vector3 axis = wheels[i].Joint.Axis2;

        displacement = Vector3.Dot(anchor1-anchor2, axis);

        if(displacement > 0) {
            amt = displacement * swayForce;
            if(amt > swayForceLimit)
                amt = swayForceLimit;
            wheels[i].Body.AddForce(-axis *amt); //downforce
            wheels[i^1].Body.AddForce(axis *amt); //upforce
        }
    }
}         


Curious people can take a look at this link and this !

LAV = Light Armored Vehicle.

Anyway I probably wouldn't start work on the graphics for such a thing until a coder was ready to take a swing at implementing it in Nexuiz.

Flying Steel wrote:LAV = Light Armored Vehicle

ok, thanks!

Flying Steel wrote:Anyway I probably wouldn't start work on the graphics for such a thing until a coder was ready to take a swing at implementing it in Nexuiz.

Yeah, you're right. This happened to me too with Percival. Once uploaded I thought that some coder told me: "Hey, put some bones on your model and rename it so so and I'll try to write some code for moving it!" Instead no one were interested. This maybe, because the atmosphere that rules on this forum is that "vehicles are inappropriate or not so useful for Nexuiz Gameplay". But ,IMHO of course, Nexuiz shouldn't represent only a well known fast paced GPL game, but also a source (with its physics, animation, gaming features) for future games that can would be created. If I ,for example, knew a code genius, and together we create a driving- shooting GPL game like GTA, maybe this wouldn't be similar to Nexuiz Gameplay, but maybe 1000 people all around the world would love it. I don't know if someone has my same thoughts.

toneddu2000 wrote:Yeah, you're right. This happened to me too with Percival. Once uploaded I thought that some coder told me: "Hey, put some bones on your model and rename it so so and I'll try to write some code for moving it!" Instead no one were interested.

Well currently only tZork is working on coding vehicles, and he has created two of them and expressed some interest in making a third flying one. He just isn't interested in making a vehicle with physics that simulates your average wheeled vehicle.

However, a skid steering wheeled vehicle (like your average tracked vehicle) might be alot more palatable, since it can turn in place, just like a player character can or the other nexuiz vehicles.

This maybe, because the atmosphere that rules on this forum is that "vehicles are inappropriate or not so useful for Nexuiz Gameplay".

I don't think anyone feels that way, anymore at least. The spiderbot and race have had a unanimously positive reception and vehicles are scheduled to become a stable feature in version 2.6.

It is just a matter of an individual coder deciding to take up the work of coding a new vehicle or vehicle type. And if he does so he has a very good supply of us artists who seem willing to do the graphics for said vehicle (at least four of us, maybe seven).

Flying Steel wrote:LordHavoc said constraints are not yet implemented; I think those would be necessary for ragdoll physics.

It sounds like div0 has implemented constraints...

toneddu2000 wrote:Now, I'm very stupid about programming, so my question (I post it to devs )is: Is it possible to use Ode "commands" inside Nexuiz like this I found on that site?

I chose not to support ode functions at all in the QuakeC side, because they would not be saved to savegames, I went for entirely entity-based implementation, all automatic (you only set it up to use physics and configure it a bit).

Any constraint configuration would be in entity fields.

LordHavoc wrote:It sounds like div0 has implemented constraints...

Good to hear, thanks div!

Flying Steel wrote:I don't think anyone feels that way, anymore at least. The spiderbot and race have had a unanimously positive reception and vehicles are scheduled to become a stable feature in version 2.6.

Well, This sounds like a good news!

LordHavoc wrote:I went for entirely entity-based implementation, all automatic (you only set it up to use physics and configure it a bit).

Thanks LordHavoc for the clarification, but is still too technical for me, there's a lot of things I can't understand. There's someone who can share a map with physics so I can take a look?

Another stupid question (don't shoot at me, please ): div0 and divVerent are the same person? I've never understood!

toneddu2000 wrote:Another stupid question (don't shoot at me, please ): div0 and divVerent are the same person?

Yes, div is div, he just uses slightly. . . difFerent callsigns for the forums and IRC/Multiplayer.

Flying Steel wrote:

toneddu2000 wrote:Another stupid question (don't shoot at me, please ): div0 and divVerent are the same person?

Yes, div is div, he just uses slightly. . . difFerent callsigns for the forums and IRC/Multiplayer.

OT a bit, but nowadays it seems it's a fashion for seasoned players to change their nick frequently on the forum, irc, and ingame.
Though at least I'm using a different nick on IRC only

ok,thanks!

Sorry I cant send you a bottle of champagne via IRC but know that I thank you... al lof you who have made this possible...

I didn't do much except testing, but well, i'll take that tyvm

/me drinks

Samual wrote:I didn't do much except testing, but well, i'll take that tyvm

/me drinks

Same here *drinks a small amount then

There's someone who can explain me how to create an element "wheel" in Nexuiz-ODE, or just tell me where to get information about it?

toneddu2000 wrote:There's someone who can explain me how to create an element "wheel" in Nexuiz-ODE, or just tell me where to get information about it?

As far as I know, the only way to create a wheel is to make a brush and use SOLID_BSP mode (so it does triangle mesh vs triangle mesh collisions).

Many physics engines do not support flat-ended cylinders, only capsules (rounded end cylinders).

ODE supports them partially - they can not collide with most primitives, so I did not implement them as their support is incomplete.

Thanks LordHavoc, but where I should use SOLID_BSP mode? In netradiant, creating an object and setting this value to it, or in Blender using the property button to add a SOLID_BSP value, or ingame in Nexuiz?

toneddu2000 wrote:Thanks LordHavoc, but where I should use SOLID_BSP mode? In netradiant, creating an object and setting this value to it, or in Blender using the property button to add a SOLID_BSP value, or ingame in Nexuiz?

In QuakeC code in Nexuiz.

However I do not know how the physics objects are set up on the Nexuiz side, I only implemented it in the engine, I think div0 is responsible for the QuakeC code for it.

It seems likely that he made the solid type configurable in the entity in netradiant.

SOLID_BSP is 4 iirc, the other physics modes are 32 or higher.

LordHavoc wrote:In QuakeC code in Nexuiz.

That was what I want to know!Thanks!

LordHavoc wrote:However I do not know how the physics objects are set up on the Nexuiz side, I only implemented it in the engine, I think div0 is responsible for the QuakeC code for it.

It seems likely that he made the solid type configurable in the entity in netradiant.

Ok, so, let's see if I understood well: If I, for istance,
1 first I create a car1.qc in data/qcsrc/vehicles and put car.qc in progs.src
2 I write at the end of the qc file void spawnfunc_vehicle_car1()
3 After compiling I open NetRadiant and create a spawnfunc car 1 object and I give it a SOLID_BSP attribute with ?? value . Now, instead of ?? what value should I put?
Is this the correct way of create a wheel?

FruitieX wrote:SOLID_BSP is 4 iirc, the other physics modes are 32 or higher.

Sorry, but I didn't understand what iirc stands for.. and where physics mode are avalaible (netradiant values ?)!

toneddu2000 wrote:

LordHavoc wrote:In QuakeC code in Nexuiz.

That was what I want to know!Thanks!

LordHavoc wrote:However I do not know how the physics objects are set up on the Nexuiz side, I only implemented it in the engine, I think div0 is responsible for the QuakeC code for it.

It seems likely that he made the solid type configurable in the entity in netradiant.

Ok, so, let's see if I understood well: If I, for istance,
1 first I create a car1.qc in data/qcsrc/vehicles and put car.qc in progs.src
2 I write at the end of the qc file void spawnfunc_vehicle_car1()
3 After compiling I open NetRadiant and create a spawnfunc car 1 object and I give it a SOLID_BSP attribute with ?? value . Now, instead of ?? what value should I put?
Is this the correct way of create a wheel?

You would be creating an entity whose classname is set to: vehicle_car1

The spawnfunc_ prefix is only used in the code.

However you also did not put enough code in there to be useful for anything, and I do not have enough time to explain what you need to put in there.

At the bare minimum for a physics object you need this line in your spawn function:
setmodel(self, self.model);

Then in radiant you need to add these fields to the entity:
"model" "models/car1/wheel.md3"
"movetype" "32"
"solid" "4"
"mass" "1"

However this will only make a wheel object, you need more code to make a car, as I said above.

toneddu2000 wrote:

FruitieX wrote:SOLID_BSP is 4 iirc, the other physics modes are 32 or higher.

Sorry, but I didn't understand what iirc stands for.. and where physics mode are avalaible (netradiant values ?)!

iirc = IIRC = If I Recall Correctly

Thanks LordHavoc, as always your reply was providential!

LordHavoc wrote:The spawnfunc_ prefix is only used in the code.
However you also did not put enough code in there to be useful for anything, and I do not have enough time to explain what you need to put in there.

No, no, of course, I understood that! I only meant to say that If I created an ENTIRE code for a car (which explains which movements it has to do, where it should steer, and so on) , it ended with that string!

LordHavoc wrote:At the bare minimum for a physics object you need this line in your spawn function:
setmodel(self, self.model);

Then in radiant you need to add these fields to the entity:
"model" "models/car1/wheel.md3"
"movetype" "32"
"solid" "4"
"mass" "1"

Ok,thanks I'll try it as soon as I can!

LordHavoc wrote:iirc = IIRC = If I Recall Correctly

OMG, it was so simple! I thought it was a Net Radiant variable!

I'm wondering what the status of ODE is now. Is it out of experimental state and enabled by default? Can it be safely used on maps as well?

not to be too demanding but when can we have this puh-lalse:
http://www.techeblog.com/index.php/tech ... estruction

having worked with bullet and ode, id have to say bullet would be better in my opinion for nexuiz. but i'd really like to see DMM, or Digital Molecular Matter, implemented.

Why would bullet be better Mizu Kitsune? And for obvious reasons, forget abt DDM in dp.