The forum

Hi. I played Fallout 3 when it first came out but never really got into mods. I'd love to re-explore that world with some of the amazing content made by modders, but don't have Windows and the process is complicated.

Edited by MaunderingMoose

It seems that people have gotten FOSE to work in the past with other versions of Wine. Is there a way I can change the version of wine in the Fallout 3 virtual drive? Every time I try it crashes.

"Couldn't find Z:\\home\\\\.PlayOnLinux\\fallout3ng.exe, make sure you're running this from the same folder as fallout3.exe"

that cannot be right. the correct path should be


/home/user/.PlayOnLinux/wineprefix/virtualdrivename/drive_c/ etc etc etc

Where exactly did you install it? It may not be a wine issue, it may be that it wasnt installed correctly.

You can change the version of Wine by:

PlayOnLinux -> click Configure -> click the virtual drive -> on the right side, you can change the wine version

You will need to first install other wine versions first, by:

PlayOnLinux -> Tools -> Manage wine versions

and selecting the ones that you want to install.

I installed it in the Fallout 3 folder, in Steam/SteamApps/common, along side Fallout3.exe

I've switched Wine versions in Configure, trying several, but all but 1.3.26-xliveless2 crash when I try to run the game. Apparently people have gotten FOSE to work with Wine 1.4.

So, do the following, as previously stated:

You can change the version of Wine by:

PlayOnLinux -> click Configure -> click the virtual drive -> on the right side, you can change the wine version

You will need to first install other wine versions first, by:

PlayOnLinux -> Tools -> Manage wine versions

and selecting the ones that you want to install.

When you Manage Wine Versions, install the 32 bit version of 1.4, and then it will become available to change to that in the Configure section.

Also, this script is only for Fallout 3, not for anything else.

That's why I think the problem is FOSE not looking within WINE like it should.

If you installed it in the default folder, it should work fine. If it was installed through POL, its using whatever version of Wine you have that virtual drive set for.

Truth be told, the installation of the mod manager may be messing up your fallout install, but I am not sure, as I have not installed it through POL. lol :)

Im wondering if there is any way to install FOSE into another virtual drive by itself (this is actually where PlayOnLinux shines), and tell it to look at Fallout 3's virtual drive.

Try to reinstall Fallout 3, from scratch (BACKUP SAVE GAMES), in a fresh virtual drive.

Then, lets try to create a NEW virtual drive, JUST for FOSE, and see if we can get it running in there. Maybe we can symlink or something to the other folder.

I tried looking, and you were right; there is very little documentation or reports on this particular thing, so we will just have to see what we can do.

Making a fresh install of Fallout 3. (Takes a while to download.)

Trying to figure out how to make a drive for FOSE and create a symlink.

PlayOnLinux -> Configure -> click New at bottom left -> select your wine version

Then, after its been made:

PlayOnLinux -> Configure -> Select new virtual drive -> Miscellaneous tab -> run .exe in this virtual drive -> select FOSE installer

There isn't an installer for fose. Is it okay to create Steam/Steamapps/common/Fallout 3 and past the fose_loader.exe and dll files into that?

Ok, so do the same thing I said, but like this:

[quote]PlayOnLinux -> Configure -> click New at bottom left -> select your wine version

Then, after its been made:

PlayOnLinux -> Configure -> Select new virtual drive -> Miscellaneous tab -> run .exe in this virtual drive -> select fose_loader.exe from that folder.

If that doesnt work, then Install steam into that new virtual drive, and then copy those over to the new virtual drive. You dont want to create the folders; let the Steam installation handle that.

Install steam by:

PlayOnLinux -> select your new virtual drive (NOT the Fallout3 drive) -> Configure -> Install Components -> Steam

Oh, I see. Sorry for the confusion.

FOSE keeps looking in /home/user/.PlayOnLinux, even with Wine 1.4 and a few other versions I've tried out.

Its supposed to. The /home/user/.wine folder has nothing to do with PlayOnLinux. It should be looking in /home/user/.PlayOnLinux/wineprefix/virtualdrivename/

Thats how it works. Your system version is irrelevant except that it needs to be installed. Everything you install in PlayOnLinux will be in /home/user/.PlayOnLinux/wineprefix/

You should use your file browser to explore the structure of the /home/user/.PlayOnLinux/ folder. This will make it a little clearer how it is put together and how it keeps every install apart from the others.

Maybe I'm being unclear. This is what's happening. http://i.imgur.com/usM7xiu.jpg

Im not sure, then. It needs to be in the same folder as the game itself, but it crashes. Im dont know what else it needs. post your debug output from installing it in the same folder as fallout and trying to run it, so we can see all of the log.

Edited by MaunderingMoose

I went ahead and installed FoMM based on the instructions at the bottom of this post:

http://brianva.wikidot.com/fallout3

I only installed the gdiplus and mono28 packages. I haven't tried any mods yet but the manager seems to work. (After I uninstall FOSE so it doesn't try to launch with that.)

Edited by MaunderingMoose

Excellent! What version of Wine?

Same version as the Fallout 3 prefix (1.3.26xliveless2)

FoMM is Fallout Mod Manager, which I had working before. Fallout Script Extender still doesn't work, but I thought I'd just try playing with some mods that don't require it.

Ah ok. I understand now. Sorry, I just havent played that one yet. Im so far behind on games, its not even funny. :)