This DirectX 9 mod is now included as a part of WOFF 2.0 Expansion [edit Polovski: and now updated versions included in WOFF3 and further in WOFFUE]

Only use it wiith WOFF1.

If you have WOFF2, WOFF3 or WOFF UE you should NOT replace its files with any existing versions of my converter. They aren't compatible for now.
If you accidentally do it you will most likely need to reinstall the expansion to repair the DX 9 shaders.[/b]


Updated on August 30th.
A new version. Hopefully stable this time
If you are not into testing, crashing your game and losing your pilots then just want to try previous version from March which is available below. And for those who like the risk here is download options:
Installer: https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_DirectX9.20140830.Setup.exe
JSGME: https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_DirectX9.20140830.JSGME.7z
Plain zip: https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_DirectX9.20140830.zip



Please report any issues in this thread, even if I don't answer immediately I'm still reading everything.

Previous stable version (March 25th) is still available at:
Installer: https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_DirectX9_Mod_Setup.20140325.zip
JSGME: https://dl.dropboxusercontent.com/u/2918136/cfs/D3D8%20Self%20Shadowing%20Mod%2020140325.7z
Plain zip: https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_D3D9_Extended.20140325.Beta.zip

Installer will automatically detect the folder where WOFF (or OFF, or CFS3) is installed or you can specify another folder, but it has to be the one where CFS3.exe is located.
Then it will ask whether you need SweetFX compatibility - this option is turned off by default but you can always edit d3d8.ini manually to change it after installation.
Finally, it will suggest to open DirectX 9 download page. If you are installing my mod for the first time - it is recommended to download and run DirectX installer from that page. If you already have this mod working - you may uncheck the option to skip this step.
You can always uninstall the mod via Control Panel -> Remove Programs. It is called "DirectX 9 Mod for Wings: Over Flanders Fields (version NNNNNNNN)" there.

Very Important!
If the game fails to start a mission while using this converter, make sure you have the latest DirectX 9 installed.
Download automatic DirectX installer here: http://www.microsoft.com/en-us/download/details.aspx?id=35
It will check whether you have the latest version. You see, there are probably 20 versions of DirectX 9, and even though it stopped being updated few years ago you may still happen not to have the latest one.

With this version you can use numpad "0" to switch extended graphics on and off while in game. This is debugging feature useful for comparing the image quality and checking FPS difference.

Additionally a simple version of the D3D9 converter (January 1st) is still available here:
https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_D3D9_Converter.20140101.zip
This version does not enhance graphics on its own, but provides a good FPS boost over the original WOFF rendering.

Important Note:
To be able to use SweetFX with any of these versions you should edit d3d8.ini with a notepad (Windows often shows this file without the .ini part just as "d3d8" with a type "Configuration Settings") and change
NoMultisampling=0
to be
NoMultisampling=1
This will turns off ingame antialiasing which seems to be incompatible with SweetFX.
Please note that I'm not providing support for SweetFX installation and settings, I just made it work with this game and now you are on your own.

-------------------------------------------------

Hi AnKor, please keep up your exploration, using SweetFX in WoFF would be awesome.

Dirk.

Hey Ankor. Blackjack you say? Sounds intriguing... I'm in for testing. Thanks for your work.
Btw, what's a DX9 ENB Series tool? Just asking. I would love to see some SweetFX options working with WOFF.

Update: I'm only getting a "Game terminated prematurely" exception error when WOFF tries to launch CFS3.

Here's what the log says:

2013/12/22 18:15:38 PatchMemorySync: Launching game
2013/12/22 18:15:38 EXE 'C:\OBDSoftware\WOFF\OBDWW1 Over Flanders Fields\CFS3.exe'
2013/12/22 18:15:38 DIR 'C:\OBDSoftware\WOFF\OBDWW1 Over Flanders Fields\'
2013/12/22 18:15:38 CMD 'cfs3'
2013/12/22 18:15:38 PatchMemorySync: waiting for sync
2013/12/22 18:15:38 EXCEPTION Game terminated prematurely
2013/12/22 18:15:38 TellUser Game terminated prematurely

ENB series is a graphics "improver" similar to SweetFX which predates the latter for several years.

I think I figured out why SweetFX didn't work - it requires multisampling to be off, but the minimum value in WOFF settings is 2 so it is always enabled.
I will add an option to override it in the converter, but I'm curious why WOFF devs restricted it this way.

If the game fails to start try installing the latest DirectX. If it doesn't help then perhaps I screwed something. The next version will have an option for writing a diagnostic log.

Has anyone else tried this converter?

My DirectX is up-to-date. Let's wait for the log option. Thank you

You can force your driver to override application settings though so doesn't matter what WOFF is set to.

Updated the download. Now it should work for everyone.


Yes, it doesn't matter for end result, the problem is that SweetFX inserts itself as intermediate layer in the rendering and doesn't work if a game has multisampling enabled.
So this config doesn't work:
Game (MSAA: ON) -> SweetFX -> GPU Driver (MSAA: OFF - Override)
but this one works:
Game (MSAA: OFF) -> SweetFX -> GPU Driver (MSAA: ON - Override)

It applies to any game, not just WOFF.

Did you edit the ini file and set NoMultisampling=1 as AnKor says at the start?

Hi Ankor,

I'm getting the same error even after making the adjustment in the ini.

Hey Ankor! It's now working perfectly with SweetFX! Thank you so much for this little miracle. S nastupayuschim Novym Godom!

@Rover,
Then it's my settings that I may have messed up somewhere. Would you mind telling me a step by step how you did it? What version of SweetFX are you using?

Nvidia inspector is 8xQs with 2x SGSS & in workshop I have aa set to 8.

Hey yaan,

I just copied the files to the same folder cfs3.exe is in and changed the NoMultisampling=1 as Ankor said.
Then I opened FlightFX (I got it here), created a new profile for cfs3.exe, ticked Enable SweetFX option on the right panel and proceeded to tuning in the adjacent tab. Looks like that's it.

