CV's & Ports & V-Base Only Arena(New Isles Map)

[Iron_Cross]

I think everyone is forgetting that the server has to move where the CV is, constantly.  Not only where it is on the map and where it needs to go but your also forgetting the flight deck, flight deck spawn point, rearm pad, arresting wires, all the guns, vehicle and PT spawn point, and ship positions.  That is just for one task group. That data also has  to go out on every packet you get.  That is every task group, every packet, every time.  Your FE will slow down if it doesn't get the positions of every task group within visual range for your FE to render.  Until it gets all the data, your FE will keep skipping a cycle.  If the packet buffer length is exceeded by trying to update every task group in visual range of your FE you will run into FR slowdown big time.

[dedalos]

Originally posted by Iron_Cross
I think everyone is forgetting that the server has to move where the CV is, constantly.  Not only where it is on the map and where it needs to go but your also forgetting the flight deck, flight deck spawn point, rearm pad, arresting wires, all the guns, vehicle and PT spawn point, and ship positions.  That is just for one task group. That data also has  to go out on every packet you get.  That is every task group, every packet, every time.  Your FE will slow down if it doesn't get the positions of every task group within visual range for your FE to render.  Until it gets all the data, your FE will keep skipping a cycle.  If the packet buffer length is exceeded by trying to update every task group in visual range of your FE you will run into FR slowdown big time.

Please stay away from software development.  Its for the better

[dedalos]

Originally posted by hubsonfire
But a CV group isn't a single object like a plane, is it? Aren't all the gun emplacements, batteries, auto ack, radar, escorts, their ack, etc separate objects that have to be tracked and updated?

Yes dedalos, I know you'd have designed the game differently, but what matters here is how it is, not how it might have been otherwise.

Thats not the point. There is no way that this is how it is.  If it is it needs afixin. All the server needs to do is know the location of the CV.  The rest are relative positions to the CV coordinates.  Really all it needs to keep track of is 2 numbers.  It already does do with 200 planes in the air and GVs on the ground.  

The only one that can answer if it is possible and how it is done is HT not the players.  I understand how the FEs may have an issue since all you have to do is look at the screen funny and the FPS goes down, but not the server.  Check the AvA map and see how many CVs are there.

[The Fugitive]

I don't know about any one else, but I'm glad dedalos doesn't work on the HTC programmers team !

[OOZ662]

If the server only needed to know where the CV started and where it is going, nobody could discover where the CV is at correctly if they logged in between the time the CV waypoint was created and the end/time of change of the waypoint. If the server needs to know where the CV currently is and where it's headed, well...isn't that the problem? Needs to know where it currently is?

[Iron_Cross]

Originally posted by OOZ662
If the server only needed to know where the CV started and where it is going, nobody could discover where the CV is at correctly if they logged in between the time the CV waypoint was created and the end/time of change of the waypoint. If the server needs to know where the CV currently is and where it's headed, well...isn't that the problem? Needs to know where it currently is?

Dedalos, this is what I'm talking about.  The way you are thinking it works, can not work.  Even if the task group was a single mesh,(witch it isn't) the server will still need to update the current location to all client machines with every packet.  

You think I would make a bad game developer, Dedalos?  I was coding up games when sprite graphics were the top of the line.  You were probably pooping your diapers back then, if you were born at all.  I've got 25 years experience writing programs, so don't tell me I'm making something out to be more complicated than it needs to be.

[hubsonfire]

edit that's bad, even for me. not going to go there.

[OOZ662]

There's also evidence in this constant updating being that the CV will be in many places for different people. This is what causes new planes to pop up in thin air off the deck; their front end is displaying the CV in a different location due to lag.

[Relorian]

I rather like the Idea of CV wars, mostly because on whole, the CV tends to just turn into a mobile base attack then gets sunk durring or soon after the base gets jumped if the attackers fail.

Id love to see mass TBM or SDB missions being supported by f4f's and f4u's but thats just because im a fan of running seaplanes.

[Yknurd]

^^^ I like this idea a lot.

I would also like to see Val's running torpedoes at a carrier escort by zekes.

[dedalos]

Originally posted by Iron_Cross
Dedalos, this is what I'm talking about.  The way you are thinking it works, can not work.  Even if the task group was a single mesh,(witch it isn't) the server will still need to update the current location to all client machines with every packet.  

ok, the problem is that I gave people too match credit I guess.  Is that what you mean about updating?  Keeping track of the coordinates?  Updating an X and Y is too match for the server?  Sending the update to the clients in every packet is just dumb.  You send the initial location when a guy logs in, the way points, the way point changes, and then you may want to sync once in a while.  The speed of the CV is constant right?  Your FE knows its location speed and destination.  You really think the server needs to send an update on every packet?
Now, lets assume that for some reason this server was designed by students and it does send updates on every packet for the CV.  You understand that it does do that for the planes then too right?  So, with your logic, the server can keep track and update locations and transmit information for lets say 200 planes but not for 200 plus 6 CVs?
Here is some more bad news for you.  The server is sending information using multicast.  It makes no difference if there is 1 client connected or 5,000.  The server sends 1 packet and every one gets it.  The problems you may see with location of CV for example is that UDP is not reliable and therefore a packet that contains information about its location could be lost.  Eventually, the server will sync the position and the CV finds its right location.  I think that kind of proves my point since if the server was sending an update on every packet about the position of the CVs you would never have this problem.

You think I would make a bad game developer, Dedalos?  I was coding up games when sprite graphics were the top of the line.  You were probably pooping your diapers back then, if you were born at all.  I've got 25 years experience writing programs, so don't tell me I'm making something out to be more complicated than it needs to be.

What, you think you'd be the first clueless programmer with 20 years experience that I would have to send home?   Sounds like you may have drawn some pretty pictures for a game.  Don't confuse your self though.  That has nothing to do with programing servers.

[Yknurd]

Can't you two go measure noodlees somewhere else?

[dedalos]

Originally posted by Yknurd
Can't you two go measure noodlees somewhere else?

 lol, the point is not who is right or wrong.  Only HT could be right in this case.  I see these things in the wish forum a lot.  Some one asks for something and a bunch of clueless dolts show up to explain why it is impossible.  Why?  Why sit here and explain why something is impossible what you cant possibly know the answer.  Its a wish.  You either like it and you say so, you dont like it and you say so, or you STFU

[OOZ662]

The CV's speed is not constant. It slows to varying speeds in different turns and will even stop if it reaches an area it cannot complete the desired turn. Also, during zigging turns, the ships fan out in many directions and vary their speeds trying to maintain distance from the flagship.

[Ghosth]

Ok so design a map around the peace symbol with a small sea in the very center.

3 landmass's coming from the outside to the center. Each country owns one landmass with ports and cv's on both sides of it. Put 3 uncapturable fields and strat's in the outermost part of the landmass. lots of Vfields around the central part. A large airfield with port on each side in the center. And one port for the central sea.

So no more than 2 cv's can cluster for any one map location except center sea which could have 3.

Fester you interested in this I'll draw you a sketch of what I had thought of.