forked from PapaJoesSoup/BDArmory
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fork Sync #82
Merged
SuicidalInsanity
merged 1,682 commits into
SuicidalInsanity:master
from
BrettRyland:master
Jun 15, 2023
Merged
Fork Sync #82
SuicidalInsanity
merged 1,682 commits into
SuicidalInsanity:master
from
BrettRyland:master
Jun 15, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ig fig in the numeric display.
Change AdjustableArmor over to FloatSemiLogRange Fix collisionDetection offset from -= to - remove frame and a half offset from unguided missile prediction time equation -Add check for radars to be on for radar missile launch stuff -Add alt tex for EMP missiles
…_FloatLogRange properly. Update BDAdjustableArmor sliders properly when toggling clamped/types.
-test and check missile optimalAirspeeds -use quad/linear equation for time or lead offset aiming calc
Switch to CPA offset calc for unguided missiles (firing trigger will still need tightening - current .35x boresight has a lot of inaccuracy) but good enough for, e.g. firing unguided missiles against ground targets -Add check for landed torpedoes, dropTime placeholder
-Guided missile lead offset calcs now use Doc's implementation. -Dumbfired LOAL missiles should now properly be able to acquire targets -Tighten up dumbfire firing tolerances. - Add radarTimeout field to missiles for inertial/radar guidance missiles.
…point of approach. Aiming for direct fire should continue to use the earliest, artillery should use either latest of closest.
-Fix missiles going skyward -loosen up boresight restriction for unguided missiles to let them fire
- Loft guidance now skips lofting if the target is directly overhead - Fixed vFactor used in some armor pen calculations resulting in erroneous results being output
- Changed logic to use the small angle (I.E. use 90 - loftAngle if loftAngle > 45) - This ensures if target is overhead the missile will climb directly to engage rather than use loft behavior
…nd semi-log sliders.
-Adjust AI drift when trying to find a recently lost target -Equipping multiple locking radars increases total number of radar locks the vessel can have -Fix laser mutator initialization -Fix NRE with DLZ calcs and multimissile launchers -Fix AI being able to see targets outside visual range -Attempting a radar lock will now check all available radars when trying to get a lock, instead of only the first locking radar on the ship. -Some additional sanity checks and logging for radar guidance -Some fixes to Multimissile launchers for decouple speed/direction and dropTime
-BnZ lead improvements
-properly lock SARH missiles when guardMode is off
Decided that AAMHybrid could be made more universal so I swapped it from an independent homingType to a boolean toggle. Should allow for some interesting guidance combinations.
Default values correspond to mild steel.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.