Good luck,

Rover

Updated: And I have sadly admit I have to disable it because it leads to about 15-20 fps loss (which is critical for me). Even without sweetfx. But that's probably my system.

If you get errors, try following options

0. If you downloaded the very first original version, make sure you don't still have it. Correct d3d8.dll is 18.5 KB in size (18944 bytes to be specific) and the older one was just above 20 Kb.

1. If you already installed SweetFX or ENB Series try removing their d3d9.dll from the game folder to see if it helps. If it does then something is wrong with their config and no with the converter.

2. Try setting WriteLog=1 in d3d8.ini so it will write d3d8.log when the game is started.
If the log is short (less than ten lines) and ends with something like "Create Device RESULT = <some number>" where the number is not 0, then for some reason my dll can't set requested screen resolution. Try changing resolution in workshop to see if any of them works. Note that 16 bit modes are not supported by the converter, only 32 bit ones work, but I doubt anyone really wants to use 16 bit colors.

If the log is a large file then something else didn't work and it will difficult to figure out
I had some free time over weekend to make this tool, but now I don't have any to support it. Sorry.

Rover_27,

This is odd. I specifically tested to see if there are any performance changes, but haven't noticed any.
Though this may really depend on your system. I have an old GTX 285 (though even being old it has a bit faster memory bus than GTX 660 for example ) and run at relatively low resolution 1680*1050.

Mine is GTX 560Ti with 256 bit bus Width. The resolution is 1920x1080.
I'll try that again later with different settings

Upd: Looks like your converter's eating away 1 GB of my memory (don't ask me how)

Look



Now it says 909 virt while usually it shows around 1800-2000. Btw, what these numbers after fps mean?

Well, maybe a bit less but it will grow eventually.

Note the same setting (planes, graphics, terrain) without converter

Wow, this is very interesting!

Thank you very much for your work, AnKor!






Will need to play around with the settings some more. Couldn't see any FPS loss. (core i5-2500k@4GHZ, GTX 470, 8 Gig RAM Win7 64 bit).

Rover_27, interesting observation, will take a closer look a bit later (and I don't really know what those numbers mean too )

Para_Bellum, if you make a good looking preset -- please share it

yeah I need some settings please;)

I have. I made a few videos using it with SweetFX and posted them in the forums. Here's the link. Great stuff AnKor! Thank you very much for doing this.

http://simhq.com/forum/ubbthreads.php/topics/3882857#Post3882857

So what's involved with setting it up?
Putting the converter and SweetFX into the WoFF directory?

I set up SweetFX for RoF, but used the FlightFX program that Jason had Laser make....

Try creating a profile for cfs3.exe in Flight FX

Yes, extract the converter into the "OBDWW1 Over Flander Fields" folder and edit its d3d8.ini to set NoMultisampling=1 so SweetFX can work. I could have made it 1 by default, but I decided that initial config should be clear of any side effects.
Then you can use FlightFX to make a profile for cfs3.exe.

Meanwhile I researched reported performance issues a bit and found that the converter may indeed cause some FPS loss. Though for me it was not even close to losing 20 FPS, but more like occasional stuttering which didn't happen without the converter. While I believe I know the cause - a single method from DX8 which doesn't exist in DX9 and for which I had to find a workaround, but currently I don't know a better solution.

How much does this hit performance? Or does it help? I will do anything for more FPS

Thank your for all your tips Ankor...using sweetfx with Para,s settings,(on the WOFF swettfx videos page)
And Woff looks fantastic... ...Spinkick ive noticed no real fps issues,but its only a key press away to go from Sweet fx to Vanilla WOFF

Experimenting with SweetFX, fiddling around with Para-Bellum's settings
(a little les bloom, a bit of bleach).



With SweetFX, everything look like they have more "volume", don't you think?

There is a bit of stuttering here and there, though as sideffect, Spinkick,
but I can live with it at the moment.

Thanks AnKor for making this possible!

Merry Christmas!

Thanks! It is good to know my mods are useful

And I think I have some good news, even though the Christmas has already gone.
It seems my initial assumption about the mod not eating any FPS was wrong. It actually did, especially with many planes around. And while I'm still unsure whether that single method I told above is optimal or not, I have discovered a simplest change which boosts FPS even over original DX8 version.

Download link in the first post is updated.

Note there is a new option in the d3d8.ini:
ForceHardwareVertexProcessing=1
which enables improved FPS by default. There is no need to edit it except for troubleshooting.

Good job mate

Ok Ankor, I have a ? for you now that you are getting to the final stages. I run and ATI card as follows:
Sapphire AMD Radeon HD 7870 Video Card - 2GB GDDR5, 1000MHz Base Core Clock, 4800MHz Memory, PCI Express 3.0, Dual Link DVI, HDTV, HDMI, Dual Mini Display Port

How do I implement your d3d8 to work on my system. I also have ENB that ran on OFF but don't know if there is a more current version. If so, where would I get it.

If you have any specific tuning info for implementing d3d8 with ENB on my system I would appreciate your suggestions.

Thanks in advance

The reason why I am asking is that when I install the D3D8 dll and ini into my ODB directory along with ENB, I get the following results in which my aircraft shows up all black. when I remove the files everything returns to normal

list of files installed:

taken from quick combat:

taken from campaign mode:

The d3d8.dll doesn't seem to like my native 3840 x 1024 resolution.

Starting up.
Forcing Hardware Vertex Processing
Create Device Adapter = 0, Type = 1, Flags = 66
Create Device Windowed: 0, Width: 0, Height: 0, Refresh: 0, Format: 0, Multisampling: 0
Create Device RESULT = -2005530516

I also had black aircraft recently until turned skin resolution to High

Thanks Rover!

