1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Talisman: Digital Edition Guide

Discussion in 'Guides' started by Daerandin, Aug 12, 2014.

  • by Daerandin, Aug 12, 2014 at 6:07 PM
  • Daerandin

    Daerandin Active Member

    Joined:
    Oct 18, 2013
    Messages:
    984
    Likes Received:
    171
    Trophy Points:
    43
    Location:
    Northern Norway
    Home page:
    Talisman is a board game by Fantasy Flight games, well known for their large selection of high quality board games, card games and role playing games. This game is really just a digital edition of the Talisman board game, allowing you to either play against the AI, or human opponents.

    talisman_title.png

    The guide will explain how to setup Steam in PlayOnLinux so that you can install and play the game in steam.

    Tips & Specs

    To learn more about PlayOnLinux and Wine configuration, see the online manual: PlayOnLinux explained

    Arch Linux 64-bit
    PlayOnLinux 4.2.4
    Wine 1.7.24

    Setup PlayOnLinux

    Launch PlayOnLinux and select 'Tools' and 'Manage Wine versions'

    In the new window that appears, scroll through the 'Available Wine versions' box to find '1.7.24' and click on the right pointing arrow to install it, afterwards it will appear on the right side under 'Installed Wine versions'
    If you have a 64-bits system, make sure you have selected the 'Wine versions (x86)' tab above, although it works well on 64-bit as well to my experience, I just will not cover it in this guide

    talisman_01.png

    Just close the window. Back at the main PlayOnLinux window, select 'Install'

    Click on 'Install a non-listed program'

    talisman_02.png

    Select 'Install a program in a new virtual drive'

    talisman_03.png

    Name the virtual drive "steam_talisman"

    talisman_04.png

    On the next window, select 'Use another version of Wine', 'Configure wine' and 'Install some libraries'

    talisman_05.png

    On the wine selection window, select the 1.7.24 version and click 'Next'. Make sure you select '32-bits window installation' if you are on a 64-bit system, although as mentioned earlier, it should also work using a 64-bit virtual drive if so desired.

    talisman_06.png

    When the wine configuration window appear, select the 'Graphics' tab, and click the checkbox for all four options. Make sure that you set the resolution to your desktop resolution. My desktop is at 1920 x 1080, so I set that for the wine virtual desktop resolution.

    talisman_07.png

    Note: Even though the language is Norwegian in my screenshot, the layout will look the same for you

    Next we will do a workaround for an issue with the Steam overlay. For some people it appears to be fixed, but there are still people reporting it as an issue on WineHQ, so it is best to disable the Steam overlay.

    Now select the 'Libraries' tab, and under 'New override for library:' type in "gameoverlayrenderer" and click 'Add'

    talisman_08.png

    Now find and select it on the list below, then click on 'Edit'

    talisman_09.png

    In the new window that appears, select 'Disable', then simply click OK to close the wine config window.

    talisman_10.png

    When you come to the selection of libraries, select the POL_Install_steam library, then click Next

    talisman_11.png

    At the time of writing, PlayOnLinux made a little change to this library, which means you have to go through the Steam install process manually. I always prefer to install Steam by using this library in PlayOnLinux since it takes care of the missing font issue in Steam, while also installing the corefonts library so it looks better than just a manual Steam install.

    Just click Next

    talisman_12.png

    Click to accept the license and click next

    talisman_13.png

    Just let it keep the default install location and click Install

    talisman_14.png

    When the Steam installation is finished, make sure you uncheck the box for starting Steam, we do not want to start Steam at this point.

    After you have unchecked the box for starting Steam, you can click on Finished

    talisman_15.png

    When it asks you for the install file to run, click on 'Cancel'

    talisman_16.png

    The virtual drive has already been set up by this point and there is no need to run any install file. Now back at the main PlayOnLinux window, click on 'Configure', it does not matter what game shortcut is selected when you click 'Configure' so don't worry about that.

    On the left side, find the virtual drive you just set up, it will be listed with the same name you typed in during set-up. Look for 'steam_talisman'. Select the virtual drive, then click 'Make a new shortcut from this virtual drive'

    talisman_17.png

    Check the screenshot above for reference. It is very important that you select the virtual drive you just set up before clicking to make a new shortcut.

    Select Steam.exe and click next. Name the shortcut "Steam-Talisman" then click 'I don't want to make another shortcut' and click next.

    talisman_18.png

    Now click on the 'Display' tab on the top. Change 'Video memory size' to reflect your GPU memory.

    talisman_19.png

    At this point you can close the PlayOnLinix configuration window and start Steam from the Shortcut in the main PlayOnLinux window. First Steam will update

    talisman_20.png

    Then you can log in to your Steam account

    talisman_21.png

    Now just find the game in your game library, and click Install

    talisman_22.png

    The game is not very large so it should download fairly quickly. Once the game is done installing, you can play it from Steam.

    The game should start up in fullscreen, but in game options are always available from the indicated icon in the screenshot below

    talisman_23.png

    Both singleplayer and multiplayer should work well.

    Screenshots

    talisman_sc01.png talisman_sc02.png
    talisman_sc03.png talisman_sc04.png

