TTLG|Thief|Bioshock|System Shock|Deus Ex|Mobile
Page 48 of 49 FirstFirst ... 3813182328333843444546474849 LastLast
Results 1,176 to 1,200 of 1205

Thread: Tafferpatcher: unofficial complete patch for Thief 2

  1. #1176
    Member
    Registered: Jul 2011
    Quote Originally Posted by Unna Oertdottir View Post
    What are you talking about? Never disable
    use_d3d_display

    if you don't have to. This is just a rescue option. A bunch of render features rely on this.
    try to capture the screen with OBS without doing that then, good luck.

  2. #1177
    Zombified
    Registered: Sep 2004
    there is like half a dozen things you can try to get whatever you want to do working properly without resorting to the DX6 mode - if it does work (semi) properly for you then fine, just don't go around recommending it as a fix-it-all thing, because that it ain't.

  3. #1178
    Member
    Registered: Oct 2013
    Didn't think it worth starting a thread on this, so will ask here.

    Is the T2X site down for anyone else? Trying to get my hands on the setup file.

    Also, will installing it work or is there some new-fangled way needed to make it work with Newdark/Tafferpatcher? Thanks.

  4. #1179
    Quote Originally Posted by Cigam View Post
    Didn't think it worth starting a thread on this, so will ask here.

    Is the T2X site down for anyone else? Trying to get my hands on the setup file.

    Also, will installing it work or is there some new-fangled way needed to make it work with Newdark/Tafferpatcher? Thanks.

    It's working fine for me, try this link?
    http://www.thief2x.com/_dlfiles/t2x_v11_full.exe

  5. #1180
    Southquarter.com/fms
    Registered: Apr 2000
    Location: The Akkala Highlands
    @Cigam - easiest way to play T2X these days is to get the FM version, which you just load up like any other fan mission using FMSel or NewDarkLoader. No real installation necessary. Get it on Ricebug's site:

    http://www.bogadocious.com/thief.html

  6. #1181
    Member
    Registered: Oct 2013
    Thanks for the links. I have also discovered that there are HD and NecroAge versions of T2X that hopefully will be simple to use with FMSel with minimum hassle. My thanks once again to the Keepers for making this stuff easier for the rest of us

  7. #1182
    Member
    Registered: Oct 2013
    Quick question about T2X. There appears to be only one lockpick and neither of the normal lockpick hotkeys bring it up. Is there any known way to bind it to a key?

  8. #1183
    Member
    Registered: Oct 2013
    Now solved it. Will leave this here in case it is of any use to other T2X players. In T2 the lockpicks have the names lockpicksm and lockpicklg, whereas the T2X lockpick is named simply lockpick.

    So in user.bnd I just changed the line

    bind 9 "inv_select lockpicklg"

    to

    bind 9 "inv_select lockpick"

    and 9 now brings up T2X's hairpin lockpick. Having to manually scroll to find the lockpick everytime I wanted to use it was getting a bit old.

  9. #1184
    Member
    Registered: Dec 2004
    Location: Germany
    The hairpin lockpick of T2X gets replaced with regular lockpicks after some missions. This might be the reason for the authors not assigning any key to the hairpin lockpick. On the other hand, they did not know that someone would turn their expansion into a "regular" FM campaign one day, which most likely would have removed any key assignments specific to T2X.

    Anyway... if some moderator comes this way someday, I'd recommend moving the last postings here into a T2X thread. They really don't have much to do with Tafferpatcher.

  10. #1185
    New Member
    Registered: Sep 2014

    Can't fix the brightness

    Hello. I have a problem with brightness. I already tried to edit cam_ext.cfg and take the ; -mark off and on but nothing changes. Anyone know how to fix this issue? Thanks.

  11. #1186
    Member
    Registered: May 2005
    Location: Leicester, UK
    Help required, please.

    I manually updated my New Dark 1.20 installation (installed with Tafferpatch ages ago) to 1.25 by copying the contents of 'new_dark.zip' and 'contrib.zip' into the existing folder.

    Performance wasn't very good - seems like the framerate is 30 when panning the camera, with none of the normal 60fps smoothness.

    I then installed the latest Tafferpatch in case there were issues with using some items from an older Tafferpatch installation. Same issue.

    My 1.20 installation on a usb stick still plays fine, so it's just the 1.25 that is causing the issue.

    Riva is reporting 60fps in game.

    Is there is a setting I need to change?

    UPDATE:

    Ignore.

    I read the installation instructions and copied "cam_ext.cfg", "cam_mod.ini" and "lg.ini".

    All is fine.
    Last edited by mrsmr2; 28th Sep 2017 at 18:55. Reason: Following instructions is too difficult for some people!

  12. #1187
    New Member
    Registered: Apr 2011

    video color issues after tafferpatcher install

    I apologize if this is covered in another thread--I did some searches and didn't find anything. I did an install with the most recent Tafferpatcher; the game is running and there are options for widescreen resolutions. The video colors, however, are in a word psychedelic and no matter what resolution I choose I can't get them to the proper colors. what did I miss, and how can I correct the problem?

  13. #1188
    Zombified
    Registered: Sep 2004
    edit cam_ext.cfg, find:
    ;d3d_disp_no_rgb10_buf
    and remove ; so it's:
    d3d_disp_no_rgb10_buf

  14. #1189
    New Member
    Registered: Apr 2011
    That took care of the problem! Thanks, Voodoo47; I appreciate your help!

  15. #1190
    Member
    Registered: Jul 2011
    Quote Originally Posted by Linda View Post
    It is very easy to make it work:

    cam_ext.cfg
    Code:
    ; enable Direct3D 9 based display system (instead of the legacy DirectX 6 one)
    ;use_d3d_display
    just add a semicolon on the use_d3d_display line, that's all.
    Found another, better way to record on OBS: open cam_ext.cfg and remove the semicolon before force_windowed. Using d3d_display got the game maximum 30 FPS, while with this trick you can have as much FPS as your screen have.

  16. #1191
    Member
    Registered: May 2015
    So, why would this be bugging out for me when Tfix worked just fine? I get a bugged flashing display on launch, and I can hear the menu in the background, does this default to some weird res that my monitor won't play well with?

  17. #1192
    Dóttirin klęšist oft móšur möttli
    Registered: Apr 2015
    If you want help, give us informations. As always.

  18. #1193
    Zombified
    Registered: Sep 2004
    ->
    Quote Originally Posted by voodoo47 View Post
    edit cam_ext.cfg, find:
    ;d3d_disp_no_rgb10_buf
    and remove ; so it's:
    d3d_disp_no_rgb10_buf

  19. #1194
    Dóttirin klęšist oft móšur möttli
    Registered: Apr 2015
    Since nobody is reading the helpful instructions that come with the NewDark.zip, Tafferpatcher might include it.
    troubleshooting.txt
    Code:
    Most config vars mentioned here are found in cam_ext.cfg, so if no other
    .cfg file is explicitly mentioned, then cam_ext.cfg applies.
    
    Many problems have multiple possible solutions listed. Try each listed
    solution one at a time, not all of them at once.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, says D3DX9_43.DLL is missing.
    Cause:
        The (correct) DX runtime libraries have not been installed.
    Solution:
        * Read the release notes again and install the "DirectX End-User
          Runtimes (June 2010)" linked to in the release notes.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, says D3DX9_43.DLL is missing even though I
        downloaded the DX runtimes and ran the downloaded EXE file.
    Cause:
        The DX runtime libraries have not been installed.
    Solution:
        * Running the downloaded DX runtimes EXE (directx_Jun2010_redist.exe)
          will only extract the DX installer to a temporary location (of
          your choice). You then have to open that location and run the
          actual DX installer called DXSETUP.EXE. (The temporary installer
          files can be deleted after installation is complete, so it's
          advisable to extract it to a new/empty directory.)
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, says that the side-by-side configuration is
        incorrect (or maybe that MSVCR90.DLL/MSVCP90.DLL is missing).
    Cause:
        The correct Visual Studio runtime libraries have not been installed.
    Solution:
        * Read the release notes again and install the "Visual Studio 2008
          SP1 C++ runtimes" linked to in the release notes.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, log file indicates that no supported hardware
        3D devices were found.
    Causes:
        Hardware 3D acceleration has been disabled in the driver or Windows,
        or no display modes were found that are supported by both the game
        and the video adapter.
    Solutions:
        * To determine that 3D acceleration is working properly, go to
          http://support.microsoft.com/kb/191660 for further information.
        * If no (supported) display modes were found then that's often
          related to monitors in portrait orientation. Adding user defined
          display modes usually solves that. See "user_mode" config vars
          in "doc\new_config_vars.txt" and/or "cam_ext.cfg".
    
    ----------------------------------------------------------------------
    
    Problem:
        Game crashes at startup.
    Cause:
        Configuration error/issue.
    Solutions:
        * Make sure the pathnames in darkinst.cfg (T2) / install.cfg (SS2)
          for resname_base, movie_path, load_path, script_module_path and
          install_path point to the correct locations. Re-install if
          necessary.
        * On some asian systems when the Windows input language is set to
          IME 2010 (/Microsoft Office IME 2010) it can help to change to
          regular IME (no 2010). The input language options can be found
          in the Windows control panel under "Region and Language" ->
          "Keyboards and Languages". 
        * Sometimes the default resolution of 640x480 doesn't work, Manually
          setting the game resolution to the same resolution as the Windows
          desktop can help. Edit "cam.cfg" and add the line (or change it
          if it already exists) "game_screen_size  ".
          For example if your desktop is 1600x900: "game_screen_size 1600 900".
    
    ----------------------------------------------------------------------
    
    Problem:
        Player seems to hover at peak of jumps, and/or moves way too slow.
    Cause:
        Frame rate too high.
    Solutions:
        * Make sure your graphics driver settings doesn't force disabled
          vsync (set it to application preference or at least enable forced
          vsync).
        * Cap the frame rate with software frame rate limiter (set
          "framerate_cap 100" or less).
        * If you've previously disabled vsync through "vsync_mode" then
          enable it again.
    
    ----------------------------------------------------------------------
    
    Problem:
        Uneven/jerky frame rate and/or laggy mouse movement even though the
        system should be fast enough to do better.
    Cause:
        Computer is rendering too many frames in advance.
    Solutions:
        * Set "d3d_disp_limit_gpu_frames 1 1".
        * Set frame rate limiter ("framerate_cap") to a frame rate slightly
          above the monitor refresh rate (for example 70 to 80 for a 60Hz
          monitor).
    
    ----------------------------------------------------------------------
    
    Problem:
        Low frame rate.
    Solutions:
        * Decrease display resolution.
        * Disable multisampling ("multisampletype").
        * Disable floating point render buffers ("d3d_disp_enable_hdr").
        * Disable postprocessing ("postprocess").
        * Disable "d3d_disp_sw_cc".
        * Disable "d3d_disp_enable_distortionfx".
        * Set "d3d_disp_no_rgb10_buf" to prevent the game from running in
          enhanced 10-bits-per-channel RGB mode.
        * If you're running with DX6 then try DX9 (set "use_d3d_display").
    
    ----------------------------------------------------------------------
    
    Problem:
        Large frame rate fluctuations with AMD dual core CPUs on WinXP.
    Solution:
        * Install the AMD CPU driver.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game crashes or objects corrupted when loading savegames.
    Cause:
        Savegames from previous versions of Dark are not supported.
    Solutions:
        * Thief: Restart mission.
        * SS2: Restart game.
    
    ----------------------------------------------------------------------
    
    Problem:
        Some object textures or entire objects are invisible (on some
        ATI/AMD video cards).
    Cause:
        Adaptive multi-sample anti-aliasing.
    Solutions:
        * Go into Catalyst Control Center and set "Anti-Aliasing Mode" to
          any setting that is NOT "Adaptive Multi-sample AA".
        * Disable multi-sampling ("multisampletype").
    
    ----------------------------------------------------------------------
    
    Problem:
        Display mode fails to set or there are miscolorations (on some
        integrated video cards such as Intel).
    Solutions:
        * Update display drivers.
        * Set "d3d_disp_no_rgb10_buf" to prevent the game from running in
          enhanced 10-bits-per-channel RGB mode.
        * Disable multisampling ("multisampletype").
        * Disable postprocessing ("postprocess").
        * Disable "d3d_disp_enable_distortionfx".
        * Try DX6 (disable "use_d3d_display").
        * Look in cam_ext.cfg for more options to disable that affect
          performance.
    
    ----------------------------------------------------------------------
    
    Problem:
        Desired display mode (resolution/color depth) is not available in
        the game.
    Cause:
        Display mode is either not enumerated by DirectX or is not in the
        game's list of default resolutions.
    Solution:
        * If resolution is just missing from the game's internal list then
          you can add custom resolutions with "user_mode1", "user_mode2" etc.
          (see cam_ext.cfg and other docs for further info).
    
    ----------------------------------------------------------------------
    
    Problem:
        HUD text is garbled.
    Solution:
        * First make sure the game is patched to the latest version.
        * Try enabling "d3d_disp_force_rgba_atex".
        * Disable HW 2D overlay/HUD with "d3d_disp_2d_surf_mode 0".
    
    ----------------------------------------------------------------------
    
    Problem:
        A HUD item suddenly turns white.
    Solution:
        * Go back and forth once between menu and game (i.e. press ESC twice).
          A slight inconvenience but this way the benefits of HW 2D rendering,
          such as HUD scaling and increased performance, are preserved.
        * Disable HW 2D overlay/HUD with "d3d_disp_2d_surf_mode 0".
    
    ----------------------------------------------------------------------
    
    Problem:
        When running in windowed mode screenshots don't work or are only partial.
    Cause:
        Technical limitation.
    Solution:
        * Make sure that the window isn't partially offscreen and if you
          have multiple monitors the (entire) window has to be located
          on the monitor that is the active display in the game's video
          settings. For example it won't work if the active display is set to
          the secondary but the game/editor window is on the primary display.
    
    ----------------------------------------------------------------------
    
    Problem:
        Movies play at first but stop working and log file contains messages
        about ffmpeg.dll failing to load.
    Solution:
        * Try enabling "no_unload_ffmpeg".
    
    ----------------------------------------------------------------------
    
    Problem:
        EAX is not enabled/working.
    Solutions:
        * With some Creative cards (X-Fi, more?) make sure "Game Mode" is
          enabled in the Creative sound/driver settings.
        * Update your audio drivers.
        * Try OpenAL. OpenAL is enabled in the Audio options menu by
          cycling through your Hardware Acceleration options, and requires
          that OpenAL is installed on your system. See release notes.
    
    ----------------------------------------------------------------------
    
    Problem:
        Various issues with OpenAL.
    Solution:
        * Try a different OpenAL device; recommended device to try is
          "snd_oal_device Generic Software".
    
    ----------------------------------------------------------------------
    
    Problem:
        Motion sickness from playing the game.
    Solution:
        * Try enabling "bob_factor" and experiment with values (for SS2 you
          may also want to change "shock_gun_bob_factor").
    
    ----------------------------------------------------------------------
    
    Problem:
        Game or DromEd is running out or close to run out of memory (i.e.
        process uses between 1.5GB and 2GB memory. Especially noticable when
        using hires texture packs or FMs with loats of hires textures.
    Solution:
        * If you have 3GB or more system memory you can try to patch the
          EXE file to enable Large Address Aware, to allow the process to
          use more than 2GB memory. A patch utility "EnableLAA.exe" is
          included, just drag and drop the game (or editor) EXE on the
          "EnableLAA.exe" file (LAA can be disable in the same fashion).
          No guarantees are made that everything will work correctly with
          Large Address Aware enabled, but running out of memory isn't exactly
          healthy either so there's no harm in trying it.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game crashes after clicking any of the Skip/Play FM buttons in FM Selector.
        (on Windows 10 in particular)
    Solution:
        * Try enabling "no_unload_fmsel" in "cam_mod.ini".
    
    ----------------------------------------------------------------------
    
    Problem:
        There's a problem with DromEd/ShockEd.
    Solution:
        * See the separate DromEd troubleshooting document
          (troubleshooting_editor.txt).
    troubleshooting_editor
    Code:
    Most config vars mentioned here are found in cam_ext.cfg, so if no other
    .cfg file is explicitly mentioned, then cam_ext.cfg applies.
    
    Many problems have multiple possible solutions listed. Try each listed
    solution one at a time, not all of them at once.
    
    ----------------------------------------------------------------------
    
    Problem:
        Editor crashes, in particular after loading mission or portalizing
        anything (like the default cube), when solid view is enabled.
    Problem:
        The 3D view isn't updated after portalization.
    Problem:
        The camera marker looks partly miscolored.
    Cause:
        The editor is running in software render mode but the editor screen
        depth is set to 32-bit.
    Solutions:
        * Stick with software rendering and change bit depth to 16 by setting
          "edit_screen_depth 16" (usually in "dromed.cfg").
        * Enable hardware rendering by specifying/uncommenting "editor_disable_gdi"
          in "dromed.cfg".
    
    ----------------------------------------------------------------------
    
    Problem:
        Some editor menu entries like Save and Portalize don't do anything.
    Cause:
        You used the supplied "menus-sample.cfg" which states that it requires
        the DromEd/ShockEd Toolkit, but you haven't installed the Toolkit.
    Solutions:
        * Forget about "menus-sample.cfg" and install the latest Toolkit
          instead.
        * Revert to your old "menus.cfg" and edit it to add functionality
          of updated editor (such as recent files menu, "toggle_lighting"
          instead of "light_bright" and "lit_obj_toggle" etc.).
    
    ----------------------------------------------------------------------
    
    Problem:
        Lines in the viewports look dimmer than normal, or lines of the
        selected brush dims when viewport is updated, when running editor
        with hardware rendering.
    Solutions:
        * Disable anti-aliasing (MSAA) support in editor window by disabling
          "d3d_disp_hw2d_msaa" (disabled by default).
    
    ----------------------------------------------------------------------
    
    Problem:
        Some editor hotkeys are not working.
    Cause:
         Editor not properly installed or configured, "default.bnd" file
         possibly missing.
    Solutions:
        * Make sure "default.bnd" is present, and contains the key bindings
          you expect.
        * Make sure there are no conflicting binds in "user.bnd".
    
    ----------------------------------------------------------------------
    
    Problem:
        The numeric key pad isn't working to input number in editor input
        fields.
    Solution:
        * Make sure num-lock is on.

  20. #1195
    Member
    Registered: May 2015
    Quote Originally Posted by Unna Oertdottir View Post
    If you want help, give us informations. As always.
    Alright Mr. Snark, how about "I get a bugged flashing display on launch, and I can hear the menu in the background", oh wait that's right, I already included that information in my last post

  21. #1196
    Member
    Registered: May 2015
    Quote Originally Posted by voodoo47 View Post
    ->
    That appears to be related to integrated graphics? I'm not entirely sure what's going on in this case, but I do know it has something to do with the way Tafferpatcher is configured vs Tfix. They both implement NewDark, but Tafferpatcher must have something else going on. I'm going to reinstall everything and go from there.

  22. #1197
    Member
    Registered: May 2015
    Quote Originally Posted by Unna Oertdottir View Post
    Since nobody is reading the helpful instructions that come with the NewDark.zip, Tafferpatcher might include it.
    troubleshooting.txt
    Code:
    Most config vars mentioned here are found in cam_ext.cfg, so if no other
    .cfg file is explicitly mentioned, then cam_ext.cfg applies.
    
    Many problems have multiple possible solutions listed. Try each listed
    solution one at a time, not all of them at once.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, says D3DX9_43.DLL is missing.
    Cause:
        The (correct) DX runtime libraries have not been installed.
    Solution:
        * Read the release notes again and install the "DirectX End-User
          Runtimes (June 2010)" linked to in the release notes.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, says D3DX9_43.DLL is missing even though I
        downloaded the DX runtimes and ran the downloaded EXE file.
    Cause:
        The DX runtime libraries have not been installed.
    Solution:
        * Running the downloaded DX runtimes EXE (directx_Jun2010_redist.exe)
          will only extract the DX installer to a temporary location (of
          your choice). You then have to open that location and run the
          actual DX installer called DXSETUP.EXE. (The temporary installer
          files can be deleted after installation is complete, so it's
          advisable to extract it to a new/empty directory.)
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, says that the side-by-side configuration is
        incorrect (or maybe that MSVCR90.DLL/MSVCP90.DLL is missing).
    Cause:
        The correct Visual Studio runtime libraries have not been installed.
    Solution:
        * Read the release notes again and install the "Visual Studio 2008
          SP1 C++ runtimes" linked to in the release notes.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game won't start, log file indicates that no supported hardware
        3D devices were found.
    Causes:
        Hardware 3D acceleration has been disabled in the driver or Windows,
        or no display modes were found that are supported by both the game
        and the video adapter.
    Solutions:
        * To determine that 3D acceleration is working properly, go to
          http://support.microsoft.com/kb/191660 for further information.
        * If no (supported) display modes were found then that's often
          related to monitors in portrait orientation. Adding user defined
          display modes usually solves that. See "user_mode" config vars
          in "doc\new_config_vars.txt" and/or "cam_ext.cfg".
    
    ----------------------------------------------------------------------
    
    Problem:
        Game crashes at startup.
    Cause:
        Configuration error/issue.
    Solutions:
        * Make sure the pathnames in darkinst.cfg (T2) / install.cfg (SS2)
          for resname_base, movie_path, load_path, script_module_path and
          install_path point to the correct locations. Re-install if
          necessary.
        * On some asian systems when the Windows input language is set to
          IME 2010 (/Microsoft Office IME 2010) it can help to change to
          regular IME (no 2010). The input language options can be found
          in the Windows control panel under "Region and Language" ->
          "Keyboards and Languages". 
        * Sometimes the default resolution of 640x480 doesn't work, Manually
          setting the game resolution to the same resolution as the Windows
          desktop can help. Edit "cam.cfg" and add the line (or change it
          if it already exists) "game_screen_size  ".
          For example if your desktop is 1600x900: "game_screen_size 1600 900".
    
    ----------------------------------------------------------------------
    
    Problem:
        Player seems to hover at peak of jumps, and/or moves way too slow.
    Cause:
        Frame rate too high.
    Solutions:
        * Make sure your graphics driver settings doesn't force disabled
          vsync (set it to application preference or at least enable forced
          vsync).
        * Cap the frame rate with software frame rate limiter (set
          "framerate_cap 100" or less).
        * If you've previously disabled vsync through "vsync_mode" then
          enable it again.
    
    ----------------------------------------------------------------------
    
    Problem:
        Uneven/jerky frame rate and/or laggy mouse movement even though the
        system should be fast enough to do better.
    Cause:
        Computer is rendering too many frames in advance.
    Solutions:
        * Set "d3d_disp_limit_gpu_frames 1 1".
        * Set frame rate limiter ("framerate_cap") to a frame rate slightly
          above the monitor refresh rate (for example 70 to 80 for a 60Hz
          monitor).
    
    ----------------------------------------------------------------------
    
    Problem:
        Low frame rate.
    Solutions:
        * Decrease display resolution.
        * Disable multisampling ("multisampletype").
        * Disable floating point render buffers ("d3d_disp_enable_hdr").
        * Disable postprocessing ("postprocess").
        * Disable "d3d_disp_sw_cc".
        * Disable "d3d_disp_enable_distortionfx".
        * Set "d3d_disp_no_rgb10_buf" to prevent the game from running in
          enhanced 10-bits-per-channel RGB mode.
        * If you're running with DX6 then try DX9 (set "use_d3d_display").
    
    ----------------------------------------------------------------------
    
    Problem:
        Large frame rate fluctuations with AMD dual core CPUs on WinXP.
    Solution:
        * Install the AMD CPU driver.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game crashes or objects corrupted when loading savegames.
    Cause:
        Savegames from previous versions of Dark are not supported.
    Solutions:
        * Thief: Restart mission.
        * SS2: Restart game.
    
    ----------------------------------------------------------------------
    
    Problem:
        Some object textures or entire objects are invisible (on some
        ATI/AMD video cards).
    Cause:
        Adaptive multi-sample anti-aliasing.
    Solutions:
        * Go into Catalyst Control Center and set "Anti-Aliasing Mode" to
          any setting that is NOT "Adaptive Multi-sample AA".
        * Disable multi-sampling ("multisampletype").
    
    ----------------------------------------------------------------------
    
    Problem:
        Display mode fails to set or there are miscolorations (on some
        integrated video cards such as Intel).
    Solutions:
        * Update display drivers.
        * Set "d3d_disp_no_rgb10_buf" to prevent the game from running in
          enhanced 10-bits-per-channel RGB mode.
        * Disable multisampling ("multisampletype").
        * Disable postprocessing ("postprocess").
        * Disable "d3d_disp_enable_distortionfx".
        * Try DX6 (disable "use_d3d_display").
        * Look in cam_ext.cfg for more options to disable that affect
          performance.
    
    ----------------------------------------------------------------------
    
    Problem:
        Desired display mode (resolution/color depth) is not available in
        the game.
    Cause:
        Display mode is either not enumerated by DirectX or is not in the
        game's list of default resolutions.
    Solution:
        * If resolution is just missing from the game's internal list then
          you can add custom resolutions with "user_mode1", "user_mode2" etc.
          (see cam_ext.cfg and other docs for further info).
    
    ----------------------------------------------------------------------
    
    Problem:
        HUD text is garbled.
    Solution:
        * First make sure the game is patched to the latest version.
        * Try enabling "d3d_disp_force_rgba_atex".
        * Disable HW 2D overlay/HUD with "d3d_disp_2d_surf_mode 0".
    
    ----------------------------------------------------------------------
    
    Problem:
        A HUD item suddenly turns white.
    Solution:
        * Go back and forth once between menu and game (i.e. press ESC twice).
          A slight inconvenience but this way the benefits of HW 2D rendering,
          such as HUD scaling and increased performance, are preserved.
        * Disable HW 2D overlay/HUD with "d3d_disp_2d_surf_mode 0".
    
    ----------------------------------------------------------------------
    
    Problem:
        When running in windowed mode screenshots don't work or are only partial.
    Cause:
        Technical limitation.
    Solution:
        * Make sure that the window isn't partially offscreen and if you
          have multiple monitors the (entire) window has to be located
          on the monitor that is the active display in the game's video
          settings. For example it won't work if the active display is set to
          the secondary but the game/editor window is on the primary display.
    
    ----------------------------------------------------------------------
    
    Problem:
        Movies play at first but stop working and log file contains messages
        about ffmpeg.dll failing to load.
    Solution:
        * Try enabling "no_unload_ffmpeg".
    
    ----------------------------------------------------------------------
    
    Problem:
        EAX is not enabled/working.
    Solutions:
        * With some Creative cards (X-Fi, more?) make sure "Game Mode" is
          enabled in the Creative sound/driver settings.
        * Update your audio drivers.
        * Try OpenAL. OpenAL is enabled in the Audio options menu by
          cycling through your Hardware Acceleration options, and requires
          that OpenAL is installed on your system. See release notes.
    
    ----------------------------------------------------------------------
    
    Problem:
        Various issues with OpenAL.
    Solution:
        * Try a different OpenAL device; recommended device to try is
          "snd_oal_device Generic Software".
    
    ----------------------------------------------------------------------
    
    Problem:
        Motion sickness from playing the game.
    Solution:
        * Try enabling "bob_factor" and experiment with values (for SS2 you
          may also want to change "shock_gun_bob_factor").
    
    ----------------------------------------------------------------------
    
    Problem:
        Game or DromEd is running out or close to run out of memory (i.e.
        process uses between 1.5GB and 2GB memory. Especially noticable when
        using hires texture packs or FMs with loats of hires textures.
    Solution:
        * If you have 3GB or more system memory you can try to patch the
          EXE file to enable Large Address Aware, to allow the process to
          use more than 2GB memory. A patch utility "EnableLAA.exe" is
          included, just drag and drop the game (or editor) EXE on the
          "EnableLAA.exe" file (LAA can be disable in the same fashion).
          No guarantees are made that everything will work correctly with
          Large Address Aware enabled, but running out of memory isn't exactly
          healthy either so there's no harm in trying it.
    
    ----------------------------------------------------------------------
    
    Problem:
        Game crashes after clicking any of the Skip/Play FM buttons in FM Selector.
        (on Windows 10 in particular)
    Solution:
        * Try enabling "no_unload_fmsel" in "cam_mod.ini".
    
    ----------------------------------------------------------------------
    
    Problem:
        There's a problem with DromEd/ShockEd.
    Solution:
        * See the separate DromEd troubleshooting document
          (troubleshooting_editor.txt).
    troubleshooting_editor
    Code:
    Most config vars mentioned here are found in cam_ext.cfg, so if no other
    .cfg file is explicitly mentioned, then cam_ext.cfg applies.
    
    Many problems have multiple possible solutions listed. Try each listed
    solution one at a time, not all of them at once.
    
    ----------------------------------------------------------------------
    
    Problem:
        Editor crashes, in particular after loading mission or portalizing
        anything (like the default cube), when solid view is enabled.
    Problem:
        The 3D view isn't updated after portalization.
    Problem:
        The camera marker looks partly miscolored.
    Cause:
        The editor is running in software render mode but the editor screen
        depth is set to 32-bit.
    Solutions:
        * Stick with software rendering and change bit depth to 16 by setting
          "edit_screen_depth 16" (usually in "dromed.cfg").
        * Enable hardware rendering by specifying/uncommenting "editor_disable_gdi"
          in "dromed.cfg".
    
    ----------------------------------------------------------------------
    
    Problem:
        Some editor menu entries like Save and Portalize don't do anything.
    Cause:
        You used the supplied "menus-sample.cfg" which states that it requires
        the DromEd/ShockEd Toolkit, but you haven't installed the Toolkit.
    Solutions:
        * Forget about "menus-sample.cfg" and install the latest Toolkit
          instead.
        * Revert to your old "menus.cfg" and edit it to add functionality
          of updated editor (such as recent files menu, "toggle_lighting"
          instead of "light_bright" and "lit_obj_toggle" etc.).
    
    ----------------------------------------------------------------------
    
    Problem:
        Lines in the viewports look dimmer than normal, or lines of the
        selected brush dims when viewport is updated, when running editor
        with hardware rendering.
    Solutions:
        * Disable anti-aliasing (MSAA) support in editor window by disabling
          "d3d_disp_hw2d_msaa" (disabled by default).
    
    ----------------------------------------------------------------------
    
    Problem:
        Some editor hotkeys are not working.
    Cause:
         Editor not properly installed or configured, "default.bnd" file
         possibly missing.
    Solutions:
        * Make sure "default.bnd" is present, and contains the key bindings
          you expect.
        * Make sure there are no conflicting binds in "user.bnd".
    
    ----------------------------------------------------------------------
    
    Problem:
        The numeric key pad isn't working to input number in editor input
        fields.
    Solution:
        * Make sure num-lock is on.
    Shockingly my issue isn't addressed within this mess, because if it was I would have already figured it out for myself, and/or you would have pointed out something more specific than a useless wall of text. Welcome to my list of annoyingly useless people, it's a rather long list...

  23. #1198
    Member
    Registered: May 2015
    Quote Originally Posted by voodoo47 View Post
    ->
    Hmm, that did in fact do the trick, thank you. I don't understand what that setting is related to though, the description states something about integrated graphics, but a gtx 960 hardly qualifies as integrated graphics. Does that setting really work for anyone, or would it be best if it were disabled by default as it is in Tfix?

  24. #1199
    Dóttirin klęšist oft móšur möttli
    Registered: Apr 2015
    This list wasn't addressed to you, but to DJ Riff, the maintainer of Tafferpatcher. Of course.
    Quote Originally Posted by mikjames View Post
    Welcome to my list of annoyingly useless people, it's a rather long list...
    Cool down.

  25. #1200
    Zombified
    Registered: Sep 2004
    it does work, and the (sky) quality improvement is not negligible, but unfortunately, it seems like every win10 update makes it incompatible with more and more graphics cards.

    TFix currently auto disables it for all steam users, and will probably disable it for everyone in the near future.


    and yeah, a TafferPatcher update that would address this (and a couple of other small things) would be nice - again, if someone knows what's up with DJ Riff, has some means to contact him, or maybe has access to the TafferPatcher source..
    Last edited by voodoo47; 30th Oct 2017 at 16:29.

Page 48 of 49 FirstFirst ... 3813182328333843444546474849 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •