iFSS

On: http://www.newvegasnexus.com/downloads/file.php?id=44566 and http://www.fallout3nexus.com/downloads/file.php?id=16951 Am getting: http://fs2.fallout3nexus.com/get.php?file=GECKScript_npp-16951-1-0.7z&deadlink=true&domain=fallout3nexus.com http://fs2.newvegasnexus.com/get.php?file=GECKScript_npp-44566-1-0.7z&deadlink=true&domain=newvegasnexus.com When trying to download. :sad: * edit - working now :)

It may be worthwhile asking in the Parallels support forums, so you can rule out virtualisation deficiencies being the culprit, before looking into anything else.

As well as archive invalidation, it could be: Load order (use BOSS) Missing compatibility patches (FOIP etc) Not creating a (new) merged patch Too many mods - remove some or merge some

FOSE has AddSpellNS, that doesn't generate the messages.

There's some instructions to follow here, maybe they will help.

Have you made sure that all of your drivers are up to date? For your graphics card, to find out what it is, go to Control Panel -> Performance Information and Tools -> View and print detailed performance and system information (for nicely formatted info). Then go to the manufacturer's (NVidia/AMD/Intel) website to get the latest drivers. You could also check your laptop manufacturer's website to find out if there's any known issues, updates, etc there. If you get crashes/problems with other 3D games (try Unigine Heaven if you need something else to run), then the problem is with Windows/drivers/hardware, so start looking in that direction if so.

It doesn't say which one - but one of the stored fomods in the mods/ directory (likely in your Fallout 3 directory if you didn't change the path) is corrupt (fomod's are just 7zip's, hence the errors). Delete all the fomod's in there (and in FOMM's Install Info/ directory), then reinstall FOMM. Just to be sure everything's ok, you should run a file system check (chkdisk) on the hard disk that the fomod's were installed to.

Oversimplified explanation: When you were doing dialogues (or other things) - did you notice the conditions that you were imposing (like GetItemCount Caps001 > 100)? Using scripts is kind of the same thing: make something happen when a condition is met (or not). You can do multiple things when that condition is met, you can do the same thing any number of times, etc. A bad example in english: if the player is in Megaton, and it is a Thursday, and it is raining, then make Moriarty dance around the bomb whilst wearing the sexy nightwear, for one minute per cap that the player possesses, or until the player drops a box of detergent. There is a lot more to it than that, though. Have a look at Cipscis' scripting tutorials if you want to try it out. If the tutorials make no sense to you, and/or you aren't really familiar with programming at all, you may be best off learning the basics of programming from another language first. JavaScript, Python or PHP are all fairly easy to get to grips with.

iNumHWThreads=2 goes in the [General] section, so move it below bUseThreadedAI=1 Did you install Fallout 3 to your Program Files folder? If so, uninstall it and reinstall it to C:\Fallout 3 instead (or anywhere outside of the Program Files folders). Windows' UAC causes odd things, may not be the cause of this problem, but will prevent others. In your first post, you mention "its vanilla i did the .ini thing" - which ini thing? That's just for the Zeta intro, where purging the buffers causes everything to freeze. Though buffer purging can cause more crashes if the game is really unstable - e.g. if someone is playing on corrupted saves, but that shouldn't happen at the start of the game (it wouldn't surprise me though, lol).

Hmm, I tested the Zeta intro repeatedly, and couldn't cause a crash or freeze. I'll check again in case I have (re)introduced a problem whilst updating the plugin. Thanks muchly for letting me know :thumbsup: Did/do the crashes still happen when disabling automatic purging via the Pip-Boy menu or hot key (hot key + 8 )? (You can do this at any time if you think the purging is causing a problem - if you find any crashes anywhere else that only happen when purging is enabled, please let me know) Glad it's helping elsewhere at least :biggrin:

Cool. If you still need a buffer purging plugin, both Zan AutoPurge Crash Protector and Yet Another Purge Cell Buffers Plugin (*cough* shameless plug *choke* *splutter*) don't cause that issue during the Zeta intro.

Are you using any cell buffer purging mods? If so, disable them (& out of curiosity, which one are you using?). Otherwise, follow the advice here.

Is your version of the .NET framework up to date? Check in Windows Update to see if there are any .NET updates waiting there.

Yeah, it should be reapplied if you remove the heat sink. Remove the grease that's there first (if you can't get isopropyl alcohol, then plain nail varnish remover works great - just use it on the metal though), then add a new thin layer. Depends on the BIOS - either just browse through the menu to find them (shouldn't take long), look in whatever manuals you got from HP, or just clear the settings - most BIOS' have an option to "load optimised defaults" or similar, or you can clear the CMOS manually ("Clearing the BIOS settings" section). You should probably look here: best graphics cards for the money - sept 2011 (look on that site for earlier comparisons if you are going 2nd-hand). You will most likely need to upgrade your power supply depending on whichever card you go for - NVidia or AMD's websites will give you the minimum recommended specs. (Your current power supply is 350 watt, +12V1 18A, +12V2 18A, no 6-pin connectors) Make sure you get a good quality power supply though, even if it means getting a cheaper graphics card. Browsing through sites like Tom's Hardware will give you clearer advice than I can anyway, have fun. :)

