Code center > Bugs and fixes

Why aren't you using 2.42?

<< < (2/19) > >>

Numsgil:
Collision response might be a little hard to fix without transfering 2.5's physics into 2.4.  Possible, but might be alot of work.


--- Code: ---for(int x = 0; x <= MaxRobs; x++)
    {
        if(rob[x] != NULL && rob[x]->AbsNum < this->AbsNum)
        {
            Vector4 normal = rob[x]->pos - this->pos;
            float mindist = this->radius + rob[x]->radius;
            mindist *= mindist;
                        
            float currdist = LengthSquared3(normal);
            
            if(currdist < mindist)
            {
                //UPDATE CHANGES IN VELOCITY
                const float e  = SimOpts.ElasticCoefficient = 0.5f;
                const float M1 = this->mass;
                const float M2 = rob[x]->mass;
                
                normal /= sqrtf(currdist); //normalize normal vector

                Vector4 V1 = (this->vel * normal) * normal;
                Vector4 V2 = (rob[x]->vel * normal) * normal;

                Vector4 V1f = ((e + 1.0f) * M2 * V2 + V1 * (M1 - e * M2))/
                            (M1 + M2);
                
                Vector4 V2f = ((e + 1.0f) * M1 * V1 + V2 * (M2 - e * M1))/
                            (M1 + M2);
                
                this->vel = V1f + (this->vel - V1);
                rob[x]->vel = V2f + (rob[x]->vel - V2);
            }
        }
    }
--- End code ---

There's the function that handles the velocity changes of collisions.  You might be able to put it directly into the VB source (you'll need to change syntax obviosuly, and handle vector math iwht functions instead of operators).

Elite:
If it's going to be a lot of work, then I'll settle for (1) and (3)  

shvarz:
OK, I said this before and I'll repeat it now.  I have been against 2.4 VB version from the very beginning (Nums knows this, but he does not care).  It is very different from 2.37.6 version and does not represent an upgrade, but rather a totally different program.  It does not comply with backword-compatibility required for a version to be called an update.  Bots from one version don't work well in the other.  So by having a 2.4 version on the server we are confusing people into beleiving that 2.4 is a valid update, while in fact it is not.  Most of discussions on this board (especially the old ones) are related to 2.37 version and don't necessarily apply to 2.4.  We've seen people come and get confused by this.  

In my view 2.37 is a more or less finished product and should be presented as such, while the new stuff should be explicitly called new stuff and be distinguished from anything that was done before.

I am using 2.37.6 and I will be using it until the new C version of DB comes out (maybe even after that).  And I think everyone should do that.  So I would say: Why don't we delete the 2.4 version from the server?

PurpleYouko:
I am still using 2.37.6 as it is now the most stable version available. We all went to a whole lot of trouble getting it that way.
I tend to agree with Shvarz that 2.4 isn't so much an upgrade as a whole new program without much in the way of backward compatability.

The leagues are still officially run in 2.37.6 ( when they get run at all) although if anyone wants to start up a new league for 2.4 then they should feel free to do so.

Generally I don't really like 2.4 very much. It's difficult to pinpoint all the things I don't like specifically but I just get a general feeling of it not being quite complete in the way that 2.37.6 is. Loads of stuff isn't working properly still and I don't really like the little diddy bots very much.

I also intend to stay with 2.37.6 and maybe even continue to build on it in parallel to the C++ version. (I am not now and probably never will be a C++ programmer. It's like an alien language to me)

I think of 2.4 as an unfinished and mostly abandoned project that quite frankly isn't worth spending time on.

If you all want to carry on and use it then that's up to you but I won't be doing so unless it gets a whole lot better.

Numsgil:
It's not that I don't care, I do care.  I just disagree.

A couple of minor things cause older bots to behave oddly, but that's hardly the first time it's happened in updates.  When PY changed the eyes from being 45 degree scanning range to 90, most bots broke.

But 2.4 is still essentially in the same spirit as 2.3.

Compare that to what I'd like 2.5 to be when it's really done (and is given the 3.0 monicer).  Most sysvars will be upgraded or discarded.  Ties will work entirely different.  -6 shots will be replaced with phagocytosis.  Metabolism will be working at least a little bit.  In every concievable way everything will have been taken one at a time and examined and changed.  That's far more fitting for a 3.0 title than 2.4, where really the only major changes are DNA flow (being made less strict) and Phsyics.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version