|
|
I wanted to make a picture. IHadFunMakingThis.jpg (125,673 bytes) |
|
|
I had thought about this also, as well, yes. One idea for this sort of thing was to make it so "once tractored, can't be untractored based on distance alone." |
|
|
I'll have to look when I'm back from work, but I think this is a bit more fucky than it lets on. If the ship id of the tractor source is lower than the tractored ships, I think the pulling effect of the source might not even work properly. |
|
|
Interesting -- definitely worth looking at, then. I appreciate it! |
|
|
Well, I found one thing about the changes you made so far, once a ship is stunned or tractored its unable to receive new decollision orders. With entity.CalculateSpeed(), it will return a non-zero number only if the ship has a decollision order on the front of the order stack. DecollisionPlanning.cs doesn't calculate decollisions for any ship that has a speed of zero though (line 242), so once a ship has zero speed they won't be able to decollide to reduce bunch ups from crowd control. On the subject of code collisions with respect to entity ID: this does appear to be an issue. The variable FramePlan_Move_NextMovePoint is not a delta between last frame and the frame after, but just holds the absolute X-Y coordinates of the ship's position at the next frame. When the tractor pulls a ship, the tractor source calculates its delta move and adds it to the other ship's position so they move in sync. But since FP_Move_NMP is an absolute position, if the ship has a higher ID than the tractor source, the tractor source will add the delta move to the ship's position but then it just gets overwritten by FP_Move_NMP. If the ship's ID is less than the tractor source's ID then everything works just fine. You've got two ugly solutions, rewrite MovementPlanning.cs to return a delta move (actually maybe not that ugly), or somehow force tractor sources to be evaluated last when moving ships around (confusing more than anything, I can see some random SVN contributor reverting things to clean up the code). |
|
|
Not exactly what you had in mind, but just checked in: * Fixed a pair of issues in the prior versions where decollision logic would not be run ever for ships with a current speed of 0 (from tractoring or whatever), so they would still stack up; and then also ships that were on the way to a wormhole or transport but then also had a current speed of 0 would STILL not be able to decollide. ** These both combined to make it so that ships were stacking up like crazy still when they were being bombarded by spiders, widows, or tractor beams. This in general looked awful and made it hard to see what ships were there, making it also a usability issue. ** This DOES of course mean that ships will be able to escape from tractor range some of the time, and that's regrettable, but generally if your tractor beams are in the direction the enemy is headed (the most common case) that's not possible anyway. The most likely scenario is ships trying to flee from a planet actually getting away from you when you were trying to stun them. Thanks! I'll respond to the next bit in a second. |
|
|
Regarding entity movement order, bear in mind that's not actually in the order of the ID. It's actually in the order of when they were added to the current planet. So a tractor beam is most likely longer-existing on a planet compared to a ship that is invading, for instance. Anyway, your point still remains, and probably those need to be changed to deltas. Seems like a good project for someone if anyone has time. For now I'm working on the galaxy map usability and then the sidebar, and achievements, etc. Trying to hit the things that nobody else can really get to. |
|
|
Fixed a long long time ago! |
- Anonymous
