Jump to content

Sjokkel

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by Sjokkel

  1. Maybe you could try lowering the clutter/grass and tree settings as a test?
  2. Performance in VR dipped after the patch for me. I had good performance in the standard F14 missions where you take off from the deck. Performance in Persian Gulf was worse that in the Caucasus map on deck in open sea but i didn't have any stutters and it was very playable. Now with the patch only the F14 caucasus mission is playable but if i look over my left shoulder to the bridge i get huge stutters. It does seem to be an issue with cockpit shadows. I'll dig in to it a bit more hopefully this evening. F18 looked a lot smoother on deck. I agree on the need for a built in benchmark.
  3. It had me start up the updater multiple times to verify. :lol:
  4. A used CV1 would be a good start but i would suggest trying the Rift S also. I went from a Vive to a Rift S last week and i due to the lack of time i only made a first flight yesterday. For me it was a huge difference in both clarity and immersion. With the vive i used to go back to Track-IR to get to know a plane. Once i knew where most of the buttons were i would switch to VR. Now my Track-IR is going on sale.
  5. This i probably due to the dynamic lights. I experience the same issue on some levels. It's clearly noticable for me in the death valley missions. You can also see the huge framedrop when they engage their lights. The strange thing for me is that when flying in formation with 3 other BS, i can get 60 FPS in flyby, but sometimes i can have 17 fps just looking at 1 BS. Try putting lights="1" in your config file and test again.
  6. Overall i'm getting good performance from BS but in certain situations FPS can drop significantly seemingly without a good reason. I know BS is mainly CPU bound but from the tests i've done this seems to be mainly a graphics problem. The FPS drops can be fixed by putting lights=1 in the config file thus disabling volumetric lights. For instance, in the mission Death Valley looking to the left form straight at the other 2 blacksharks i would get 34 FPS. From the moment they turn on their lights the FPS drops to 18 FPS. In other missions i hardly see any FPS drops when they turn on their lights. A few days ago i was starting up from a farp for some MP nightflying. Looking 45 degrees to the left i would get 17 FPS, looking 45 degrees to the right i would get 60 fps. When i would get my head close to the cockpit dash only filling the screen with 1 part of the dash a piece of farp flooring and 1 dynamic light on the farp would still give me 17 FPS. It seemed that that one light was causing the huge drop in FPS. On the other side of the cockpit doing the same would even raise my FPS to about 70. I'm just wondering why in certain situations these lights can cause huge framedrops. Since its a rather simple lighting effect as seen in many other games it shouldn't be such a graphical strain. Is this caused by a mix of the wrong materials in some situations making the effects of the light causing a bottleneck on the GPU? Is it nvidia related, related to win7? Is everybody experiencing these extreme slowdowns regarding to dynamic lights? I tried many different drivers ranging from the 18x.xx range to the 19x.xx range. My specs are C2Q 9550, GF GTX285 1 gb, 4GB ram, Win 7 RC, currently running 195.36 drivers as a test.
  7. Sorry for the late reply. I've been checking with other drivers with the same result. In the process i swapped my freetrack setup for a Trackir and suddenly i started experiencing strange problems in windows 7. After uninstalling drivers and reinstalling, updating sound and networkcard drivers it finally turned out to be a defective mouse causing problems to the usb root hub in the PC . After all the fiddling around with freetrack i can't seem to be able to reproduce the startup slowdowns anymore. Because of my hectic way of working i cant pinpoint what could have fixed the issue. Maybe the defective mouse flooding my USB hub with unused commands had a hand in it. I'm going to keep looking and try a driver rollback to see if i can reproduce it again.
  8. Hey Falcon, Did you try disabling your AV ? If it runs in safe mode it must be something interfering with modman. Antivirus is the first thing i can think about. Did you always have this problem or did it suddenly pop up?
  9. Sorry, I was in a hurry, forgot to post my specs. I tested it both on the same machine in Vista 32 and Win 7 64. It's a Q9450 with 4 GB Ram, GTX 280 1GB running the latest WHQL drivers 191.7. I just noticed it yesterday so i didn't test it with different drivers. Hope this helps!
  10. I replicated the problem yesterday. I forced Anti aliasing and anisotropic filtering through the nvidia control panel. When i tried to load a mission it would take nearly 5 minutes. Resetting it to default fixed it for me. So a graphics driver setting could be causing the long loading times.
×
×
  • Create New...