Jump to content
Battlefront is now Slitherine ×

rune

Members
  • Posts

    3,769
  • Joined

  • Last visited

Everything posted by rune

  1. Did you do the alt tab out of the game, and go back into the game? Rune
  2. OK 1024 by 768 I got 36 fps. Settings improved/improved. Desktop 1280 X 960 I got 24 fps @improved/improved. Better/better @1280 X 960 I was getting a consistent 24 fps. The trick is the alt tab it seems. Try and let me know. Rune
  3. Oh, and try balanced/balanced, I will try other settings next. Rune
  4. Guys, make sure you try the various thing i posted. One time play anothe scenario then go back and play allah's fist. Next time, if still slow, alt tab out of the game and then alt tab back in. Doing this this morning, and I am getting a consistant 31 fps. Keep testing and let me know. Rune
  5. Nvidia released a new driver today, I tested with my quad core system with the nvidia 8800 card. I loaded Allah's fist, blue side, default location. The first frame rate I got was 37.2 fps! The bad: I exited the game, then went back to the scenario, and was down to 13 fps. The good again, I loaded a different scenario, exited then went back to the allah's first scenario. Kinda hard to see, but if you look in the bottom right here, you will see a 31.3 fps for allah's fist. The driver is 163.67 available from Nvidia 163.67 Beta Test, and if you get slow fps, load another scenario and go back, or tab out or the game and go back. The driver was released a few hours ago. Let me know your framerate. Rune [ September 10, 2007, 10:43 PM: Message edited by: KwazyDog ]
  6. I sent the thread to Charles to have a look see. I just sent it, so hopefully he can see if this means something to him. Rune
  7. Not going to happen, and we listed reasons why multiple times. You can skin the game, but new vehicles and etc will be handled internally. Rune
  8. If you are going to 8 GB of memory, you have no choice but to go to Vista 64. Works, but some drivers are hard to find, if they exist at all. I am running Vista 64 on one of my systems. Rune
  9. Dirtweasle, No problem, glad you are in the game and playing. For a true test, send me your email, will send you a scenario to make your system cry. Rune
  10. Sirocco, Since you want me locked in a room, toss me your email. [insert Evil Rune Laugh here} Rune
  11. Fox, yep, I know...but with testing, I don't want to throw another unknown into the mix, and actually turn off oc'ing when doing the fps stuff. The 680i chipset is picky on memory, but at least the bios problems seem to be ironed out. I also have a XP system with 6800 and a Vista system with 6800 card, identical systems, and no surprise, the XP system runs faster. I temporarily unhooked my Vista X64 system with a 7800 card in it, so can't do a comparision there. I should try different desktop sizes to see how much a difference it makes. Rune
  12. Fox, eVga card, so it is a 8800GTX overclocked. Yes, I posted the initial startup screen, blue forces without moving the screen or mouse, so default on everything. Actually with my motherboard, i am running at 3.00 ghz overclocked, using the Asus Booster and overclock program. I could do better if I had better memory, but the Striker Extreme motherboards are very picky with memory. Rune
  13. Pele, You assume Charles was the only one to get a system. Vista Ultimate 32bit Intel Quad Core 6600 4 MB DDR2 memory eVga 8800GTX with 768 memory 163.44 beta drivers [also tested with the 162.22] Game settings balance/balance at 1280 X 1024, Dell Monitor @ 60mhz Allah's first scenario, default screen US which everyone is complaining about, 14-16 fps. With FSAA turned off, I got 25 fps. I tried with single core and multcore and no difference. I have been emailing with Charles doing tests. Rune
  14. It's you, :0 people have completed the mission with only wounded. Rune
  15. As a mattre of fact, #2 is how the QBs are supposed to work. Attacker sets up in blue and defender in red, would be a bug if this is not happening. Let me know for sure. Rune
  16. Steiner, That would be an idiotic way to make a game. You code work arounds, and then ATI or NVidia fix their drivers and break the game again. You code to the standard and hope the card people do the same, then you test with what you have. If you notice, not all Nvidia cards have the problem neither did all ATI cards. You would possibally have to code to each driver release, and that is insane. Rune
  17. Bug, and already being worked on. Rune
  18. This is expected. There was a message psoted someplace here in the technical forums. Changes to the code, sorry about that. Will also be true for 1.03 when it comes out, be forewarned. Rune
  19. Bug, being addressed in 1.03. This is a priority bug to be fixed. Rune
  20. When the modules come up, there will be some updates o the Syrian forces included. Rune
  21. sgt goody, One of them is done, the other is almost done. It may be included with the patch. it was based on a real situation that never developed, but Imperial Grunt can fill you in with it more if he chooses. It WILL slow you down, and the other I am working on will also do to a forest. I just have to finish the AI plans on that one. Raptor, I agree it takes more thinking, but it forces you to use proper military tactic, and is not a "puzzle" type scenario that some complain about. How you attack is completely up to you, also hopefully had some "cool" moments in it as well. Rune
  22. And you missed the point, other people didn't think it was hard at all. Rune
×
×
  • Create New...