If you are using the "VonS_MaxFPSnGraphicsGPUtuner_ver1.1" with the new WOFF BH&H II V1.36 PATCH, you will likely get a "DLL" crash. It seems this mod will need an update.

Best Regards

Thanks RJW for that info. -- have now double-checked and the WoFF GPU Tuner works fine on my rig, in the latest patch 1.36 of BH&H2. Recommended is to check compatibility with other mods. that you have loaded, and/or if other mods. are causing the DLL crash in your WoFF install. I am including, at the bottom of this post, the list of mods. I have activated in my BH&H2 install -- no conflicts or crashes that I have experienced. By the way, I tested patch 1.36 of BH&H2 with only the various Tuner Patches loaded -- everything else was stock -- no crashes at my end.

If for some reason you continue to experience trouble with the Tuner Patch(es), might I recommend the "FrankenBHAH Enhancement Package Ver. 1.1" located under this post (slightly lower FPS that way than with the older GPU Tuners, but better graphics/terrains at distances) -- the Enchancement Package can further be supplemented with the "FrankenMiniTuner Ver. 1.2" located under this (long) post, to squeeze out a few more FPS.

GPU Tuner Patch 1.1.1 (with addon Tuner Patch 1.3 loaded over it) Running in BH&H2 1.36


FrankenBHAH Enhancement Package 1.1 (with the FrankenMiniTuner 1.2 added) Running in BH&H2 1.36
(NOTE: FPS are noticeably lower, by the way, because I have rolled my ReShade profile for BH&H2 into the Enhancement Package on my rig -- the ReShade profile is available separately under the WoFF/WoTR addons thread on CombatAce and is not included in the Enhancement Package itself)


Mods. I am Currently Running in BH&H2 (patch 1.36)
(NOTE: some mods. have been re-named from their original titles, for convenience on my rig -- thanks to all modders for the mods.)

Generic Mod Enabler - v2.6.0.157
[C:\OBDSoftware\WOFF\MODS]

01_AutoConsolidatedModVer2.6
02_AutoSupplementHavrincourtWood
03_AutoSupplementVerdunForts
04_Effectstrailersmoke
05_FrankenBHAHenhancementPackageVonS
06_SkinFixesRemovalsJerbear1.8
07_UserSkinsJerbear9.0
08_HistoricallyPopulatedAirfieldsVer1.5
09_HistoricalWeatherVer2.1
10_WOFFueBH2_SelectSounds
11b_FrankenBHAHenhancementHardcoreCompensatoryForWoFFueAI_AddonVer1.16_VonS
12_BHAH2_FrankenMiniTunerVer1.2_VonS
13_WOFFconsolidatedSceneryMod
14_BBfullWeatherVer5.0
01.5c_AviatikB.I_Early_105hp
01c_PfalzA.I_80hp
01e1_MoraneTypeL_Early_80hp - load only one
02c_PfalzE.III_95hp
02e_BristolScoutC_80hp
03.5c_AlbatrosBenzD.I_150hp - load only one
03c_FokkerE.II(a)_105hp
03e_Nieuport10_80hp
05e_Nieuport11_80hp
06c_AlbatrosD.V_170hp
06e_Nieuport16_110hp
07c_AlbatrosD.V_180hp
07e_Nieuport17Vickers_110hp
08c1_FokkerDr.1_Early_110hp - load only one
08e2_Spad7_150hp - load only one
09c2_PfalzD.III_170hp - load only one
09e3_Nieuport23Vickers_110hp - load only one
10e_Nieuport17bis_130hp
11e_Tripehound_Late_135hp
14c_FokkerD.VI_Siemens-Halske_160hp
15c_FokkerD.VII_Early_180hp - load only one
15e4_Camel_LeRhone_110hp - load only one
16c_FokkerD.VII_OAW_205hp
16e_Nieuport24bisVickers_130hp
17c_FokkerD.VIIF_BMW_230hp
17e_Nieuport24Vickers_130hp
18c_AlbatrosD.Va_200hp
19e_Nieuport27Vickers_130hp
20e_Tripehound2Gun_LongStrokeClerget_142hp
21e5_Spad13_200hp - load only one
22e_Se5a_Hisso8Ba_200hp
23e_Nieuport28_165hp
25e_Camel_Bentley_153hp
04e1_MoraneTypeL_Late_80hp - load only one

Cheers,

Thanks for the quick response VonS.

I can confirm that I was running the GPS Tuner mod standalone and it always fails on woff V1.36 patch. If I remove your mod the patch runs fine.

I will look into the FrankenMiniTuner try it and see what happens.

Best Regards.

Hi VonS

I tried your "FrankenBHAH Enhancement Package 1.1 mod but I still get the DLL crash and that is with no other mods loaded.
Woff BH&HII gets as far as attempting to load the aircraft on the runway screen and then crashes back to the quick combat screen.

Has anyone else on a similar system as mine, complained of a problem with your mod?

Best Regards

Hi @Robert,

a short info:
I have installed "FrankenBHAHenhancementPackageVer1.1" at first, then "BHAH2_FrankenMiniTunerVer1.2"; no problems with 1.37 or previous versions and better FPS.

I hope, you will find the reason for it.


Greetings!

Hi Becker;

I have tested it on V1.36 and V1.37 and it's a no go!

Hi RJW -- no complaints that I've noticed -- the forums are quiet here and no PMs on CombatAce either, regarding the various GPU Tuners and/or Enhancement Packages. So I am assuming that they work well on a variety of rig setups. I've been looking over the d3d8.ini files that are available in said packages and the only thing that might be worth tinkering with -- and this is purely a hunch -- is the "troubleshooting options" section:

