Space Engineers

Space Engineers

CAMP | Construction & Assembly Material Processor
Showing 1-10 of 63 entries
< 1  2  3  4  5  6  7 >
Update: 8 Jul @ 11:02pm

Update: 8 Jul @ 10:51pm

Incremented mod version

Update: 8 Jul @ 10:46pm

## Summary

Here's what changed:

### Previous Logic (Problematic)
- Only throttled when **no components were available at all**
- If you had even 1 steel plate, it would continue rapid scanning even with no targets
- This still caused performance issues when components were available but no blocks needed work

### New Logic (Fixed)
- **Always throttles when best effort welding is enabled** and no current target is found
- Uses a **30-second minimum interval** between scans when no targets are available
- **Doesn't matter if components are available** - if there are no valid targets, it throttles
- This prevents the scanning loop regardless of inventory contents

### Key Changes Made

1. **Removed component availability check** - the throttling now applies whenever best effort welding is enabled and there's no current target

2. **Renamed variables for clarity**:
- `MIN_SCAN_INTERVAL_NO_COMPONENTS` → `MIN_SCAN_INTERVAL_NO_TARGETS`
- `_lastNoComponentsScanTime` → `_lastNoTargetsScanTime`

3. **Updated comments** to reflect the new behavior

### Behavior Now
- **With components + no targets**: Throttles (30-second intervals)
- **With components + valid targets**: Scans normally
- **No components + no targets**: Throttles (30-second intervals)
- **No components + valid targets**: Scans normally (though targets won't be workable)

This should completely eliminate the sim speed drops when best effort welding is enabled, regardless of whether you have steel plates or other components in your inventories.

Update: 8 Jul @ 10:42pm

## Summary

I've successfully implemented a solution to fix the issue where two separate CAMP blocks (one in weld-only mode and another in grind-only mode) could target the same block, creating conflicts.

### The Problem
The original claiming system only tracked which CAMP block owned a claim to a specific block, but didn't consider what operation that CAMP intended to perform. This meant:

A camp trying to grind and another trying to weld could perform work on the same block causing an infinite loop.

Update: 19 Jun @ 9:21pm

Update: 19 Jun @ 1:57am

Update: 18 Jun @ 11:45pm

Update: 18 Jun @ 6:47pm

Update: 18 Jun @ 1:32pm

Update: 17 Jun @ 11:28pm