Jump to content

yellow_jacket

Members
  • Posts

    67
  • Joined

  • Last visited

Everything posted by yellow_jacket

  1. Sharp, have u tried to set compatibility bits to "AssetoCorsa" for SLI? It works for the 368.69 driver but not 368.81.
  2. Flying at tree top level can't be expressed in words.
  3. Ghost, Did you go though the alignment of the three vertical lines and three horizontal lines on the rift during setup? This is super important I think
  4. Pixel density works in alpha as far as I can tell, but you gotta force it through debugger.
  5. Does anyone have a youtube video of how the zoom function in the Rift works in 1.5.4? Also is there any way to stop sending picture to monitor while I'm in rift ? it just uses up my graphics card %, while I need as much as I can in the headset. Can I use second card only for the rift instead?
  6. I had same issue several months ago. If you try to search for my posts, I'm pretty sure I have logged a comment, on what I did to fix it. I can't remember for the life of me what I did. Possibly remove over clock from chip.
  7. I've seen comments stating that turning pixel density up to 5 makes it even clearer. So it's like the screen really isn't the biggest hurdle, but our hardware is. Wait for the 1080 Titan.
  8. Looks like it might be the local pub back there.
  9. Not a direct answer to your question, but wrt SLI. I've noticed it works to some small extent (both cards have high % usage) in DC's of you set( add )dx11 compatibility bits for "Assetto Corsa" title. It doesn't work with latest nvidia driver xxx.81 but installing just the previous to that one works, as the latest driver broke it for me. Just making that one line change does it. Although I noticed that when CPU heavy stuff is taking place that brings you down to 20-30 you don't see a boost at all. More than anything SLI seems to just even out the fps spikes as you look around, other than that I am not sure. At least I feel a bit better when the other card just doesn't sit there collecting dust.
  10. Where is the submarine shot from? Something you're working on?
  11. Dot, I'm just reading through references and starting out with missions. So I definitely hope you get the answer you need here. Flying pixels since someone asked 'why would anyone want a computer?'
  12. Looks like what I've been searching for, unfortunately I won't have a chance until first week of August due to family stuff..
  13. Dev versions on latest weekend videos show 2.1 combined maps. So it will happen eventually. I just don't know when.
  14. Wow, I did not expect those numbers to be so high. Considering that I get somewhat better and steadier numbers in NTTR map, you may have easier time getting what you need once 2.5 rolls in.
  15. What fps do you get without the rift for the exact same view? Just using the 1440 monitor.
  16. Well, after that shot I'm officially aboard the hype train. :punk:
  17. Last photo looks amazing. Can't wait to emergency land in foot deep water on the beach and see the waves rolling around.
  18. Actually it does say he was also a pilot at one time in the third paragraph. He was asked to drink a 72 ounce slurpy while flying though.
  19. Rico, does 80fps really feel any different than 90? I'm just wondering if the 90 is something used from convenience more than anything and the real nausea limit is somewhere between 75 -90.
  20. Can't wait for this map. Very excited.
  21. I'm sorry to hear that, I have same chip and have actually taken it back to stock speeds. I didn't see any improvement except for dx9 games. And it cured some hangups.
  22. For me, using Starways texture package in 1.54 open beta works perfectly, and solves stutters.
  23. Does it make spotting other aircraft any different (easier?)
  24. I could not until I copied over the file from 2.0 alpha.
  25. Just wanted to give input regarding trackir limits are not correct or don't feel right, can't look backwards at all. I can get used to outside view being changed by track ir, ...sort of.
×
×
  • Create New...