Author Topic: Official v7.00 Bugs Reporting Thread  (Read 43815 times)

0 Members and 1 Guest are viewing this topic.

Offline sloanjh

  • Global Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 2805
  • Thanked: 112 times
  • 2020 Supporter 2020 Supporter : Donate for 2020
    2021 Supporter 2021 Supporter : Donate for 2021
Re: Official v7.00 Bugs Reporting Thread
« Reply #60 on: December 10, 2015, 07:56:40 PM »
Well, I don't know what I did. All I did that I do know is close Aurora from the main bar without closing all the other windows. Now I get the following 380 error then the 3201 (infinitely) whenever I try to open Aurora, I cant even play anymore :'(. I'll try to retry it after a computer restart, but if that doesn't work I may have to uninstall then reinstall. Sadly, no, the restart didn't work. However this time I got a dialogue to see Aurora_Wrapper.log in the C drive, so I'll take a look at what that has for me.

My guess is that you got unlucky and corrupted your database.  Try replacing it with a backup copy and restart....

John
 

Offline Zincat

  • Captain
  • **********
  • Z
  • Posts: 566
  • Thanked: 111 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #61 on: December 11, 2015, 01:26:14 AM »
Well, I don't know what I did. All I did that I do know is close Aurora from the main bar without closing all the other windows. Now I get the following 380 error then the 3201 (infinitely) whenever I try to open Aurora, I cant even play anymore :'(. I'll try to retry it after a computer restart, but if that doesn't work I may have to uninstall then reinstall. Sadly, no, the restart didn't work. However this time I got a dialogue to see Aurora_Wrapper.log in the C drive, so I'll take a look at what that has for me.

That happened to me. And I was curious so I tried around until I found out what causes that. Here are the stps to reproduce the bug.

Using the provided clean database here, so no idea if that happens with the other database as well. I activated in the main game launch window the option "NPRs activate other NPRs" Then saved the options. Started the game, quit, restarted. And then that problem happens. Solution for me was to delete and re-extract the database. No idea if there is a non destructive option.

Did you recently change that option too?
« Last Edit: December 11, 2015, 01:36:45 AM by Zincat »
 

Offline MarcAFK

  • Vice Admiral
  • **********
  • Posts: 2005
  • Thanked: 134 times
  • ...it's so simple an idiot could have devised it..
Re: Official v7.00 Bugs Reporting Thread
« Reply #62 on: December 11, 2015, 01:31:47 AM »
Automatic detection seems to be broken, every new game I've started fails as soon as I set it to auto.
" Why is this godforsaken hellhole worth dying for? "
". . .  We know nothing about them, their language, their history or what they look like.  But we can assume this.  They stand for everything we don't stand for.  Also they told me you guys look like dorks. "
"Stop exploding, you cowards.  "
 

Offline 83athom

  • Big Ship Commander
  • Vice Admiral
  • **********
  • Posts: 1261
  • Thanked: 86 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #63 on: December 11, 2015, 09:36:47 AM »
I activated in the main game launch window the option "NPRs activate other NPRs" Then saved the options. Started the game, quit, restarted. And then that problem happens.

Did you recently change that option too?
Yes I did actually. Now I'm scared cause I did it again after my reinstall (didn't see your post), but I have yet to close the game for fear of that happening again, so now I never want to close it until a hotfix fixes it.
Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life.
 

Offline GreatTuna

  • Lt. Commander
  • ********
  • Posts: 203
  • Thanked: 1 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #64 on: December 12, 2015, 07:20:27 AM »
I don't even know what happened. I was just adding modules (engineering spaces to be exact) to the ship, when this happened.
Version is 7.00.

Error screenshot attached with the class design window just in case it's my fault.
It followed with errors in UpdateGameLog (with same id) continuing infinitely until terminated process.
 

Offline Ostia

  • Warrant Officer, Class 1
  • *****
  • O
  • Posts: 98
  • Thanked: 2 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #65 on: December 12, 2015, 07:59:17 AM »
Dump Question: You did update BOTH the executable AND the database?
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11675
  • Thanked: 20470 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #66 on: December 12, 2015, 08:03:31 AM »
Sorry for the delay in answering on this thread. Work is a little mad at the moment so I will get to it in the next few days. Sounds like you should avoid using auto-detect for the moment and I suggest any major campaigns wait for v7.1.
 

Offline GreatTuna

  • Lt. Commander
  • ********
  • Posts: 203
  • Thanked: 1 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #67 on: December 12, 2015, 08:37:09 AM »
Of course I did. I doubt the game would run at all if I didn't.
That aside, I think I know where the problem lies.
After going to Aurora folder to check the database, I found that the database became 2GB big!
 

Offline db48x

  • Commodore
  • **********
  • d
  • Posts: 641
  • Thanked: 200 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #68 on: December 13, 2015, 12:51:38 AM »
I've seen this a few times.  It goes into an infinite loop, and after I kill it I see all of my officers getting reassigned.

Error in CreateGameLog
Error 76 was generated by Aurora
Path not found
 

Offline Garfunkel

  • Registered
  • Admiral of the Fleet
  • ***********
  • Posts: 2796
  • Thanked: 1054 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #69 on: December 13, 2015, 09:44:04 AM »
I've seen this a few times.  It goes into an infinite loop, and after I kill it I see all of my officers getting reassigned.

Error in CreateGameLog
Error 76 was generated by Aurora
Path not found
Manually create a C:\Logs directory/folder for Aurora to use.
 

Offline db48x

  • Commodore
  • **********
  • d
  • Posts: 641
  • Thanked: 200 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #70 on: December 15, 2015, 04:11:40 AM »
Ah, interesting.  The portable wrapper script is creating a link (junction) pointing to a Logs directory in my installation folder, which is missing.  Thanks!

Here's another "bug" though; I have an administrator named "Adele Desjardins (surname)".  Probably the "(surname)" bit should be removed from the name list.  :)

 

Offline alvin853

  • Petty Officer
  • **
  • a
  • Posts: 24
  • Thanked: 7 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #71 on: December 15, 2015, 01:04:05 PM »
So one of the civilian ships on the left just rammed into one of the hostile ships on the right. . .  Didn't know my ships were 200m km big
 

Offline Erik L

  • Administrator
  • Admiral of the Fleet
  • *****
  • Posts: 5657
  • Thanked: 372 times
  • Forum Admin
  • Discord Username: icehawke
  • 2020 Supporter 2020 Supporter : Donate for 2020
    2022 Supporter 2022 Supporter : Donate for 2022
    Gold Supporter Gold Supporter : Support the forums with a Gold subscription
    2021 Supporter 2021 Supporter : Donate for 2021
Re: Official v7.00 Bugs Reporting Thread
« Reply #72 on: December 15, 2015, 03:45:31 PM »
Reactor design option in tech window. There are two entries for size 1.
 

Offline Mastik

  • Lieutenant
  • *******
  • M
  • Posts: 178
  • Thanked: 4 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #73 on: December 15, 2015, 08:26:40 PM »
Error in RecoverSurvivors
Error 3421 generated by DAO.Field
Data Type conversion error
 

Offline Mastik

  • Lieutenant
  • *******
  • M
  • Posts: 178
  • Thanked: 4 times
Re: Official v7.00 Bugs Reporting Thread
« Reply #74 on: December 15, 2015, 08:59:16 PM »
Not sure if this is a bug, but combat ships ramming commercial shipping doesnt seem like a good strategy.