CFS3Config error

ok! that is a lot of information to digest! I'm an FS2004 man myself and used to a .cfg file rather than a .xml file. I will try this out and see how it goes. right now I just want to get the ankors installed, and maybe go into the editing process in the future.
 
attachment.php
attachment.php

so I get this when I do the first step. however, when I take the files out of the CFS3 install, it works fine.
 

Attachments

  • error1.jpg
    error1.jpg
    72.2 KB · Views: 10
  • error2.jpg
    error2.jpg
    44.8 KB · Views: 12
Are you being asked to re run cfg exe afterv installing the 3 shaders folder/files?

Are you using the config.exe file to set up your cfg or are you going straight into the xml (if so, doing what)?

Try something like MajorMagees in the appdata folder below is my version of his (AFAIK!) You should open your configOverrides.xml in appdata AFTER you have set up your config by running the cfg.exe. Then copy mine from

<TextureLimits>
<aircr......................................................

and below to the end. Above that I believe is more related to your own setup. Andy, feel free to correct me!:wavey:


<Config>
<FileVersion val="60"/>
<Adapter val="0"/>
<Device val="0"/>
<Mode val="35"/>
<MultisampleType val="D3DMULTISAMPLE_NONE"/>
<VendorId val="4318"/>
<DeviceId val="5058"/>
<VersionNumberLowPart val="0"/>
<VersionNumberHighPart val="589824"/>
<TextureLimits>
<aircraftmodels Scale="0" MaxDim="4096"/>
<compositeterrain Scale="0" MaxDim="4096"/>
<compositeterrainsource Scale="0" MaxDim="4096"/>
<effects Scale="0" MaxDim="4096"/>
<hud Scale="0" MaxDim="4096"/>
<nonaircraftmodels Scale="0" MaxDim="4096"/>
<precompiledterrain Scale="0" MaxDim="4096"/>
<shadows Scale="0" MaxDim="4096"/>
<ui Scale="0" MaxDim="4096"/>
<uncategorized Scale="0" MaxDim="4096"/>
</TextureLimits>
<ConfigOverrides>
<DisableWarningBoxes val="n"/>
<DisableSound val="n"/>
<DisableIntroMovie val="y"/>
<DisableMovieUI val="n"/>
<DisableUIAnimations val="n"/>
<SafeMode val="n"/>
<NoDXT1 val="n"/>
<NoDXT3 val="n"/>
<NoDXT5 val="n"/>
<DisableIndexBuffers val="n"/>
<DisableVertexBuffers val="n"/>
<Disable1600x1200 val="n"/>
<Disable1280x1024 val="n"/>
<Disable1024x768 val="n"/>
<DualPassRender val="n"/>
<HighResolutionZBuffer val="y"/>
<TerrainDetailTexture val="y"/>
<DisableWindowed val="n"/>
<DisableValidateDevice val="y"/>
<DisableWriteOnlyVB val="n"/>
<DisableWriteOnlyIB val="n"/>
<DisableTriangleStrips val="n"/>
<UnsupportedHardware val="n"/>
<UnsupportedDriver val="n"/>
<DisableCompositeTerrainTextureMips val="n"/>
<DisableCompositeTerrainTextures val="n"/>
<DisableCompositeGroundPlaneTextures val="n"/>
<DisableCompositeAircraftTextures val="n"/>
<DisableScenery val="n"/>
<DisableEnvironmentMapping val="n"/>
<DisableShadows val="y"/>
<DisableWhiteOut val="n"/>
<DisableTerrainLighting val="n"/>
<DisableSceneryLighting val="n"/>
<DisableSun val="n"/>
<DisableStars val="n"/>
<DisableRenderText val="n"/>
<DisableLabels val="n"/>
<DisableTacticalDisplay val="n"/>
<DisableTargetCone val="n"/>
<DisableHUD val="n"/>
<DisableChat val="n"/>
<DisableAdvisor val="n"/>
<DisableSimWarnings val="n"/>
<DisableTimeCompress val="n"/>
<DisableWeather val="n"/>
<DisableClouds val="n"/>
<DisableBlendToOffscreen val="n"/>
<DisableClear val="n"/>
<DisableTerrainRender val="n"/>
<DisableTerrainUpdate val="n"/>
<DisableSceneDBRender val="n"/>
<DisableWaterRender val="n"/>
<DisableWaterShorelineRender val="n"/>
<DisableWaterReflectionRender val="n"/>
<DisableWaterAnimationRender val="n"/>
<DisableTerrainTextureRingBlend val="n"/>
<DisableFog val="n"/>
<DisableRain val="n"/>
<DisableTexturedAlphaMaterial val="n"/>
<DisableShellCasings val="n"/>
<DisableTerrainDiffuseLighting val="n"/>
<DisableTerrainDecalRender val="n"/>
<DisableVCFog val="n"/>
<DisableInCloudEffect val="n"/>
<DisablePropDiscs val="n"/>
<CompositeAircraftTextureBudget val="10240"/>
<CompositeAircraftTextureMaxDim val="4096"/>
<CompositeAircraftTexturePool val="D3DPOOL_DEFAULT"/>
<CompositeAircraftTextureUsage val="D3DUSAGE_RENDERTARGET"/>
<CompositeTerrainTextureBudget val="five"/>
<VertexBufferPool val="D3DPOOL_DEFAULT"/>
<IndexBufferPool val="D3DPOOL_DEFAULT"/>
<PreCompiledTerrainTextureBudget val="four"/>
<UserShadowTextureBudget val="1"/>
<AIShadowTextureBudget val="30"/>
<ObjectShadowTextureBudget val="500"/>
<UserShadowSize val="512"/>
<AIShadowSize val="256"/>
<ObjectShadowSize val="256"/>
<MaxParticles val="2000000"/>
<ZBiasBitsResolution val="15"/>
<ZBiasTerrainDecal val="0"/>
<ZBiasWaterPolyNear val="1"/>
<ZBiasWaterPolyFar val="0"/>
<ZBiasWaterLineNear val="1"/>
<ZBiasWaterLineFar val="0"/>
<ZBiasFlatEffects val="25"/>
<ZBiasShadow val="0"/>
<ZBiasTerrainAlphaNear val="0"/>
<ZBiasTerrainAlphaFar val="0"/>
<ZBiasObject val="0"/>
<ZBiasObjectFar val="0"/>
<ZBiasEffects val="1"/>
<ZBiasClouds val="1"/>
<TerrainVertexBufferCapacity val="16384"/>
<TerrainIndexBufferCapacity val="32768"/>
<VertexCacheSize val="15"/>
<BackClipDist val="128748"/>
<InteriorWaterLoadingFactor val="0.5"/>
<WaterDetailTextureSize val="5"/>
<WaterElevationBias val="4"/>
<WaterElevationBiasFactor val="0.5"/>
<NearPassBackClipDist val="13200"/>
<FarPassNearClipDist val="13000"/>
<FogStartDist val="128748"/>
<CloudScale val="10"/>
<TerrainBestImageQuality val="0"/>
<MaxLandClassVariations val="0"/>
<TerrainMaxBlenderInstPerFrameNear val="256"/>
<TerrainMaxBlenderInstPerFrameFar val="128"/>
<SceneryTriangleBudget val="five"/>
<TerrainTriangleBudget val="five"/>
<MaxModelLOD val="100"/>
<FullscreenSwapEffect val="D3DSWAPEFFECT_DISCARD"/>
<CompositeTerrainTexturePool val="D3DPOOL_DEFAULT"/>
<CompositeTerrainTextureUsage val="0"/>
<TextMaxTextures val="0"/>
<OverallGraphicDetail val="5"/>
<AircraftDetail val="5"/>
<SceneryDetail val="5"/>
<TerrainDetail val="5"/>
<EffectsQuality val="5"/>
<CloudsQuality val="5"/>
</ConfigOverrides>
</Config>
 
