[chief1983]

Do:

• Stop and think
• Check your directory structure to make sure nothing seems out of place.
• Run a debug build and capture the fs2_open.log file after a crash or a problem and attach that to your post.
• Make sure you only have retail .vp files in your root Freespace2 folder - that means only root_fs2, smarty_fs2, sparky_fs2, sparky_hi_fs2, stu_fs2, tango1_fs2, tango2_fs2, tango3_fs2, and warble_fs2.  Anything else is not retail.  The only other files you might be ok having in there are the FS2OGGCutscenes, and the multi-mission and multi-voice packs.  Anything else is a no-no.
• Move your data folder.  You don't really need it honestly.  Anything in it can be recreated by the game engine.  Just back it up somewhere else for testing.
• Run the game with -no_glsl (check the disable GLSL option in Troubleshooting).  It should detect it properly whether you can run it or not, but you might as well try.  Also disable normal maps in the Graphics section.  In fact, pretty much just uncheck everything, and then disable GLSL.  See if that helps and then start turning things on.  This is especially true for older hardware, or you GMA950 and ATI X1950 users.
• Listen to what the staff says.  If we say you don't need something, trust us.

Don't:

• Leave old random VP files sitting in your root FS2 folder.
• Leave any shader files in your root fs2 folder.
• Put stray .tbl or .tbm files in your fs2/data/tables or other folders, unless you know what you're doing or you were asked to test something - and remove it later.
• *****.  We're volunteers.  We respond much better to the carrot than the stick.

[Topgun]

what could happen if you leave shader files in the root dir?

[chief1983]

They conflict with the ones specifically designed for use with the MediaVPs, and any other mods that would like to use their own custom set.  So leaving them as a global file isn't a good idea anymore.  It makes a support headache for everyone working a project when someone reports a problem with it and it's shader related.