I did just that, and with some fiddling, I came up with some awesomely deep and rich coloring.
I honestly didnt think WoFF could look much better (I like the way it looks already!), but WOW!
I started with Para's settings, but then rather than messing around with SweetFX, I used FlightFX which allows presets and much easier tweaking. I thought Para's sky was a little too electric blue. I found that the settings I made for RoF worked terrifically as-is for WoFF.
I'm actually using the same preset config I made for RoF.
Here's some screens:






The screenshots make it look a little darker than it actually is.
For anyone sitting on the fence about SweetFX/FlightFX, it really makes WoFF look GREAT!

Robert_Wiggins, I'll look into black aircrafts issue (which presumable aren't triplanes from Collishaw's Black Flight ).
As for ENB and SweetFX... It may be better if someone else explains how to install and use them. They aren't something new and there ought to be some good instructions somewhere.
In short, you can get SweetFX here: http://www.guru3d.com/files_details/sweetfx_shader_suite_download.html
Extract everything into "OBDWW1 Over Flanders Fields" and then edit SweetFX_preset.txt file by first deleting whatever there are and then copy-pasting there all #define lines from this post http://simhq.com/forum/ubbthreads.php/topics/3882997/Re_WOFF_SweetFX_videos#Post3882997


And which resolution did you use initially? Did black aircraft appear every time or only occasionally?
And by the way, did the latest version improve FPS for you?


Thanks for the log. I've seen this kind of error and this is something I have to look into.

Hi, I use 1920x1080. Black aircraft is usually the active one. Either mine or the one I switch to in Player/Target view. Choosing High quality skins eliminated the problem. Btw, I've seen some weird terrain artefacts with the converter but I forgot to screenshot them. Next time.

As for fps - yes. I don't know what changed but it's now the same as without the converter. However, I had a one-time experience when it dropped to 2 and stayed there for a minute. Then it climbed back to 50-60. Probably some CPU glitch or smth.

OK. Thanks.
I think I've seen both of those glitches: the framerate dropped to 1-2 with no apparent reason and stayed there from some time and almost at the same time terrain textures on some tiles appeared completely wrong.
I suspect both of them may be related to the game running out of video memory (I have 1 GB card).

I get the black camel every timeand my resolution is 1920 x 1080.
I even removed and reinstalled the enb and d3d8 and it was always the same reproducable.
I can send yu my ENB settins (ini) if you would like to see it.

I get another strange glitch with terrain textures.
Seems like the TAC and parts of the sky superimposed on the terrain.





EDIT: Oh, I just saw you're already aware of it.

I have a 4GB GFX series 7 card and 16 GB of RAM...

Hi AnKor,

Don't know what you did, but it's working perfect now with no effect on the FPS. Except for the occasional drop which you mentioned. I notice that it would usually happen after time acceleration and when I'm starting to enter no man's land.

Yes, it is most noticeable after using time accel or over the front because the game has to load a lot new terrain.


Yep, that's exactly what I saw. And your specs confirm that it is not related to memory issues.
I think I've found the likely cause, but again I don't have a solution. Already spent more hours on it than I wanted to

If anyone has problems with it just set
ForceHardwareVertexProcessing=0
in the ini and everything will be back to normal at the cost of some FPS.

I doubt I'll be able to solve it anytime soon.
The main problem is that the CFS3 engine is so old and does such stuff which more modern games (i.e. those for DirectX 9) shouldn't do. Especially nasty is the way it uses screen buffer to do terrain texture combining. At first I though it is a bug, but looks like it is intentional. First of all it is very slow and apparently with hardware vertex processing something happens in a wrong order and that's why you may see parts of the screen drawn onto terrain.

ok will work on this

at the mo it turns my planes skin to black.

I did set ForceHardwareVertexProcessing=0
and still having the weird terrain issues.
I think I'm going to disable SeetFX at the moment...

I don't know how SweetFX specifically interacts with the game files.

When I use sweetfx I get much higher FPS than without it (both in campaign and QC). Also, if I disable everything in the settings file, I can enjoy all the default color schemes from the original game.

Interesting....I've flown QC and a bunch of campaign missions with FlightFX (the RoF version of SweetFX) and have no issues like what is being posted....

Looks like a miracle has happened.
While trying to fix that one method which bothered me so much (and caused all performance loss and texture glitches) I decided to override some texture settings in a desperate attempt to try a different implementation. However to my surprise after this change the game just stopped using that "bad" function at all!
I'm not entirely sure about the reason, but it looks like CFS3 is programmed better than I already started to suspect. Anyway this means I no longer need to find a workaround for that problematic function

This override is controlled by a new option in the d3d8.ini file which is turned on by default:
ForceRenderTargetTextures=1
It gives noticeable performance boost as is, but with hardware vertex processing results are even better.

The first post is updated with a download link for this new version (20131228).

Now, about other reported issues:
- Black planes: tried different skin res settings, but haven't seen this glitch yet. It might be solved with this new version though.
- Some screen resolutions not working - got an idea about possible fix, but haven't implemented it yet.

I really appreciate that you are working so diligently on this.

/this



Thank you for all your efforts, AnKor!

Really appreciate your outstanding work.

I'm trying to use it with OFF: HiTR...following all directions to the letter, but get the following log file (not working):

Starting up.
Create Device Adapter = 0, Type = 1, Flags = 130
Create Device Windowed: 0, Width: 1440, Height: 900, Refresh: 0, Format: 22, Multisampling: 0
Create Device RESULT = -2005530516

Maybe OFF doesn't work with it (unlike WOFF)...but if it does, any ideas? The error seems to be similar to what another has reported above.

Pertinent specs are Win7 32-bit (OFF, not WOFF), GTX 560 Ti, 314.22 drivers, all OFF and Win7 updates/patches current. Any tips appreciated. I've tried the various changes suggested in the total thread above, but no luck.

To make it work with OFF or even original CFS3 just run cfs3config.exe while d3d8.dll is in place and select the resolution again, even if it already shows the correct one.
When I have some free time I'm going to make a new version to solve this problem, but for now the trick is to reset the resolution.

