TERA CTD on startup!
- hallowieners
-
Topic Author
More
- crosire
-
More
- hallowieners
-
More
- JBeckman
-
More
8 years 6 months ago - 8 years 6 months ago #4
by JBeckman
Replied by JBeckman on topic TERA CTD on startup!
www.microsoft.com/en-gb/download/details.aspx?id=8109
You could try the full version, my opinion is that it should have been part of Windows by default but for some reason MS decided to leave out some of the additional DirectX component unless you install this.
(Or run the web version which will check and update as required but running the full version doesn't hurt, just that it hasn't been updated since 2010 though the components are still used in newer versions of Windows so it's a good idea to ensure it's been installed.)
EDIT: I think that by default you only have the "core" of DirectX installed whereas this installs the "add-on" components and subversions such as the various _xx files where "xx" is a number up to I think the newest is 47
(There's probably a more accurate term for this with the DirectX documentation and it's SDK which is now included with the Windows SDK as a single larger install for developing on Windows.)
Most of the components are up to date with Windows 7 but since this runtime hasn't been updated in a few years (And instead it's now part of the larger Windows SDK and it's DirectX components.) anyways there's a few newer components with Windows 8 and D3D11.x which Microsoft didn't include with the OS so games using these generally have those files in their binary folders and they are not included in the above DirectX install, I believe that it's the D3DCompiler_46.dll primarily. (D3D11.1 related I think.)
With 8.1 Microsoft actually included the new DirectX files by default (D3DCompiler_47.dll primarily, I think it's for D3D11.2 but it might be used in other DX API's too for all I know.) so it seems to be a bit random if components are included with Windows or separated and left to the SDK and then distributed on a per-game basis though the older runtimes are as mentioned still not part of a default Windows install and have to be installed separately.
(It's a bit different from one runtime to another on how you are allowed to redistribute the files or the installer, for the VC++ runtimes I believe you are only allowed to include the MS installer and not the actual component .dll files.)
If you use Steam or Origin or UPlay most of the games will actually contain runtime redistributable files for DirectX, .Net and VC++ (2005 to 2015 depending on the game.) so it's highly likely you actually have a up to date DirectX install already but it doesn't hurt to re-install it, it won't overwrite anything if it already exists.
Anyway that's nothing important, check the full redist above (It's from Microsoft directly so it's clean.) and see if that fixes the error though if the web installer already said it was up to date it should already be installed, likely as part of another game setup via one of the digital download clients, Steam primarily but Origin and UPlay have similar systems for these required runtimes.
You could try the full version, my opinion is that it should have been part of Windows by default but for some reason MS decided to leave out some of the additional DirectX component unless you install this.
(Or run the web version which will check and update as required but running the full version doesn't hurt, just that it hasn't been updated since 2010 though the components are still used in newer versions of Windows so it's a good idea to ensure it's been installed.)
EDIT: I think that by default you only have the "core" of DirectX installed whereas this installs the "add-on" components and subversions such as the various _xx files where "xx" is a number up to I think the newest is 47
(There's probably a more accurate term for this with the DirectX documentation and it's SDK which is now included with the Windows SDK as a single larger install for developing on Windows.)
Most of the components are up to date with Windows 7 but since this runtime hasn't been updated in a few years (And instead it's now part of the larger Windows SDK and it's DirectX components.) anyways there's a few newer components with Windows 8 and D3D11.x which Microsoft didn't include with the OS so games using these generally have those files in their binary folders and they are not included in the above DirectX install, I believe that it's the D3DCompiler_46.dll primarily. (D3D11.1 related I think.)
With 8.1 Microsoft actually included the new DirectX files by default (D3DCompiler_47.dll primarily, I think it's for D3D11.2 but it might be used in other DX API's too for all I know.) so it seems to be a bit random if components are included with Windows or separated and left to the SDK and then distributed on a per-game basis though the older runtimes are as mentioned still not part of a default Windows install and have to be installed separately.
(It's a bit different from one runtime to another on how you are allowed to redistribute the files or the installer, for the VC++ runtimes I believe you are only allowed to include the MS installer and not the actual component .dll files.)
If you use Steam or Origin or UPlay most of the games will actually contain runtime redistributable files for DirectX, .Net and VC++ (2005 to 2015 depending on the game.) so it's highly likely you actually have a up to date DirectX install already but it doesn't hurt to re-install it, it won't overwrite anything if it already exists.
Anyway that's nothing important, check the full redist above (It's from Microsoft directly so it's clean.) and see if that fixes the error though if the web installer already said it was up to date it should already be installed, likely as part of another game setup via one of the digital download clients, Steam primarily but Origin and UPlay have similar systems for these required runtimes.
Last edit: 8 years 6 months ago by JBeckman.
Please Log in or Create an account to join the conversation.
- crosire
-
More
- hallowieners
-
More
- crosire
-
More
- hallowieners
-
More
- JBeckman
-
More
8 years 6 months ago - 8 years 6 months ago #9
by JBeckman
Replied by JBeckman on topic TERA CTD on startup!
Is it a specific preset you are using or did you download the default 1.00 version from here?
If you did not download ReShade from here you could try that and then start the game when you are using the default ReShade files and that could tell if it's something with that particular preset or not, of course if you're already using the original 1.00 release from this website this won't really be of much help.
TERA is using CryEngine I believe which I don't think there's any particular compatibility problems with unless as a MMO they use some form of anti-cheat detection which could block ReShade or just trigger the game to crash when it detects ReShade trying to inject into the game data.
I'll search around a bit to see if there's some more info on TERA and ReShade compatibility, I also noticed from the tracelog that you have the game on the
drive (There's no real personal info in that file but it shows from where the game was started with full folder paths.) but I don't think ReShade has a issue with such setups though some older games have had problems if they can't access a Documents folder on the drive where the game was installed but that doesn't have anything to do with this issue.
(Pretty sure the tracelog mentioned the game using DirectX 9 and being 32-bit as well so no issues there, something when it tries to compile some triangle shader and then it crashes which is probably why Crosire asked about the D3D compiler files since that's where it looks like things fall apart.)
EDIT: Tera is UE3 it seems, I don't think that's a issue either (There is a problem with UE4 however but that's not the problem here.) and ReShade does attempt to load and initialize when the game is started so it's something else later on in that process.
(UE3 can have problems initializing the depth buffer hook of ReShade or well ReShade has problems grabbing the depth info from UE3 but as a MMO game it will be blocked anyway as part of the protection in ReShade to avoid exploits in multiplayer as it turns off the depth detection when network traffic is detected.)
EDIT: Can't find anything on if ReShade has any problems with TERA, just the usual advice on how you should make sure the anti-virus solution isn't blocking things or other overlays causing conflicts.
(Running as admin might help but as the game is located on a separate HDD Windows UAC shouldn't try to block it though I don't know how it works when ReShade is injected, probably terrible advice but you could always try to copy D3DCompiler_43.dll from SysWoW64 into the bin folder of TERA and see if that helps but I don't think it will and it's best to leave system files alone but if you do try it remember to copy the file, never move files from the Windows folder.)
(Actually it's probably a terrible practice to leave system files in other folders but some programs do so anyway, xinput1_3.dll is pretty common to find in various game folders and programs such as UPlay and then there's the earlier mentioned d3dcompiler_46.dll which I think is used in most Frostbite and CryEngine engine game installs and also other programs such as for example Firefox and EA Origin though with that particular file there's not much of a choice since it's neither part of Windows by default nor part of the current DirectX runtime redistributable.)
If you did not download ReShade from here you could try that and then start the game when you are using the default ReShade files and that could tell if it's something with that particular preset or not, of course if you're already using the original 1.00 release from this website this won't really be of much help.
TERA is using CryEngine I believe which I don't think there's any particular compatibility problems with unless as a MMO they use some form of anti-cheat detection which could block ReShade or just trigger the game to crash when it detects ReShade trying to inject into the game data.
I'll search around a bit to see if there's some more info on TERA and ReShade compatibility, I also noticed from the tracelog that you have the game on the
drive (There's no real personal info in that file but it shows from where the game was started with full folder paths.) but I don't think ReShade has a issue with such setups though some older games have had problems if they can't access a Documents folder on the drive where the game was installed but that doesn't have anything to do with this issue.(Pretty sure the tracelog mentioned the game using DirectX 9 and being 32-bit as well so no issues there, something when it tries to compile some triangle shader and then it crashes which is probably why Crosire asked about the D3D compiler files since that's where it looks like things fall apart.)
EDIT: Tera is UE3 it seems, I don't think that's a issue either (There is a problem with UE4 however but that's not the problem here.) and ReShade does attempt to load and initialize when the game is started so it's something else later on in that process.
(UE3 can have problems initializing the depth buffer hook of ReShade or well ReShade has problems grabbing the depth info from UE3 but as a MMO game it will be blocked anyway as part of the protection in ReShade to avoid exploits in multiplayer as it turns off the depth detection when network traffic is detected.)
EDIT: Can't find anything on if ReShade has any problems with TERA, just the usual advice on how you should make sure the anti-virus solution isn't blocking things or other overlays causing conflicts.
(Running as admin might help but as the game is located on a separate HDD Windows UAC shouldn't try to block it though I don't know how it works when ReShade is injected, probably terrible advice but you could always try to copy D3DCompiler_43.dll from SysWoW64 into the bin folder of TERA and see if that helps but I don't think it will and it's best to leave system files alone but if you do try it remember to copy the file, never move files from the Windows folder.)
(Actually it's probably a terrible practice to leave system files in other folders but some programs do so anyway, xinput1_3.dll is pretty common to find in various game folders and programs such as UPlay and then there's the earlier mentioned d3dcompiler_46.dll which I think is used in most Frostbite and CryEngine engine game installs and also other programs such as for example Firefox and EA Origin though with that particular file there's not much of a choice since it's neither part of Windows by default nor part of the current DirectX runtime redistributable.)
Last edit: 8 years 6 months ago by JBeckman.
Please Log in or Create an account to join the conversation.
- hallowieners
-
More
I downloaded the default version. I've also tried a custom preset but that I still crashed.
I just tried copying the D3DCompiler_43.dll to TERA's directory, but that didn't seem to alleviate the crash.
Thanks for the extra info though.
I just tried copying the D3DCompiler_43.dll to TERA's directory, but that didn't seem to alleviate the crash.
Thanks for the extra info though.
Please Log in or Create an account to join the conversation.
- amckinlay
-
More
- amckinlay
-
More
- SingAlongThemeSong
-
More
8 years 5 months ago #13
by SingAlongThemeSong
Replied by SingAlongThemeSong on topic TERA CTD on startup!
Hey everyone!
I've got some curious info to add to this mystery. I was in the same situation a few months ago with TERA CTDing on startup. After some searching on Google, there seems to be an issue with the newer versions of Reshade and TERA, causing immediate CTDs. Apparently, only the older versions of Reshade work with TERA. I'm not a programmer so I have no idea why TERA stopped working with newer versions of Reshade.
Looking at my TERA folder, it says version "0.18.0.832" of Reshade is being used.
So if you absolutely have to use Reshade, you should probably find a version around that number(OR just use Sweetfx?). It's a bit of a shame though, because all the new stuff is really fantastic, and like the compat page says, none of the depthbuffer-dependent effects work
I've got some curious info to add to this mystery. I was in the same situation a few months ago with TERA CTDing on startup. After some searching on Google, there seems to be an issue with the newer versions of Reshade and TERA, causing immediate CTDs. Apparently, only the older versions of Reshade work with TERA. I'm not a programmer so I have no idea why TERA stopped working with newer versions of Reshade.
Looking at my TERA folder, it says version "0.18.0.832" of Reshade is being used.
Warning: Spoiler!
: warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
Warning: Spoiler!
So if you absolutely have to use Reshade, you should probably find a version around that number(OR just use Sweetfx?). It's a bit of a shame though, because all the new stuff is really fantastic, and like the compat page says, none of the depthbuffer-dependent effects work
Please Log in or Create an account to join the conversation.
- crosire
-
More
- amckinlay
-
More
- SingAlongThemeSong
-
More
- crosire
-
More
- SingAlongThemeSong
-
More
- amckinlay
-
More
- crosire
-
More