I think it is something to do with the rifle & pistol powder items in the inventory as when you purchase all the powder items 4 of each in this case, then it will crash, purchasing just 1 of the powders the other 3 disappear from the inventory.

I have had a problem a couple of times with AI's being stuck in one position & being unable to kill them, this has only happened with legion troops up to now, but the companions waste a lot of ammo before your able to get them out of range,
new vegas has updated but the problem still exsists.
I habe also seen a few card decks around but would be unable to pick them up, even if I wanted to.

I'm not sure what you mean by the first one. Creatures/NPCs do sometimes glitch through the landscape and can't be hit and companions will fire on them regardless. Don't expect that to be fixed, the issue has been around since Oblivion was released.

Card decks can't be picked up at all. They aren't something you are meant to interact with.

Don't Listen to the excuses for lack of quality control. Even if you are not suffering from CTD's and Freezes ( Like Me ) It does not take long (In Game) to start noticing or being affected by the many in game bugs ( Even after 3 patches ) some of which are still quest breakers. Add to this the initial state that the game was released in - and what you have is a candy coated turd.

In Retrospect, I never had this quanity of issues/bugs in Oblivion or Fallout 3.

We the consumer, put money in the deveoplers/distributers pockets - Hold them responsible. I for one, did not pay to test a late Beta Version.

Care to specify what's this "DLC Glitch"?
As far as I know no DLC has yet been released for FONV.

There has been - the pre-order DLC though it has been demonstrated that the error is completely unrelated. The name given to this bug among Xbox360 users is somewhat of a misnomer due to an unhelpful error message.

Xbox users received an error message upon trying to load a corrupted savegame that would incorrectly inform the player that it could no proceed because DLC required by the save game was missing. The glitch had nothing to do with DLC but it was the error message xbox users would receive upon encountering the same save game corruption some PC users experienced at Vault 3 and REPCONN.

I have had a problem a couple of times with AI's being stuck in one position & being unable to kill them, this has only happened with legion troops up to now, but the companions waste a lot of ammo before your able to get them out of range,
new vegas has updated but the problem still exsists.
I habe also seen a few card decks around but would be unable to pick them up, even if I wanted to.

Was that a double post with a six and a half hour gap?

Crashing after killing monsters? Are you kidding me? This bug is STILL in this engine? Holy crap, what the hell.

I have read the rest of your posts on the crashing and I will say I have had my share of unfortunate crashes (JACKPOT LOST) but as for killing things and then having the game crash I fixed this issue in the weirdest way POSSIBLE with Fallout 3. I put my audio device into 7.1 Surround mode. Never tested this with 5.1 but after setting my Realtek HD Speaker Config to 7.1 and then unchecking the optional speakers I fixed my issue in Fallout 3. What makes this better? If you use headsets this causes the computer to relay surround sound to your headsets... okay I need to test this with stereo. I maybe under placebo.

Yeah so if you use Realtek as your audio chipset set it to 7.1 Surround and then uncheck the optional speakers. If you use anything else? I have never tested this with my Creative Audigy SE Soundcard. The things old and unsupported anyways and the only support I would get is from a very faithful Creative sound card user who releases unofficial patches and the such.

Just popping in to do my daily check. No patch yet? Well I'll check back tomorrow.

Sure would be nice if they cared as much about the quality of their product as they do the number of units shipped. My "Cowboy" has been shut down by this stupid weapon reload bug in the latest patch. No point in playing until it's proper again.

Bethesda know that people will buy the Fallout games, no matter how buggy. I personally haven't had anywhere near the trouble I've been reading about on the forums, apart from about four CTD an hour up until the first patch was releasedm now I don't have any problems with the game except for the occasional mod-f@ckup. That is, until I started using Cowboy Repeater, Trail Carbine etc etc. Now I'm mad.

I think if Bethesda are going to push out buggy games far too fast, they should be pushing out the patches even faster, and actually fix the things that matter. I'd way rather have my Trail Carbine working properly than be able to see where my companions are on the map.

I agree there as if I'm going to pick up a new companion I'll go back to the lucky 38 & leave them there, then go & pick up the new one. So caopanion tracking is petty usless to me,

Why do you keep empty quoting posts and then adding additional posts afterward? The mods have already cleaned this thread once.

Are you having an issue with the forums that someone can help you with?

maybe because I've been using reply

twice I have diven Boone the anti materiel rifle, & both times the weapon has degraded very rapidly, I checked it before setting out to get Driver Delphi it was at 100% before we got to killing Delphi the weapon was at 0%, the maximum shots Boone could have taken was about 30 if that. yet another flaw. gone back to giving him the sniper rifle.

