Jump to content

vonOben

VALUED MEMBER
  • Content count

    353
  • Joined

  • Last visited

Everything posted by vonOben

  1. Hi Is it possible to get rid of these graphical errors (white squares) I have in BHaH using a ATI Radeon HD 5770 video card? It usually starts when a plane catch fire and is gone after a short while. Cheers vonOben
  2. Thanks for the info BirdDog, much appreciated! S! vonOben
  3. Thanks for the info Olham, should be good to know when enlisting in August 1918. S! vonOben
  4. Thanks, yes it was possible with a little help from my friends over here Cheers vonOben
  5. Hi Great information in the "Flying and air fighting" series! Thanks a lot for writing them! There are no links to the Fe2b and to the DrI…. S! Cheers vonOben
  6. And a few from my Jasta 9 campaign: 17 June 1917: Jasta 9: Nieuport 24 on fire: Cheers vonOben
  7. Hi A few screen shots from my Jasta 2 campaign: 10 June 1916 Jasta 2, Lagnicourt after a completed mission: 3 November 1916 Jasta 2: BE2c on fire: 10 November 1916 Jasta 2: BE2c on fire: 10 November 1916 Jasta 2: BE2c on fire: 10 December 1916 Jasta 2: Balloon busting 10 December 1916 Jasta 2: heading home: 21 December 1916 Jasta 2: Fe2b on fire Screen shots directly from the game. Only converted to jpg's. Cheers vonOben
  8. Hi New settings CFS3 Config: Aircraft: 5 Terrain: 4 Scenery: 3 Effects: 5 Clouds: 5 Game runs smooth and no graphical problems so far. Cheers vonOben
  9. Hi I was referring to the TweakGuide Von Paulus linked to, not the OFF ATI Tweak Guide. :wink2: http://www.tweakguides.com/ATICAT_7.html Cheers vonOben
  10. Hi Thank you very much for your kind help! I've changed my CCC settings to the same as Olham, but I'm unsure about Adaptive Anti-Aliasing: Quality. Is that the same as Anti-Aliasing Mode: Adaptive Multi-sample AA? I can't find "Wait for vertical refresh: Always On". Do I need to use the D3DOverrider for that? I didn't change the CFS3 Config since I wanted to test the new CCC settings first. Frame rate increased about 10% after these changes. Thanks for the link to the Tweak Guide, but it seems slightly outdated and it doesn't explain for example the differences between the AA filter settings. Cheers vonOben
  11. Hi guys If they crashed it must have gone fast! It was a matter of a few minutes from I saw them diving to they was gone from the TAC. :wink2: No I didn’t know that and I haven’t seen any of the AI land yet, but that’s because I don’t want to wait for them long enough. Perhaps I shall follow them and see what they are up to sometime. As I wrote above did I checked the TAC on maximum distance and the enemy AC did show up fine so it was set to show aircraft. Doesn’t the AI obey rejoin commands after the goals completed message? Cheers vonOben
  12. Hi I’ve been out of OFF action for a while. My specs: CPU: AMD Phenom II x2 550BE 3.1 GHz VC: ATI Radeon HD 5770, 1GB GDDR4 4GB RAM Windows XP My CFS3 Config: 1920x1200 and 8 AA Aircraft: 5 Terrain: 4 Scenery: 4 Effects: 5 Clouds: 5 ATI CCC settings: AA mode was on quality (Super-Sample AA) and I turned it down one notch to “Adaptive Multi-sample AA”. But the frame rate was not improved. It’s around 30 as before. And the problem persists. Which of the AA filter settings is recommended for OFF? There are Box, Narrow-tent, Wide-tent and Edge-detect. What are the differences? I’m currently using Edge-detect at Level: 4x Samples:12x I haven’t had this problem with the previous used driver, but I recently installed HiTR. Is HiTR more demanding than BHaH? Cheers vonOben
  13. Hi I flew a ground forces attack mission today, but I couldn’t detect any ground forces at the way point. Should there be ground forces there and if so suggestions to find them would be most welcome. Thanks! Cheers vonOben
  14. Hi Guys Thanks for your replies. I've been away on vacation so that's the reason for my late reply. No wonder it was hard to find if ithe target is only one soldier.... Cheers vonOben
  15. Check in the bottom of that page and click on the green "Download File" Icon. Good Luck! Cheers vonOben
  16. HPWDM 2.2 update

    Herr Prop-Wasche Thanks for this update and for your dedication to get this DM as accurate as possible! Much appreciated! S! vonOben
  17. Hi I've followed the tip from RAF_Louvert and corrected my flying time like this: Find your Pilot**Log.txt file that are located in your \CFSWW1 Over Flanders Fields\campaigns\CampaignData\Pilots folder Open Pilot**Log.txt and correct the flying time. In the OFF Manager Log book the times are displayed correctly, but the total time doesn't match with the time in the log book. For example if I add the actual flying time from the log bok it becomes 2,7 hours, but the total time that the Off manger displays is 1,9 hours. Do I have to make more corrections than in the Pilot**Log.txt or is it the OFF Manager that can't count time properly? Cheers vonOben
  18. Thank you for those kind words, sir! :yes: Cheers vonOben
  19. Hi Installed Catalyst driver 10.5 a few weeks ago. I haven’t been able to reproduce the problem above with the new driver. I’ve downloaded and installed HiTR and sometimes there are other graphical glitches like this example (weird squares in the terrain): Any ideas what to do? It only happens sometimes, but it would be nice if it’s possible to fix. Cheers vonOben
  20. Hi Morris Thanks for the tip I've never thought of that ! Cheers vonOben
  21. Correct flying time: The OFFManager doesn’t always give the correct actual flying time. You can manually correct this by editing your Pilot**Log.txt file that are located in your \CFSWW1 Over Flanders Fields\campaigns\CampaignData\Pilots folder Open Pilot**Log.txt and correct the flying time. Thanks for the tip RAF_Louvert Cheers vonOben
  22. Correct flying time

    Some additional information posted by RAF_Louvert in another thread:
  23. It was not my intention to sound harsh. Thanks for pointing it out. I'll be more careful how I express myself in the future! I never use Warp but it happens that I use pause. Thanks for pointing it out! RAF_Louvert I suspected there was something I had missed! Since my first mission was much longer than the logged time I got an initial error of about 50 minutes. Thanks a lot for solving my problem! I'm well aware of the updates but as I wrote earlier "there are no information about what's going to be improved in P4. And since you don't have some sort of bug or strange issues list where we can inform you about these things." Polovski "Unrealistic OFF environment" OK that was badly expressed. As I wrote to Creaghorn I'll be more careful how I express myself in the future! "still not correct" Here I meant that I had posted about this problem earlier and even if I manually correct the time I still don't get it right. Perhaps I expressed myself badly, but that was what I meant. Can't it count? I actually wrote: Do I have to make more corrections than in the Pilot**Log.txt or is it the OFF Manager that can't count time properly? Waldemar Kurtz Thanks for that info! All this is totally new to me! I never pay attention to such times as patrol for 18 minutes. I fly between the way points as I'm ordered to and, but I don't care about the time. Perhaps I should? Thanks guys! Cheers vonOben
  24. Thanks for the tip Olham! Cheers vonOben
  25. Hi WM I'm enjoying the sim, but I have never flown CFS3 and I'm fairly new to OFF BHaH. I have no interest in ROF, so that's no alternative. So when I run into these "minor issues" I want to know if I'm doing something wrong or if I can correct it myself some how. If that's not the case I think it's good for the OFF Team to know about it since there are no information about what's going to be improved in P4. And since you don't have some sort of bugg or strange issues list where we can inform you about these things. Ignore mode on? Perhaps is the OFF Team not interested in feedback from their customers? Cheers vonOben
×

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..