WOFF doesn't have cfs3config anymore, but I suggest trying to switch between resolutions in workshops. Somehow it worked for me.

The problem is not in the resolution as is, but in the way CFS3 stores them in config - instead of saving all parameters like width, height and bits per pixel it just keeps a single number for "screen mode". My converter however has different mode numbers (because it skips 16bpp ones) and that's why the game might be unable to select proper one.
I only figured it out only recently and was too busy solving performance issues (the converter has little use if it eats FPS), but now it is my priority.


Thanks

Now I'm flying HiTR with SweetFX, can't see any performance hit and it looks awesome. It's like removing a protection film from your monitor, the effect is quite prominent in the split screen.

Thanks,
Dirk.

AnKor...thanks. did your suggestion, and it goes through everything until the game screen should appear with live action, but then gives me the window that says CFS3 has stopped working (you know the one). The error log is now slightly different from what I had before:

Starting up.
Forcing Hardware Vertex Processing
Create Device Adapter = 0, Type = 1, Flags = 66
Create Device Windowed: 0, Width: 1440, Height: 900, Refresh: 0, Format: 22, Multisampling: 0
Create Device RESULT = -2005530516

I'll try it without forcing vertex processing and see what happens (and I'll also reset resolution again).

Regardless, thanks for your continuing help!

With ForceHardwareVertexProcessing=0, I get same error as initially reported (several posts above).

To cover all bases, I tried Enabled=0 to see if the game runs, and it runs just fine...so I'm not sure where the problem is...

Thanks. Makes perfect sense and that got it working.

Hmm... I just noticed - although the width and height are correct, the 'Refresh' value in your logs is 0 which is not right. It should be your monitor's refresh rate (like 60) instead.
Never seen this problem before, I'll see if I can do anything about it.

Thanks for taking a look, AnKor! Just wondering...do you - or anyone - have a copy of the Nvidia Control Panel settings you're using for CFS3? Maybe I have something screwed up in there (btw I'm using a GTX 560 Ti). I've given both this http://simhq.com/forum/ubbthreads.php/topics/3884065/Re_WOFF_at_Max_Settings_video#Post3884065 and this http://simhq.com/forum/ubbthreads.php/topics/3884827/Re_WOFF_at_Max_Settings_video#Post3884827 a try, but no luck thus far.

GTX 670

Ambient Occlusion Quality
Anisotropic Filtering 16X
Antialiasing FXAA ON
Antialiasing Gamma Correction ON
Antialiasing Mode Override Application
Antialiasing Setting 16xQ CSAA
Antialiasing Transparency 8X Supersample
CUDA GPUs All
Max Pre-Rendered Frames 3
Multi Display Multiple (Triple Head 2 Go)
Power Management Adaptive
Texture Filtering (Anisotropic) OFF
Texture Filtering Negative LOD Clamp
Texture Filtering Quality High Quality
Texture Filtering Trilinear ON
Threaded Optimisation Auto
Triple Buffering OFF
Vertical Sync OFF

