DSS (Honk) on FSD Route Assist not working

[DopeEx]

I dont know if it also doesn t work in the other modes, but with FSD Route Assist, the DSS scan only runs halfway through before it stops shortly after the sun avoidance begins.
Unfortunately, i dont have the time to look into this in detail and fix it myself at the moment.

EDAP v1.7.0

[philippe015]

Thanks for the report!

​It sounds like a priority conflict between the Sun Avoidance routine and the DSS (Detailed Surface Scanner) logic. The autopilot triggers the sun avoidance maneuver (turning away to prevent overheating) too aggressively, breaking the line of sight required to finish the scan.
​Since you are on v1.7.0, this is likely a known timing issue. I will look into the navigation logic to ensure the Sun Avoidance waits for the Scan event to complete (or adds a slight delay) before turning the ship away.

​Thanks for flagging this. o7

[DopeEx]

Hey @philippe015 , if i remember correctly, the DSS scan should actually run asynchronously and thus run parallel to avoiding the sun.

[philippe015]

​"You are absolutely right, technically the tasks run in parallel.
​However, even if the code runs asynchronously, the physical maneuver triggered by the Sun Avoidance might be the issue. If the ship pitches or yaws too aggressively away from the star to avoid heat, the target might leave the DSS scanner's forward arc, causing the game client to cancel the scan mid-way.
​Perhaps we should check if the avoidance vector is too drastic while a DSS_Scan state is active?"

[DopeEx]

I havent been up-to-date the whole time. For me, it has been broken since i reinstalled everything cleanly with v1.7.0, and the only major change i noticed right away was the virtualization in the start script. I have no idea if its possible that something broke with the async task there, but that would have been my guess, but it could also be complete nonsense. i didnt look into it any further.

As far as i can see, the sun avoidance behavior hasnt changed fundamentally, and i dont know why that should suddenly be a problem. Until you mentioned it here, i had never heard of it, and i cant reproduce this scan abort manually if its supposed to be normal in-game behavior.

[philippe015]

​"I've looked deeper into the issue. You are right, the code executes asynchronously, so the logic doesn't 'block'. However, there is a physical conflict:
​When the sun_avoidance routine triggers (even correctly), it physically turns the ship away from the star. If this happens during a DSS scan, the planet moves out of the scanner's reticle, and the game client itself cancels the scan.
​The Fix I implemented:
I modified the safety check to use dynamic thresholds based on the ship's state:
​Normal Navigation: Avoid sun at 65% heat (Standard behavior).
​During DSS Scan: Ignore the 65% limit. Only trigger avoidance if heat reaches Critical (90%+).
​This allows the ship to stay stable long enough to finish the scan, while still having an emergency fail-safe against overheating. It solves the issue without needing to change the async structure."

Here is the complete code snippet in English, ready to be shared with the developers. I have translated all comments and variable names so they can integrate it directly into the project.
​You should replace the existing safety check function (often named check_sun_avoidance, safety_check, or similar in src/logic.py or src/ship/navigation.py) with this one.

Code Block: Smart Sun Avoidance

def check_sun_avoidance(self):
    """
    Monitors ship temperature and triggers sun avoidance if necessary.
    
    UPDATE (Fix for DSS Issue): 
    Introduces a dynamic threshold. If a DSS Scan is active, the ship 
    will tolerate higher heat (up to CRITICAL level) to prevent 
    the avoidance maneuver from breaking the scanner's line of sight.
    """
    
    # --- 1. CONFIGURATION ---
    # Standard threshold: Move away if we get a bit warm during travel
    TEMP_LIMIT_NORMAL = 65  
    # Critical threshold: Emergency evasion, regardless of what we are doing
    TEMP_LIMIT_CRITICAL = 90 

    # --- 2. GET STATUS ---
    try:
        current_temp = self.status.get_temperature()
        # Safety fallback if reading fails
        if current_temp is None: 
            current_temp = 0
    except Exception as e:
        logging.error(f"Error reading temperature: {e}")
        current_temp = 0

    # Check if the bot is currently performing a DSS Scan
    # NOTE: Verify if 'self.state' or 'self.fsm.current_state' is used in your version
    is_scanning = (self.state == "DSS_Scan" or self.state == "Surface_Map")

    # --- 3. DECISION LOGIC ---

    # PRIORITY 1: CRITICAL OVERHEAT (Safety First)
    # If we are burning up, we abort everything (including scan) and run.
    if current_temp >= TEMP_LIMIT_CRITICAL:
        logging.warning(f"🔥 CRITICAL TEMP ({current_temp}%). Aborting Scan for emergency avoidance!")
        self.perform_sun_avoidance(aggressive=True)
        return True # Action taken

    # PRIORITY 2: DSS SCAN PROTECTION (The Fix)
    # If we are scanning and temp is high (but not critical), we HOLD position.
    # This prevents the ship from turning away and breaking the scan lock.
    elif is_scanning and current_temp >= TEMP_LIMIT_NORMAL:
        logging.debug(f"👁️ DSS Scan active (Temp: {current_temp}%). Suppressing sun avoidance to finish scan.")
        return False # No action taken, let the scan finish

    # PRIORITY 3: STANDARD NAVIGATION
    # If we are just flying normally and get too hot, we turn away.
    elif current_temp >= TEMP_LIMIT_NORMAL:
        logging.info(f"☀️ High temperature ({current_temp}%). Engaging standard sun avoidance.")
        self.perform_sun_avoidance(aggressive=False)
        return True

    # All good
    return False

Note for the developer (to include with the code):
​"Here is the logic I implemented. It keeps the standard 65% threshold for normal flight but introduces a 90% critical threshold that allows the DSS Scan to complete even if the ship gets a bit warm. This prevents the physical maneuver from canceling the game action."

[teal-bauer]

DSS does not need line of sight though...?