Arcathia. I've used this for City/Star/County names for a few decades now.
SpykeAlpha
Unrest on any size map shouldn't be a problem if handled correctly. One of the Fortress upgrades (I think it's a Level 5 choice) is the option to lower unrest by 30% across your entire kingdom. That translates to 30 points of unrest negated in every city you have. Period. So your 48% unrest would be down to 18% unrest. With a second Fortress city set up this way you'll have 60 points of unrest negated. I'm playing on the 2nd largest map
Looking at some of the threads out there based on that text string, I'd say it was the BIOS toggle, tbh. Microsoft lists your soundcard being disabled in BIOS as one of the main reasons for that error. So if for some reason the system thought it was disabled at the BIOS level... Seeing as how the drivers had been updated fairly recently, that was the only thing that I did that I think made any difference.
They are. I went and fiddled around with a few things (updated the realtek drivers, toggle the sound card off in BIOS then back on, etc). Something in all of that seemed to get it out of that state and just to "muted" normally. Now the sound is coming across fine. This is quite awesome.
One thing I've already noticed that makes this not very useful for me is that you have to have speakers (or headphones) plugged into the PC that you want to stream music from. I was hoping that you could use this on a PC without speakers to stream the music to a primary PC (since I use Input Director to control multiple PC's from one). Problem is, the secondary PC's don't have speakers... so Windows has the sound on mute because "N
To add to this. All of the PC's are physically connected via network cable. They all run into the same local switch as well.
My Primary is running XP. The right hand secondary is Vista. The left hand secondary that is having this problem is XP. All three are running the version that was on Impulse as of last night... so... 1.21.017. The message I see is as follows. [machine name] is where the name of my secondary PC is normally: [B]Connection to [machine name] lost[/B] Your connection to [machine name] has been lost due to a network error. Multiplicity will try to connect in the
I'm running into the same problem. I upgraded to the recent version that's on Impulse and am fine as far as connecting to the initial secondary PC on the right that I use. But I just recently set up a new PC to connect to on the left. It connects fine via the systray but as soon as I move my mouse over to that screen it throws up an error message saying that it has lost a connection to that machine. As soon as I move the cursor back over into the primary monitor Multiplicity immediat
As to the previous poster (Reply #17) I am able to get control back, as well. It's more of an issue of a) it happening to begin with (especially with Stardock's own programs) and b) most of the time when it happens it causes my Vista primary to loose the ability to move anything outside of windows. A I said above it'll lock down my ability to move icons on my desktop, or to drag and drop and icon from one window to another (luckily I can see right click cut/copy/paste if needed) until
I can replicate this with Stardock Central and TweakVista as well. Which is weird since they are both Stardock applications so you figure they'd play along with Multiplicity. An added annoyance for me is that once I get any application that causes this "lost mouse" functionality it also (about 80%) of the time makes it so that I loose the ability to move any icon/file on my Vista box (which is the primary PC). I have to reboot my machine if I want to move around any of my icons or mov
@hjf288 - If you're running your RAM at 1066 or higher (even if they aren't overclocked), try dropping it down to 800 and see what happens. It looks like a lot of the issues could be related to fast(er) RAM. In some cases it turns out to be bad RAM, but in my case by severely under-clocking my RAM I haven't had any issues yet (in the little testing I've done... I'll know more tonight/this weekend). Basically, it looks like there's some sort of issue between how the TDR (read:
Found some information for people that might be having the same issues. Here's some information from Nvidia from their forums on the subject: Link: NVIDIA Statement on Vista TDR Errors Seems like it is all based on an interaction between the drivers and the application. Also, here's some information from Microsoft on the specifics of the driver resetting: Link: <a href="http://www.micros
Roger that. I'll be emailing you my dxdiag in a couple of minutes. To list everything I've tried so far in Vista Ultimate 32-bit: Nvidia Driver 158.24 (current release), 162.22 (Beta), 163.11 (Beta) No compatibility mode selected, XP SP2 Compatibility Mode Aero enabled, Aero disabled 1650x1080, 1280x1024, Windowed Mode No AA, 4x AA (selected from within game) No external apps running except for Multiplicity, Windows Defender, Anti-Virus, G15 Keyboard LCD m
Tried it in windowed mode with Aero disabled and Aero enabled. No dice either way. At least I'm able to get some auto-saves in so my game is SLOWLY progressing. I'm running out of ideas on things to try.
Last thing to try today. I tried running the game in XP compatibility mode just to see if that'd make a difference. No dice. Will try it in various resolutions later. Taking a break for now.
Btw, if anyone from Ironclad or Stardock are reading this, I'll be more then happy to run some sort of debug client that has extra logging to try and help you with this. I'm sure it's not directly "just an issue with Sins" but some combination of Sins and the Nvidia driver, and I'd love to do anything I can to help.
I don't often feel stupid. Or silly. Meh. It was an honest mistake.
Actually I never mentioned which games I had tried, that was someone else. But you do bring up a valid point about Sins could be calling something "different" then the others. For me Company of Heroes (especially in DX10 mode) and Supreme Commander are the two benchmarks I use for taxing a system. SupComm has a great built in benchmark tool that will cause almost any machine to come to
For S&G's I just tried it after unloading Multiplicity. The game barely had time to load up my save game (fairly late in this game so a lot of stuff to load) before it tripped the Vista video driver reset. This is frustrating.
You sure you dont got any programs running in the background that could interfere with the game? Again, why would Sins be the only game having issues when I've run other games/programs that are much more graphically complex/intensive on both my CPU and GPU hardware? If there is a program running in the background, it's only interfering with this game. But with that said, due to this issue with Sins I do
Well if it is a setting that I flipped, it's only being impacted by Sins, and no other game that I've played since getting this box (which is why I think it's something with Sins specifically, but I don't know what). But I haven't tweaked any settings in the Nvidia drivers. They are all still set at default settings based on whatever was installed originally. So basically it's set to "let all the programs figure everything out". I wonder if it's the difference between Vista 3
I've got the same thing going on in Beta 2 running Nvidia drivers with my 8800. I'll try running the game at a non-widescreen resolution to see if that helps. But I'm in a similar boat where I'm able to run pretty much everything else at my screen's native resolution without any problems at all. I've even run 3DMark '06 for ~18 hours without any sort of reset, lock, or crash. But playing Sins has it randomly trigger Vista's "your video driver has been reset" from anywhere f