Last edited:
If you check the properties of your cfs3.exe file what file version does it show? Mine is 3.1.0.30203. I know that the shaders have trouble recognizing some of the older revisions of cfs3.exe and this has been a problem for a few people.

The part of the config file content that is the most machine specific and will need to match your GPU is
<VendorId val="4318"/> (Nvidia)
<DeviceId val="5056"/> (GTX 980)

The part that AnKor's Shaders look at to make it so you don't have to rerun cfs3config.exe every time you update your video drivers is
<VersionNumberLowPart val="0"/>
<VersionNumberHighPart val="589824"/>

If you have a copy of CFS3 working without the shaders installed, then make a copy of the
ConfigOverrides.xml in the \AppData\Roaming\Microsoft\CFS3 folder. This will insure you have settings that work with your system. Change the version number lines in your copied ConfigOverrides.xml to match the ones needed for AnKor's Shaders, and use that copy after you installed the shader related files.

By default, I have xml files set to edit as text with notepad on my system (Win 10)
 
it is 3.1.0.30203 the same as yours. I believe I am getting in over my head. I don't really understand much of what you are explaining, as I'm not a techy person. could you possibly try to explain how to even correctly use the CFS3Config.exe? that might be a start, as I cannot seem to figure out how to edit things with it. It simply runs, says it is configured, and then closes.
 
