Thank you, 77_Scout, will try this.

I'm wondering if anyone has had this problem. I can't get the newest version to work, so I rolled back to the March version and now it works fine until I enter combat. As soon as the enemy planes show up it freezes and then goes to the outcome screen. Has anyone else experienced this?

Just some thoughts on how the self-lit material feature could potentially be used in WOFF. Nighttime ops will become a bigger deal when the Gothas and Zeppelins are released. I'm fairly certain I've heard of at least some WWI aircraft gauges having markings painted with phosphor to make them glow in the dark. We could also have glowing exhaust manifolds, which was key to locating enemy aircraft at night, and the searchlights would also greatly benefit from being self lit. Right now they just use a specular effect to make it look like they are lit up. It could possibly also be used to put lit windows on buildings and vehicles, etc. From what I understand of what Ankor has said about this feature most or all of this should be possible.

Latest version doesn't work for me either. Get dropped back to menue after a few seconds or half a minute.
It says it couldn't load some .dll.

Check Direct X9 install as per page one of this thread?

Only for info I've been now using daily the 030714 version since its release, no problem to report.
System in my sig. Woff is installed in the "flight sims" partition of one of my WD 1To HD.

I had to redo the Dx9 procedure after a driver update once.

Me rolled back from the July release to the one from march. Now it works, and WOFF is such a beauty!!

Sorry for disappearing without notice, I've been quite busy and will likely be for a month or so.

I think I have an idea about the probable reason of all these crashes (thx to Robert_Wiggins), but I just can't get the game to crash or behave incorrectly on my PC and thus can't find the exact cause.

I'd be more than willing to help if I can. My system doesn't crash though. I only get the strange parts movement we talked about. By the way, I have just flown a mission with the latest July release and I will share the video with you once the YouTube is loaded up with it. Ankor, you are correct that the TAC and "Z" key display problem is fixed in this latest release but the graphical problem still exists and I think you are aware of this.

PM me if you want me to try to capture anything for you.

Best Regards;

I had an interesting observation about FPS in the cockpit after applying the 4GB patch mentioned here to my CFS3 exe: http://simhq.com/forum/ubbthreads.php/topics/3984750/Performance_Tool#Post3984750

Prior to the patch and with your latest shaders installed, I could run at 60 FPS in external view and about 30-45 in the cockpit depending on where the shadows were as I described earlier. I would occasionally get a crash if I ever reached the 2GB limit while flying and if I turned the graphics sliders all the way up, a crash was guaranteed in less than a minute. (I had been experiencing this kind of crash before installing your shaders, so I know it is unrelated to your work, just including it to give more details as to what my system has been doing.)

With the 4GB patch installed, I have yet to experience a crash even with sliders turned all the way up. At my usual settings (scenery and terrain sliders at 3 and 2, respectively and everything else at 5) I get the same FPS I described above. With all sliders set to 5 I got around 30 FPS in external view over cities and dense scenery environments, and up to 60 in empty areas like over the ocean. In cockpit view the FPS remained around 30 (sometimes up to 45 over the ocean and depending on where the shadows were). Even over dense scenery it kept up a steady 25-30, roughly the same as external view. I would have expected it to drop off proportionally and be around 15 FPS in those areas. It seems then that whatever is limiting FPS in the cockpit is independent of the load put on the system by the environment you are flying in and not affected by it. I hope you find this information helpful in some way or other.

Gecko. This 4GB patch is ALREADY applied. If you have replaced the cfs3.exe yourself (or something else did) all bets are off anyway, but there is no need to patch the CFS3.exe once WOFF is installed.

This is also one of the reasons why we require a 64 Bit OS.

Sorry, forgot to specify, the test was not carried out in WOFF. I often post test info from CFS3 here as it often applies to both and I have greater flexibility to test different parameters in CFS3 than I do in WOFF.

OK no problem thanks Gecko, I just had to clarify for others reading.

Hi All,

Just wondering what kind of settings you guys use for sweetfx, to show such beauty ingame, which I have yet to experience.

Anyone can share his settings?

Thx

Ive PM,d my settings to you LTCasey

Thx, will Check it tonight!

Without having read into your discussion, I only want to say: WOFF is running fine on my Windows 7 (32bit).

Yes it can run fine, but we have not tested it and don't officially support it, so the info on the website still applies.

If I remember you run on lower settings Olham for scenery and terrain so probably don't use so much memory.

I'm using the quality values 5-4-4-5-5;
Aircraft skins on "high res";
and the "Workshop" "Terrain Detail Textures" on "normal";
and "Wood/Forest density" on "medium".
Works fine.