wulff

Free Play Account
  • Content count

    444
  • Joined

  • Last visited

Community Reputation

0 Green Tag

About wulff

  • Rank
    Member
  • Birthday
  1. Thank you for replying, I got it working. Wassail. Snjarulfr. wulff.
  2. After hours of fruitless trying I read a post that said portrait mode won't work in BE, even though the setup program shows the resolution. So, I just switched to the normal landscape mode, I guess that is going to have to be good enough. Wassail. Snjarulfr. wulff.
  3. I tried some different compatibility modes and windows is telling me that ww2.exe is incompatible. I have no idea what to do now. Wassail. Snjarulfr. wulff.
  4. Well duh, I finally remembered to install DirectX, c++runtime and .Net Framework, but still no joy. I can get all three monitors working in Two Worlds Two, but BE is still crapping out on me when I try to launch. I am going to install a few Steam games and see if I can get it going that way. Wassail. Snjarulfr. wulff.
  5. It's not the eyefinity set up I think. I couldn't get BE to launch on even 1 monitor. Wassail. Snjarulfr. wulff.
  6. Hi guys, I need some info. I have my windows desktop at 3240x1920 with three monitors. Whenever I try to launch BE there is a short black flash, then the system goes to the desktop. I installed the latest vid drivers and am downloading a fresh copy of BE right now. I have no idea what to check next, usually when something works properly in Windows it works perfectly in BE. Any thoughts, ideas, clues? Thank you. Wassail. Snjarulfr. wulff.
  7. I feel your pain man, I have been getting random ctd's while flying for the past couple of days. The last one happened just as I was moving into a perfect position to kill a hawk. Normally my rig is stable as a rock. It's only the last few days that the gremlins have been acting up and I have no idea why. In my case what has been happening is that everything is going fine, then suddenly the game closes and returns me to the desktop. No error, no explanation. My new rig is almost here, that is the one that I will do the troubleshooting on to ensure a stable system. Till then I am just going to put up with it. Wassail. Snjarulfr. wulff.
  8. I just had this error a couple of minutes ago. I got back to the desktop and relaunched, no problems. The mission I created was showing in the missions list, but was 1 rifle short. Wassail. Snjarulf. wulff.
  9. Thanks for writing such a clear and informative article! Wassail. wulff.
  10. I feel like a traitor, but I am downloading Red Orchestra as I type. For the StG44 and as a protest against CS&R not working. The price was right, too, less than ten bucks. Wassail.
  11. Wow, you guys are good players. I had one death and one kill that did not register properly on CS&R. Database functions should not be screwing up after 10 years in existence, that's 10 long years to debug them and make them robust. Database errors are not acceptable, as they are a basic function throughout the game. It seems to indicate lack of foresight somewhere along the line, at least to me. That is my opinion, your mileage may vary. I am going to practice off-line or on the training server for the rest of the weekend, or play Red Orchestra. Wassail. Edit: I can put up with a lot of graphical bugs, lag, wtf deaths, CTDs, etc.etc. but when a basic low level system starts screwing up, I start wondering if there is a better place for my money. This is the kind of bug that frustrates me enough to consider unsubbing, and I am pretty much a fan-boy.
  12. I had an ei kill in Stenay earlier. It showed in AAR, but not in CS&R. I only care about K/D when mine is less than 1.0, like it is now. When I can get it to 1.01 or better, then I know I am an asset to the Axis team. Not much of an asset, but an asset none the less. Wassail. Edit: I think CS&R is more or less corrupted for the weekend. I just gave the Allies a free kill by not paying attention to the fight while conversing on chat and my k/d changed properly, but nothing else. My death was not registered in the sortie, shown RTB instead of KIA, the sortie did not show a kill for the ei, but did name him in last 9 killers. CS&R is completely borked, I will be nasty and say "you would think they would have gotten the hang of properly updating a database by now".
  13. Fixed already. No problems with login past two days. Wassail.
  14. Hahaha, the windows gremlins and linux daemons are having a war and everytime one gets killed that error occurs. As good an explanation as anything. Wassail.
  15. It's 3:30 am here and still getting the error. I uninstalled, downloaded a completely new client, cleaned the registry, rebooted, installed and still getting that error. No clue what changed, I had zero problems logging in before. Time for some sleep. Wassail. Edit: I did the trace route thing just for giggles: Tracing route to 66.28.224.141 over a maximum of 30 hops 1 * * * Request timed out. 2 12 ms 12 ms 11 ms 64.59.132.2 3 10 ms 23 ms 15 ms 66.163.71.25 4 29 ms 27 ms 27 ms 66.163.77.26 5 48 ms 48 ms 47 ms 66.163.77.125 6 44 ms 44 ms 44 ms 144.223.21.41 7 45 ms 47 ms 46 ms 144.232.5.132 8 47 ms 43 ms 43 ms 154.54.10.37 9 46 ms 45 ms 45 ms 154.54.1.97 10 68 ms 67 ms 69 ms 154.54.5.173 11 68 ms 69 ms 70 ms 154.54.46.218 12 68 ms 69 ms 69 ms 154.54.26.34 13 66.28.30.146 reports: Destination net unreachable. Trace complete. And some good vibes for you: Q0Vcvo_gD98&feature=channel_video_title