Fixes for Pathfinding + Metaverse Error 12

Test build - volunteers needed

By CariElf on November 12, 2007 12:02:42 PM from

GalCiv II Forums

CariElf

Stardock

Join Date 08/2001

+54

Edit: (original text below)

The most current version of GalCiv2 is 1.8g, which is available for download on Stardock Central. It fixes pathfinding bugs that were introduced in 1.8e, and in many cases will fix people's problems with error 12 when attempting to submit a metaverse game. As long as your serial numbers have not changed in the registry since you started the saved game, you should be able to submit it. However, the problem still remains if you have had to re-install GalCiv2 and have updated serial numbers from the lookup serial function in Stardock Central, so it's always a good idea to try and finish a metaverse game before re-installing Windows or anything else that would cause you to need to update your serial information. If that's not possible, you can get the original serial number that was saved into your save game from the xml file in My Documents\My Games\GC2DarkAvatar\Metaverse that is created when you attempt to submit the game. You should have this file and the end game save zipped and attached to any e-mails you send into support regarding metaverse error 12.

If Stardock Central is showing that you have the latest version installed but your Dark Avatar titlescreen still says 1.8e, you will need to either re-install Dark Avatar to get the latest version or edit the key in the registry.

Here are instructions on how to edit the version string in the registry:

First, close Stardock Central. Go to Start->Run and type in regedit. On Vista, type it in the search box. As soon as the registry opens, click on the My Computer icon and choose File->Export to backup the registry.

The install info for GalCiv2 is under HKEY_LOCAL_MACHINE, in the path Software\Stardock\Drengin.net\GalCiv2\DarkAvatar.

Just change the version string to 1.7 and SDC will show an update to 1.80g.

Here are instructions to make sure that you get the latest version once you've either re-installed or changed the version string in the registry:

Befiore installing the update, go to Tools->Settings and click on Internet. US-1 is usually the best choice for servers because sometimes we have sync errors with US-2. Click Refresh XML Data. Also, if you have the setting turned off to check for updates to Stardock Central, turn it back on and then re-start Stardock Central. If Stardock Central finds an update, let it update then restart SDC when prompted.

If the above method doesn't work for you, it may be a more general issue with Stardock Central and I'll need you to send in these files to support@stardock.com:
Program Files\Stardock\SDCentral\Installed\gc2_DarkAvatar.log
Program Files\Stardock\SDCentral\Installed\gc2_DarkAvatar.xml

(Original text follows:)

Hey everyone,

I'm sorry about the bug with the pathfinding. I didn't realize the code that was causing it made it into the 1.8e build, as I wasn't expecting to make that build and I had already started backporting some code from TA intended to fix the error where ships in gigantic galaxies will (1) seemingly randomly lose their destination, (2) not go to rallypoints and (3) fail to move towards a destination, but I hadn't had a chance to test it at that point.

As for the error 12 when submitting scores to the metaverse, I found a bug in the code that gets the serial number from the registry that may have been there for quite awhile. So people who weren't getting the error 12 may start getting it now with this build because now the game will be submitting the correct serial number, so they may have to change the serial that their character is using.

We're not going to have time to properly test a Dark Avatar build this week, so I'm going to put up a link to a build for you to test here, and you can test it if you want to. However, I recommend backing up your save games and your current build before trying it, since there is the risk that this will change the serial number that is being submitted to the metaverse.

To use this build, you should already have DA 1.8e installed. If you have the latest version of Dark Avatar installed from SDC, go to the folder where GalCiv2 is installed and open the DarkAvatar subfolder. Copy the GC2DarkAvatar.exe and Lib3D.dll files into another folder to back them up. Then extract this zip to that folder:

(edit: I have removed the link because the SDC build is now the latest one)

Please make bug reports regarding this build in this thread or e-mail gc2bugs@stardock.com so that it will be easier for me to find them. If you e-mail gc2bugs@stardock.com, please make sure to say in the body of the e-mail that it's the 1.8f test build, and include your debug.err file. If you have a save game to reproduce a problem, please zip the save game and attach it as well.

chazzie, no, if you're getting blank icons in Dark Avatar, that's probably unrelated. E-mail a screenshot and your debug.err to jbrindle@stardock.com and he'll check it out. You can take a screenshot by hitting CTRL+Printscreen, and it will be saved in your My Documents\My games\GC2DarkAvatar\ScreenShots folder.