; Troubleshooting options
Enabled=1
ForceHardwareVertexProcessing=1
ForceRenderTargetTextures=1
EnumAllDisplayModes=1
AutoGenMipMaps=1
Numpad0Switch=0
WriteLog=1

Might be worth a try to set "AutoGenMipMaps" to a value of 0, also "WriteLog" to 0 -- then to resave, reload via JSGME, and test. Other than that I can't think of anything else that might be causing those DLL crashes on your system when loading the tuners. (It's very strange that all was well to BH&H2 patch 1.35 but that the DLL crashes showed up with patch 1.36 and later -- hopefully some solution will emerge. I suggest also trying Panama Red's various tuners and/or blue-triangle-removal mods. Can't remember the link to those mods now...somewhere on the WoFF SimHQ threads, possibly also on SandBagger's site...the PR mods were tested specifically on nVidia cards, while mine were tweaked on AMD vid cards.)



Hi Becker, thank you for that feedback; pleased to read that the tuner(s) give better FPS.

Cheers to you and RJW,

thanks for the suggestions VonS.

I will try your suggestions and keep you posted here. I originally planned to PM you on SimHQ but you have that turned off.

I used to use Panama Red's mods but stopped when we moved to BH&HII. I don't know if they are compatible but I can try. I found your tuner to be better for my system so I switched to it.

Best Regards

Hi VonS;

I tried your suggestion but it was a "No Go"!.

The following link shows the shaders log from the attempt with your mod: Franken_EnhancedShaders Log

The following link shows the shaders log from the stock BH&HII V1.37 without your mod: Stock_EnhancedShaders Log

Have a look as it might tweak your mind for possible problem resolution.

Best Regards

Hi RJW -- I disabled PMs a while back on SimHQ since I don't log in here regularly (so messages might go unread for weeks/months on end), although I am keeping PMs functional on CombatAce since I am more frequently there.

Have now double-checked those log files -- and from what I can gather, the following error overwhelms and crashes your WoFF install if you are trying to load my tuners and/or enhancement packages:

FakeDevice::CopyRects - D3DXLoadSurfaceFromSurface - FAILED. HR = 0x8876086C

In other words, your video card is not fully recognized if you load any of the tuners, thus the DLL crash you're experiencing (specifically, ability to convert to and from compressed texture formats is unable to load for some reason, according to that error).

Possible solutions may include:

a) reverting to a previous version of drivers for your nVidia card and/or re-installing the version of drivers that you have

b) to try what's known as a "repair upgrade" within whatever version of Windows you have, to fix possible DirectX corruption (since, as far as I know, DirectX cannot be uninstalled/reinstalled separately)

c) if you have a DirectX control panel somewhere on your computer, open it and look for the setting called "Enable Hardware Acceleration" (and make sure, counter-intuitively, to have that option unchecked, since checking it to register as on actually disables hardware acceleration)

d) go into the System Configuration/Services settings on Windows (via msconfig.exe) and make sure that all of your nVidia services are enabled, in particular "NVIDIA Local System Container" if you have that option, since from what I've been able to find it is sometimes turned off

e) change, in all instances of d3d8.ini in my tuner and/or enhancement packages, the "TerrainPatchPixelDim" value from 100 to 256; also change, in all instances of the terrains/compositetexturebudgets file in my tuner and/or enhancement packages, the "Budgets PatchPixelDim" value from 400 either to 512 or 1024

As always when troubleshooting, try the less invasive options listed above first. Hope you manage to find a solution to the DLL crash. (Might also be worth it to re-install the d3dx9 version provided in one of the WoFF folders, before attempting option (b) listed above -- option (b) should, really, be a last resort -- although I would in that case sooner re-install WoFF and then troubleshoot further.)

Cheers,

VonS

I appreciate your suggestions. I do however question those suggestions labelled a, b, c, and densely since the stock woff loads fine for me and the problems only manifest with you mod.

Why do you suspect the above options?

I will look into option "e" for now, but I did try replacing your d3d8 with the stock one and it still failed.


Best Regards

Hi RJW,

No real way of telling what the specific problem is, and so I have listed all of those possible options/solutions to choose from. Best, as you've indicated, is to begin with the less invasive options. Might I also suggest loading the FrankenMiniTuner without loading the base Enhancement Package, via JSGME. If that trick works, it will have narrowed down where the problem is coming from. If you decide to try that standalone FrankenMiniTuner trick, change the relevant dim nos. first in terrains/compositetexturebudgets, as specified in option (e) of my previous post.

My hunch is either that hardware rendering has changed over to software rendering in your DirectX control panel(s), somewhere in your upgrade process in WoFF (perhaps around patch 1.36) -- or, you have developed a "read-only" file somewhere in your WoFF install, around patch 1.36, and that's why WoFF can't read compressed textures files if you attempt loading any of my tuner/enhancement packages. The problem might not manifest in stock WoFF form but a read-only file, somewhere in WoFF, may be the culprit when tuner mods are being loaded (and that change settings in various texture files).

Resolution of that would probably require a full re-install of WoFF -- but I recommend first trying the tips suggested in this post, as well as in option (e) of my previous post. If that doesn't work, a WoFF re-install might be the best route, before tinkering with any of the other options listed in the previous post, such as (a) (rollback of nVidia drivers).

Beyond the suggestions I've given in the last couple of posts under this thread -- I wouldn't know what else might be causing the problem or what possible solutions might be needed (especially considering that the tuner patches and/or enhancement packages don't appear to be causing crashes on other rig setups post-patch 1.36 of WoFF). I hope that you manage to narrow down what the problem is and to find a fix for it. Do let us know if you find a solution -- might be of help if anyone else encounters a similar problem with the tuner/enhancement packages in the future.

Cheers,