Celton88: Thanks for the reply. How do I check to see which WINE engine it is using? And as far as your other suggestions go, they sound nice, but I think they may be too technical for me. I've played around with WINE and could never really get it to work.
Right-click/Control-click on the Application Wrapper for Fallout. There should be an option that says "Show Package Contents...". Select it, and you'll actually be delving right inside the wrapper's guts.
At the top level of the folder structure for the application wrapper there *should* be an application within called "Wineskin". Open it. This is the configuration app that should be bundled within all Wineskin-derive wrappers, that controls all of the workings and configuration details for WINE. Click on the "Advanced" tab and you should be brought to a configuration window that says the version of the WINE engine bundled in the wrapper and the version of the wrapper itself. If you click in the Options tab you'll be able to, among other things, launch regedit, winetricks and winecfg, in addition to changing/updating the version of WINE used in the wrapper.
That was why I was so excited about PaulTheTall's wrappers, I didn't have to muddle around with all the technical details.
And this is the reason why I recommend CrossOver for 90% of people who want to run GOG games (or Windows games in general) on OS X through WINE. Configuration and maintenance of compatibility environments is far, far,
far easier and more straightforward in CrossOver compared to Wineskin.
I love Wineskin, and I use it just as much as I use CrossOver for games, but Wineskin isn't for people who want a streamlined, simple, "zero-config" solution for most Windows games out there. The tradeoff is that Wineskin is far,
far more powerful for the technically savvy who don't mind spending tons of time tweaking and troubleshooting. However, for users who are fazed by more technically complex solutions, CrossOver is the better choice.