Successfully updated karma reason!

Okay - If I can get it to happen again I'll send it in!

I'll try now so it will be soon if I can get it to do it again! - my experience with these sort of things is that it won't happen now no matter what I do!!

You're all doing a great job here - considering that your all working on TA as well!

just don't forget that sleeping is also good!

Successfully updated karma reason!

[Begin heated rant>>}

Dark avatar 1.8f/g is so crashy I have no idea what in the world is wrong(no driver changes or anything... I should've stayed with 1.

!!), but every DA (not TOA weirdly) game I play it will without fail crash when I select a planet, or after an invasion. Its never the 1st one, bu at some point it happens and it is so damn frustrating I give up and think of uninstalling. Why is DA STILL broken a month after 1.8e broke it? I understand all the resources put into TOA (which i have) bu you cannot leave a product broken for that long, no matter what the case. Yes I can play ToTA beta... and even though its a beta its more stable than this current incantation of DA.

Please Fix DA, 1 month of excuses, waiting, "testing". I am sorry to be harsh, but it seems all SD is workin on is TOTA, and it even got an extension to January...make sure DA is fixed back to the point where i worked well.... What was the problem with 1.8 c/d anyways.

rant over, but still my basic point stands.
(yes I a using DA 1.8g, unfortunately... where is 1.

....)

Successfully updated karma reason!

Yeah, well I'm waiting for the official update. Not some zip file that I have to find the correct directory to unzip it into. I'm in the MV League and I don't what to introduce new errors in a half completed game. A game that I don't even know if I'll be able to post due to this Metaverse Error 12.

So yeah, I'm not a happy camper either, and I think 1 month should be long enough to fix this.

Successfully updated karma reason!

Attention please Cari.

My error 12 issue.

Updated from 1.

through E to the G build in this thread. After having the game run buggy for some time it was a welcome change for it to run so well. Thankyou.

But...Error 12 has appeared. I cannot submit to the MV.

I emailed support hoping to get this fixed but the only information they gave me was to re-register the game with the serials from my jewel case's.

I did this and still nothing plus i tried to register the serials from the SDC email (yes i get two different serials for DA and TA) and that has not worked either.

I am hoping that by pleading to you here that you may have a fix for me or a few minutes of your precious time to spare to help me out. (flowers and choccies are on the way..thanks in advance

)

I can of course send you anything you need, endgamesaves, original serials, sdc serials...whatever....

Help me Carielf Kenobi...you are my only hope! (here's hoping your a Star Wars fan!)

Edit - Has anyone had this fixed succsesfully? If so, what did ya do?

Successfully updated karma reason!

Well...I will at least give you some good feedback on 1.80g LOL. Had updated to 1.80e through SDC, and having dealt with the fleet movement bug (thank goodness this round of the MVL called for a Tiny Map haha) came looking for answers and found this thread. By that time you had already updated your link to 1.80g. I've played a few games now, no fleet issues, no Error 12 (which i've never received before either), and no strange crashes, and thats even with me having Vista and NVidia hahaha. Maybe I'm one of the lucky ones. In any case thanks for taking the time to even attempt to fix these issues, we all know that you are busy.

Successfully updated karma reason!

OK. I'll give 1.80g a try. (closes eyes and pulls trigger)

Successfully updated karma reason!

neilo, I need you to e-mail in your save game that you can't submit, plus the corresponding xml file from your My Documents\My Games\GC2DarkAvatar\Metaverse folder. Make sure that you zip the save game so that it doesn't get stripped. I've told support to assign tickets about error 12 to me.

As for those of you calling for another public update, I don't want to put up another build before it's ready. I have been having trouble tracking down the memory leaks that people are having. I've put up another test build that fixes a bug where a ship on auto-attack or an AI ship would keep trying to attack a mini-freighter under a planet but never reach it because planets come first in hit detection. I've also added some code that may help with the memory problems.

Successfully updated karma reason!

Cari, sent email to you. Thanks for looking into this.

Successfully updated karma reason!

OK. I'll give 1.80g a try. (closes eyes and pulls trigger)

BANG! Thud...

