Dev: Custom Conquer Client

Quote:

Originally Posted by InfamousNoone I'm inclined to strongly disagree with this post. It's much easier to achieve cross platform with minimal with C# as opposed to the hoops you have to jump through with C++.

Quote:

Originally Posted by .Ocularis seriously cool project Angelius. besides the obvious, what are your intentions for development of a custom client for conquer? Also, how did you learn what you needed to know to reach the current point in the development progress?

Quote:

Originally Posted by { Angelius } As to how I learned the stuff that got me this far the answer it simple. I Googled it LMAO.

Quote:

Originally Posted by .Ocularis A "whole new game" would be great, but why expand past the resources you already have? It seems a bit rabbit-trailish to me. IF you built a custom client to improve on the current Conquer client, you could upgrade to your stuffy maps later while having a complete working project. A possible upgrade for your users to keep their interest more-so would be more prospective imo.

Quote:

Originally Posted by .Ocularis Another opinion and idea on upgrading to your stuffy maps, why? when your view remains 2d isometric? Visualize with me.. a 3d map, resting on a needle point, and a camera with pan and zoom. As the camera pans, the edge of the map; relative to the center of the camera, is pressed down until the same isometric perspective is reached as in Conquer's 2d isometric view. Transformation matrix?

Quote:

Originally Posted by CptSky Don't forget the client was developed in the early 2000s and wasn't truly updated since then. A lot of things have changed since they started CO2. Coding practices for games and MMOs too.

Quote:

Originally Posted by .Ocularis "I don't think there's anything else that you guys ne[end of video]" NOOOO SHOW ME MORE Looking forward to more of these updates :D

Quote:

Originally Posted by pro4never Awesome progress and interesting to watch. I'm not denying for one single moment that TQs client sucks and is a mess in terms of performance but keep in mind that scattering 100 mobs and the client crashing is a server issue, not a client problem (ok... it's both but it's a bug no playable server should have) The client has a max buffer size for single packets. If you send too many targets in a single skill packet (max # of targets changes with client version as they make each target use more and more data), it will cause an unhanded exception and crash the client. Totally unrelated just irked me cause I've seen that complaint so many times. Generally if you see that on a pserver it's a good sign it's a shit server or at least one that still needs some dev work :)

Quote:

Originally Posted by CptSky Don't forget the client was developed in the early 2000s and wasn't truly updated since then. A lot of things have changed since they started CO2. Coding practices for games and MMOs too.

vector<> everything;//this is the vector that contains everything 

for (i = 0; i < everything.size(); i++)
{
     everything[i].process();//mapobject
}

mapobject::process()
{
      if(distance <= )
      {
           InteractiveLayer::ApplyShow(this);//determine when to draw this 
      }
}

vector<> finalvector;//cleared every frame 
InteractiveLayer::ApplyShow(mapobject object)
{
     for (i = 0; i < finalvector.size(); i++)
     {
           if (xyz)
	    {
                  int bInsert = i; 
                  for (int n = i - 1; n >= 0; n--)
                  {
                 
                  }
                  finalvector.insert(begin() + bInsert, object);//Draw me after anything < bInsert and before anything > bInsert
            }
            else
            {
                  nOverLayAfter = i;
                  for (int n = i + 1; n < dwSize; n++)
                  {

                  }
                  finalvector.insert(begin() +nOverLayAfter, object);
            }
     }
}

and then when it's time to draw 

for (i = 0; i < finalvector.size(); i++)
{
     finalvector[i].draw();
}

Quote:

Originally Posted by KraHen ^ That. With that said, software/hardware batching was and is available, all their monsters use the same material, so all mobs on the screen can and should be drawn with a single draw call, the fact that they cannot do that proves incompetency. The fact that the client is old is not an excuse for not optimizing/updating it (it wouldn't even change a single thing visually for the end users).

Quote:

Originally Posted by { Angelius } ... Agreed, but why should they? I mean it works the way it is and they are making money and everyone is happy lmfao. But hey joking aside, I really don't see a problem with that I mean draw calls are cheap and are becoming even cheaper every year, Modern GPU's are designed to handle an insane amount of draw calls per second with little to no effort. so if the CPU is not being burnt out and is able to keep up with the GPU then where is the problem? I mean if I am not mistaken (correct me if i am wrong) the only time you would benefit from a single draw call is when you have a shit load of low poly objects to draw and by a shit load i mean hundreds if not thousands.