Please note that it's generally best to start a clean game when a new build becomes available as changes to the code may adversely affect your save games.
Here are some guidelines that should help us deal with bug reports and suggestions:
1) Do not e-mail either bug reports or suggestions for GC2 to support@stardock.com. Make reports here in the forum, and if you have files that you need to send in, send them to gc2bugs@stardock.net. Sending gc2 stuff to support just creates more work for support and it takes longer to get to the dev team who are the ones who need it.
2) Please be as detailed as possible when making bug reports. Tell what you were doing when the bug occurred, who you were playing as, the in game date, whatever. If it's something that can be reproduced with a save game, we're going to want that. Screenshots are often useful particularly if the bug is graphical in nature. We will also almost always want your debug.err file.
3) Install SmartException from https://www.stardock.com/products/smartexception. For those of you who have had installed since the GC1 beta, there is a new version available that has a few improvements, so you'll want to uninstall the old one and install this new one. This program creates log files when GC2 crashes, and we'll always ask if you have a SE report if you report a crash.
4) Do not report different bugs under someone else's post. Make your own. If you reply to someone else's bug report, it should be to offer suggestions or to add your own experience with the bug. So if someone makes a post that says "I researched trans-galactic communications and now all my ships are moving backwards," and your ships are moving backwards, you can post "my ships are moving backwards, too, but I think it started when I researched warp drive." What I don't want to see in that thread is another report that says "my ships are all green. wth?" So please try to be relevant.
5) Please don't put suggestions in the same posts as bug reports unless it's related to the problem you're reporting.
6) If you get string not found errors, e-mail the debug.err file to gc2bugs@stardock.com as the debug.err file will contain information on which string the game couldn't find.
Ok, these are all the things that I can think of for right now. I'll put some thought into how to make an in game bug report mechanism but I can't promise anything since implementing it will take away time from implementing other stuff.