Author Topic: v1.70 Bugs Thread  (Read 10719 times)

0 Members and 1 Guest are viewing this topic.

Offline smoelf

  • Commander
  • *********
  • Posts: 337
  • Thanked: 142 times
  • 2021 Supporter 2021 Supporter : Donate for 2021
Re: v1.70 Bugs Thread
« Reply #15 on: April 19, 2020, 02:33:26 PM »
The 'Exclude High Grav' button in the mineral search window excludes everything other than high-gravity planetary bodies.
 

Offline knife644

  • Leading Rate
  • *
  • Posts: 7
  • Thanked: 1 times
Re: v1.70 Bugs Thread
« Reply #16 on: April 19, 2020, 02:39:34 PM »
Thanks for hard work steve :)
 

Offline DFNewb

  • Captain
  • **********
  • D
  • Posts: 508
  • Thanked: 103 times
Re: v1.70 Bugs Thread
« Reply #17 on: April 19, 2020, 02:40:28 PM »
I am unable to create colonies in 1.70. I tried clean install, update from 1.6.3. and even from 1.0. But nothing helps. I click the button and colony is not created. Anyone encountered this?

Yes same issue, tried every-way I can, can't even unload colonists on planets anymore.

Major bug.
 

Offline Speagott90

  • Able Ordinary Rate
  • S
  • Posts: 2
Re: v1.70 Bugs Thread
« Reply #18 on: April 19, 2020, 02:42:10 PM »
Quote from: Black link=topic=10934. msg125850#msg125850 date=1587324694
I am unable to create colonies in 1. 70.  I tried clean install, update from 1. 6. 3.  and even from 1. 0.  But nothing helps.  I click the button and colony is not created.  Anyone encountered this?

I am having this problem as well.
1. 7 updated from 1. 6. 3 (deleted exe and db before copying)
Conventional start, trying to create colony on Mars from the system window, nothing happens.
 

Offline Ektor

  • Lieutenant
  • *******
  • E
  • Posts: 191
  • Thanked: 103 times
Re: v1.70 Bugs Thread
« Reply #19 on: April 19, 2020, 02:42:13 PM »
Besides being unable to create colonies, it seems the windows I open aren't appearing. I can see them on the taskbar but they don't appear.
 
The following users thanked this post: SpikeTheHobbitMage, Bubbaisagod

Offline Inglonias

  • Lieutenant
  • *******
  • I
  • Posts: 170
  • Thanked: 69 times
Re: v1.70 Bugs Thread
« Reply #20 on: April 19, 2020, 02:42:28 PM »
I am unable to create colonies in 1.70. I tried clean install, update from 1.6.3. and even from 1.0. But nothing helps. I click the button and colony is not created. Anyone encountered this?
Confirmed. This is a gamebreaker.
 

Offline GodEmperor

  • Commander
  • *********
  • Posts: 312
  • Thanked: 30 times
Re: v1.70 Bugs Thread
« Reply #21 on: April 19, 2020, 02:43:11 PM »
I am unable to create colonies in 1.70. I tried clean install, update from 1.6.3. and even from 1.0. But nothing helps. I click the button and colony is not created. Anyone encountered this?

Yes same issue, tried every-way I can, can't even unload colonists on planets anymore.

Major bug.
That makes three of us.
."I am Colonel-Commissar Ibram Gaunt. I am known as a fair man, unless I am pushed.
You have just pushed me."
 

Offline Demonius

  • Warrant Officer, Class 1
  • *****
  • Posts: 83
  • Thanked: 25 times
Re: v1.70 Bugs Thread
« Reply #22 on: April 19, 2020, 02:46:21 PM »
confirmed game breaker
 

Offline Pedroig

  • Lt. Commander
  • ********
  • P
  • Posts: 240
  • Thanked: 67 times
Re: v1.70 Bugs Thread
« Reply #23 on: April 19, 2020, 02:46:57 PM »
Tried in SM mode as well.  New game, and also original game db....

Will await 1.71 tomorrow.  ;)
si vis pacem, para bellum
 

Offline Randy

  • Sub-Lieutenant
  • ******
  • Posts: 146
  • Thanked: 1 times
Re: v1.70 Bugs Thread
« Reply #24 on: April 19, 2020, 02:59:53 PM »
It also appears to consume major system resources while running. As in mouse pauses/becomes unresponsive even when not processing a turn...
 

