UPLOADED: Ankor's Shaders Update 22 October 2019!

I can't check right now, but there should be an option in d3d8.ini, something like "EnumAllDisplayModes=1" (don't remember exact name) which adds 16-bit modes into the list. Maybe it was lost in the latest release?

However, I think the shaders should always use 32-bit mode regardless of what the game reports.
I'm also not sure if switching display modes in game ever worked with my shaders.
 
Setting it to EnumAllDisplayModes=0 restored the in game indication to 32 bit.

As mentioned previously, it does not appear to make any difference to the shaders in how the graphics are being rendered either way.
 
Thanks for the update. Weird thing. I can't get cfs3 to run on any version (including the latest) after January 2017. That version goes smoothly. Bit of a puzzle :dizzy:

A bit more information: Installing a later version, I get the "configoverrides is out of date. please rerun".... etc screen and cfs3 exits. Trying to run cfs3 after that gets only so far as the first small splash screen, no messages, the splash screen just vanishes. Nothing shown running in the Task Manager - cfs3 just fails to boot up.
 
The newest one included in the December 4th update does.

David try running the config utility several times. I seem to recall something weird like that happening once to me a while ago. I don't have any other ideas unfortunately.
 
@MajorMagee, I think they did have that setting. I always go through the ini and add it if it isn't there.

@ Daniel, thanks for the tip. In the past, sometimes I had to simply ignore the config message and run it again. However I will give it a go, twiddle with the configoverrides file, and go through the process several times. There are a series of entries at the top of the configoverrides file that seem to get stuffed up. For example, about the fifth entry (is it ModeVer?) the entry is normally 60, and after an abortive attempt to run the shaders, it will be changed to -1. If I change those top lines to those in a working version of an install, then it seems like the cfs3 startup goes a bit further, and sometimes goes through to completion. God knows what all those entries mean.

My progress will be slow, as it is summer, and I am in my best shape for 3 years. It has taken a long time to recover from nasty chemo drugs, so I may even go for a swim! :biggrin-new:
 
I always use MajorMagee's cfg setup except for the first section. At least his one from a year or so ago!
 
I previously posted a list of values I was using for the d3d8.ini file based on the initial October release of the 2019 shaders. With the updated December release I noticed that there was a Terrain and Scenery section that changed. These parameters are new with the 2019 versions and their values are mostly undocumented, so I have no idea how to go about adjusting them.

The initial October release had:

; Terrain Lighting and Bump Mapping
TerrainDiffuse=1
TerrainDetailBump=0.2
TerrainDetailColor=0.75
TerrainSpecular=0.5,0.5,0.5
TerrainBumpFactor=0.125,0.125,0.125
; Scenery Lighting
SceneryDiffuse=0.5
; Facility Lighting - FacilityBrightness works as a multiplier for diffuse color of building. So if you have a texture pixel with RGB value = 200 and FacilityBrightness = 0.8 the result will appear as if RGB value was 200 * 0.8 = 160. It can also make objects brighter if you use value >1.0.
FacilityBrightness=0.825

The revised December version has:

TerrainDiffuse=1.5
TerrainDetailBump=0.5
TerrainDetailColor=1.0
TerrainSpecular=-8.4, 8.0, 2.4
TerrainGlossiness=4.0
TerrainBumpFactor=1.0, 1.6, -3.0
; Scenery Lighting
SceneryDiffuse=1.0
; Facility Lighting - FacilityBrightness works as a multiplier for diffuse color of building.
; So if you have a texture pixel with RGB value = 200 and FacilityBrightness = 0.8 the result will appear as if RGB value was 200 * 0.8 = 160. It can also make objects brighter if you use value >1.0.
FacilityBrightness=1.0

The December version is a much closer match to the way the terrain looked with all the previous versions of AnKor's shaders. The October values are much more flat and dark, so I'm going with the December values as the default now.
 
A question re d3d8.controls.txt and d3d8.pointers.txt in the Dec 2019 version. I note the content is blank while the ones in my install(s) have content. I assume I don't need to replace them?
 
They are written when you start cfs3. The Real Systems Module references these for some of its functions.
 
Noted with thanks Dan.
Also, NB, re the TextureMagic.ini, if one had added various other dds files and things in the [ShipWake] and [HighAltSprite] sections for example, in the previous TextureMagic.ini, then one probably will have to add them into the December version. I recommend ExamDiff app or similar to see.
 
You must log in or register to reply here.
Back
Top