Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About cazna

Profile Information

  • Location
    New Zealand


  • Website
  1. FWIW, it is not the intention to muck around with the registry to get the game to run. The purpose of the steps I'm walking through with Havoc04 are to confirm the exe's are configured as required. This information is held in the registry. Havoc04, can you post the values in the "Data" column that are assocaited with each of the registry keys please. This will help to confirm whether or not the exe's are defined to run with appropriate values. It may also be worth grabbing the latest OFF patch (1.3) and installing that, just in case your DVD has a corrupted file.
  2. Ok, so please try the following next. I acknowledge that you said that you are using the administrator but can you try this anyway. 1) Open Windows Explorer and navigate to "H:\OBDSoftware\CFSWW1 Over Flanders Field" 2) Right mouse click on OFFManager.exe and select the "Properties" menu item 3) Click on the "Compatibility" tab 4) Click on the "Show settings for all users" button 5) Tick the "Run this program in compatibility mode for:" checkbox and select "Windows XP (Service Pack 2)" in the drop down list. 6) In the "Privilege level" group box, tick the "Run this program as an administrator" checkbox. 7) Click the "Ok" command button 8) Click the "Ok" command button 9) Repeat steps 2) through 8) for the file CFS3.EXE Try running OFF by double clicking on "H:\OBDSoftware\CFSWW1 Over Flanders Field\OFFManager.exe" to run OFF. Could you please post whether or not this is successful and also whether your registry now contains the values I asked about previous. Regards, cazna
  3. It's no lemon. I'll offer a few things to check (and no doubt others will too) to try to remedy the issue you are encountering. I had similar issues when installing but they have been emedied now, albeit that I'm on Vista32 rather than Vista64. The first thing I would suggest is a sanity check in the Windows registry that the executeables are defined as recommended. Can you look at the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Nt\CurrentVersion\AppCompatFlags\Layers and post a reply telling (a) if there are values listed similar to those below and (b) what data value they have D:\Program Files\OBDSoftware\CFSWW1 Over Flanders Fields\CFS3.exe D:\Program Files\OBDSoftware\CFSWW1 Over Flanders Fields\OFFManager.exe Secondly, try running the program cfs3.config.exe as the administrator. The file is found in the install directory (e.g. for me this is D:\Program Files\OBDSoftware\CFSWW1 Over Flanders Fields).
  4. An FYI. I happened to see that a new driver version for Nvidia cards was released on April 2nd (available via Nvidia driver download). Don't know what is included the update but as a rule I'm inclined to stay up to date with GPU drivers.
  5. Trackir

    Your mileage may vary but the following was applicable for me. 1) Running Vista 2) OFF Manager run as an administrator user 3) When TrackIr is not run as an administrator user, nothing doing in OFF. 4) When TrackIr is run as an administrative user, it works fine in OFF. i.e. the bottom line for me was both OFF Manager and TrackIr needed to be run as an administrator user. cazna.
  6. It's a "feature" at the moment for some people. Altering the details sliders won't necessarily solve the problem (I still encountered it when all of the settings were 1). There is another thread (here) which, if you have dual core CPUs, talks about setting the CPU affinity (i.e. which CPU cfs3.exe is to run on) to try to remedy the problem. This could be a challenging "feature" to remedy as it looks like the issue may be in cfs3.exe (i.e. the MS executable) rather than the OFF manager (i.e. the OBD executable). One of the developers may be able to enlighten us on this.
  7. Well I tried all three different campaign regional activity settings and it had no impact. I also used the reset CFS3 option in the workshop (bye, bye pilots) and this resulted in no change either. I've now flown at least 10 missions in patch 1.28 with no enemy encountered (including 3 enemy-less scrambles). I flew with both the TAC and labels on so I'm confident there were no enemy (plus warping too, which will kick you out of warping if enemy are within about 4 NM). I've popped a mail describing the scenario to OFF support to ask them to have a look. I will post any outcome as circumstances dictate.
  8. You are not alone (well you are in the sense of no enemy). I am seeing this issue too and posted about this earlier (see the topic http://forum.combatace.com/index.php?showtopic=38103). I think my scenario is similar to yours i.e. flying as French, ESC 3 in early January 1916. I do wonder if the 1.28 fix (that includes an alteration to the date from which an aircraft begins to appear) had an adverse impact on things. I'm tweaking a few settings (e.g. enemy activity low/medium/high) and I'll let you know if there is a change.
  9. There were no white spots on the radar. Per your suggestion about a test pilot in 1918, I tried that and ran into enemy aircraft. So that suggests it's not an across the board problem. I subsequently flew another January 1916 mission over enemy lines but still no enemy aircraft. I struggle to believe that I've seen no enemy in the six most recent missions post the 1.28 patch yet prior to the patch it was a very rare occurrence to fly a mission and not bump into anything. If anyone else is seeing this please shout - it would be nice to know I'm not going mad!
  10. January 1916. So the last few campaign flights I haven't seen any german aircraft. Here I was thinking, boy they must be somewehere else today and I've just been lucky. But then this evening I had a "scramble" scenario in the campaign. Except, there weren't any inbound enemy aircraft! I exited (accidentally, as since 1.28 I have started experiencing the "M = exit" behaviour rather then "M = map" reported elsewhere) and thought, "that was weird". So went straight back in and it ran the same scenario. Complete with no enemy aircraft. Is anyone else seeing no enemy aircraft? If so, have you resolved it and, if you did, how did you fix it? TIA. cazna.
  11. I'm not aware of a visual indicator but the audio indicator I use is the engine noise (or lack thereof). Keep clicking the ctrl-minus until the engine cuts out and then ctrl-= to wind it back until the engine comes back in again. As an example, flying a Nieuport 11, I have to click ctrl-minus about 75 times at 5000ft to get the engine to cut-out and then I will click ctrl-= about 5 or so times. And don't forget to enrich the mixture on your way back down too - having the engine cut out at low altitude because the mixture is too lean is more deadly than it cutting out at high altitude because the mixture is too rich. Also, not all planes have the ability to adjust the mixture. Perhaps reply with what plane you are flying and someone who flys that plane may be able to indicate whether or not it has the ability to adjust the fuel mixture. HTH
  12. Aroth, from the previous forum I can recall you were having issues with not being able to invoke your nvidia control panel. Did you manage to resolve that issue? The reason I ask is my suspicion would be that if your GPU DLLs aren't quite right, it may result in issues when rendering graphics. This is just a BST.
  13. Iron sight view

    There is a configuration option named "Virtual Cockpit View". Perhaps this is what you are after. If so, set the value for this option to be the function key you desire.
  14. WIBNI = Wouldn't It Be Nice If ... (a.k.a. a feature request) From a previous post I made at SOH re:a question on Warping and flight time and some subsequent sniffing around in the OFF generated data file for a campaign mission, I am wondering whether some consideration could be made for inclusion in a future release for the following: Flight Time = Sum of all non-Warp flight time I has actually thought that this was the case but I recently flew a mission with a substational component of warping (call me lazy!) and I think I still received a significant flight time credit (30 minutes) when it should have been about 5 minutes. Fold, mutilate or spindle this suggestion as you see fit. cazna.

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..