Offline Ancalagon

  • Lieutenant
  • *******
  • A
  • Posts: 187
  • Thanked: 41 times
Re: v1.70 Bugs Thread
« Reply #25 on: April 19, 2020, 03:01:08 PM »
I also can't create any colonies on v1.7.  Makes for a very peaceful gameplay experience.  :)

Also, unrelated bug: the industrial screen on v1.7 opens up on my second monitor for some reason the very first time I open it. That never happened on other versions of C#. That might be bad for people who don't have two monitors.
 

Offline Iceranger

  • Registered
  • Commander
  • *********
  • I
  • Posts: 391
  • Thanked: 230 times
Re: v1.70 Bugs Thread
« Reply #26 on: April 19, 2020, 03:05:52 PM »
I think the missile design text is editable so you can copy and paste it out...

Yes, that is correct. Changing it does nothing.

There is probably a property somewhere that allows copy but not edit. Something like TextBox.ReadOnly = true should fix it?
 

Offline freddy72nz

  • Able Ordinary Rate
  • f
  • Posts: 1
Re: v1.70 Bugs Thread
« Reply #27 on: April 19, 2020, 03:07:05 PM »
Hi there,

I am running Linux Mint and when I run Aurora. exe I get the following error messages one after the other:

Function #2490: cannot call this method if SelectionMode is SelectionMonde. None
Function #2492: cannot call this method if SelectionMode is SelectionMonde. None
Function #2493: cannot call this method if SelectionMode is SelectionMonde. None

Then it loads into the map screen and everything seems to work from there.  Not sure what it's missing but I am a complete neophyte at this amazing game :)

Thanks!
 

Offline HeroicHan

  • Petty Officer
  • **
  • H
  • Posts: 26
  • Thanked: 2 times
Re: v1.70 Bugs Thread
« Reply #28 on: April 19, 2020, 03:07:18 PM »
System connection/numbering is super weird in this version.
Started a new game, 1. 7.
Random Stars, 100 star limit, 50/15 for local.

I wanted to 'map' a galaxy by space master exploring all the jump points.
Firstly, I could go over 100 systems.  I stopped at 101, but definitely could have gone more. 
Secondly, only one exploration led back to another system, which was sol (and had an unexplored point).
Third, I noticed in a previous version that if your system theme runs out of names, it will start labeling them "System #x" where x is presumably the internal system id.  (which isn't available to display easily anymore)
In 1. 7, this results in "System #0" every time except one, which was for some reason "System #-3"
I know Sol is canonically id'd as system 0, so I'm guessing that this is tied to the fixes for the other Sol related jump point connection issues.
 

Offline Froggiest1982

  • Gold Supporter
  • Vice Admiral
  • *****
  • F
  • Posts: 1334
  • Thanked: 592 times
  • Gold Supporter Gold Supporter : Support the forums with a Gold subscription
    2021 Supporter 2021 Supporter : Donate for 2021
    2022 Supporter 2022 Supporter : Donate for 2022
    2023 Supporter 2023 Supporter : Donate for 2023
Re: v1.70 Bugs Thread
« Reply #29 on: April 19, 2020, 03:17:12 PM »
System connection/numbering is super weird in this version.
Started a new game, 1. 7.
Random Stars, 100 star limit, 50/15 for local.

I wanted to 'map' a galaxy by space master exploring all the jump points.
Firstly, I could go over 100 systems.  I stopped at 101, but definitely could have gone more. 
Secondly, only one exploration led back to another system, which was sol (and had an unexplored point).
Third, I noticed in a previous version that if your system theme runs out of names, it will start labeling them "System #x" where x is presumably the internal system id.  (which isn't available to display easily anymore)
In 1. 7, this results in "System #0" every time except one, which was for some reason "System #-3"
I know Sol is canonically id'd as system 0, so I'm guessing that this is tied to the fixes for the other Sol related jump point connection issues.

100 Stars limit is not exact limit. This tells Aurora when to start generating new Systems but all the systems already generated before reaching that number do have already their JP generated prior the reach of the cap. It is quite normal to have more than 100 systems. What is intended with 100 system limit is to do not reach 200 or even 250 for instance. This was also for VB6 Aurora. It can happen to have dormient JP and I think it's same for C#, I believe I've asked once during development and Steve confirmed. The last part I don't know, maybe a bug.