Jump to content

alont

Members
  • Posts

    17
  • Joined

  • Last visited

  1. Depending on the cpu, motherboard and memory, beyond a certain frequency one might see significant DROPS in games and other benchmark software. Try lowering the clocks a little bit (5GHZ? seriously?)
  2. I've put my seedbox on the job, so hopefully you guys will get some decent speeds. Currently upping at 1MBPS
  3. Can't wait for beta 6! It sure will bring interest to an otherwise rather slow weekend :D
  4. Two IAF F-15i flying over Nevada during red flag
  5. I just told you I did... and it freezes in all of em >_<
  6. Pretty much any mission. It can be a mission I just made up in the editor, it can be one of the quick start missions in the main screen, it can be a mission someone else made in hyperlobby etc.
  7. O.k I reinstalled everything and I do not get the error. I still have problems when loading an actual mission though... any ideas about how to fix that?
  8. I have the cd version of lock on, and I have the digital download version of FC. I'm going to try and reinstall LOMAC and flaming cliffs.
  9. Tried to do that, still no go. Tried simply closing everything unnecessary, still no go. Tried reverting back to 1.11 and still nothing :cry:
  10. Q6600 8800 GTX 4GB ram 600 GB HDD Vista Home Premium 32 bit Microsoft sidewinder force feedback 2 LOMAC:FC v1.12b
  11. I just got into lock on this morning and the starting loading screen froze at "initializing input"... Tried restarting and disconnecting my joystick, but it still freezes in the same exact point every time. :helpsmilie::helpsmilie::helpsmilie:
  12. Cmon guys I wanna play this game badly... any ideas??
  13. I still have the loading screen problem... Havent tried taking control in a tutorial yet but that isn't very important for me, I just want to be able to load missions without the fear of the game freezing up. I just tried disabling the driver AA, and now the loading screens freeze all the time. Tried using driver AA again, still freeze...
  14. Huh, turns out my A.I tuner settings in my bios were set as AUTO instead of Standard... I will post back once I get a chance to see if that helped.
  15. Not overclocking, and I have a 750 watt thermaltake toughpower psu, so I don't really think that could be the reason:helpsmilie:
×
×
  • Create New...