Installieren FOSE. Kopieren Sie "Console Key Binder.esp" um Ihre Fallout 3\Data Ordner. Aktivieren Sie "Console Key Binder.esp" in FOMM, und klicken Sie "Launch FOSE". (Mein Deutsch ist leider ein wenig eingerostet, so auf Englisch: Install FOSE. Put "Console Key Binder.esp" in your Fallout 3\Data directory. Enable "Console Key Binder.esp" in FOMM, and click "Launch FOSE") Drücken Sie "F4"

Console key binder sollte funktionieren, oder sehen: console troubleshooting.

No worries, glad you got all that sorted :) I added the audio cache increase to the wiki article - surprised it wasn't in there to begin with.

Games for windows live. You can get round the error in FOMM by going to Tools -> Install tweaker, placing a check next to "Use fake xlive.dll" & click apply.

Yeah, they also go ballistic if you pick Talon Company as your backstory... :devil: When you quit and exit the game, reboot Windows, then load it back up, does the problematic save start crashing again? If so, then the save game is likely to be corrupt - it's not a good idea to continue with it. Being at Rivet City with everything successfully loaded, may have given you a reprieve from the crashing when switching to the wonky save. Hopefully whilst you're testing out loading the mods you'll find the actual cause though.

When you open the DCUpgrade quest with the Geck, is DCUMetalPlatesSCRIPT set as the script in the data tab? If so, it may be worth going through it thoroughly to make sure there are no errors that the compiler isn't catching. Try Cipscis' validator. I can't help with that, sorry, hopefully someone else can.

Having that extra Data folder is probably the cause of it not working for you, all of the stuff in there should be in the proper Data directory above it. Move everything in that extra directory to the parent directory. Make sure the songs are in: "Bethesda Softworks/Fallout 3/Data/sound/songs/radio/GNR" And that only one of the GalaxyNewsRadio[...] esp's is in your "Bethesda Softworks/Fallout 3/Data" folder & activated in FOMM - GalaxyNewsRadio20[M].esp if you're only using 20 songs (delete the other esp's). If GNR More Where That Came From still doesn't work, delete GalaxyNewsRadio20[M].esp and the whole "Bethesda Softworks/Fallout 3/Data/sound/songs/radio/GNR" directory to uninstall it.

Which error - "Unknown variable or function" or "Missing variable name in set command"? Could you repost the sections of the scripts as they are now please, along with the error? Just to check: did you click the save button (the disk icon) to compile the script after you edited it, and then save the edited plugin before you exited the Geck? Is DCUpgradeSCRIPT definitely set as the quest script for the DCUpgrade quest?

Every time I have seen that error it has indicated a hardware problem for Vista users (different hardware problems too, from overheating to faulty sticks of RAM, probably because Vista taxes the hardware so much). Check your BIOS settings, when you were doing hard reboots it may have recovered the default settings & clock speeds. If you had warmer weather last week, then definitely check your cooling. It may be worth running some stress tests/Memtest out of Windows to be sure (SystemRescueCd and UBCD are good for this). * edit - forgot to note that thermal grease doesn't last forever, if you're overclocking (& therefore generating more heat) it will dry out & become ineffective quicker. Another reason to check your cooling. I had problems with "GNR More Where That Came From" not playing songs, I couldn't figure out the cause, and all the other custom stations that I have work okay. I installed GNR Enhanced instead, and it works fine. There's an article in the wiki about stuttering audio if that continues. Yes, though make sure to follow prensa's guide to fix the Broken Steel bug. Some mods override some of the fixes in the unofficial patch (e.g. FWE unintentionally reverts the bug fix for bear traps and toilet traps that stops you losing your voice after being caught in one), but it's worth it for the fixes that remain.

It should be: set DCUpgrade.DCUMetalPlate to DCUpgrade.DCUMetalPlate + 1 But you haven't declared DCUMetalPlate alongside the other 5 variable declarations in DCUpgradeSCRIPT: short DCUMetalPlate 0 (I didn't realise that variables could be initialised in their declarations - the documentation for the scripting language is somewhat lacking. Learn something new every day if that's correct...)

That sounds like your graphics card overheating. Are you overclocking it (or overclocking your CPU/RAM?), if so go back to the normal speeds. Check that the fan on the card is still working, that the heatsink is attached firmly to the card, and that it isn't clogged up with dust. If the card is passively cooled (no fan), check the other fans inside the case to make sure that they are still spinning dust-free. If the problem doesn't go away, either try underclocking the card (use RivaTuner), increase the fan speed (RivaTuner again), or if passively cooled - remove the side of your PC case and stick a desk fan next to it (temporary solution), or buy a new graphics card. Buying a replacement heatsink/fan set for that card isn't really worth it, as you can get decent 2nd-hand graphics cards off eBay for a few pounds more. (Just to note, some of the earlier NVidia 8400's had a bad problem with overheating - supposedly just the mobile versions) The unofficial patch is a supplementary patch, to be used in addition to the official patches. So definitely use the official patch.