IASER Troubleshooting Guide

Comprehensive troubleshooting guide for common IASER issues and their solutions

Quick Issue Search

Common Issues

Connection Failed - Cannot Connect to IASER

DCS mission cannot establish TCP connection to IASER system, showing "Connection Failed" or timeout errors.

✅ Solution Steps:
  1. Ensure IASER executable is running before starting DCS mission
  2. Check Windows Firewall - allow IASER through firewall
  3. Verify port 8080 is not being used by another application
  4. Try running IASER as Administrator
  5. Check antivirus software - add IASER to exclusions
# Check if port 8080 is in use (Command Prompt) netstat -an | findstr :8080 # Kill process using port 8080 if needed netstat -ano | findstr :8080 taskkill /PID [ProcessID] /F

IASER Executable Won't Start

IASER executable crashes on startup or fails to initialize strategic systems.

✅ Solution Steps:
  1. Run as Administrator - right-click executable and select "Run as administrator"
  2. Install Visual C++ Redistributable (usually included with Windows)
  3. Check system requirements - Windows 10/11, 8GB RAM minimum
  4. Temporarily disable antivirus and try again
  5. Download fresh copy if file may be corrupted

GUI Interface Not Loading

IASER_Unified_GUI.exe shows blank screen or GUI elements are not displaying properly.

✅ Solution Steps:
  1. Update graphics drivers to latest version
  2. Try running with compatibility mode (Windows 8/7)
  3. Check display scaling - set to 100% temporarily
  4. Use alternative executable (IASER_Complete_Embedded.exe)
  5. Restart Windows and try again

DCS Scripts Not Loading

DCS mission shows script errors or IASER integration scripts are not being loaded.

✅ Solution Steps:
  1. Verify script files are in correct DCS Saved Games folder
  2. Check file permissions - ensure DCS can read script files
  3. Remove Windows file blocking - right-click script files → Properties → Unblock
  4. Verify exact file paths in mission triggers
  5. Check DCS.log for specific script error messages
-- Correct DCS script path %USERPROFILE%\Saved Games\DCS\Scripts\IASER\ -- Example trigger code dofile(lfs.writedir() .. "Scripts\\IASER\\iaser_loader.lua")

Performance Issues / High CPU Usage

IASER using too much CPU/memory or causing DCS performance degradation.

✅ Solution Steps:
  1. Adjust IASER performance settings - reduce update frequency
  2. Use lighter executable variant (IASER_Complete_Embedded.exe)
  3. Disable debug logging in configuration
  4. Close unnecessary applications
  5. Increase virtual memory (pagefile) size
-- Performance optimization config IASER_CONFIG.performance = { update_frequency = 20, -- Reduce from 30 Hz max_processing_time = 30, -- Reduce processing time thread_pool_size = 2, -- Use fewer CPU cores optimization_level = "MEDIUM" -- Reduce from HIGH }

Strategic AI Not Responding

Strategic AI systems appear to be running but not making decisions or responding to battlefield events.

✅ Solution Steps:
  1. Check IASER console for strategic system status messages
  2. Verify mission has proper strategic elements (units, objectives)
  3. Ensure sufficient time has passed for AI analysis (30+ seconds)
  4. Check strategic AI configuration settings
  5. Enable debug logging to see AI decision process

Diagnostic Tools

IASER System Diagnostic

Run this diagnostic to check IASER system health:

# IASER Diagnostic Commands # Run in Command Prompt (Admin) echo "=== IASER System Diagnostic ===" echo "1. Checking IASER executable..." dir "C:\IASER\*.exe" echo "2. Checking port availability..." netstat -an | findstr :8080 echo "3. Checking Windows Firewall..." netsh advfirewall firewall show rule name="IASER" echo "4. Checking system resources..." systeminfo | findstr "Total Physical Memory" wmic cpu get name echo "5. Checking DCS folders..." dir "%USERPROFILE%\Saved Games\DCS" echo "Diagnostic complete"
DCS Integration Test

Test DCS-IASER connection with this simple script:

-- DCS Integration Test Script -- Place in Mission Trigger local socket = require("socket") local test_client = socket.tcp() test_client:settimeout(5) local result, err = test_client:connect("127.0.0.1", 8080) if result then env.info("✓ IASER Connection: SUCCESS") test_client:send("TEST_CONNECTION\n") local response = test_client:receive() env.info("IASER Response: " .. (response or "No response")) else env.error("✗ IASER Connection: FAILED - " .. (err or "Unknown")) end test_client:close()

Advanced Troubleshooting

Before Advanced Troubleshooting

Try basic solutions first. Advanced troubleshooting should only be attempted if basic solutions fail.

Log File Analysis

IASER generates detailed logs that can help identify issues:

Log File Locations: - IASER System Log: iaser.log (same folder as executable) - DCS Integration Log: DCS.log (in DCS Logs folder) - Windows Event Log: Windows Event Viewer → Application Logs Key Log Messages to Look For: ✓ "Strategic Warfare System Connected" ✓ "All strategic systems operational" ✗ "Connection refused" ✗ "Access denied" ✗ "Timeout waiting for response"

Registry Check (Windows)

Sometimes Windows security settings can interfere:

# Check Windows Defender exclusions Get-MpPreference | Select-Object -ExpandProperty ExclusionPath # Add IASER folder to exclusions (PowerShell as Admin) Add-MpPreference -ExclusionPath "C:\IASER"

Network Troubleshooting

# Test network connectivity ping 127.0.0.1 telnet 127.0.0.1 8080 # Check local firewall rules netsh advfirewall show allprofiles state netsh advfirewall firewall show rule name=all | findstr IASER # Reset Windows network stack (if needed) netsh winsock reset netsh int ip reset

Getting Additional Help

If you're still experiencing issues after trying these solutions:

📋 Collect Information
  • IASER version and executable used
  • Windows version and build
  • DCS World version
  • Error messages (exact text)
  • Steps that led to the issue
📄 Check Documentation
🌐 Community Support
  • GitHub Issues
  • DCS Community Forums
  • IASER Discord Server
  • Reddit Communities
Configuration Guide FAQ