Metaverse Error 12. I've got the same problem as neilo.

I installed the patch though, and it got rid of the pathfinding problem, just not the Metaverse Error 12.

Successfully updated karma reason!

I noticed a new version available: 1.80g

I have been using 1.80f. I haven't had many problems with it.
I can play a huge universe and don't have it slowing down like
earlier versions. I still use 1.60 to generate universes. I think
it gives more habitable 10+ planets. Though I haven't checked the
latest versions.

What's new or fixed in the new 1.80g?

Successfully updated karma reason!

This is part of what is included in 1.80g, or at the very least its Cari's most recent mention of her updating the link build. It is the version I am using and I have not encountered any issues or bugs so far, but each computer is unique so no promises. You should always make sure to back up your files before altering programs.

Successfully updated karma reason!

That fix you sent me Cari, did not work. It was not a massive scoring game, only 30K so i am not too worried but if you ever find a way to fix it i will surely be interested. As long as my games from now on post i will be a happy camper.

Thanks for time and effort, i think Frogboy should give you a raise!!!

Brycej, Everything is fine in the the new build, no pathfinder or fleet bugs at all. The only thing is you might find yourself with the MV submition Error 12 issue. But if i am correct it is only on older save games started under a different build, though i am not certain of that.

Bar for my game that won't submit, this G build is perhaps the best DA has ever ran for me.

Successfully updated karma reason!

Several times in 1.8g I ran into a bug where the ai signs peace treaties with you without asking you first. I was at war with the Drengin when suddenly I get a message "Drengin Empire has signed a peace treaty with Terran Alliance(me)"
Other than that 1.8g works very well.

Successfully updated karma reason!

I've noticed the treaty problem too. I decided I would just uninstall the entire game and reinstall it. (get back to the good ol' days)

I love the game and the new features in the updates are awsome, but I just wanted to get away from what has become very frustrating and tedious.
I hope it resolves soon.

Successfully updated karma reason!

That's happened to me, but it seemed to always happen at the same time they signed a treaty with an ally. Like the ally had gotten "Make peace with..." out of the deal?

Successfully updated karma reason!

Cari - is there any chance of this build to be made final on SDC? Or is there still issues that need to be fixed?

My reason for asking is that I've just started the DA campaign and in the current state I can't play it, and I'm not brave enough to risk using beta patches.

I realise with all of the work going into TA that this is alot to ask but I did not want to start a TA game without finishing DA first!

Successfully updated karma reason!

I'm going to try and get one up this week. It may not fix the memory errors that people have been getting, but it should take care of the pathfinding bugs and the error 12s, although I recommend that people submit any metaverse games they want to submit before updating just in case.

Successfully updated karma reason!

what about the bug with the enemies signing peace treaties with you without your consent?

Successfully updated karma reason!

what about the bug with the enemies signing peace treaties with you without your consent?

Nope, sorry, I haven't addressed that.

Successfully updated karma reason!

I know this thread is a bit old, but I think my problem applies to it. Those pathfinding issues mentioned earlier on in the thread are still present in 1.8g, at least in my case. I am running the updated version, but I keep getting this problem with my fleets anyways.

I try to move them, but anything more than 2 p/secs outside their maximum moves in a single turn results in something like "4/0 moves left". If I disband the fleet, they move fine. The second any two ships are together though, this problem rears it's ugly head. It makes conducting a war very, very micromanagement intense, with about seven or eight fleets moving around, all of which I have to move manually every turn. Anybody else still have this problem around?

PS: Is this the right place for this?

Successfully updated karma reason!

Check to make sure that the titlescreen says 1.8g as we've had some reports of Stardock Central failing to update correctly to 1.8g.

Successfully updated karma reason!

Yes i would say this is the right place for your problem mate. I have been running the latest g build for some time now and i have had no issues. Are you playing an older saved game, AFAIK that can still have those lingering affects. Your best bet is to zip up a debugg file and your save game and email them into gc2bugs@stardock.net.

Hope you get it sorted mate.

Successfully updated karma reason!

gc2bugs@stardock.com, but first check to make sure that it actually updated to 1.8g

Successfully updated karma reason!

Ahhh sorry Cari...sometimes i forget which is which...

Successfully updated karma reason!