Sad to see people like you spreading so much false information around about CPU's. A slower C2D running at 2.4 ghz would outrun a P4 running @3.4 ghz all day long just because of architecture changes. Go look up benchmarks and learn how a CPU actually works instead of going by clockspeed.

Wrong.

You can't optimize the microcode much further than 1 average opcode per clock cycle, and the Pentium 1 already had most opcodes running on a 1 cycle average. Executing one assembler instruction on a 3,4 Ghz CPU takes 294 picoseconds, on a 2,4 Ghz CPU it will take 417 picoseconds that's a 40% faster execution.

The hindering factor were and still are jumps. One step below assembly language the CPU-command is split up in even simpler commands that can be executed simultaneously. Our 1 clock cycle opcode still actually takes 5 or more clock cycles to be done, but meanwhile the execution of the following commands already begins, once this runs, the CPU finishes one opcode per cycle.

The problems are jumps, because the pre-execution of the following commands will be in vain when they are never executed (on assembly level) due to a jump. So after a jump, depending on size of the queue and the opcode in question, the execution of our 1 cycle opcode take the same 3-10 clock cycles it once took on a 386.

To prevent this, the CPU preloads the code from a fixed jump's target, and tries to figure out beforehand where to continue after a conditional jump. The P4E already was pretty well optimized in this regard, so later CPU generation couldn't optimize that much, because there simply wasn't much left to optimize.

At the same time the CPU clock approached the limit where HF-effects play a major role, and where the ever shorter wavelengths of the CPU-clock would make much smaller structures neccessary, so since micro-architecture can't be optimized much further, going multiprocessor was the obvious way out. If only the programs would actually start and make use of it.


To cut a long story short, running a single-thread program, a 2,4 C2D can't even dream of playing in the same leaque as a P4E 3,4Ghz, even a 2,8 Ghz Pentium might outrun it. A multi-thread program is another story, but beyond benchmark programs tailor-made for modern CPU-Architecture you still won't find much multi threading programs, especially not in games that take 2-3 years to develop.

Of course I can (and have done) write an assembly program that forces the prefetcher into dumping its preloaded code all the time, these programs may run better (as in: less slow) on a processor with an even better optimized prefetch algorithm but this is a completely theoretical effect, you'll never see in a real program. In practice, a slightly optimized prefetcher can never make up for a 40% speed advantage.

A 3GHz C2D certainly runs about as fast as a 3,4Ghz P4E but everything else is either a result of a biased benchmark sponsored by CPU-manufacturers, or a demonstration of the possible gain of writing multi-threaded programs.


But we're completely off topic now. If there is still stuff to discuss, let's do it per PM.

Question from a console user here.

Do PC users who have a computer that is well beyond the recommended system requirements still have trouble with the game; like game freezes? Sometimes I think that my PS3 can't handle game, mostly because the game usually has choppy movement before it finally freezes.

twice I have diven Boone the anti materiel rifle, & both times the weapon has degraded very rapidly, I checked it before setting out to get Driver Delphi it was at 100% before we got to killing Delphi the weapon was at 0%, the maximum shots Boone could have taken was about 30 if that. yet another flaw. gone back to giving him the sniper rifle.

This has also happened with the sniper rifle, seems the last update has included another bug never had it before.

Okay, you posted that twice. Again.

I haven't seen any sign of Boone's weapons degrading faster than normal, but he does have a habit of putting his gun in front of mine resulting in me shooting his gun and damaging it.

The AMR has slightly more health than the sniper rifle, but does more base damage per shot so it will degrade faster than the sniper rifle in all probability. I'm not sure how many shots that should be, though, but probably more than thirty.

sorry about that I'm having some trouble with mozilla not updating & thought it hadn't posted. I was using a sniper rifle on both occasions & Boone's weapon degraded a hell of a lot faster than mine, when his were at 0% mine was still above 80%. it only seems to have happened since the last update as before that there were no problems with Boone's weapon degrading as fast.

The Boone weapon degrade does not seem to effect the riot shotgun, as he has fitrd yjst weapon with using at least 3 times as many shots as when he was using the anti materiel eifle or the sniper rifle, the riot shot gun was still at well over 90% after all these shots. I have tested using the AMR & Siniper rifle using 80 shots & both remained above 65% after that many shots. as the rate at which weapons degrade in the hands of a companion then the AMR & sniper eifle are degrading way faster rhan thay should.
As I said before this problem was not noticeable before the last update, as Boone was using the sniper rifle & there were no signs of degredation.
The Gun Runners crash seems only to be effective around level 15 as I have tried it since with no crash, but the rifle & pistol power itens have been below 4, & if you only purchase 1 the others still disappear from the inventory,