Jump to content

molotov_billy

Members
  • Posts

    506
  • Joined

  • Last visited

Everything posted by molotov_billy

  1. Yes. I've tested with the previous drivers and the brand new ones.
  2. I have two rigs that are running shock force at very low frame rates - Core 2 duo 2.66 ghz Nvidia 7950 w/ 512 vram 2 gigs ram WinXP Quad Core at 2.66 ghz Nvidia 8800 w/ 768 vram 4 gigs ram WinXP Both are updated to the latest Nvidia drivers, running version 1.01 of the game. I've got the windows update that fixes the flickering shadows. These performance issues are visible on both machines with everything turned off, and everything low. I get a maximum of 15 or 20 fps, running resolutions as low as 1024x768. All movement controls are laggy as a result, and the game is unplayable as-is.
  3. I'm getting similarly poor results on my work machine - max of 20 fps, usually around 15 fps. This is with absolutely everything turned down and off. QUAD core 2.66 ghz NVIDIA 8800, 768 MB vram 4 gigs of RAM Something is seriously wrong here.
  4. They said it to me when I was reviewing the game. </font>
  5. May I ask what drivers you're using? The actual version number. Maybe the brand new drivers are worse? Anyway, define for me a "poorly configured rig." It runs everything else at high settings, 1920x1200 perfectly fine. Armed Assault runs smooth as silk. The performance for this is so far off the mark that it has to be some kind of bug, which is why I'm posting this.
  6. As I said in my post, I have everything turned off.
  7. I said that the really laggy camera movement came from right click panning. WASD has an intentional delay at the beginning, which is irritating, but not as laggy as the panning.
  8. Where has BF said this? I haven't seen it anywhere.
  9. I just updated my drivers, got the windows patch for dual core (which did fix flickering shadows.) Running version 1.01. Core 2 Duo 2.6 ghz NVIDIA 7950 GTX 512 megs vram, 2 gibs of RAM At my native resolutions with settings towards the middle, I was literally gettings seconds per frame. With everything turned down/off, and my resolution at 1024x768, I get around 10-15 FPS. Completely unplayable. Furthermore, the camera is extremely laggy. When I use right click to rotate, it continues to rotate a full 1-2 seconds longer after I've stopped moving the mouse. What the hell? :|
  10. No kidding. Last time I order something from BF.com.
  11. Before release! That would be great. Thanks for the info.
  12. I think alot of people would find it beneficial to their purchase decision-making if battlefront would post a list of what's actually fixed and tweaked in 1.01. It's hard to put these 1.0 reviews into perspective without that information. So far, testers and whatnot have been claiming it as a vague "fix-it-all" patch that will alleviate all concerns, which seems highly doubtful given that it has only been in development for a couple of weeks.
  13. I'm just trying to clear up the confusion about what version of the game is being reviewed. The original author of this post is/was under the impression that the version being reviewed was 1.02, when in fact the only person to mention a 1.02 was a user (and he was merely speculating.) I think I'm just confusing things further.
  14. This is in reply to another comment where a user speculates that an Nvidia bug will be fixed in 1.02, not 1.01. Nobody is saying that they've played 1.02 - it doesn't exist.
  15. So you're saying that version 1.0, the version sent to reviewers, has considerable problems with the basic core functions of the game - AI, user interface, and pathfinding - however, these are all magically fixed in a 1.01 patch? I don't believe you. Sorry
  16. I don't see any place where he says he's running 1.02. I think the author of this post is confused. I wouldn't discount anything the article has said - especially considering that another reviewer agrees with him in the comments section.
  17. I don't think anyone is playing a 1.02 yet, and as far as I know, 1.01 is being developed as of right now and will be released on the 27th. Reviewers have been playing 1.0. Having said that, the problems he mentions deal with the basic core of the game, and I can't imagine they'd be "fixed" in any patch. From what I've read, 1.01 deals with smaller issues such as glitches with Nvidia cards, etc.
  18. Toleran, I think you misunderstood my post. I was defending the way you set it up - there isn't any graphic violence, so there needn't be a warning for it.
  19. The video has all the violence of a low budget fireworks show. I'm sure if the video actually contained any sort of graphic violence, he would have warned us about that as well.
  20. Have to say I agree. 90% of the games I play are QB. I just like to be able to purchase my units instead of using whatever a scenario designer happens to give me. I wonder if this is possible - a scenario designer chooses the AI units, positions, and strat AI, but the player just gets a set of points to buy his own units?
  21. They were created by two entirely different development teams - Battlefront published theatre of War, they didn't develop it. From what I've read and heard, Shock Force is very much an upgraded Combat Mission. Played in real time mode, shock force may not feel entirely different than theatre of war.
  22. Looks like there's also a screenshot thread. Screenshots
  23. So I understand that Strat AI is done by the scenario designer. What happens in the 'quick battle' option where the computer and I buy random force mixes? If I play as a defender, will the AI attack without any pre-planned strategic AI?
×
×
  • Create New...