Rogue Keeper on 3/12/2008 at 09:44
Well, it greatly breaks the continuity of the story and spoils enjoyment from discovering facts step by step, following some rational path. Once I released Pa, I had options to ask him about Project Purity without him mentioning it, and such. But I stopped myself there, I shall reload the pre-TL save and try to get to Rivet City first. Perhaps there is a cheat which can return active quest to previous stage...
When it comes to narrative logic, Beth seems to fail big time.
EvaUnit02 on 3/12/2008 at 10:00
Quote Posted by BR796164
Oh that's just perfect. And this thing was supposed to provide more comfort for gamers. Thank you again Microsoft for making our lives more difficult.
How is that Microsoft's fault? It's Bethesda that was inept enough to send out their gold master with a buggered file.
Rogue Keeper on 3/12/2008 at 10:08
Is this GfW Live thing really of any use to you?
Judith on 3/12/2008 at 10:15
Quote Posted by EvaUnit02
How is that Microsoft's fault? It's Bethesda that was inept enough to send out their gold master with a buggered file.
The latest live redistributable version works fine, I tried it yesterday with Gears of war, everything runs smoothly (but the version on gears dvd is buggered too :)).
EvaUnit02 on 3/12/2008 at 10:23
Quote Posted by BR796164
Is this GfW Live thing really of any use to you?
To me personally? My copy of Gears of War PC won't work without it. Neither will the PC version of GTA4 apparently.
Gryzemuis on 3/12/2008 at 13:19
Quote Posted by dethtoll
If it were a hardware issue then why don't I have trouble with other games?
As I wrote earlier:
Quote:
The fact that the machine reboots happen with some games, but not others, can be explained by the fact that some games are more intensive on the hardware. A game can use a single core, another game can use 4 cores. One game can use just a few features (and thus transitors) of your videocard, another game could use all transistors.
The same thing is true about drivers. There can be a bug in the part of the Nvidia driver that does shaders. But if your game never uses shaders, that bug is never encountered.
I don't know how much you know about PCs and operating systems. But let me explain anyway.
Modern operating systems implement something called hardware abstraction. The OS (the kernel and the drivers) run in a special mode, where they are allowed to mess with the hardware. Normal processes, like games and other applications, can only ask the OS to do stuff for them. For the rest each game or application lives inside its own "process", with its own protected memory space. These 2 seperated worlds are called "kernel space" and "user space". An application can not mess with other process. Nor with the OS. That means that an application can never bring down other application, nor the OS itself.
If a machine reboots, something went wrong in kernel space. That means that either the kernel had a bug, a driver had a bug, or the hardware did something really weird and unexpected. It is very very unlikely that a machine reboot is caused by an application.
Now in Windows of course the handling of drivers is almost a "user issue" in stead of an "admin issue". That means that users can mess around with drivers as much as they want. And this can result in situations where not all leftovers of old drivers are removed. Or where different drivers are installed that are slightly incompatible. And it's as good as impossible to figure out what is wrong.
Next time your machine crashes, try to look at the error message. The hexadecimal addresses are as good as useless to users like us. But the errors sometimes points to a dll. E.g. if the crashes always point to nv4_disp.dll it is more likely to assume there is something wrong with your videocard or its drivers.
june gloom on 3/12/2008 at 13:34
Well nothing in the error logs point to any one particular file save fallout3.exe. I looked for "Fault bucket 990002266" (one of the weirder messages in the application event log) and someone else got the exact same error. As I said before, I honestly don't believe it's a hardware issue when all signs point to the game.
Someone did suggest adding not just fallout3.exe but the launcher .exe to the ffdshow exclude list- if I get up the ability to give a shit and reinstall the game again, I'll try that. More likely I'm just going to wait for Bethsoft to come up with a real patch.
Rogue Keeper on 3/12/2008 at 14:08
Oh, so you're an optimist.
june gloom on 3/12/2008 at 14:56
Well it's either that or a proud 360 owner.
Sulphur on 3/12/2008 at 16:21
But I thought you wanted to play MGS4 at some point. You... turncoat!? :weird:
Anyway, I decided to get off my ass, stop playing Fallout, and set my ass back on the couch to finish MGS3.
MGS4 invokes pretty much all of MGS's vast and storied history, and quite a bit of the story in the middle act has to do with MGS3. I felt rather awful playing through it without knowing what happened to Big Boss, so... out with new, in with the old - MGS3 tally ho!!
(Just finished the fight with The End. That bald old bastard had it coming. :mad:)
