Jump to content

TAnker737

Members
  • Posts

    118
  • Joined

  • Last visited

Everything posted by TAnker737

  1. Ah, Thanks. Great news.
  2. Can I get a link to the post?
  3. I just don't see leap working for toggle switches. I need feedback and also I don't want to ram my hand on my monitor or drink.
  4. I'm suffering here, using my track ir with the rift in stereo mode. I only can play for 10 min before I start getting dizzy because the screen warping. so close, WHY AMD! why... oh and the cockpits look way more crisp than what others led me to believe.
  5. Right now I have a i7 3930k and run around 25 fps on high settings with low gpu usage. I think AI vehicles can wait, I can't even have AI vehicles in a combat scenario before my frames tank.
  6. All I can do is watch youtube videos with my DK2 of people playing dcs. Looks amazing, please fix this amd problem.
  7. Oh, didn't realize that you needed to sign in to see the log. Oculus SDK Added “Pause Service...” option to the Configuration Utility, which temporarily releases DK2 sensor, allowing 0.3.x SDK applications to run. Added Mac OS support. Mac does not currently include a display driver, so it always works in Extend Desktop mode. Added ovr_InitializeRenderingShim function that can be used to hook rendering, needed Direct to HMD Mode, without spinning up the rest of LibOVR. Removed SSE4.1 requirement that was problematic for some older AMD CPUs. Fixed OpenGL support on AMD cards in direct mode. Resolved Blue Screen that happened starting some demos with some video adapters. Fixed Blue Screen or boot-up Black screen issued caused by interaction with Display Link. Display link is are still incompatible with Direct Mode. Improved OpenGL support in the driver shim. I don't think it's a dcs issue that is making only AMD users have a blackscreen. Sounds more like a driver problem.
  8. Ver .4.1 is out, it says it fixes amd's Opengl issue. Not sure if this is the cause of dcs's blackscreen problem. Getting my DK2 later today will try it. Change Log https://developer.oculusvr.com/?action=hist
  9. I'll be receiving my DK2 tomorrow and it's a real bummer that I wont be able to load up DCS.
  10. Actually I take it back, once I took ALL the scenery off and a clean map with no NPCs I get 60 FPS. Objects seem to be killing my frames, I have everything else on high MSAA at 16xQ shadows high my res at 2560x1440. Once I start adding object like tree, buildings CPU chokes. I searched on the forum and it seem my issue is that this game is still doesn't have multi-core Support. So I'm only using 1/12th of my CPU, EDGE can't come sooner...
  11. At best I get 40 fps with no civilian cars / scenery. and I have to overclock my cpu from 3.8ghz to 4.7ghz Edit: Drops to 20 if I pan to a small town with buildings.
  12. Hello I also have awful fps which I don't understand. I have a 7970 , 3930K and 32GB of ram. Any help would be appreciated.
  13. Can't wait to see this on my PC, looks amazing.
  14. This is great news, if ED has support for the rift I'm getting a dev kit. Not waiting anymore.
  15. Great post thanks guys
  16. I totally agree. I would like to see the opposite happen. Instead of fighter planes going to fsx I want civilian aircrafts coming to dcs.
  17. I think its the HDR, not sure.
  18. Thank you guys, I have been looking for quality rudders.
  19. Calm down and take a breather. I'm sure ED will take your advice and maybe even pay you for your epic wisdom and experience.
  20. I think right now 4+ gigs of ram is a no because the 32bit version and I also think moving forward they should go exclusively 64bit.
  21. Yeah crossfire right now on DCS is just a very unsaturated bluish green screen. Is this AMD's issue?
×
×
  • Create New...