You modified a few ShipPlaced functions to take a different set of parameters for unclear reasons... The originally-passed CombatShipPtr contains a pointer to the ship you replaced it with... so why the change?
There is already a mechanism to add ship nodes to the combat wnd set up, but you seem to have ignored it and instead added a new method involving a direct dependency between CombatSetupWnd and CombatWnd, with the former having a member pointer to the latter... Why?
There can Be only One pathingengine Object which is in Combat wnd. I Need that Object to create à combatShip Structure which is Stores in the any stucture of the Node. So ill have to Call à function in combatwnd that created the Structure. For this Structure i Need the Ship and the Node Object which takes the shipplaced func.
The addship func simply isnt called when placing ships.
I suppose cause it Needs à combatship struct which cant created in combatsetupwnd.
There is some pathing stuff that adds obstacles for pathing around the star, planets and asteroid belts in the CombatWnd setup, but this ignores the wrapping of this sort of code in #ifdef that's used elsewhere.
The ifdefs are old. I wanted to make less changes As possible cause other People work on it , too.
I suppose that i enabled the ifdefs... If you mean the static opensteer obstacles Testung stuff.
You moved ray intersection code between files... why?
You mentioned Not looking for strings if determining weter à Ship and getting the any struct.
But it isn't stored in the Object returned by the Ray intersection.
So i had to make à workaround.
The ship animation stuff might be useful. It looks like the added MoveCombatShip function sets the ship's animation stuff so that it will move along a path that was determined by the collision system. Does this animated movement happen automatically over the next few seconds of rendering, without the MoveCombatShip being recalled?
If ships are themselves collision objects, and are moving around, doesn't the collision detection and pathing need to update for other ships moving, rather than relying on a path determined based on where things were when the move started? Or is is that already handled automatically?
we should Set up the Animation System to à Dynamic Position update. If you have 500 ships, the Time between collision Updates and steering Updates should Be longer.
Opensteer always returns wether there is steering needed that will Be made by this func.
Regardless, if my summary was right, then MoveCombatShip should probably be renamed SetShipMovePathAnimation or somesuch, to more clearly indicate what it does.
Could AddShield be modified, or the shield material be set up, so that the geometry of the shield could be calculated from the passed-in ship geometry? (I don't know what's really possible with this system...)
i have à Material half Ready for this, but i had Problems with the transparency.
Actually i discovered that there are powerful material ediord for this already exist.