First and foremost thanks for the kind words. It's exactly what I hoped to share with the community (but also wanted people to be able to pick and choose what appealed to them rather than bundling everything into a single mod).
I had vision and sensors set to 600m for about half of a campaign (almost the full LRM range of 630), and I found that I had information on the opposing forces so early it was like having no fog-of-war at all. Decisions were made with near-perfect information which sounds good on paper but gradually got dull and boring and took away some of the fun.
These values seemed to work well to allow effective long range attacks when combined with a mech in a scouting or flanking role. I would occasionally guess wrong when sending my flanker out and around the main force and discover another enemy lance. With these values that mech could usually escape with minor damage due to the distance from the hostiles and the evasion from sprinting. The main cost was a round or two of wasted movement, but it added spontaneous tension to the battles that I really liked and found fun and exhilarating!
The reason I made the vision distance longer than sensors was to all some (small) utility in hiding behind hills, forests and other obstacles that break line of sight.
If the sensor range is too much smaller than visual range the AI sometimes derps-out and stands there while you attack it because it doesn't detect you. It seems to work best if you keep the difference to a minimum if sensor range is smaller than visual range. The bigger the difference the more likely to get into an AI derp situation.
HBS set sensor range 33% larger than visual range, so we're operating outside of where the coding, design focus and QA testing would have been.
Give Feedback
4 comments
A question, why limited to 500, 450? Why not further so long range weapons can more effectively be used?
I had vision and sensors set to 600m for about half of a campaign (almost the full LRM range of 630), and I found that I had information on the opposing forces so early it was like having no fog-of-war at all. Decisions were made with near-perfect information which sounds good on paper but gradually got dull and boring and took away some of the fun.
These values seemed to work well to allow effective long range attacks when combined with a mech in a scouting or flanking role. I would occasionally guess wrong when sending my flanker out and around the main force and discover another enemy lance. With these values that mech could usually escape with minor damage due to the distance from the hostiles and the evasion from sprinting. The main cost was a round or two of wasted movement, but it added spontaneous tension to the battles that I really liked and found fun and exhilarating!
The reason I made the vision distance longer than sensors was to all some (small) utility in hiding behind hills, forests and other obstacles that break line of sight.
HBS set sensor range 33% larger than visual range, so we're operating outside of where the coding, design focus and QA testing would have been.