Grid Sage Forums

Grid Sage Forums

  • May 14, 2024, 09:21:42 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

LINKS: Website | Steam | Wiki

Author Topic: crash when i set spotters to explore  (Read 963 times)

Enno

  • Derelict
  • **
  • Weekly Seed Participant Supported Cogmind Alpha Access 2015-2017 (Prime Tier)
  • Posts: 69
    • View Profile
crash when i set spotters to explore
« on: January 02, 2016, 04:22:18 PM »

first time since i play cogmind under linux that it completly crashed.
was in the recycling and found a programmer as a friend who assimilate
me two spotters. back on the main floor in -6 i just play around with
my little army, try some orders and so on...crash. again..crash...wtf.
now i know...the game don't like it when i set the spotters to explore.
i really don't need these spotters but my game crashed a few times
and i just want you to let you know that.

sad to say that i can't test that under windows at the moment...
but i can send u all the files .
Logged

Kyzrati

  • Administrator
  • True Cogmind
  • *****
  • Posts: 4324
    • View Profile
    • Cogmind
Re: crash when i set spotters to explore
« Reply #1 on: January 02, 2016, 05:32:39 PM »

It's not a Linux thing--there was a problem with the Spotter AI that was added in Alpha 5.

It was reported a couple weeks ago and already fixed for the next release (Alpha 6).
Logged
Josh Ge, Developer - Dev Blog | @GridSageGames | Patreon

Enno

  • Derelict
  • **
  • Weekly Seed Participant Supported Cogmind Alpha Access 2015-2017 (Prime Tier)
  • Posts: 69
    • View Profile
Re: crash when i set spotters to explore
« Reply #2 on: January 02, 2016, 05:47:54 PM »

ooops  ::) ... didn't noticed yet but good to know about a fix.
Logged

Kyzrati

  • Administrator
  • True Cogmind
  • *****
  • Posts: 4324
    • View Profile
    • Cogmind
Re: crash when i set spotters to explore
« Reply #3 on: January 02, 2016, 05:52:32 PM »

Yep, thanks for letting me know, though it's a good idea (especially when it's been a little while since the last release) to first quickly scan the Confirmed Bugs board to see if what you've found has already been reported :). There aren't a whole lot of bugs with each new build, and they're often found within the first week of release. Too bad this one in particular was discovered shortly after 5c was out, otherwise it wouldn't still be out there in the wild!
Logged
Josh Ge, Developer - Dev Blog | @GridSageGames | Patreon