There’s a well known, often forgotten bug in the config program that if you edit the config with it and just close with the X button your changes are forgotten. You must use the menu to save and close.
 
ok. so I did all that, and I copied over the shaders folder, the d3d8.ini and .dll files. I have found that everything works properly until I add the d3d8.dll file to the main CFS3 folder. then when I try and run CFS3, it says my config file is outdated. I exited the CFS3 and tried to run the CFS3Config.exe which always says: CFS3Config.exe has stopped responding. this only happens when I have the d3d8.dll file copied to the main CFS3 folder.
 
ok. so I did all that, and I copied over the shaders folder, the d3d8.ini and .dll files. I have found that everything works properly until I add the d3d8.dll file to the main CFS3 folder. then when I try and run CFS3, it says my config file is outdated. I exited the CFS3 and tried to run the CFS3Config.exe which always says: CFS3Config.exe has stopped responding. this only happens when I have the d3d8.dll file copied to the main CFS3 folder.

Try something simpler. When you get to the stage when, after adding d3d8.dll it asks you to run cfs3config.exe, just close out of the game and restart the game. Ignore the need to redo the config.exe (if you are happy with the contents of the configoverrides.xml). Once the shaders get traction, they will override cfs3's insistence that the config needs redoing. There is actually a line in Ankor's latest shaders which fools CFS3 into not asking to rerun the cfs3config.exe.

So just shut down, and start CFS3 again. I think the mistake is to try to re-run cfs3config.exe after installation of the shaders.
 
could be Hornet just belongs to the few unlucky ones, who cant run the Ankors at all, any way.

well, in case of a later system then WinXp is used to run CFS3, the admin mode and older system compatibility for any .exe files should be checked. next issue can be, and usually is, is the DirectX drivers. DirectX9 should solve it, see DirectX End-User Runtime Installer.

supposing a small percentual value only of CSF3 players owns a PC/notepad which their videocard doesnt support the game Ankors injected. still it can happen.
 
I second BoreK's statement. I can't run the shaders package with my current laptop. I'm one of the unlucky few. Try all you can but if all else fails then it may not be a option for you to use this feature.
 
well, Ive tested the CFS3 on a few PC rigs where one of them really wasnt Ankors compatible doe the very weak videocard, but it literarly said to me something like this is not supported there.

however I still believe all your issues are just a matter of drivers - in case the other Ankors how-to run steps has been achieved correctly.
 
the Ankors are DirecX9 infact, so your GT430 should be ok.

Ive looked hows that solved at WOFF, as we know its Ankors defaulty injected. the readme says:


"IMPORTANT REQUIREMENT:Install DirectX 91) You need to install the full DirectX 9 install from Microsoft.Yes even in Windows 7, 8, 8.1 or 10. Yes even if Windows tells you not to, and yes even if you think it’salready included/built-in/installed whatever, no excuses you must do this!

(Note the direct X 9 installation file is in your C:\OBDSoftware\WOFF\Toolbox\DX9Redist folder. The file is called directx_Jun2010_redist.exe (if you installed elsewhere look for the Toolbox\DX9Redist folder there)

Or download from: http://www.microsoft.com/en-us/download/details.aspx?id=8109

Or download from SIMHQ:http://simhq.com/forum/ubbthreads.php/topics/3555696/Direct_X9_June_2010_Redist.html

Now run the directx_Jun2010_redist.exe file, it is a “self-extracting” compressed file. It will unpack thefiles contained inside itself to a temporary folder of your choice. So do that, then once it unpacks now goto that temporary folder you chose and run the DXSetup to install it. You must do this step, or it won’tbe installed!

DirectX 12, 11 and 9 do not conflict with each other. You can install and update them in any order.You will already have DirectX 11 (or DirectX 12 in Windows 10), which is meant to be compatible with DX9but you will still need some components Microsoft chose not to include. Do not skip this step, even if youthink you already have DX9 installed."


WOFF FAQ / manual here.
 
ok. that fixed it!!! I put in the other d3d8.dll into the sim and it works now!!! now to figure out how to get everything else working!
 
Back
Top