Comments

Discussion in 'Guides' started by Daerandin, Aug 12, 2014.

  1. booman
    Uh Oh, another Steam guide ;)
    Hopefully Steam updates won't break anything else in the future.

    Looks like a cool game
  2. Daerandin
    Haha, I know Steam guides can be risky but I will not let that prevent me from doing guides for the games I like.
  3. booman
    Tell me about it...
    I have a bunch of Steam games I plan to do guides for, so hopefully they can keep from breaking anything else
  4. JoZ3
    Thanks for the guide, unfortunately does not work in my Manjaro x64 with the latest catalyst drivers... :(

    Tested with wine 1.7.24 to 1.7.40
  5. booman
    Welcome to the forums.
    Are you able to play any other games in Manjaro?
    Do you have the 32-bit libraries installed?
  6. JoZ3
    Thanks for replying... actually I have installed under steam with wine, these games: Back to the Future ep. 1, The Binding of Isaac, Brawhalla, Ethan: the meteor hunter, Orcs Must Die!, Path to Exile, PayDay: The Heist, Risen, Scribblenaults unlimited and unmasked, The Ship, Speedball 2 HD and Torchlight; all games work fine!!.

    And I have installed the 32-bit libiraries, I followed the instructions in the guide, but when I running the game always appears a windows in black and nothing happend...
  7. booman
    JoZ3 likes this.
  8. Daerandin
    I will test this game once again to see if things work for me. As booman said, please post your debug output when running this game as it might give us clues as to what is causing your problem.
    JoZ3 likes this.
  9. JoZ3
    Hi, sorry for the delay... this the debug information:

    Code:
    [04/22/15 14:42:43] - Running wine-1.7.24 Steam.exe (Working directory : /home/myuser/.PlayOnLinux/wineprefix/steam_talisman/drive_c/Program Files/Steam)
    [0422/144246:ERROR:network_change_notifier_win.cc(174)] WSALookupServiceBegin failed with: 8
    [0422/144246:ERROR:gpu_info_collector_win.cc(103)] Can't retrieve a valid WinSAT assessment.
    [0422/144301:ERROR:renderer_main.cc(227)] Running without renderer sandbox
    [0422/144301:ERROR:renderer_main.cc(227)] Running without renderer sandbox
  10. booman
    Thats all?
    Try clicking debug in PlayOnLinux instead of using the Terminal.
  11. Daerandin
    As booman say, you get all the debug output when you run the game by clicking on Debug on the tab on the side instead of the normal Run button.

    debug.png

    An extra window will open, you can try running the game and exit it when it fails to run. Then copy everything from the additional debug window and post it here.
    JoZ3 likes this.
  12. JoZ3
    Hi, thanks all for replying and sorry for the delay... This the debug information taken as say @Daerandin.

    Code:
    [04/26/15 11:12:21] - Running wine-1.7.24 Steam.exe (Working directory : /home/myuser/.PlayOnLinux/wineprefix/steam_talisman/drive_c/Program Files/Steam)
    fixme:ver:GetCurrentPackageId (0x33e490 (nil)): stub
    fixme:advapi:EventRegister {47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x3f006c70, 0x3f040ce8, 0x3f040ce0
    fixme:advapi:EventRegister {58a9201e-73b0-42ce-9821-7e134361bc70}, 0x3f006c70, 0x3f040d20, 0x3f040d18
    fixme:advapi:EventRegister {3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x3f006c70, 0x3f040cb0, 0x3f040ca8
    fixme:advapi:EventRegister {1432afee-73b0-42ce-9821-7e134361b433}, 0x3f006c70, 0x3f040d58, 0x3f040d50
    fixme:advapi:EventRegister {4372afee-73b0-42ce-9821-7e134361b519}, 0x3f006c70, 0x3f040d90, 0x3f040d88
    fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
    fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
    fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
    fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
    fixme:advapi:EventRegister {47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x3f006c70, 0x3f040ce8, 0x3f040ce0
    fixme:advapi:EventRegister {58a9201e-73b0-42ce-9821-7e134361bc70}, 0x3f006c70, 0x3f040d20, 0x3f040d18
    fixme:advapi:EventRegister {3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x3f006c70, 0x3f040cb0, 0x3f040ca8
    fixme:advapi:EventRegister {1432afee-73b0-42ce-9821-7e134361b433}, 0x3f006c70, 0x3f040d58, 0x3f040d50
    fixme:advapi:EventRegister {4372afee-73b0-42ce-9821-7e134361b519}, 0x3f006c70, 0x3f040d90, 0x3f040d88
    fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
    fixme:imm:ImmGetOpenStatus (0x1d2718): semi-stub
    fixme:ver:GetCurrentPackageId (0x33e360 (nil)): stub
    fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
    fixme:ver:GetCurrentPackageId (0x31e5c0 (nil)): stub
    fixme:process:SetProcessDEPPolicy (3): stub
    fixme:heap:HeapSetInformation (nil) 1 (nil) 0
    fixme:imm:ImmDisableTextFrameService Stub
    fixme:thread:GetThreadPreferredUILanguages 56, 0x33f784, (nil) 0x33f788
    fixme:winsock:WSALookupServiceBeginW (0x33f670 0x00000ff0 0x33f6ac) Stub!
    [0426/111232:ERROR:network_change_notifier_win.cc(174)] WSALookupServiceBegin failed with: 8
    fixme:iphlpapi:NotifyAddrChange (Handle 0x33f7b8, overlapped 0xb27f28): stub
    fixme:win:RegisterDeviceNotificationW (hwnd=0x100a6, filter=0x33f7c4,flags=0x00000000) returns a fake device notification handle!
    fixme:win:RegisterDeviceNotificationW (hwnd=0x100a6, filter=0x33f7c4,flags=0x00000000) returns a fake device notification handle!
    [0426/111232:ERROR:gpu_info_collector_win.cc(103)] Can't retrieve a valid WinSAT assessment.
    fixme:win:EnumDisplayDevicesW ((null),0,0x33f094,0x00000000), stub!
    fixme:ver:GetCurrentPackageId (0x270e014 (nil)): stub
    fixme:ver:GetCurrentPackageId (0x33fbac (nil)): stub
    fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
    fixme:wbemprox:client_security_SetBlanket 0x7c7e7430, 0x20179f0, 10, 0, (null), 3, 3, (nil), 0x00000000
    fixme:wbemprox:client_security_Release 0x7c7e7430
    fixme:hnetcfg:fw_apps_get__NewEnum 0x2017b40, 0xdaee51c
    fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
    fixme:wbemprox:client_security_SetBlanket 0x7c7e7430, 0x201bd58, 10, 0, (null), 3, 3, (nil), 0x00000000
    fixme:wbemprox:client_security_Release 0x7c7e7430
    fixme:hnetcfg:fw_app_put_ProcessImageFileName 0x201bcb0, L"C:\\Program Files\\Steam\\steam.exe"
    fixme:hnetcfg:fw_app_put_Name 0x201bcb0, L"Steam"
    fixme:hnetcfg:fw_app_put_Enabled 0x201bcb0, -1
    fixme:hnetcfg:fw_apps_Add 0x2135220, 0x201bcb0
    err:ole:CoGetClassObject class {e2b3c97f-6ae1-41ac-817a-f6f92166d7dd} not registered
    err:ole:CoGetClassObject no class object {e2b3c97f-6ae1-41ac-817a-f6f92166d7dd} could be created for context 0x1
    fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
    fixme:wbemprox:enum_class_object_Next timeout not supported
    fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
    fixme:wbemprox:enum_class_object_Next timeout not supported
    fixme:wbemprox:enum_class_object_Next timeout not supported
    fixme:wbemprox:enum_class_object_Next timeout not supported
    fixme:wbemprox:enum_class_object_Next timeout not supported
    fixme:iphlpapi:NotifyAddrChange (Handle 0xa8d05ac, overlapped 0xa8d05b0): stub
    fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_HANDLE_INFORMATION
    fixme:win:RegisterDeviceNotificationA (hwnd=0x100b0, filter=0xe0fe510,flags=0x00000004) returns a fake device notification handle!
    fixme:advapi:EventUnregister deadbeef: stub
    fixme:advapi:EventUnregister deadbeef: stub
    fixme:advapi:EventUnregister deadbeef: stub
    fixme:advapi:EventUnregister deadbeef: stub
    fixme:advapi:EventUnregister deadbeef: stub
    err:ole:CoGetClassObject class {77f10cf0-3db5-4966-b520-b7c54fd35ed6} not registered
    err:ole:CoGetClassObject no class object {77f10cf0-3db5-4966-b520-b7c54fd35ed6} could be created for context 0x1
    fixme:winhttp:get_sy
  13. Daerandin
    I'm not seeing anything helpful in the debug output, so unfortunately I can't think of anything helpful at the moment.

    Just to clarify, this debug output you have here is from when you try to run the game and get the black window?

    It could be that you are missing some 32 bit libraries, so I want you to try and install this again in PlayOnLinux, but this time use a 64-bit virtual drive when you are asked. I was considering to also give it a try myself with a clean Manjaro install in Virtualbox and see if it runs, but I will probably not have time for that until next week.
    JoZ3 likes this.
  14. JoZ3
    Yes, is the debug output when I get the black window

    Thanks mate, I will try what you say :)

Share This Page