I'm not sure which settings could affect this. I haven't yet made a new version to fix the issue.
Instead (and I'm a bit sorry, but I hope you understand ) I tried something different, which for me is actually the main reason I'm working on this converter.




It may not be as obvious from the screenshot, but it looks nice in action.
What I did is per pixel diffuse and specular highlights as well as some bump-mapping. For those familiar with my ROF mods - bump mapping is done in the same way I did it for terrain there - by color detection. It doesn't work as well (and it is messed up on screenshots but it takes some time to figure out why) for aircraft skins, but we'll see what I can do.

I'm not releasing this version right now, and it may take a while to get it ready for use, because a lot of things are still missing - look at the glass windshield at the second screenshot for example.

Bump mapping is one of my all time favorites! Not to mention it works in Mods off and MP. Thanks, Ankor.

That looks fantastic AnKor. I look forward to when you release this. Thank you for all of your efforts on this. You are really making WOFF shine even more!

Fantastic news, AnKor!
It would be great if it could be applied to the terrain as well...

MajorMagee...thanks, I'll give those settings a try! And AnKor, thanks for all your efforts. You guys all make the great stuff even greater!

Updated download link in the first post. I really hope it will solve all startup issues, but if it doesn't - I'm out of ideas

Simply amazing. Thanks Ankor for your work on this.

The updated version still doesn't include bump mapping, does it?

Hellshade;

I need a little help here, what is "Bump mapping"

No, it doesn't. Just a bugfix to try to make it work out of the box for most people.

It will take me some time to get advanced lighting working. What I shown on those screenshots is not even close to correct implementation, instead it is just one step above "completely broken" state.
So don't expect it to be ready anytime soon. Probably sometime before 2015

Robert_Wiggins,
"Bump mapping" is a relatively simple graphics enhancement to add more fine details to otherwise flat surfaces. Take a look on my screenshots (especially the second one) on the previous page. Do you see anything unusual with on wings?

Thanks for your work AnKor!
I still have the version you released a week or more ago...everything works great with no issues that others are seeing.

Will your bump mapping be a mod or an addition to sweetfx?

With a few mods showing in the forums, I'm thinking of setting up JSGME for easy mod on/off usage.

Well, other than what appears like reflected light illumination on the upper wing above the cockpit and some additional contrast is there something I'm missing?

By the way, just posting this to help, but I found this SweetFX configurator program (link below) makes testing out settings and understanding what they do much easier. Install SweetFX as normal, add Ankors new files and then install this program below wherever you like (doesn't have to go into same WOFF directory).

Just remember, you have to add the CFS3.exe file using the "Add new game" button, not the WOFF.exe. The one you want to add is located by default at [INSTALL DRIVE]\OBDSoftware\WOFF\OBDWW1 Over Flanders Fields\CFS3.exe

Dont try and use the "Launch selected game button" either. Just make your setting changes, save new config and then launch WOFF as normal. Whats cool about this as that you can leave it running and Alt-Tab out of the game, make changes, alt-tab back into the game and see them as you are playing. Keep in mind that the default on/off key for SweetFX is Scroll Lock, which WOFF uses to toggle between panning and snap view. You can change that in either program of course.

Link to configurator program:
http://sweetfx.thelazy.net/?cat=3

Thanks, Madmatt!


Nothing I think
Anyway, one has to see it and it looks better in movement than on screenshots. When done properly (and it isn't yet) it adds more volume and details to textures.

AnKor, I have been following your post on this for some time and I am certainly interested in your results as they are looking positive. Unfortunately I can't even try them at the moment as my PC is in parts on the floor awaiting a new MB and processor. (God I wish it would get here!!!). Once I am up and running I will jump in. I have an ATI 7870 that will be running on an Intel I7-4770K processor on an ASUS Maximus VI Extreme board. The boot and sims will be on separate Samsung 250 gb SSD's. I shouldn't have any performance issues due to hardware limitations, but we shall see!

AnKor, reports from the fields are that the latest version adds even more smoothness and increases FPS, actually you do wonders with that converter in OFF/WoFF.

Thanks,
Dirk.

AnKor, MajorMagee, Hellshade, and Madmatt...thanks to all. But I still have no luck enabling the DX8 to 9 convertor (newest one in 1st post of thread). I've tried messing with everything, but no luck.

Mind you, my settings give a nice pic, but I would have liked to see what the DX9 with SweetFX does. But I keep getting similar error logs with all attempts; all settings give the following error log entries:

Starting up.
EnumAdapterModes 0, 0 : 0 = 640, 480, 60, 22
EnumAdapterModes 0, 1 : 0 = 640, 480, 72, 22
EnumAdapterModes 0, 2 : 0 = 640, 480, 75, 22
EnumAdapterModes 0, 3 : 0 = 640, 480, 59, 22
EnumAdapterModes 0, 4 : 0 = 720, 480, 56, 22
EnumAdapterModes 0, 5 : 0 = 720, 480, 60, 22
EnumAdapterModes 0, 6 : 0 = 720, 480, 72, 22
EnumAdapterModes 0, 7 : 0 = 720, 480, 75, 22
EnumAdapterModes 0, 8 : 0 = 720, 576, 56, 22
EnumAdapterModes 0, 9 : 0 = 720, 576, 60, 22
EnumAdapterModes 0, 10 : 0 = 720, 576, 72, 22
EnumAdapterModes 0, 11 : 0 = 720, 576, 75, 22
EnumAdapterModes 0, 12 : 0 = 800, 600, 56, 22
EnumAdapterModes 0, 13 : 0 = 800, 600, 60, 22
EnumAdapterModes 0, 14 : 0 = 800, 600, 72, 22
EnumAdapterModes 0, 15 : 0 = 800, 600, 75, 22
EnumAdapterModes 0, 16 : 0 = 1024, 768, 60, 22
EnumAdapterModes 0, 17 : 0 = 1024, 768, 70, 22
EnumAdapterModes 0, 18 : 0 = 1024, 768, 75, 22
EnumAdapterModes 0, 19 : 0 = 1152, 864, 75, 22
EnumAdapterModes 0, 20 : 0 = 1280, 720, 60, 22
EnumAdapterModes 0, 21 : 0 = 1280, 720, 75, 22
EnumAdapterModes 0, 22 : 0 = 1280, 720, 59, 22
EnumAdapterModes 0, 23 : 0 = 1280, 768, 60, 22
EnumAdapterModes 0, 24 : 0 = 1280, 768, 75, 22
EnumAdapterModes 0, 25 : 0 = 1280, 800, 60, 22
EnumAdapterModes 0, 26 : 0 = 1280, 800, 75, 22
EnumAdapterModes 0, 27 : 0 = 1280, 960, 60, 22
EnumAdapterModes 0, 28 : 0 = 1280, 960, 75, 22
EnumAdapterModes 0, 29 : 0 = 1280, 1024, 60, 22
EnumAdapterModes 0, 30 : 0 = 1280, 1024, 75, 22
EnumAdapterModes 0, 31 : 0 = 1360, 768, 60, 22
EnumAdapterModes 0, 32 : 0 = 1360, 768, 75, 22
EnumAdapterModes 0, 33 : 0 = 1366, 768, 60, 22
EnumAdapterModes 0, 34 : 0 = 1366, 768, 75, 22
EnumAdapterModes 0, 35 : 0 = 1440, 900, 60, 22
EnumAdapterModes 0, 36 : 0 = 1440, 900, 75, 22

Then, depending on what settings/switches I'm using, I've had the log end with these additional lines:

Forcing Hardware Vertex Processing
Create Device Adapter = 0, Type = 1, Flags = 66
Create Device Windowed: 0, Width: 1440, Height: 900, Refresh: 0, Format: 22, Multisampling: 0
Create Device RESULT = 8876086c

or:

Create Device Adapter = 0, Type = 1, Flags = 130
Create Device Windowed: 0, Width: 1440, Height: 900, Refresh: 0, Format: 22, Multisampling: 0
Create Device RESULT = 8876086c

or simply:

Cleanup
Exiting

I'm wondering if there's a problem with my Galaxy GTX 560 Ti card, or with the 314.22 drivers I'm using (sticking with those due to the well-known issues with 500-series cards and later drivers). Like you said, that "Refresh: 0" is strange...

Anyway, thanks for your assistance. I may keep tinkering, in part because it's an "interesting" problem that I'd like to figure out...but if any of you have a new idea, let me know...but thanks again. I'll be flying nonetheless!

Looking at your log makes we wonder if you're running a newer high frequency monitor and the files are only looking for 75 Hz or less and interpret anything higher as 0 Hz.

I'm on 331.82 drivers with a GTX 670 card, and 3840 x 1024 60 Hz screen. As long as I run cfs3config.exe first it starts up fine. The only thing I noticed with the latest dll update was that config now defaults to 16 bit colors and I had to make sure I changed that back to 32 bit.

MajorMagee, thanks for the ideas, but "unfortunately", I just checked and verified that my monitor is indeed running at 60 Hz (it's an old Dell digital monitor from 2009), and I did also run cfs3config.exe (the one in OFF's directory) before each flight attempt. But please - if you come up with anything else - I'm "all ears"! I'd love to solve this issue, especially since there's no apparent reason for the problem.

One possibility I thought of is that maybe my files are not placed correctly? But I thought I was sure to follow installation instructions with both SweetFX and the DX8 => DX9 convertor files in the first post. I'm at a bit of a loss right now for the answer, but the stubborn part of me will probably keep trying (and continue welcoming any ideas)...

Well, I also suspect the monitor - especially if you say it actually runs on 60Hz, but according to the log the system reports that 75Hz mode is supported. Then it might be the case that the game attempts to set the best reported mode, but fails.

Is there a line with something like GetDisplayAdapterMode after all those Enum... lines? It should tell which mode is used for your windows desktop.

Everything else seems to be ok, I also used the same older drivers until a couple of days ago.
You may try removing sweetfx's d3d9.dll from game folder to see if it makes any difference though.

MajorMagee, do you have to run cfs3config every time? I thought it has to be run only once. Something isn't right then.

If we find a confirmation that it is refresh rate related I may add an override option. Though I wonder why it works out of the box for DX8 and doesn't for DX9.

And now for something completely different (that's why I decided to make another post instead of editing previous one):





As you can see I'm making some progress and experimenting with the look.
I was able to replicate the original lighting (except that it is now per pixel which really improves highlights) and enhanced airplane model with bump mapping + fake environment reflections (apparently overdone) just to see how it works. And it looks nice

One thing I really want to add is "self" shadows - where parts of the airplane will produce real shadows on other parts and in the cockpit. This would have been a very simple task with modern shaders, but only if I had some control over CFS3 rendering engine. Which I don't.

Yes, it's just once, but I do need to do it again each time I update the d3d8.dll file to a newer version.

The bump mapping looks very nice.

You are performing some kind of magic tricks there, AnKor!
If you could implement self cast shadows it would be a real miracle!
I hope the devs will notice this thread and provide you any help needed.
As said in another post I would like to see your bump mapping extended to the terrain as well.

elephant,
The terrain in WOFF doesn't need bump mapping as badly as its ROF counterpart. Here it already has sharp and detailed textures, and that's why I haven't touched it yet - I just like how it looks as is.

There are also some difficulties with improving it. It is drawn by a very primitive method and lighting is not calculated on the GPU but comes pre-computed by CPU. I can work around it but then there are other problems - trees and static building are drawn in the same way as terrain and thus has to be separated to avoid messing them. Since I don't have any control on that part - my converter doesn't know what is being drawn it just intercept drawing calls - it may be difficult to work around. Then as I said ground textures are already well detailed and not very suitable for color difference algorithm - note how on my first screenshot on this page the brighter green field already appears bumpy because the texture is painted by an artist as if it was already lit from one side. Adding bump mapping will cause such textures to appear weird, especially if the sun shines from opposite side.

With this said I'm still going to try some terrain enhancements and of course I'll give bump-mapping a go. It is just much lower priority than airplane models.

Wow, you have some amazing skills for working with shaders. I will be following this thread closely!

Thanks so much for the detailed explanation, AnKor!
Planes should be the first priority, by all means...

AnKor, thanks for your continuing help. No, there is no line which contains "GetDisplayAdapterMode" after all those Enum... lines. My previous post included *every* line appearing in the various error logs.

I also tried removing SweetFX's d3d9.dll from game folder to see if it makes any difference (as you suggested), along with all other tips in the readme.txt and elsewhere, but to no avail. Like you said, it seems like my monitor isn't "recognized" (for lack of a more technically correct word on my part).

But I'll keep fiddling. I still would like to verify that my file structure is correct with respect to placement of all of the SweetFX files/folders; I'm not 100% sure that it is, since file placement for the SweetFX stuff is not explicitly stated (for example, some dx8 => dx9 files and some SweetFX files are found in both the main program folder containing the cfs3.exe file as well as in the \SweetFX\ subfolder or the \SweetFX\dlls\FXAA DX9 dll\ sub-sub-subfolder).

Like I say, I'll keep fiddling (I need to figure this out), but as always, thanks for your continuing !

Edit: tried running the monitor at 75 Hz, but no change in results.

When WOFF was released, it changed my life. And now I find this thread. The metamorphosis continues.

Thank you , these are good news !

Now, does this mean one can have better graphisms with no negative impact on the FPS ?

If yes, can some of you post an easy and clear step by step method on using Sweet FX with this dx9 converter (for the dumb...) ? thanks in advance !

Dummies guide, eh? I felt that way, too. Welcome to the club. I posted the same question as you. Check out the 2nd page + the OP on first page.

Here's how I did my SweetFX install:

1. Download the latest converter files from here http://simhq.com/forum/ubbthreads.php/topics/3881675/DirectX_8_to_9_converter_updat#Post3881675 and install the d3d8.dll and d3d8.ini files where your cfs3.exe file is. This can be done for each install of CFS3 you may have.

2. Edit the ini file to NoMultisampling=1 for compatibility with SweetFX.

3. Run CFS3Config.exe and make sure you choose your proper display options selection again (i.e. it may show 800 x 600 x 16).

4. Download FlightFX from here http://riseofflight.com/Forum/viewtopic.php?f=49&t=34103 and install it on your computer.

5. Since version 1.0 of Flight FX does not have latest version (1.5.1) of Sweet FX included you need to download that from here http://forums.guru3d.com/showthread.php?t=381912 and extract all of it to the FX folder where you have Flight FX installed. Let it overwrite any of the files that may have the same names as what FlightFX already had.

6. Now you can run Flight FX and click on Register New Game at the bottom left. It will open a dialog box where you'll navigate it to your cfs3.exe file. That will populate the paths at the top right of Flight FX for you.

7. Click on Enable Sweet FX and it will copy most of the needed files into your CFS3 install. It misses SweetFX_compatibility_settings.txt which is in the Flight FX / FX / SweetFX folder and needs to be manually copied into the matching one Flight FX created in your CFS3 directory.

8. Select the FX Preset you want to use from the pull down list. The files behind this list are located in the Flight FX / FX / SweetFX / Presets folder. They are just text files so you can create new presets manually by cut and past if you like. Make a back-up copy of any of your favorites because it is all too easy to overwrite them by mistake in Flight FX.

That is really all there is to it. At this point you can edit any of the settings under the FX Settings tab and the effect will be immediate.

By default the Scroll Lock key will toggle the shader effects on and off.
The Print Screen Key will place a screenshot in your CFS3 root directory (This overrules CFS3 that normally wants to save screenshots in the CFS3 folder under My Documents).
If you uncheck the Enable SweetFX box in Flight FX it will uninstall SweetFX (but not the D3D8 and SweetFX_compatibility_settings files you did manually) and you're back to normal.

Thank you ...I take a breathe and here I go..!

Very first test of self shadows.

They are more broken than you can imagine

Note that shadows on the side of cockpit are just a texture. However shadows on the seat, floor and a wing are real-time. Also note that upper aileron's shadow is missing - the game doesn't try to draw objects which aren't on screen anyway and thus I can't create a shadow for it.

There still a lot of technical issues to solve and I'm not even sure I will be able to get reliable results.
That's why I need to ask: do they really worth trying? Do you like what you see on this screenshot?

Um... hell yes? But seriously... hell yes.

But I would like to acknowledge that I have no idea what enormous kind of time and expertise you must be putting into this, so whatever you realistically can do or can't do, we certainly appreciate the effort. And the results!

I don't like to use hyperbole, but yeah, this thread is made of Awesomesauce!

I don't know what magic you do, but....



You're the MAN AnKor. STUNNING in my book!

MajorMagee, following your instructions above, and replacing all of my pre-existing DX8=>DX9 converter and SweetFX files, it's now working perfectly...thanks a bunch!!! Those instructions should be referenced for anyone having troubles with this stuff. And thanks again to AnKor as well for his coding work!

Edit: one other item I had to do (but was not aware of) is that I had to close MSI Afterburner; not sure if doing so was required by DX8=>DX9 converter, or SweetFX, or both, but it was needed to enable it all to work.

Very good improvements, guys, than you! I´m experiencing a performance boost when using the dx9 converter files only!!!

When using sweet FX I have a problem, though. The movies don´t play any more (Intro and Campaign vids), and when ALT-Tabbing, the mission ends, with an error message saying "WOFF DLL did not start or WOFF runtime crash".

Anybody else experiencing this or any suggestions? Thanks!

Thanks Ankor for the great job, and Major for the helpinng hand ....runs very well!

Are self shadows and bump mapping worth it?

Do members of the ursidae family defecate in forested areas?

I would certainly use them if you got them working to your satisfaction sir. I think self shadows would be a fabulous addition to the immersion of WOFF, even if they aren't perfect. If you are willing to invest the time and effort, I'm sure they would get a lot of use from a great many folks...especially after they see them in videos.

Wow. Definitely worth it. Self shadowing and lighting is the only piece of magic which makes some other sims out there look more modern graphically. So please keep it going. Good Stuff.

OK, that was a stupid question. Thanks for your support
Screenshot just cannot convey how cool it is too see shadows move when you turn your plane.
Still have major issues to sort out, but some things turned out to be better than I expected.


Glad you get it working
Does that MSI Afterburner has any kind of screen overlay functions - like drawing some text or graphs on screen while you playing a game? I have one report of very odd issues with my converter which I suspect are caused by some sort of overlay application.


Interesting. I've seen some issues with movies as well, but not sure what was the cause.
Unfortunately I can't suggest anything and since I'm really busy with "enhanced" converter right now I just don't have time to look for bugs in the current version.

AnKor, yes, MSI Afterburner can show frame rate and frame time, as well as GPU temp, GPU usage, fan speed, fan tachometer, core clock, shader clock, memory clock, and memory usage in the on-screen display, although I wasn't using any of those at the time. But I was displaying GPU temp and fan speed in the system tray (which was, however, covered over by the full-screen game display).

I posted my SweetFX settings and zipped them up for those that want to just dump the settings into their presets folder. I really like the final settings that I'm using. Feel free to tweak them or use them as a starting point.

I started a new thread on this since this thread is moving in a different and VERY interesting direction

Here's the link:
Sweet FX settings

These are excellent instructions.

Thanks for saving me from Mod Hell when installing SweetFX!

MSI afterburner and EVGA precision will conflict with the sweetfx injector so its not Ankor's fault :-)

This really needs some pictures of where the settings are and how to cxhange them for us computer retards.

Here do I find the ini file so I can change it?

The instructions that are here are meant for people with some know-how. I'm pretty much monkey-see, monkey-do.

Thanks.

HotTom, did you follow Major Magee's instructions on page 9? If you do that you'll have flightfx installed as well, so you just run that and can play with sliders that work instantly ingame (you can alt-tab out to adjust).

Or if you did follow them, let us know where you're stuck.

Thanks, Glubber.

Where I'm stuck is Step 2 in Major Magee's instructions:

2. Edit the ini file to NoMultisampling=1 for compatibility with SweetFX.

I cannot figure out in what folder that ini file is located.

It's probably very obvious but I've searched and searched.

Gracias!

Look in the game directory, here:

C:\OBDSoftware\WOFF\OBDWW1 Over Flanders Fields

The file is called d3d8.ini

Report back if you get stuck. We need to get you up in those beautiful skies.

Pics for an Alternative way to install would be:

1. download SweetFX from publisher's website
http://forums.guru3d.com/showthread.php?t=381912

2. download converter from here:
http://simhq.com/forum/ubbthreads.php/topics/3881675/DirectX_8_to_9_converter_updat#Post3881675

3. open converter zip file and copy into WOFF directory



4. change the d3d8.ini file



5. open the sweetfx zip file and copy to WOFF directory



optional step -
6. copy and overwrite sweetfx settings - I used Fifi's settings.



7. open sweetfx settings and change values to remove bloom

I'm still stuck. I downloaded and installed the two converter files again but, I'm not getting that .ini file. All I get is a readme that is titled Configuration Settings and is just a readme. This is downloaded from Post #1, is there another updated download at another location I am missing?

Nice of you to show the pics (and of Aris to cheer ) but I'm still stuck on Step 2.

I'll monkey with it some more. I'm baffled.

HotTom,

Only one converter file
Get it here: https://dl.dropboxusercontent.com/u/2918136/cfs/WOFF_D3D9_Converter.20140101.zip

then open the zip file and copy it to your WOFF directory as the pics above.

HotTom,


It looks like a readme, but it's the ini file. The first two lines should look like this:

[D3D8]

; Use NoMultisampling=1 to turn off multisampling in the game.
; Using this option is required for SweetFX compatibility (it doesn't like multisampling).
NoMultisampling=1


The bottom line might say 0 instead of 1, so that's where you would change it. The semicolons on the first line denote a comment line. The bottom line without the semicolon is the code.

That's the right file. Windows sometimes hides file extensions so instead of "d3d8.ini" you just see "d3d8" and the file is called "Configuration Settings" because well, that's what it is.
It opens in notepad but it is not a readme, it just had a lot of text describing what each option does. Just look at screenshot #4 above.

I expected all those descriptions to make it a bit more friendly, but looks like a wall of text may have a reverse effect
Next time I'll do it differently.

Thanks, Ankor.

So, where on that page are the settings I need to change?

All I see is the descriptive text:

[D3D8]

; Use NoMultisampling=1 to turn off multisampling in the game.
; Using this option is required for SweetFX compatibility (it doesn't like multisampling).
NoMultisampling=0

; By default CFS3 (and WOFF) uses Mixed Vertex Processing which means that some geometry calculations are done by the CPU.
; Perhaps it made sense for early GPUs which were slow or had incompatibilities, but in modern world it should be a non-issue.
; This converter can force Harware Vertex Processing which will utilize GPU better and should increase FPS.
; Use ForceHardwareVertexProcessing=0 for troubleshooting if something doesn't work as expected.
ForceHardwareVertexProcessing=1

; Use Enabled=0 to turn off the converter and keep using original Direct3D 8.
; Might be useful for troubleshooting if you want to compare how the game works with and without the converter.
Enabled=1

; This option should solve performance issues and terrain glitches caused by switching from Direct3D 8 to 9.
; It doesn't seem to have any bad side effects, so don't turn it off unless something goes really wrong.
; Note that cfs3config.exe has built-in options to use Render Target for terrain and airplane textures.
ForceRenderTargetTextures=1

; DirectX 8 and 9 behave diffirently when game asks for a list of available display modes.
; When this option is set to 1 the wrapper uses DirectX 8 code to create such list.
; This should solve startup issues when game cannot set correct video mode.
; Use EnumAllDisplayModes=0 to try DirectX 9 mode list if something doesn't work right.
; You will have to start cfs3config.exe and select resolution again after changing this option.
EnumAllDisplayModes=1

; Use WriteLog=1 to write d3d8.log file with debugging information.
; Do not use it unless asked by the author
WriteLog=0

HotTom,

The bottom line, which I've bolded.


; Use NoMultisampling=1 to turn off multisampling in the game.
; Using this option is required for SweetFX compatibility (it doesn't like multisampling).
NoMultisampling=1

EDIT: Glubber beat me to it.

Yeah, but yours is much nicer.

Excellent work on the self shadowing AnKor!

Doh! Got it (finally)! Thanks, Guys!

See? I told ya I gotta have pictures.

Okay, I got it all set up including setting NoMultisampling to 1, but if I have SweetFX enabled and try to start WOFF it crashes immediately. With SweetFX disable it starts right up.

Any guesses what I have configured incorrectly?

Is this what you see in FlightFX?

Yup, except I have a RoF profile in there, too (not active). Otherwise, the settings are identical.

I copied Barn's setting for the detailed stuff. Haven't tried going back to the defaults (yet).

Your FlightFX folder looks like this?



And your FX folder inside your FlightFX folder looks like this?




And step 7 went well?

7. Click on Enable Sweet FX and it will copy most of the needed files into your CFS3 install. It misses SweetFX_compatibility_settings.txt which is in the Flight FX / FX / SweetFX folder and needs to be manually copied into the matching one Flight FX created in your CFS3 directory.

I copied it and put it in the SweetFX folder that was created in my WOFF folder.

I don't see a separate CFS3 directory. Where is it?

Hi Folks;

Is anyone using "D3D9" and "SweetFX" with an AMD 7870 card?

I'm looking for some help to implement these two products with my system. I would certainly appreciate some guidance from anyone else on an AMD 7870.

Best Regards;

You did it right. And if your other two folders are similar to what I posted above I'm not sure what to tell you. Everything seems to be in the right place.



Hi Robert,

I'm not using a 7870, but a 6950 with no probs. Are you having issues as well?

I looked at the folders you showed above and everything you have there is in mine although there are several other items in each of mine.

Maybe I need to scrap it and start over?

Well, I'll tinker with it some more tomorrow...thanks for all your patience!

No prob! Like to get you set up.

Have you used flightfx/sweetfx before with other stuff (you said you had a ROF profile)?

Maybe when you attack it again tomorrow you can post screenies so we can see what you've got going on.

Hi Glubber. Thanks for responding. I'm not having any problems to speak of. Just not sure how to implement Sweet and D3 on my kind of system. Most people are using FX cards. I could use some guidance here.