Player Features and Ideas Discussion

Step one, it isn't the cluster handling the bumps, it's that single shard running the system. Jits is on it's own speshul system, so using that as a comparison is right out.

Collision detection *IS* the physics model. I mean, that's the PRIME job of a physics engine, is to work out collisions.

Also, again IIRC, there is no friction in EVE collision. Someone worked out the math long ago, but the rebound is simply done via a percent comparison based off of mass and velocity. This is why MWD works so well for bumping, it adds both.

Yes, programming is modular in a perfect world, in brand new code straight off the CVS. Now add ten years of patches, hacks hooks, and "just make it works".

You've still danced around exactly what I proposed. Rather than a simple DB call and compare at the (as you put it yourself) the rare instance of intentional collision, you want to install an overarching real-time module to physics engine check that does not currently exist. We're also doing this when the vast majority of the EVE playerbase, and CCP itself is happy with the current system of human evaluation of intent, if-when needed.



Anyway, lets say we install your system. After X MWD in Y timeframe, CONCORD shows up and kills the bumpers. No problem. I'll only bump in Y+1 time, and bring enough buddies to fill in the time. Make 5 minutes your timeframe, sure. I'll bring 25 buddies to bump (not hard at all). That's a bump per 15 seconds.

Any code fix you try to employ, is a fix I can work around. The only way to stop bumping is to ban it, and...CCP likes bumping. They've coined it as the "poor man's point" and toss it up as an example of unplanned emergent gameplay.

You're not quite understanding. A physics engine (I don't know EvE's so I'm being general) only handles physics. It shouldn't care about MWD. It doesn't care about collisions.

If I was programming a very simple program that dealt with this stuff I would have the graphics engine (only handles graphics), a physics engine (only handles pure physics), a collision detection model (only handles collisions), a flagging system (only handles flagging).

If in my program a ship collided it would be detected by my collision detection model. The collision detection system (CDS) would call the flagging system (FS) with the ships object id (ship1, ship2), the flagging system would examine ship1 and ship2 data and do its stuff. The CDS would then call the physics engine (FE) with the same id's. The FE would examine the ship1 and ship 2 data and do its stuff. It doesn't even know that a MWD exists, it exists just to handle physics so it does it stuff based on ship1 and ship2 data. The CDS doesn't call the graphics system because that's handled by the main system which called the CDS.

As for your only bumping x number of times well true but that's infinitely better then as many times as you like.

Not at all. I have given my point of view, explained my reasoning politely and you have responded with a one line comment attacking me and also tried to bypass the filter. Therefore I have reported you.

If you would like to explain why you think I'm ******** for saying the collision detection is separate from the physics engine then please do so. If no you're simply trolling and being offensive.

Here, I'll do it by stealing a line from the Havok (a physics engine) website.

"Havok Physics offers the fastest, most robust collision detection and physical simulation technology available, which is why it has become the gold standard within the games industry and has been used by leading game developers in over 400 launched titles and many more in development. - See more at: http://www.havok.com/products/physics#sthash.W21KFwkG.dpuf"


Here's a second one just in case. Bullet:
Bullet is a Collision Detection and Rigid Body Dynamics Library. The Library is Open Source and free for commercial use, under the zlib [LICENSE].



Duder, if a physics engine company itself says it's system does collision detection, that's good enough for me.

phys·ics (fzks)
n.
1. (used with a sing. verb) The science of matter and energy and of interactions between the two, grouped in traditional fields such as acoustics, optics, mechanics, thermodynamics, and electromagnetism, as well as in modern extensions including atomic and nuclear physics, cryogenics, solid-state physics, particle physics, and plasma physics.

mechanics plural of me·chan·ics (Noun)
Noun
The branch of applied mathematics dealing with motion and forces producing motion.

col·li·sion
/kəˈliZHən/
Noun
An instance of one moving object or person striking violently against another.

A physics engine does physics.

Its not the physics engine at all. ... Its a detection method for bumping which has nothing to do with the EvE physics.