You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's always been difficult for me to tell how a fit's ewar will exactly affect a target ship's behaviour at range. Projecting the fit only gives you accurate results at close range, and it's difficult to tell exactly at what range the target can lock you back if you're in the falloff of your damps, or at what range can a sniper fit still shoot at you when it starts to outrange your disruptor optimal.
It occurred to me that a janky way to simulate that would be to make the target ship's ewar automatically project onto the source in the DPS sim. There might be a better way to do this, it certainly feels very dirty, but I did manage to get a working prototype going with a few hours of tinkering:
I simply abused the ewar graph code to query the target fit's ewar strength when checking lock range and application at each point. There might be a cleaner way of doing this as well, but it worked for a quick prototype. For a final version, you'd probably want a toggle in the graph settings for this or something, it's very hard to tell what's going on if you don't know this is happening.
The text was updated successfully, but these errors were encountered:
It's always been difficult for me to tell how a fit's ewar will exactly affect a target ship's behaviour at range. Projecting the fit only gives you accurate results at close range, and it's difficult to tell exactly at what range the target can lock you back if you're in the falloff of your damps, or at what range can a sniper fit still shoot at you when it starts to outrange your disruptor optimal.
It occurred to me that a janky way to simulate that would be to make the target ship's ewar automatically project onto the source in the DPS sim. There might be a better way to do this, it certainly feels very dirty, but I did manage to get a working prototype going with a few hours of tinkering:
![image](https://private-user-images.githubusercontent.com/112854031/324199875-03d13320-b484-41ca-85b1-ce109afa2a83.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM5MjU1MDcsIm5iZiI6MTcyMzkyNTIwNywicGF0aCI6Ii8xMTI4NTQwMzEvMzI0MTk5ODc1LTAzZDEzMzIwLWI0ODQtNDFjYS04NWIxLWNlMTA5YWZhMmE4My5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgxN1QyMDA2NDdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04MjczZTFlNzI5MGQ2M2VmZWNiMmE4MWEzZTMzNzJmMmEyY2NkNjQwZWJjYzcxNTA0YjJkZDQ4OWQ4Njc4NGE0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.fNqJkgubpxUsYD-NIeBTUpD3LwJyOIdxf0v15LtHCFw)
I simply abused the ewar graph code to query the target fit's ewar strength when checking lock range and application at each point. There might be a cleaner way of doing this as well, but it worked for a quick prototype. For a final version, you'd probably want a toggle in the graph settings for this or something, it's very hard to tell what's going on if you don't know this is happening.
The text was updated successfully, but these errors were encountered: